Revision that fails often looks busy: you open chapter one, fix a metaphor, notice a subplot, chase a typo, and three hours later the midpoint is still soft. The manuscript did not get worse — your attention did. Passes fix that. Each pass has one question. Tools that jump you to the relevant scenes keep the question honest.
Search finds strings. Appearances find entities. Together they turn a 90,000-word haystack into a checklist.
Why “one more full read” fails
A full read is a reader experience. Revision needs a mechanic experience. On a full read you will:
- Fix surface prose before structure is stable
- Miss a subplot that went quiet for eighty pages
- Forget the POV rule you set in chapter four
Passes isolate failure modes. Structure first if needed — see the midpoint problem — then the passes below.
A pass you cannot finish in a week is not a pass. It is a second draft wearing a costume.
Pass 1 — Subplot payments
Job: Does every named plotline get paid?
Open each plotline (or colored thread). Use the plot grid or scene tags. For each beat that was promised, confirm a scene exists. Jump via links — do not rely on memory.
- Gap → outline one scene or cut the promise
- Pile-up → split turns across scenes
- Orphan color → merge or delete
Deep dive: tracking subplots without confusion.
Pass 2 — POV integrity
Job: Does every scene keep one camera?
If scenes are tagged with a POV character, filter or sort by that tag. Read only those scenes in order for one viewpoint. Ask:
- Knowledge the narrator should not have
- Emotional access that belongs to another head
- Accidental hops inside a scene
Search for the other characters’ interior verbs (“she realized,” “he knew”) inside a Mara-POV scene. Appearances on Mara’s card show every scene she owns — walk them like a beat sheet. More on immersion breaks: POV mistakes that break immersion.
Pass 3 — Continuity & naming
Job: Does the bible match the draft?
For each major character and location:
- Open the bible card (eye color, injury, allegiance, hook)
- Open appearances — jump scene to scene
- Search alternate spellings and nicknames
- Update the card or the prose; never leave them disagreeing
This is also when you merge duplicate cards. Series hygiene habits help: keeping a series bible clean.
Pass 4 — Voice & dialogue (optional, high leverage)
Job: Does each speaker sound like themselves?
Filter tagged dialogue / thought if you mark speech in the draft. Or search distinctive diction. One character per sitting. Bible traits stay open beside the editor. See dialogue that sounds like your character.
How to use search vs. appearances
| Tool | Best for | Weak at |
|---|---|---|
| Search | Exact strings, typos, banned words, alternate spellings | Pronouns, “she” scenes, renamed entities |
| Appearances | Every scene linked to a bible entity | Untagged mentions you never indexed |
Appearances only work if you tagged or linked entities while drafting — or if you invest one indexing pass before revision. That investment pays for every later pass.
A practical revision week
- Mon–Tue: Subplot pass (grid + missing beats)
- Wed–Thu: POV pass for primary and secondary viewpoints
- Fri: Continuity on the five messiest characters/locations
- Next week: Line polish only on scenes marked Revised
Statuses make this real — draft vs revise vs polish: from zero draft to readable manuscript.
What not to do
- Start a “style pass” before the midpoint turn exists
- Combine POV and subplot into one heroic weekend
- Trust Ctrl+F alone for characters who are mostly pronouns
- Polish chapters you might still cut
FAQ
How many passes does a novel need?
Three focused passes beat ten vague rereads. Add voice and line passes when structure and continuity hold.
Beta readers before or after?
After subplot and POV passes. Continuity can overlap with beta if you warn them you are still combing names.
Short fiction?
One continuity pass and one voice pass. Subplot grids are usually overkill.
Search and appearances in one studio
BlaezForge keeps manuscript search, story-bible appearances, plotlines, and scene statuses in one project — so each revision pass jumps to the scenes that matter instead of scrolling a single endless document.
Blaez