1
Root issue: protagonist’s goal appears too late. Tasks: revise opening scene objective, add consequence in chapter 2, remove redundant explanation in chapter 4.
16 Revision Plan Examples
Use these examples to study structure, specificity, tone, and variation. They are demonstrations—not claims about a real person or organization unless the example itself makes that explicit.
Before you copy
What to notice in the examples
A useful revision plan states the manuscript goal, separates evidence from proposed fixes, groups symptoms under root issues, ranks work by impact and dependency, maps changes to locations, defines pass-level success tests, protects working material, tracks ripple effects, and includes checkpoints where the author rereads before committing to finer editing stages.
- Evidence intake: beta patterns, editorial notes, self-read findings, continuity/fact issues, and deliberate author goals kept traceable to their sources.
- Diagnosis and priority: root problems, affected manuscript functions, confidence, severity, dependencies, and what should not be changed.
- Pass architecture: whole-book structure first, then chapter/scene/section work, then paragraph/line work, then copy/proof stages when content is stable.
- Task map: each revision has a location, action, dependency, expected effect, status, and ripple locations to recheck.
- Checkpoint system: reread and test after major passes before accepting the fix or moving to a lower-level stage.
2
Root issue: nonfiction chapters repeat the same principle. Tasks: merge chapters 3/5, reassign examples, create missing implementation chapter.
3
Pacing pass: mark scene goal, conflict, and change for chapters 8–14; cut two scenes where the state does not change.
4
Evidence pass: list every major claim, source currently supporting it, and whether interpretation exceeds the evidence.
5
Character pass: track decisions at inciting incident, midpoint, crisis, and climax to ensure the arc is behavioral rather than narrated.
6
Continuity pass: build timeline for travel, injuries, weather, and communication delays before copyediting.
7
Voice pass: after structural changes, compare three representative chapters for tone drift created by rewrites.
8
Final stage: freeze major content before line edit → copyedit → proofread.
9
Priority 1: move the protagonist’s explicit goal into chapter 1; dependent tasks = chapter 2 consequence, chapter 4 exposition cut, midpoint goal escalation.
10
Pass split: first rebuild the nonfiction framework and chapter order; only afterward revise transitions and sentences that explain that framework.
11
Ripple log: changing the murder date affects alibis in chapters 3, 7, 12, the police timeline, weather reference, and final reveal.
12
Protected-strength note: preserve the kitchen reconciliation scene while shortening the surrounding travel sequence because beta readers consistently identify the scene as the emotional turn.
13
Experiment: combine chapters 5 and 6 to remove repeated evidence; success test = each remaining chapter performs a unique reader job and the transition still makes sense.
14
Conflict resolution: beta readers disagree about the ending; plan two ending experiments and test which better fulfills the stated genre/character promise rather than choosing by vote.
15
Escalation: repeated feedback says “the middle drags,” but self-diagnosis cannot identify why; schedule a developmental edit before line polishing 30,000 unstable words.
16
Stage gate: after structural and scene passes, perform a clean read specifically for new continuity gaps before handing the manuscript to line/copy editing.
Keep the underlying decision or pattern, then replace the subject, evidence, relationship, constraints, and tone with details that belong to your situation. If your final line still works after swapping only one noun, it may be too close to the example.