A beta reader is not an editor, not a proofreader, and not a friend doing you a favour. They are the closest thing you get to watching a stranger read your book, and almost everybody wastes them.

Send it after your own pass, not before

The temptation is to send the draft the day you type “the end”, because you cannot bear to look at it again. Resist it. You get one first read per person, and spending it on problems you already know about is expensive.

Do the pass you can do alone first: the chapter that sags, the character whose name drifted, the filler words you use nine times a page. Then send it. What you want back is the things you cannot see, and you cannot tell which those are until you have removed the ones you can.

Three or four readers, not twelve

Past four, notes start contradicting each other, and the natural response to contradictory notes is to average them. Averaging your readers is how a book loses whatever made someone want to argue with it.

Four gives you enough signal to spot a pattern. If three of them slowed down in chapter nine, chapter nine is the problem. If one of them did, that is one reader’s taste and you are allowed to ignore it.

Ask three questions, not “any feedback?”

“Let me know what you think” produces “I really enjoyed it!”, which is kind and useless. Give them a brief instead:

  1. Where did you get bored? Not where was it bad. Where did you consider putting it down, or start skimming.
  2. Where were you confused? Who is this, where are we, wait, when is this.
  3. Where did you stop believing someone? The moment a character did something that felt like the author needed it rather than the person wanting it.

Those three cover most structural problems, and they ask for observation rather than diagnosis. A reader reporting that they got lost in chapter four is reliable data. The same reader proposing that you add a flashback is not, and you are not obliged to take it.

Tell them explicitly not to line edit. A beta reader who hands the draft back with the commas moved has misunderstood the job, usually because nobody told them what it was.

What to send

Send something that is easy to read and hard to lose track of.

For readers on a phone or an e-reader, an EPUB. For readers who want to scribble, a PDF. Word is a reasonable third option if you actively want inline comments, though it invites the line editing you just asked them not to do.

Give each reader their own copy with their name on it. Not because your unpublished novel is likely to leak, but because if it does, that watermark is the only thing that tells you where from. Galley builds one watermarked file per reader from a list of names, which makes it a thirty-second job rather than a reason not to bother.

Give them a deadline and a way out

Four to six weeks is a reasonable ask for a novel. Say the date out loud, and say plainly that if life happens they should tell you rather than go quiet, because the alternative is you not knowing whether to chase.

Expect attrition. Two out of four coming back is a normal outcome rather than a betrayal.

Beta readers are not ARC readers

These get conflated constantly, and they happen at opposite ends of the process.

A beta reader reads an unfinished draft, privately, to tell you what is wrong with it. An advance reader copy goes out weeks before publication, after the book is finished, to produce reviews timed to launch. One is diagnosis and the other is marketing.

Sending an unrevised draft to an ARC list is how a book gets its first one-star review, and that review does not go away when you fix the chapter.

Then decide what to change

The last step is the hard one. Your readers are reliable about where they stumbled and unreliable about why. Collect the stumbles, look for the ones more than one person hit, and work out the cause yourself.

Revision tools · Galley for querying writers · Copies made for other people