How to find and use beta readers: what to ask, where to look, and what to do with the feedback

Beta readers are the dress rehearsal before publication: a small audience of ordinary readers sees the book while it can still change, and reports what a launch-day crowd would report too late. This guide covers what a beta reader does, what feedback to ask for, where to find readers, how many and when, and how to interpret the results. The self-editing passes that come first are covered in how to edit your novel.

What is a beta reader?

Savannah Gilbo's definition: beta readers are "everyday readers who agree to read your full manuscript and share their experience of the story before publication." Reedsy's is procedural: "a beta reader is simply someone who reads a completed or near-completed book manuscript to give the writer feedback prior to publication," one who will "act as a test audience for your manuscript prior to publication." Wikipedia, the source of our glossary entry, adds the useful standpoint, feedback "from the point of view of an average reader." The name comes from software beta testing; the job is the ordinary reader's report: where the story carried them, where they were confused or bored, and what "errors, plot holes, or inconsistencies" they noticed (Reedsy). Barbara Linn Probst's survey on Jane Friedman's blog compresses it into one line: "They're civilians, proxies for our future readers."

Beta readers, alpha readers, editors, sensitivity readers

Betas do none of the neighbors' jobs. Gilbo's division of labor: they do not "Fix your grammar and typos (that's a proofreader)", do not "Rewrite your sentences (that's a line editor)", and do not "Promote your book when it's published (those are ARC readers)."

• Alpha reader. "typically the first person who reads and provides feedback on your manuscript, usually while it's still a first draft" (Reedsy).
• Editor. "an editor should be reserved for the end of the writing process, when you need specialized expertise and a professional touch" (Reedsy); betas "don't have the expertise to help a new author implement the needed changes."
• Sensitivity reader. "a reader who is specifically engaged to assess a manuscript for cultural accuracy," often "a member of the group or culture being depicted in the story" (Helen Sloce, quoted by Reedsy).

What feedback to ask beta readers for

Ask for reactions, not rewrites. Andrew Noakes, on Jane Friedman's blog, calls beta readers "in effect, a focus group whose reactions to your book will tell you how successfully it communicates with its intended audience," so the method is "Structured feedback means asking a list of carefully chosen questions," broad first ("Where did the story slow down for you?", "Which parts did you skim?"), then narrow ("Was there any point where you felt inclined to stop reading?", "How did you feel about the ending?"). Reedsy's contributing editors converge on the shape: develop "ten questions that cannot be answered by yes or no" (Sandra W.), ask where the reader felt "bored, confused, or tempted to skim" (Tee T.), and include "If you had to describe what this book is about in one or two sentences, what would you say?", whose answer is the seed of a book blurb. And "don't inundate them" with questions before the read (Reedsy); the discussion comes once they finish.

Where to find beta readers

Writing and critique communities come first, being where "the most honest, candid, and potentially useful feedback" is found (Reedsy):

• Writing communities. K.M. Weiland's peer-vetted list runs from Absolute Write and Critique Circle through Scribophile, Critters Workshop ("for Speculative Authors") and Fantasy-Writers.org; Reedsy adds the Absolute Write Water Cooler's "Beta Readers, Mentors, and Writing Buddies" board, and "Facebook groups, Discord servers, and forums like Scribophile are great places to start" (Gilbo), who cautions: "Begin with a single chapter or short section to test compatibility before you share the whole draft."
• Groups run for the purpose. The "Beta Readers and Critique Partners" Facebook group counts "over 24,000 members" (Reedsy).
• Your own readers. A mailing list works because its members "are already invested in you and your career" (Reedsy).
• Paid services. "Companies such as The Spun Yarn provide trained beta readers who offer reliable, structured feedback" (Gilbo).

Vetting starts with genre: "If a suspense author relies only on romance beta readers, they might not have the instincts for suspense that are needed to provide the appropriate feedback" (Reedsy). Weiland frames the search as a relationship you build, "just as you would build any important friendship," so "go where writers go" and "offer to trade critiques."

How many beta readers, and when

"Start with three to five readers who know what to look for in your kind of story" (Gilbo); Reedsy's Sandra W. recruits wider, "twelve to twenty likely readers of this genre," expecting attrition. The sources agree the read happens on a complete draft after your own revisions (for the stage before, see how to write a first draft), and differ on one detail: Reedsy runs self-editing, then betas, then a professional editor; Gilbo usually recommends "working with an editor first," after which "beta readers can confirm that the story now lands the way you hoped." After major revisions, "another small group of readers" can "confirm that the fixes now create the experience you intended" (Gilbo).

Running the beta read: deadlines, formats, thank-yous

• Set the deadline in the invitation. "A standard timeline for most novels is 2-4 weeks" (Gilbo); Reedsy's Sandra W. allows that a longer process "should take four to six weeks, depending on your manuscript length and their schedule."
• Put expectations on one page: the timeline, the feedback method, "Your 5-10 most important questions," and "Permission to be honest" (Gilbo). Check in halfway with a friendly "How's it going?" email, and while you wait, "don't start revising."
• Count flattery as failure: "I've had plenty of betas who 'yes' me to death and while nice for the ego, it's not what you need" (Probst's survey).
• Close with thanks. The going rate is "a free copy and a mention in the acknowledgements page" (Reedsy): "Writing a good book really takes a village!"

How to interpret beta feedback

First, patterns over outliers: "don't get hung up on every single comment. Look for patterns" (Tee T., via Reedsy); three readers flagging a scene is a finding, one disliking the protagonist is taste. Kristen Kieffer puts a number on it: change only what you wholeheartedly agree with, "or if more than 50 percent of your beta readers made the same critique."

Second, the reader is right about the problem and often wrong about the fix. Neil Gaiman's fifth rule for writing, from The Guardian's "Ten rules for writing fiction": "Remember: when people tell you something's wrong or doesn't work for them, they are almost always right. When they tell you exactly what they think is wrong and how to fix it, they are almost always wrong." The work in between is diagnosis, the "reverse engineering" one of Probst's respondents describes: a reader who wants the love interest gone by chapter three is reporting that the romance has not earned its place, and the fix is rarely deletion. Gilbo sorts the aftermath into four buckets, from Must Fix Issues to Things You'll Politely Ignore.

The failure mode is over-compliance: "It's way too easy to ask ten people for comments, and then implement all their comments and lose what I intended for the story." The distinction to keep is Probst's: "Just remember the difference between asking for someone's experience and asking for her expertise."

Beta reading for web serials

A novel gets one dress rehearsal; a web serial gets a rolling one, because serialization replaces the publication date with a schedule (see choosing a release schedule). The beta window moves into the buffer of chapters written ahead of the free release (see advance chapters and Patreon advance chapters, explained); our glossary frames the serial beta pass as the last check before a chapter enters it. In practice:

• The unit shrinks. Betas read an arc, not a book: where did you skim, what did you predict, does the arc's ending pull you into the next one.
• The pool is nearby. A serial's regular commenters are the standing version of the author mailing list; the author's note is the channel that reaches them.
• The turnaround is shorter, and fixes happen before the chapter ships. A buffer measured in chapters sets the deadline, and it is where revision is still private: several readers confused by a twist is a finding; one objection is a preference.

The best beta from this book is the first name on the list for the next one.