Questions to Ask Beta Readers
Questions for a writer sending a manuscript out to beta readers, designed to get reactions rather than edits: where attention slipped, what was confusing, who they cared about, and whether the ending landed.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
How long did it take you to read, and how many sittings?
The least threatening question and one of the most informative. A book read in three evenings and a book read across six weeks are giving you very different data, and the gaps usually fall in the same places for every reader.
- 2
Where did you stop each time you put it down?
Chapter ends are neutral. Stopping mid-scene means the scene lost them, and if several readers stop within the same twenty pages you have found a soft section without anyone having to name it.
- 3
Was there a point where you nearly did not pick it back up?
Readers rarely volunteer this because it feels unkind, but they will answer it directly when asked. It locates the one place where the book stops earning attention, which is worth more than a page of line notes.
- 4
Who did you care about most, and when did that start?
The when is the useful half. If a reader only warmed to your protagonist at page eighty, you now know how much of the opening is running on patience rather than on interest.
- 5
Did you mix up any of the characters?
Names starting with the same letter, similar speech patterns, and characters introduced in a cluster are the usual causes. Readers assume this is their own failing and will not mention it unprompted.
- 6
At what point did you feel you knew what the book was about?
You are measuring the distance between where you think the premise lands and where it actually lands. If the answer is a third of the way in, that gap is the reason agents stop reading.
- 7
What did you think was going to happen, and were you right?
Both answers help. Being right too early means the setup is louder than intended, and being wrong in an interesting way often points at a better book than the one you wrote.
- 8
Was there anywhere you had to go back and reread?
Rereading signals a mechanical problem: an unclear pronoun, a jump in time, a name introduced too casually. These are cheap to fix and nearly invisible to the person who wrote them.
- 9
Did you skim anywhere, even a little?
Give explicit permission for this answer. Skimming is a stronger signal than boredom, because it shows the reader still wanted the story and had decided this part was not part of it.
- 10
Which scene do you still remember now, a week later?
Memory a week out is a fair proxy for what a reader would tell a friend. If nothing from the middle third survives, you have learned something specific about the middle third.
- 11
Was there a moment when you did not believe a character would do that?
This is where plot mechanics show through. Readers feel the author's hand exactly when a character does something the story needs rather than something the person would do, and they can usually point at the page.
- 12
Did the setting feel like a real place, and was there a point where it stopped?
The second half of the question finds the problems. Worlds tend to be built densely in the first chapters and then thin out once the plot takes over, and readers notice the thinning even when they cannot name it.
- 13
Was the timeline ever confusing?
Ask this even if your book is strictly chronological. Season, time of day, and how long has passed since the previous chapter are the three things writers track in their heads and forget to put on the page.
- 14
How did the first five pages read?
Ask about the opening separately and late in the conversation, once they have relaxed. By then they have read the whole book and can tell you what the opening promised that the book never delivered.
- 15
Did any of the dialogue feel stiff, and did anyone sound like themselves?
Ask them to name the character whose voice was clearest. Whoever they name is the one you have written well, and everyone else is probably closer to your own voice than you think.
- 16
Did the ending feel earned?
The word earned matters more than satisfying. A reader can enjoy an ending and still feel it arrived from outside the story, and that distinction is the note you need before starting a revision.
- 17
Was there anything you expected from the ending that you did not get?
This catches promises the book made without you noticing: a minor character who felt like a setup, an object introduced with weight, a question raised in chapter two. Unpaid promises read as a weak ending.
- 18
How would you describe this book to a friend, in one sentence?
Their sentence is your book's real pitch, stripped of everything you intended. If it does not match the story you think you wrote, that difference is usually where the marketing problem and the structural problem both live.
- 19
Who is the reader for this, and would you have finished it if you did not know me?
Asking the second half plainly gives the reader permission to be honest and gives you the answer that matters commercially. Expect a pause before the reply, and let the pause happen.
- 20
What do you think I was trying to do, and did I do it?
Save this for last. It moves the conversation from reaction to intent, and it is the one question that can tell you whether the problem is the execution or the idea underneath it.
Running a useful beta read
Practical guidance for the conversation itself.
Setting it up
Setting it up
- 1Tell readers what stage the draft is at and what you are not fixing yet, so they do not spend their attention on typos in a structural draft.
- 2Give a deadline and keep it modest. Four to six weeks gets more finished reads than an open invitation does.
- 3Send the questions with the manuscript, but ask readers not to answer as they go unless a question says otherwise. Reactions written in hindsight are smoother and less accurate.
- 4Ask for one thing during the read only: a mark in the margin wherever they got bored, confused, or stopped believing it.
- 5Use three to five readers rather than one. A single reader gives you an opinion, and several give you a pattern.
Asking in a way that gets truth
Asking in a way that gets truth
Ask about experience, not solutions
Readers are reliable about what they felt and unreliable about how to fix it. Where did you lose interest is answerable. What should I change turns a reader into an inexperienced editor.
Do not explain while they answer
The urge to say what that scene is meant to do is strong and it ends the useful part of the conversation. Explain it and you have taught them to read the book you intended rather than the one on the page.
Take the location, not the fix
When a reader says a scene did not work and then suggests a repair, the first half is usually right and the second half usually is not. Note where the problem is and solve it yourself.
What to do with the answers
What to do with the answers
- Look for places where two or more readers stumbled, even when they describe the problem differently. Agreement on location beats agreement on cause.
- Discount notes asking the book to be a different kind of book, especially from readers who do not read your genre.
- Record anything that made a reader laugh or reread a line for pleasure, since positive detail is as useful as criticism and much rarer.
- Wait a week before revising. The first reaction to feedback is not the useful one.
- Thank readers with something specific from their notes, since that is what gets them to read the next draft.