Revision in Writer Mode has three tools behind it: version history for single chapters, alternate drafts for whole-project experiments, and the AI assistant for line work. Using the right one for the right size of change is most of the skill.

The order matters more than the tools. Big to small, always: story, then arrangement, then sentences, then correctness. Never polish a chapter that might get cut. How to revise a novel covers the five passes in detail.

Before you start

Put the draft away for at least two weeks. You cannot see your own book while it is still in your head, and no tool substitutes for the gap.

Then read it once without fixing anything, taking notes. The temptation to start editing on page one is what produces beautifully polished chapters that get deleted in week six.

The structural pass

This is where books get meaningfully better, and it is the pass people skip because it feels destructive.

Work from your chapter list rather than the manuscript. For each chapter write one line: who wants what, and what stops them. Chapters where you cannot answer are candidates for cutting or merging. Then look at the shape of the whole list rather than the quality of the prose.

Version history makes this safe. Every chapter keeps its own saved versions, and you can view and restore an earlier one. Cut aggressively. If you were wrong, it comes back.

Alternate drafts are for anything bigger than a chapter. Reworking the second half, changing a POV, trying a different ending: create a full branch of the project and do it there. The draft is a complete, independent copy including chapters, assets and images, so the original is untouched while you find out whether the new version is better. Merge it back if it wins, delete it if it does not.

Doing a major rewrite in place, with no branch, is the reason a lot of second drafts end up worse than the first and unrecoverable.

The line pass

Now sentences. The assistant is genuinely useful here in a specific way: as a diagnostic, not a replacement.

Shorten on a slow paragraph shows you what was carrying it. You do not have to keep the result. Seeing your paragraph at 60% length tells you which 40% was padding.

Rewrite on a passage that is not landing gives you an alternative rhythm to compare against. Take the insight, write your own version. Accepting the output verbatim is how a draft loses its voice, which Keeping your own voice covers properly.

Expand is for thin scenes, particularly ones where you named an emotion instead of showing it. Then cut the named emotion, because it will usually leave both in.

Manual line edits that repay the time:

• Cut the first and last sentence of most scenes.
• Delete filter words: felt, saw, heard, noticed, realized, thought.
• Read dialogue aloud. Every unnatural line announces itself.
• Delete any sentence explaining the sentence before it.

The continuity pass

Do this separately, with a list rather than by reading. Continuity errors are the ones readers write reviews about.

Check names and spellings, physical descriptions, the timeline, how long journeys take, ages, and who knew what at which point. If your book is part of a series, check every fact against the Series Bible rather than against your memory of book one.

Character status in the Bible is the guardrail that catches the worst class of error: somebody reappearing after they should not.

The proofread

Last, and on the exported file rather than in the editor, because formatting introduces its own errors. Export to EPUB or PDF and read it on a device.

Reading your own book in a different format is also the most reliable way to find pacing problems. You will skim. Wherever you skim is a cut.

What the tools will not do

Nothing can tell you whether the book is about the right thing, whether the ending pays off the opening, or whether the protagonist changes. That is the developmental pass, it is the one that matters most, and it is yours.

Beta readers are useful for exactly two questions: where did you get bored, and where were you confused. Ask for those specifically and ignore the suggested fixes.