How to find beta readers and get feedback you can use

Beta readers read your finished, revised draft as ordinary readers and tell you where they got confused, bored or stopped believing. The best ones read your genre and aren't close enough to you to be polite. Find them in genre reading groups, critique-swap sites, writing organizations and your own mailing list. Recruit two small rounds of three to five, send each reader a short brief, a deadline and a list of questions, and act on the problems that more than one of them reports.

What beta readers do

A beta reader reads a complete draft the way a buyer would read the finished book, then reports on the experience: where they were hooked, where they were lost, which characters they believed and whether the ending paid off. They aren't editors, and they won't fix your structure or your commas. They give you your audience's reaction before your audience sees the book. (The name comes from software, where a beta version goes to outside testers after the team's own alpha round.) It helps to know which kind of early reader you're asking for:

How many beta readers, and when

Send the draft after you've revised it yourself at least once, so readers spend their attention on problems you can't see rather than ones you already know about. Send it before you pay for line or copy editing, since there's no sense polishing sentences in a scene your readers will tell you to cut. If you plan to query agents, finish your beta rounds before the first query goes out. An agent who requests the full manuscript should get the version readers have already tested (see how to get a literary agent).

There's no fixed number, but the reasoning is simple. Three is the floor: with fewer, you can't tell a pattern from one person's taste. Past ten or twelve, the reports start repeating each other and take longer to sort than they're worth. A better plan is two rounds of three to five. The first round finds the big problems, you fix them, and a fresh round tells you whether the fixes worked. Round-one readers can't test the revision, because they already know how the story ends.

Give a deadline, and make it realistic. Adults read fiction silently at about 260 words a minute on average, according to a 2019 review of 190 reading studies by the psychologist Marc Brysbaert. At that pace a 90,000-word novel is close to six hours of reading before anyone stops to write a note. For someone fitting that around a job, four to six weeks is fair. Check in once at the halfway point. If a reader goes quiet past the deadline, thank them and move on without fuss.

Where to find beta readers

Start where readers of your genre already gather, then widen. Two or three of these sources together give you a better mix of readers than any one alone.

Genre organizations are worth a look if your book fits one. SCBWI regional chapters help members find critique groups for children's and young adult books, and the Guppies, an online chapter of Sisters in Crime, runs critique groups and manuscript swaps for mystery writers. Your local library or writing center may host a group too.

What to look for in a reader

• They read your genre, and recently. A literary fiction reader will find your thriller too plotted, and a thriller reader will find your literary novel slow. Neither note helps.
• They can say why. "I stopped caring about Ruth around chapter 9" is worth ten "It was good." Ask a candidate about the last book they abandoned and listen to how they explain it.
• They finish things. Readers who disappear halfway leave you with half a report and no idea why.
• They have no stake in your feelings. Allow one friend or relative at most. Keep one or two writers in the mix for craft-minded notes, and one subject expert if the book needs it, such as a nurse for a hospital thriller.

A recruiting post works when it says what the book is, who it's for and what you're asking, in that order. Here is one for an invented novel:

Paying vs swapping

Most beta reading is unpaid. Readers do it because they love the genre, because they like you, or because you'll read their book in return. The usual thanks is a line in the acknowledgments and a copy of the finished book.

A swap is the fairest trade when the other writer works in your genre and at a similar length: one book each, one report each. It costs you a couple of weekends, so swap with writers whose books you'd enjoy anyway.

Paying makes sense when you need a deadline you can count on, or you've run out of readers you know. Prices vary widely: gig marketplace listings for a full novel start in the tens of dollars, and established independent beta readers charge a few hundred. Before you pay, ask for a sample report, confirm what it covers (a questionnaire, inline comments, a summary letter), and ask whether the reader writes it without AI tools. A paid beta reader is still one reader, and the report is not an edit.

What to send your beta readers

Send three things: the manuscript, a one-page brief and the questions. The manuscript should be clean enough not to distract: spell-checked, chapters numbered and page numbers on, so a reader can write "page 112" instead of "the bit with the dog." Standard manuscript format works well. Let each reader pick the format: a Word file for people who comment as they go, a PDF for people who print, an EPUB for e-readers. Amazon's Send to Kindle accepts EPUB files, so Kindle owners can read it there.

The brief tells readers what kind of help you want and, just as important, what to ignore. Without it, half your notes will be about commas.

Questions to ask beta readers

Ask open questions before specific ones: if you ask "Did you find Ruth sympathetic?" before the reader has said anything about Ruth, you've planted the answer. Ask about places in the book wherever you can, and keep the list short enough to answer properly: pick eight to ten of the end-of-book questions below, not all fourteen. A long form gets short answers.

AFTER EACH CHAPTER (a line each is plenty)
1. Where did your attention drift, if anywhere?
2. Was anything unclear: who someone was, where we were, what just happened?
3. Did you want to start the next chapter? Why or why not?

AT THE END
4. In two or three sentences, what was this book about?
5. Where were you first hooked? Where, if anywhere, were you tempted to stop?
6. Which character did you care about most? Which one could the book lose?
7. Did anyone make a choice you didn't believe? Where?
8. Which parts felt slow? Which felt rushed?
9. Was anything you expected to be explained never explained?
10. Halfway through, what did you think would happen? Were you right?
11. How did the ending leave you feeling? Did it fit the rest of the book?
12. Did you mix up any names, places or terms?
13. Who do you know who would enjoy this book?
14. What one change would make it a better book for you?

GENRE ADD-ONS (use the ones that fit)
Mystery or thriller: When did you suspect the culprit? Did the solution feel fair?
Romance: When did you start wanting them together? Did the obstacles feel real?
Fantasy or science fiction: Were the rules of the world clear when they mattered?
Memoir: Where did you want more reflection, and where less?
Nonfiction: Which chapter could you skip without missing anything?

How to handle beta reader feedback

Criticism of a book you've spent a year on stings, even when it's fair. A routine helps. It keeps you from rewriting in a panic after the first report, and from waving away the fifth.

1. Read all the reports before changing anything

   Wait until all or nearly all reports are in. Read them straight through without replying or taking notes, then put them away for two or three days. Your first reaction to a hard note is rarely the one to act on.

2. Reply with thanks, not explanations

   Thank each reader within a day or two of their report arriving, even before you've digested it. If a note puzzles you, ask a neutral follow-up, such as "What did you think was going on in that scene?" Don't explain what you meant. The reader only had the page, and so will everyone who buys the book.

3. Tally the problems by location

   List each issue with its chapter and the number of readers who raised it, as in the table below. Patterns show up within minutes.

4. Separate the problem from the suggested fix

   Readers are usually right that something is wrong and often wrong about the cure. "Make Ruth nicer" may really mean "I don't understand why her sister puts up with her." Find the cause and fix it your way.

5. Weigh each note by who wrote it

   Notes from your target readers count most. A note from someone who rarely reads your genre counts for less, unless it's about confusion: if a reader couldn't follow the plot, genre doesn't excuse it.

6. Revise, then test with new readers

   Make the changes the patterns support, keep a copy of the draft your readers saw, and send the revision to a fresh round.

Mistakes that waste a beta round

• Sending the first draft. Readers spend their notes on problems you'd have caught yourself, and then they've read the book.
• Asking everyone at once. Nobody can read your book for the first time twice. Hold half your readers back for the revision.
• Recruiting only friends, or only writers. Friends soften their notes. Writers tend to suggest how they'd have written it. Most of your readers should simply read your genre.
• Leaving the deadline open. "Whenever you get to it" usually means never. A date, plus one check-in, gets most reports back.
• Treating readers as editors. A reader who rewrites your sentences is guessing at a fix. Ask for their reaction and leave the rewriting to you.

Running a beta round in Strokes

If you write in Strokes, a few features fit a beta round. Keep the book as a project with a document per chapter. Before you send anything, save a version: later you can preview exactly what your readers saw, with the changes since then marked. Export the draft as Word, PDF or EPUB, whichever each reader prefers, or share a sample chapter to the web as a link while the file stays on your machine.

When the reports come back, import them (Word files come in directly), add them to a chat with the AI Assistant and ask it to group the comments by chapter and count how many readers raised each issue. In Agent mode it can read every report in the project and write the tally as a new document, showing each step for you to accept. Check its counts against the reports. It can't replace the readers, though: a model can guess that a chapter is slow, but only a person who put the book down can tell you where.