How to Critique Writing: A Structured Manuscript Review Method for Writers and Beta Readers

Overview

Before beginning a manuscript critique, establish the purpose of the review. A developmental critique looks at the larger experience of the manuscript, while line editing focuses on sentences, rhythm, word choice, and clarity. Copy editing checks consistency, grammar, usage, and mechanics. These kinds of feedback can overlap, but they should not be confused. A manuscript with structural problems usually needs a different response from one that is structurally sound but difficult to read at the sentence level.

Read the manuscript once for overall experience before making detailed notes. Record your immediate reactions: where you became curious, where your attention weakened, which characters or ideas stayed with you, and where you felt confused. Then make a second pass using the checklist below. Separating the reader response from the technical review helps prevent individual sentences from distracting you from larger problems.

A strong critique distinguishes between an observation, an interpretation, and a recommendation:

• Observation: “The protagonist learns the secret in chapter three, but the consequences are not addressed until chapter eight.”
• Interpretation: “This delay made the discovery feel less important than it seemed at first.”
• Recommendation: “Consider showing an immediate decision or consequence so the discovery changes the direction of the story.”

This approach is more useful than a vague comment such as “the middle is slow.” For additional guidance on giving reader feedback, see these beta reader questions and form templates.

Checklist by scenario

For a first-read manuscript critique

Start with the reader’s journey rather than correcting every sentence. Ask:

• What does the manuscript appear to promise in its opening pages?
• Is that promise clear enough to create interest?
• Who or what is the central focus?
• What does the main character want, and what prevents them from getting it?
• Does each major section change the situation, deepen the problem, or reveal meaningful information?
• Where did you feel most engaged?
• Where did you begin skimming, lose track of events, or need to reread?
• Does the ending resolve the central question or provide a satisfying next step?

For fiction, note the moments when the character makes choices and whether those choices produce consequences. For nonfiction, track the promise made to the reader, the order of the information, and whether each section supports the stated purpose.

For a developmental review

Use this part of the checklist when the writer is still able to make substantial changes to structure or content:

• Structure: Does the order of chapters or scenes create a logical and engaging progression?
• Conflict or problem: Is the central difficulty specific, consequential, and sustained?
• Character: Do the main characters have distinct goals, pressures, decisions, and changes?
• Pacing: Are important moments given enough space, while repetitive or low-value sections are controlled?
• Point of view: Is the narrative perspective consistent and appropriate for the material?
• Theme: Do recurring ideas emerge through action and detail rather than repeated explanation?
• Continuity: Do timelines, facts, character knowledge, settings, and relationships remain consistent?
• Payoff: Do setups lead to consequences, answers, or deliberate unresolved questions?

Do not treat every interesting detail as equally important. Mark patterns. One slow scene may be a local issue; several scenes that repeat the same emotional beat may indicate a pacing or structure problem.

For a prose and clarity review

Once the larger structure is stable, inspect the writing at paragraph and sentence level:

• Can you identify who is acting, speaking, or thinking in each passage?
• Are sentences varied without becoming confusing or decorative for their own sake?
• Do concrete details support the mood, argument, setting, or character?
• Are abstract statements supported by examples or observable action?
• Does dialogue sound distinct between characters?
• Are scene transitions clear?
• Do modifiers, filler phrases, and repeated words weaken otherwise strong sentences?
• Is the level of explanation appropriate for the intended reader?

Read difficult passages aloud or use text-to-speech as a proofreading aid. Hearing the manuscript can reveal abrupt rhythm, repeated sentence openings, missing words, and dialogue that does not sound natural. This is a supplement to human judgment, not a substitute for it.

For a beta reader report

A beta reader does not need to diagnose every technical issue. Their most valuable contribution is an honest account of the reading experience. Ask them to report:

• What they expected the manuscript to be about after the opening.
• Which characters, ideas, or sections they cared about most.
• Where they felt confused, unconvinced, bored, or emotionally distant.
• What they remembered after finishing.
• Whether the ending felt earned and complete for the type of work.
• What single change would most improve the reading experience.

Give beta readers focused questions rather than asking whether they “liked” the manuscript. A yes-or-no reaction is difficult to revise from; a specific moment and explanation can reveal a pattern.

What to double-check

After completing the first review, sort your notes into three levels of importance. This prevents minor copy edits from competing with major revisions.

1. Priority one: reader-blocking problems. These include a confusing premise, missing motivation, broken timeline, unsupported conclusion, unclear instructions, or an ending that does not address the central question.
2. Priority two: experience-shaping problems. These may include repetitive scenes, uneven pacing, weak transitions, an underdeveloped relationship, inconsistent tone, or sections that do not support the manuscript’s purpose.
3. Priority three: polish. These include word repetition, punctuation, formatting, sentence rhythm, and isolated awkward phrases.

Then check whether your recommendations are actionable. “Make the character deeper” is a broad judgment. “Give the character a decision in this scene that costs them something” points toward a possible revision while leaving the writer room to solve the problem in their own way.

Also double-check the difference between a genuine problem and a preference. A reviewer may prefer first-person narration, shorter chapters, or a different ending, but those preferences are not automatically revisions the manuscript needs. Frame subjective reactions honestly: “I wanted more context here because I could not understand the character’s decision,” rather than “This character should not make that choice.”

For a full self-editing pass after the critique, use a dedicated self-editing checklist for fiction and nonfiction manuscripts. If you are comparing tools for annotation, drafting, or revision, the writing apps comparison guide can help you choose a workflow without letting software replace editorial judgment.

Common mistakes

• Commenting on every line too early: Extensive sentence notes can hide a structural problem. Review the manuscript at the level that matches the current revision stage.
• Using broad labels: Words such as “boring,” “confusing,” or “unrealistic” are starting points, not complete feedback. Identify the passage and describe the reader effect.
• Rewriting instead of critiquing: A reviewer’s version may solve one problem while changing the writer’s voice. Explain the issue before offering an example.
• Giving equal weight to every note: A missing motivation matters more than a repeated adjective. Prioritize changes by their effect on comprehension and reader engagement.
• Ignoring the manuscript’s intended audience: The right level of explanation, complexity, humor, and pacing depends on what the work is trying to do and whom it is trying to reach.
• Overloading the writer: A long report is not automatically a useful report. End with the three to five revisions most likely to improve the manuscript.

Feedback should be candid without becoming personal. Describe what the text does, what you experienced, and what might help. The writer can then decide how to revise.

When to revisit

Return to this checklist whenever the manuscript enters a new revision stage. After a major structural change, reread for plot logic, character motivation, pacing, and continuity before polishing sentences. After a line edit, read selected passages aloud to check whether the revised prose still sounds natural. After receiving beta feedback, look for repeated reactions rather than treating one reader’s preference as a universal rule.

It is also useful to revisit the critique before sharing a new draft with another reader. Remove resolved comments, record open questions, and state what kind of feedback you now need. For example, a second review might focus only on the opening, the ending, or the clarity of a nonfiction framework.

Practical next step: Copy the checklist into your notes, read the manuscript once without editing, and write a one-page report containing three strengths, three evidence-based concerns, and three prioritized revision actions. Then wait until the report is complete before changing individual sentences. This simple sequence keeps the review focused on the reader’s experience and gives the writer a clear path from feedback to revision.