First-draft revision guide
Revise the story before polishing every sentence.
A revision pass needs a question and an end condition. Separate structural decisions from sentence-level edits so you do not spend days polishing a scene you later remove.
Rereading from page one and changing anything that catches your eye can produce a cleaner opening without solving the book. Start by deciding what kind of problem you are looking for.
Protect the draft and make a reverse outline
Save a dated backup of the whole project before beginning. A chapter snapshot is useful for a local change, but it is not a substitute for an independent backup of the book vault. Keep the unedited first draft identifiable.
Summarize each existing scene in one sentence: who wants what, what blocks them, and what changes. Record what the scene actually does rather than what the outline originally intended. For The Lantern Archive, “Elara visits the Archive” is less useful than “Elara gains entry by giving Rowan a reason to distrust her.”
Mark scenes with no consequential change. Do not delete them immediately: first ask whether the book needs the information or emotional movement and whether it belongs elsewhere.
Try it with your own story
Keep a protected draft before editing.
Work from structure to local consequences
Choose one structural question, such as whether the central choice is clear or the middle increases pressure. Map the scenes that support it, then decide what must move, expand, combine, or disappear. Avoid a sentence-editing detour while those decisions remain open.
After moving a scene, inspect the joins. Check knowledge, travel, time, possessions, and relationship state in the neighboring chapters. Keep a review note when a change depends on a decision you have not yet made.
Scriptorum’s snapshots, passage-anchored notes and deliberate tracked-change sessions support different revision jobs. Choose the lightest tool that lets you understand and undo your own decision. Do not treat an unresolved note as a change already applied.
Try it with your own story
Describe the effect of the scenes you actually wrote.
Make a prose pass with a defined finish
Once the sequence works, choose a prose goal: clearer viewpoint, less repetition, more precise action, or a consistent narrative distance. Work through the manuscript with that question rather than asking every sentence to solve every problem at once.
Export a reading copy and inspect it away from the editing context. DOCX is useful for editorial changes; PDF gives stable pages; EPUB lets you test a reflowable reading experience. Check the actual output rather than assuming the editor view and exported layout are identical.
End the pass when its checklist is satisfied. Put new structural concerns into a separate list and decide whether they justify another pass. Revision should produce a clearer book, not an indefinite queue of cosmetic changes.
Try it with your own story
Review a file in the format its next reader will use.
Common questions
Useful things to know.
Should I turn on tracked changes for every draft?
Not necessarily. Use backups and snapshots for draft boundaries, notes for questions, and tracked changes when you deliberately want to review individual edits.
Plan. Write. Publish.
Give your story a workspace.
Scriptorum for Windows 10 & 11. A one-time purchase for up to three personal devices. Activate online, then write offline.
Questions before you buy? →One-time purchase. A perpetual license for the version you buy, on up to 3 personal devices.
Applicable taxes calculated at checkout.Checkout is handled by Stripe/Link for Mayfly Creative Studios LLC. Your license key and installer link arrive by email.
Refunds and purchase terms ↗