How do I organize feedback from several beta readers?

One copy each, or one copy for everyone

Decide this before anything goes out. A single shared copy is easy to send, but readers see each other's comments, and the third reader tends to agree with the first instead of telling you what they noticed. One copy per reader keeps every response independent. It also means several files to collect afterwards, which is the price of honest feedback.

For a shared Google Doc, the notifications arrive fast once five people are reading. Open Tools › Notification settings and choose Comments for you (@mentions and threads involving you) or None. Read the comments on your own schedule from the comments panel instead, opened with Show all comments at the top right, where you can filter to open or resolved threads.

In Word, separate copies can be merged into one file later; the steps are on combining comments in Word.

A form and a tracking sheet

Margin comments tell you where a reader stumbled. They rarely say whether the ending worked. A short questionnaire, sent when a reader finishes, catches the whole-book reactions; a form tool like Google Forms or Microsoft Forms will collect the answers into a spreadsheet for you. Keep it to a handful of questions: where they lost interest, who they didn't believe, what confused them, and what they would tell a friend.

Then build one tracking sheet for everything, with a row per note and these columns:

• Chapter (and scene, if you number them)
• Reader
• The note, in a line
• Kind of note, such as plot, pacing, or a single line
• The reader’s grade for the scene, 1 to 10, if you asked for one
• Your decision: fix, consider, or leave

Sort by chapter and the pattern shows. One reader confused by a scene is an opinion. Three readers flagging the same page is a problem, whatever they each suggested as the cure. Sorting by kind tells you whether the revision is structural or a polish.

Grades sort the same way. James N. Frey, in How to Write a Damn Good Novel (1987), asks readers to score every scene, and the scenes that all of them put below about 6 are the ones he says to punch up. A low grade from one reader is weather. From everyone it is a verdict.

Deciding what to change, and what to say

A note is a report of what happened to one reader, not an instruction. Frey’s rule is to change the words only when you are firmly convinced the change makes the manuscript better. A suggestion you would make only to please the person who wrote it fails that test, however politely it was offered.

Nor should you answer the criticism. In How to Write a Damn Good Novel II (1994), Frey tells writers never to defend or explain their work to a critic. Say thank you and take the note away. If the scene needed explaining, the book has to do the explaining, because it will not have you beside it later. There is a practical reason too. I build Tabularia and write a fantasy series alongside it, and I have found that my biggest critics are occasionally my largest fans.

In Tabularia

Send the same draft to several people with the Editor role, and each works alone. Nobody sees another reader's notes. When one presses Submit to Author, their review comes back as a separate draft, filed under the version you sent, carrying their proposed wording and the comments they anchored to passages. The Drafts & Sharing button counts reviews waiting for you, so nothing needs a notification email.

You then work through one review at a time, in the chapter where each note sits, and accept or reject each change separately. What Tabularia does not do is tally readers against each other. Nothing counts how many reviews flagged the same passage. The questionnaire and the tracking sheet stay outside it, in whatever spreadsheet you already use.