How-to

How to get feedback on your novel

Feedback is how you learn what the book does on the page, not only in your head. The goal before an agent or editor sees it is honest signal: where readers stumble, where continuity breaks, and which questions are still yours to answer as the author.

Decide what kind of feedback you need

Not every pass asks the same question. Early structural feedback asks whether the story holds together. Line-level feedback asks whether sentences earn their keep. Continuity feedback asks whether facts and timelines agree across chapters. Mix those requests in one round and readers will answer the loudest problem, not the one you meant to test.

Write a short brief for readers: stage of the draft, spoiler comfort, and three questions you actually want answered. Vague “tell me what you think” invites vague praise or scattershot notes.

Beta readers and critique partners

Human readers are still the best test of pacing, emotional payoff, and whether a plot turn lands. A good beta reader tells you where they skimmed, where they got confused, and which character they stopped believing. A critique partner who knows craft can go deeper on scene goals and structure. Neither job is the same as a spellcheck or a continuity list.

Protect the relationship. Give a deadline you both accept, say whether you want margin notes or a letter at the end, and do not argue chapter by chapter in the first reply. Thank them, sit with the notes, then decide what to change.

What to fix before you ask for a full read

Readers forgive a rough sentence. They resent spending weekends on a draft whose timeline collapses or whose protagonist changes eye color twice. Before a full beta round, do a self-pass for known weak spots: chapter order, major plot promises, and character facts you have already established. Clean continuity is a courtesy to the people giving you time.

If you use software for that pass, treat it as an audit of what is already written. Tools that invent new prose or “improve” your voice are a different category. For feedback, you usually want problems named, not a rewritten chapter you did not ask for.

Continuity checks are not beta readers

Novilot’s Continuity Guardian reads a manuscript, looks for contradictions across chapters, and quotes both conflicting passages so you can verify the conflict. That is useful before or between human rounds. It is not a substitute for beta readers. It will not tell you if a twist is satisfying, if a romance lands, or if chapter two is slow. It audits consistency. Humans still judge the reading experience.

Use both on purpose: run a continuity pass so betas are not stuck reporting typos of fact, then ask humans about story. When you revise, you can run another audit to see whether fixes introduced new conflicts.

A feedback sequence that saves rounds

1. Self-edit for clarity and completeness of scenes.
2. Run a continuity audit and fix verified contradictions.
3. Share with betas with structured questions (plot, character, pace), not a blank “thoughts?”.
4. Synthesize themes in the feedback before rewriting everything at once.
5. Re-audit continuity after the revision pass, then export when the file is stable.

Related: tracking characters, Beta Reader Hub, guest demo, and indie author workflow.