Novel craft and story design

How to get feedback on a book

August 16, 2026 · The StoryProp team

Getting useful feedback on a book is four decisions, not one favour: who you ask, what you ask them, how you brief them, and how you read what comes back. The favour is not small — every reader you recruit is agreeing to several hours of unpaid attention on a whole manuscript. Spend that badly and you get the answer everyone gets. The first time you hand a draft to another person, you almost certainly ask the wrong question. What did you think? It produces the least usable answer there is: a warm paragraph about how much they enjoyed it, one gentle reservation about a character's name, an offer to read the next one. You have spent a reader — a non-renewable resource, since nobody reads your book for the first time twice — and learned nothing you can act on.

Not because readers are unhelpful. Because feedback is an instrument, and an instrument nobody designed doesn't measure anything. Useful notes come from deciding what you need to know, choosing people who can know it, asking in a form they can answer, and reading what comes back with a cold eye. All four steps are yours, and most writers skip all four, then conclude that beta readers are a waste of time.

Readers feel, writers diagnose, professionals prescribe

Three kinds of reader can help you, and they answer three different questions. Ordinary readers — people who read the sort of book you wrote, for pleasure, without craft vocabulary — are the only source of one irreplaceable thing: what it is like to move through your pages without knowing where they lead. They can tell you they got lost on page nine, that they skimmed the flashbacks, that they stopped at chapter four and never came back. On all of that they are authoritative. On why it happened, they are guessing.

Writers diagnose. A peer who has finished a book can look at the same stumble and name a mechanism: the scene has nowhere to go because Daniel states his suspicion in the opening line; the reader confused two characters introduced in the same room doing the same thing. Rarer service, different hazard — writers read with their own book running in the background, and some portion of any craft note describes the novel they would have written instead. Take the mechanism, be careful with the aesthetics.

Professionals prescribe. Someone you pay to read is being paid for a plan: an ordered set of changes, with reasons, on a schedule. That work is sold in three distinct shapes, and the names matter the moment you ask for a quote. A manuscript evaluation buys a report on the whole book and what is wrong with it. A developmental edit buys structural work on the book you actually have. A line edit buys sentences, and is wasted on a draft whose structure is still moving. Ask which of the three you are being quoted for before you ask what it costs, because the single word editing covers all three and they are not interchangeable. All of it is the most expensive kind of note and the least useful before you know what hurts. So ask each instrument the question it can answer, and don't ask a friend who reads two novels a year to explain your structural problem — out of kindness, they will oblige, badly.

The fourth instrument is a machine, and its range is worth stating precisely. A whole manuscript fits now: Anthropic publishes a one-million-token context window for Claude Opus 5 and Sonnet 5, and its own conversion puts a million tokens at roughly 555,000 words on the tokenizer those models use, which puts a 100,000-word novel at about 180,000 tokens by that ratio, or about 133,000 by OpenAI's published rule of thumb of three-quarters of a word per token — a fraction of the window on either count, and worth checking against a vendor's own token counter before you rely on it. What varies is where you run it. OpenAI's published figures for its Business plan give GPT-5.6 Sol a 272,000-token window inside ChatGPT against 1,050,000 in the developer API, for the same model. And capacity is not attention: Anthropic documents that accuracy and recall degrade as the token count grows, and that its consumer product summarises earlier messages to make room, which is why a long chat about your book starts losing the middle of it (why chatbots lose the plot). A machine reader is very good at the things a marking scheme catches — a promise made and never paid off, a character who disappears for ninety pages, a rule of your own world that gets broken in chapter twelve. It cannot tell you it was bored, because it wasn't.

Ask for reports, not verdicts

Once you know who you are asking, design the questions. You want reports, not verdicts. A verdict — good, bad, works, doesn't — is a judgment your reader is not equipped to make and will soften anyway. A report describes something that happened to a person while they were reading, and you can check it against your own pages.

Questions that reliably produce reports: Where did you stop reading, each time you stopped? When did you feel you knew what the book was about? Who did you have to page back to identify? Which parts did you skim, honestly? These can be answered without craft vocabulary and without hurting anyone's feelings, which is why they get answered honestly. They are also about the reader rather than the book: where were you bored is a fact about a person; where is the pacing bad is an opinion about a manuscript, and that one is yours.

For readers who will not write you an essay, give a marking scheme instead of a questionnaire. Three marks in the margin, no explanation required: a wavy line where they got bored, a question mark where they got confused, an X where they didn't believe it. It costs a reader almost nothing, and marks land on exact locations where commentary lands on memories of them. Say explicitly they are not looking for typos; hunting mistakes in your manuscript — a name that changes spelling, a chipped cup that changes which part is chipped — is a separate pass with different eyes.

And ask the question you are afraid of. Most writers know the weak place and build a questionnaire that walks carefully around it. If you suspect the middle sags, ask outright whether they considered quitting, and where.

Logistics that respect everyone's time

Beta readers are volunteers doing skilled unpaid labor, and the brief decides whether anything comes back. Send a draft you have already revised once; a raw one burns readers on problems you would have caught yourself, and it teaches them the book is rough, which tints everything after. Choose people who read what you wrote — a patient friend who reads literary fiction will give a thoughtful, entirely misdirected response to your thriller, because the expectations they bring are not the ones your book was built to satisfy. If those people are not already in your life, the places writers find them run on reciprocity. Critique Circle and Scribophile are exchange economies: you earn the right to be read by critiquing other people's chapters first, in credits on one and karma points on the other, so the readers you get are other writers, with a writer's eye and a writer's blind spots. Reddit's r/BetaReaders works the opposite way, as an open noticeboard where you post your genre, your word count and what kind of read you are asking for, and readers volunteer for the books that appeal to them — which selects, usefully, for people who already like the sort of thing you wrote. Genre groups on Goodreads and Discord behave the same way.

Ask a handful at a time rather than everyone you know, and recruit past the number of responses you need, because some share of any volunteer group never files a note and that is a fact about volunteers rather than a verdict on the book. Keep some readers in reserve for the draft that comes back from revision, when the question is no longer where does this break but did the repair hold. Give a deadline, and give permission to quit: if you stop, that's fine, just tell me the page and what you were feeling. That converts silence, your worst outcome, into your most valuable data point. A reader who abandons the book at chapter four has told you more than one who finishes and calls it lovely.

When the notes arrive, do not explain the book. The urge is enormous: they missed the thing and you could clear it up in a sentence. But you cannot ship that sentence with the manuscript, and every explanation contaminates what follows: from then on they respond to your account of the book instead of the book. Say thank you, and ask follow-ups only about experience — where exactly, what did you think was happening, how did you feel about her there.

The note under the note

Readers are reliable about location and unreliable about cause, and the art of receiving feedback is separating the two. A note arrives as a package — an observation, an interpretation, a proposed fix — in roughly reverse order of usefulness. Suppose three readers finish a draft of The Quiet House. One says the ending felt abrupt and suggests an epilogue. One says she never warmed to Mara. One says the middle dragged around the hardware store.

Taken as instructions, that is three incompatible rewrites. Taken as reports, it is plausibly one problem: Mara makes the decisive choice about the house offstage, between chapters, so the reader is told what she decided instead of watching her decide. The ending feels abrupt because the real turn happened earlier and invisibly. Mara feels distant because her largest act is never dramatized. The middle drags because attention drifts to Daniel, who at least does things on the page. One cause, three symptoms, and none of the readers named it.

So: count locations, discount prescriptions. When several independent readers stumble in the same place, something is wrong there, about as close to a law as this work offers. What they think is wrong, and what they propose you do about it, is a stranger's guess. Look for the earliest point where the symptoms could share a cause, because problems surface downstream of where they were planted.

When feedback is noise

Not every note is signal, and treating them as equally valid is its own way of ruining a book. Sort what comes in into three piles. Confirmed: several readers, independently, in the same place — those go into the revision plan. Suspected: one reader, but it lands on a doubt you already had, like the chapter you knew was doing two jobs. Discarded: notes asking for a different book. A reader who wants the ghost to be real in a novel about grief is reporting a preference, not a flaw.

Two other tells. A note delivered with great confidence and no location attached is usually a personality rather than a problem. And a note that lands on something deliberate — the unlikable narrator, the thread left open — needs a higher standard of evidence than one about something you did by accident, because a deliberate risk is indistinguishable from a mistake right up until it works.

What you are left with is a set of diagnoses rather than a to-do list, and turning diagnoses into an ordered sequence of passes is the next problem, covered in how to revise a novel. The thing worth adding is that notes evaporate: a marked-up file, four conversations, a voice memo, and by the time you sit down you are revising from memory of what somebody said in March. Keeping them attached to the work is exactly what a project-aware writing setup is for, and StoryProp is built that way. Reader notes and your decisions about them stay in the project's ongoing conversation, and the ones you commit to become records the agent reads before it writes. What you agree to gets written down; what a reader merely suggested stays a suggestion.

Feedback is not a verdict and it is not a vote. It is instrumentation, a way of learning what your pages do to someone who is not you, which is the one fact rereading can never give you. Ask precisely, listen for location, keep the deciding for yourself, and the pile of notes stops being frightening and becomes a map with the difficult places marked. Most of the distance between a draft that nearly works and one that does is drawn on it.

Reader notes are only worth as much as what survives the week after you get them. StoryProp keeps the ones you act on as decisions the agent writes from, so the fix you agreed to in March is still shaping chapter nine in June.

← All posts