Most first-time authors revise by starting at page one and fixing whatever they notice. Six weeks later they have beautiful sentences in chapter two and a structural problem in chapter nineteen that means chapter two is getting deleted.
Revision has an order, and the order is the whole trick: big to small, always. Never polish a sentence that might not survive.
The five passes
1. Developmental edit (the story)
Is this the right book? Does the premise hold? Is the protagonist's arc real? Does the ending pay off the opening?
This is the pass that changes what the book is about. It is also the one most writers skip, because it is the only one where the answer might be "this needs rewriting from chapter one".
Do this with a printed outline, not the manuscript. Write a one-line summary of each chapter, lay them out, and look at the shape rather than the prose. Story structure gives you something to check against.
2. Structural edit (the arrangement)
Same content, better order. Are chapters in the right sequence? Is the opening in the right place? Should these two characters be one character? Is the subplot in chapter seven earning its space?
This is where most books get meaningfully better. Merging two thin characters into one interesting one, cutting a POV, and moving the opening chapter to chapter four are all standard fixes and all feel drastic the first time.
Deletion is the main tool. If a scene, a subplot or a character can be removed without breaking anything, that is not evidence it is harmless. It is evidence it is doing nothing.
3. Line edit (the prose)
Now sentences. Rhythm, clarity, voice, word choice, whether the paragraph lands. This is the craft pass, and it is where show don't tell, dialogue and pacing get fixed at the line.
The reliable line-edit moves:
- Cut the first and last sentence of most scenes. They are throat-clearing and summary.
- Delete filter words: felt, saw, heard, noticed, realized, thought. "She heard the door open" is weaker than "The door opened."
- Kill adverbs propping up weak verbs.
- Read dialogue aloud. Every unnatural line will announce itself.
- Vary sentence length on purpose. Uniform sentence length is the most common reason competent prose reads flat.
4. Copy edit (correctness and consistency)
Grammar, punctuation, tense consistency, spelling conventions, and continuity: eye colour, timeline, character names, whether the city was four days away in chapter two and overnight in chapter nine.
Continuity errors are the ones readers actually write reviews about. A dedicated continuity pass with a list of your own facts is worth more than another read-through.
5. Proofread (the last look)
Typos, formatting, spacing, chapter headings, the page numbers. This happens after formatting, on the exported file, because formatting introduces its own errors.
Why the order is non-negotiable
Every pass invalidates work from later passes. Line-editing before the structural pass means polishing prose you are about to cut, which is both a waste of weeks and, worse, a reason to keep bad chapters. Writers protect sentences they have worked hard on, and that is how structurally broken books get published.
The rest between passes
Put the draft away for at least two weeks between finishing it and starting the developmental edit. Four is better. You cannot see your own book while it is still in your head, and the gap is doing real work, not procrastination.
What to do yourself and what to pay for
Do yourself: the developmental and structural passes. You know your book better than any editor will, and the questions are answerable if you are honest.
Worth paying for, roughly in order of value per pound: a copy edit, then a proofread, then a line edit, then a developmental edit. That ordering surprises people, but errors are objective and cheap to fix, while a developmental edit is expensive and only as good as the fit between you and the editor.
Beta readers are not editors. They cannot tell you why something is wrong and they are not supposed to. What they can tell you, accurately, is where they got bored and where they were confused. Ask for that specifically and ignore their suggested fixes.
If you hire, ask for a sample edit of a few pages before committing, get the deliverables and the deadline in writing, and be suspicious of anyone who guarantees an outcome.
Doing this in BookZeta
Two features do most of the practical work here.
Version history on every chapter means the structural pass is not frightening. You can cut, merge and reorder aggressively knowing you can restore an earlier save of any chapter. Most under-revised books are under-revised because the author was afraid of losing something.
Alternate drafts are the right tool for a big rewrite. Create a full branch of the project, rework the second half in it, and compare the two versions properly instead of destroying the original to find out whether the new idea was better. Merge it back if it wins, delete it if it does not.
For the line pass, the AI writing assistant is useful in a specific and limited way. Select a paragraph and use Shorten to see what it looks like tightened, or Rewrite to see an alternative rhythm. Take the diagnosis, not the output. The value is noticing that four of your sentences started the same way, not accepting a machine's version of your voice.
What it will not do is the developmental pass. Nothing can tell you whether the book is about the right thing.
Then, when the manuscript is done, how to self-publish a book picks up from there.
