Where the term comes from
Wikipedia defines a beta reader as a test reader of an unreleased work, typically literature, who gives the author feedback from the point of view of an average reader. That feedback can be used to fix remaining issues with plot, pacing and consistency, and to see whether the work has the intended emotional impact. The term was borrowed from the software industry, where beta testers use an unreleased product for a real task, partly to find problems.
Merriam-Webster defines a beta test as a field test of the beta version of a product, especially by testers outside the company, carried out before commercial release, and dates the term to 1983. Wikipedia also separates the role from its neighbours. A beta reader usually reads a draft that has been revised at least once, while an alpha reader sees an earlier, unrevised one. A proofreader focuses on grammar and spelling, and a critique partner reads as a writer. A sensitivity reader is a type of beta reader with knowledge of a culture the author does not know well.
An example
Gideon Hale finishes his second draft of a seaside ghost story. He sends the first ten chapters to three readers, with three questions: where did you get bored, which character did you trust least and what did you think the ghost wanted? One reader stops at chapter six and says the pace dropped when the family moved into the lighthouse. Another thinks the ghost is the mother, which Gideon did not intend. A third answers every question with "I liked it". Gideon learns the most from the first two, rewrites the chapter six sequence and then asks a new pair of readers to look at the changed ending.
Common mistakes
- Sending a first draft that is not ready, so readers spend their time on problems you already know about.
- Asking "what did you think?" instead of specific questions.
- Choosing only friends and relatives who will not tell you what is wrong.
- Defending the manuscript when a reader reports confusion. Confusion is the data you asked for.
- Changing the book because one reader disliked something, rather than looking for patterns across several.
How to check your manuscript
Before sending, read the draft yourself and fix everything you already know is wrong. Then write three or four questions about the reading experience, not about line-level style. After feedback, mark the points that more than one reader raised and treat those first. For related terms, see pacing, plot twist and stakes.
In Musael, beta reader links let you send chosen chapters and see how far each reader got, which shows whether your chapter endings are pulling people forward.