Self-editing has a bad reputation it half deserves. You cannot replace an editor, because you cannot read your own book for the first time. What you can do is arrive at the editor with a manuscript that is worth their fee, which roughly halves what you pay and doubles what you get back.
Why one pass fails
Because the four jobs use different attention and they interfere. Reading for structure means holding the whole book in your head; reading for commas means holding one line. Trying both at once produces the familiar experience of spending an afternoon on chapter two and having no idea whether the book works.
| Pass | Question | Unit | Do it |
|---|---|---|---|
| Structural | Is this the right book? | The whole thing | Once, before anything else |
| Section | Does each part earn its place? | Chapter or scene | Chapter by chapter |
| Line | Is every sentence doing work? | Paragraph | Slowly, in sittings |
| Proof | Is anything wrong? | The word | Last, and ideally not you |
Before the first pass: put it down
Two to four weeks, not touched. This is the only technique on the page that reliably lets you read your own work as text rather than as memory, and it is the one people skip because it feels like doing nothing.
Then change how it looks before you read it. Export the PDF and read it on a tablet or on paper rather than in the editor you wrote it in. The same words in a different setting are startlingly easier to see — which is one practical argument for a manuscript that exports in one step, because a reading copy should cost you nothing to produce: Markdown to PDF.
Pass one: structure
Read the whole thing in as few sittings as possible, with a notebook, and change nothing in the manuscript. The rule for this pass is absolute: notes only. The moment you start fixing, you stop reading the book and start reading a paragraph.
- Write a one-line summary of every chapter as you go. Chapters you cannot summarise in a line are chapters that are doing two things or nothing.
- Mark where you got bored. Trust it. If you are bored by your own book, a stranger left three pages earlier.
- Look for the real beginning. Non-fiction usually starts one or two chapters later than the draft does; fiction often starts a scene later.
- Check the order against the summaries. Written as a list, the wrong sequence is obvious in a way it never is while reading.
- Find the missing chapter. Almost every non-fiction draft has one thing the reader needs that the author knew and never wrote down.
- Count the repeats. Ideas stated three times in three chapters are one idea in the wrong place.
The output of this pass is a list of moves, cuts and gaps — not a better manuscript. Then make those changes, all of them, before reading again. How long should a chapter be is a useful check while the summaries are in front of you.
Pass two: section by section
Now the book is the right shape. This pass asks whether each chapter earns its place, and it is the one that removes the most words.
- Read the first and last paragraph of each chapter, back to back. If they say the same thing, the chapter went nowhere.
- Delete the run-up. Most chapters start with half a page of throat-clearing before the point. Cut until the first sentence is the point.
- Cut the summary at the end unless the chapter was genuinely complex. Readers do not need to be told what they just read.
- One example, not three. Three examples of the same idea is one example and two paragraphs of padding.
- Move the best line to the front. It is almost always buried in the middle of the third paragraph.
Pass three: line by line
Slow, and best done in short sittings — an hour at a time, a chapter at a time. This is where prose stops being competent and starts being readable.
| Hunt for | Fix | How to find it |
|---|---|---|
| Filter words | "She saw the door open" → "The door opened" | Search: saw, felt, noticed, realised, seemed |
| Hedges | Delete them | Search: very, quite, rather, somewhat, just, really |
| "There is / there are" | Rewrite with a real subject | Search the phrase |
| Passive voice | Only where the actor matters | Search: was, were, been, being |
| Adverbs propping up verbs | A stronger verb | Search: ly |
| Repeated sentence openings | Vary them | Read a page aloud |
| Paragraphs of identical length | Break the rhythm | Look at the page, do not read it |
And read it aloud. Not as a metaphor — actually out loud, whole chapters. It is the fastest way to find a sentence that cannot be spoken in one breath, and it catches things no search will: the clause that doubles back, the rhythm that flattens, the word used twice in a line.
Pass four: the proofread
The one you are worst at, on your own work, for a reason that has nothing to do with skill: you read what you meant. Do it anyway, then pay somebody, because this is the cheapest professional pass and the one whose absence is most visible in a review.
- Change the setting again. New typeface, new size, or read it backwards paragraph by paragraph.
- Have it read to you. Any device will do it, and a text-to-speech pass finds missing and doubled words instantly.
- Check the things that are not prose: chapter numbers in sequence, the contents matching the headings, cross-references, image captions, every URL actually opening.
- Check the mechanical layer the export produces — widows and orphans, smart quotes and dashes, and whether any heading is stranded at the foot of a page.
- Then hire a proofreader. $300–$1,200 depending on length, and the best money in the whole budget: what it costs to self-publish.
What plain text does for this
Two things, both practical. Search-and-replace across the whole book is one operation rather than a word processor's crawl through a hundred-page document, which is what makes the line-pass hunts above actually usable. And a manuscript in version control gives you a diff — you can see exactly what changed between passes, and get back the paragraph you cut on Tuesday and want on Thursday.
The other thing worth doing between passes: re-export. Reading pass two in a fresh PDF, properly set, is a different experience from reading it in the editor, and finding the structural problem is easier when the book looks like a book. Writing a book in VS Code covers the setup; the editing benefit is the underrated half of it.
What you still cannot do
Be honest about this, because the whole point of the four passes is to spend your editing budget on what is left.
- Read it for the first time. No technique replaces this. A developmental editor or two sharp early readers are the only route to the note you cannot generate.
- See your own habitual tic. Everyone has one — a construction used four hundred times, invisible to its author.
- Judge whether the argument holds for somebody who does not already agree with you.
- Proofread reliably. You will find most of them. Most is not enough at the length of a book.
Which gives you the budget question in a usable form: if you can afford one professional pass, buy the proofread. If you can afford two, add a developmental read at the outline or first-draft stage, where its notes are cheapest to act on. Everything between those two is what the four passes above are for.