How do you track revisions in a manuscript?
- Microsoft Word’s Track Changes is the industry standard for editor handoff.
- Dated snapshots capture what was true at each handoff.
- Comments mark editorial questions; markup shows accepted changes.
- A revision log records what changed, when, and why.
- Never edit a snapshot — always make changes in the current file.
You track revisions by maintaining one current file with explicit change markers — track changes, comments, or version control — and dated snapshots of each major revision pass. The current file shows what is open; the snapshots show what was true at each editor or beta-reader handoff. Most working novelists use Word’s Track Changes or a version-controlled workspace.
Chapter i·Why it matters
Editors and writers communicate through revision marks. Without them, "I cut chapter three" is a sentence; with them, it is a documented action with a date and a rationale. Tracked revisions also let collaborators jump in halfway through a draft without re-reading the whole book to understand what has been decided.
Chapter ii·What to include
- Track Changes (or equivalent) for editor passes.
- Comments for "consider this" and "why did you do this" questions.
- Dated snapshots before and after each revision pass.
- A revision log: pass number, date, summary, who.
- A clean "accept-all" copy after each pass for your own reading.
- A "frozen" copy per editor that they can refer back to.
Chapter iii·Example
A debut novelist receives a developmental edit on her 92,000-word draft. The editor returns the file with Track Changes and forty comments. The author saves the marked-up version as draft-2-edit-marks-2026-03-15.docx, accepts and revises into draft-2-clean-2026-04-10.docx, and logs the revision pass with a one-line summary. No version doubt at any point.
WriteLoom’s Edit studio shows revisions with a clean diff against any snapshot, so editor passes don’t require comparing files by hand.
See the Edit studio