Somewhere in your drafts folder is a sentence you spent five minutes getting exactly right. The rhythm, the comma, the final clause turning at precisely the right moment. You were proud of it. A week later, the structure edit deleted the whole paragraph it lived in, and your five best minutes went with it.
Every writer does this, and it isn't a character flaw. It's a workflow flaw. Polishing early feels productive because small fixes are completable, and completability is what an anxious brain reaches for under uncertainty. Professionals separate editing into passes for the same reason surgeons separate procedures: each pass asks one question, and attention doesn't split cleanly.
This article walks one paragraph through all four passes so you can watch the changes happen. Steal the workflow whole, or steal the order, which is the part that matters.
The setup, and the specimen
Three things happen before pass one. The draft cools for at least a night, because you can't edit what you're still admiring. A working copy gets saved, because cuts feel safer when the original is recoverable. And you answer one question in writing: who is this for, and what should they do when they finish reading?
Then you meet the specimen. It's the opening paragraph of a 900-word company blog post about cancelling a weekly status meeting, and it has problems at every altitude, which is exactly what makes it useful:
One hundred and sixteen words, one sentence. The news, that the meeting is cancelled, arrives around word ninety. Let's take it down the mountain.
The structure pass
The question: does each section earn its place, in the right order? At paragraph scale, that becomes: where does the news live, and what is each clause doing here?
Reading for placement only, three things surface. The news is buried behind ninety words of history. The history itself is warm-up; it exists because the writer lived it, not because the reader needs it before the announcement. And "this post is going to explain why" is a signpost for a post that explains itself by existing. Delete the signpost, compress the history to a clause, promote the news to sentence one:
Last month we cancelled our weekly status meeting, because studies show that most meetings are a waste of time. The meeting had run since the company was six people in one room, and it had become an institution. But sitting in it week after week, we noticed something: it had become the place where information went to be filed rather than to move. Here is what we saw, and what we do instead.
Notice what the structure pass missed, on purpose: it promoted the "studies show" clause right along with the news, because promoting text is structure's job and judging it isn't. That's next.
The argument pass
The question: does every claim hold weight? Highlight the assertions and interrogate them one at a time.
"Studies show that most meetings are a waste of time." Which studies? Most meetings, measured how? That's borrowed confidence, and worse, it isn't even the post's real reason; the team has direct evidence of its own. Replace the borrowed claim with the specific arithmetic: twelve people, forty-five minutes a week, updates that were already written down before the meeting began. And "the place where information went to be filed" is a claim about the team's behavior, so support it with the behavior. The notes get read. The room doesn't.
Last month we cancelled our weekly status meeting. It had run since the company was six people in one room, and it had become an institution. But the arithmetic stopped supporting it: twelve of us were spending forty-five minutes a week hearing updates that had already been written down before the meeting started, updates most of the team then read in the notes rather than heard in the room. The meeting had become the place where information went to be filed rather than to move. Here is what we do instead.
The word count went up. That's normal, and it's the sign of a healthy argument pass: evidence gets added even as the throat-clearing disappears. This is not a cutting pass.
The line pass
The question: do the sentences work? Now, finally, the prose itself.
Read the argument-pass version aloud and the flaws announce themselves. The "had run, had become, had become" chain of past perfects. A third sentence doing two jobs at once. The strongest observation, the filing-cabinet one, is buried at the end of a long sentence when it deserves a short one of its own. Fix the rhythm: split the arithmetic from the interpretation, and let the buildup land on a picture.
Last month we cancelled our weekly status meeting. It ran on tradition; it had survived since the company was six people in one room. But the arithmetic stopped supporting it. Twelve of us spent forty-five minutes a week hearing updates that were already written down. Most of the team read the notes and skipped the room. The meeting had become a filing cabinet with chairs. Here is what we do instead.
Sentence lengths now run 8, 16, 6, 15, 11, 9, and 6. That contrast is the whole secret of sentence rhythm: variety, not uniform quality. A readability checker will report that the average barely moved, which is fine. The average was never the problem.
The polish pass
The question: is everything clean and consistent? The prose is done moving, so now the small stuff, and this is where tools earn their keep.
Run the paragraph through a grammar checker for agreement and tense slips. Then do the consistency sweep, which tools only partly cover. Elsewhere the post says "organize" and "favorite," American spellings, so "cancelled" becomes "canceled"; if that pair has never crossed your mind, our guide to British versus American spelling will save you an inconsistent draft. The number policy says words under ten, numerals above, so "twelve of us" stays and the "40 people" later in the post stays. A double space after "room," a souvenir of an earlier edit, gets collapsed.
Last month we canceled our weekly status meeting. It ran on tradition; it had survived since the company was six people in one room. But the arithmetic stopped supporting it. Twelve of us spent forty-five minutes a week hearing updates that were already written down. Most of the team read the notes and skipped the room. The meeting had become a filing cabinet with chairs. Here is what we do instead.
One word changed, one space collapsed, and the paragraph is finished. The polish pass is small when it goes last. Run it first, and you'll do this work four more times as the passes above keep moving the sentences around.
Time budgets and tools for each pass
Your numbers will differ with genre and experience, but a rough budget per thousand words keeps a pass from swallowing a day:
| Pass | The one question | Rough time per 1,000 words | Tool that earns its keep |
|---|---|---|---|
| Structure | Does each section earn its place? | 15 to 25 minutes | word counter, for section lengths |
| Argument | Does every claim hold weight? | 20 to 30 minutes | None. This pass is judgment. |
| Line | Do the sentences work? | 30 to 45 minutes | readability checker, find-and-replace for filler hunts |
| Polish | Is everything clean and consistent? | 10 to 15 minutes | grammar checker, spelling checker |
The line pass is the longest because it touches every sentence. The polish pass is the shortest because everything before it kept the mess from arriving. If your polish passes keep running long, the diagnosis is that they're absorbing the line pass, and the cure is re-sequencing, not working harder.
Frequently Asked Questions
Can I run the passes in one long session?
You can, for short pieces, but expect each pass after the first to be weaker, because the passes need different kinds of attention and attention fades within a session. If one sitting is all you have, at least take a real break between passes and change something: the font, the room, the chair.
How is this different from how publishing splits editing?
Publishing separates developmental editing, line editing, copyediting, and proofreading as jobs done by different people. The solo writer merges the roles but not the passes; the four passes here are the same altitude discipline scaled to one person. The editing versus proofreading guide maps the professional levels in detail.
What if a pass reveals the structure was wrong all along?
Then the system is working. A structure pass that exposes a deeper structural problem sends you back to the top with better information, and re-running pass one on the reshaped draft is normal. Long projects loop. The passes keep each loop cheap by confining the damage.
Does drafting get its own pass?
No, drafting is the thing being passed over. The one rule during drafting is to edit only forward, never backward. Beating writer's block is partly about refusing to reread yesterday's sentences, and this workflow is the container that makes that refusal safe.
How do I know when to stop?
When a pass produces almost no changes, the document is done at that altitude. One full cycle of four passes plus a final read-aloud covers most work. A second full cycle is for manuscripts and anything with your name on the cover.
The rule the whole workflow serves
Every pass asks a smaller question than the one before it, and that order is the entire method. Big questions first, small questions last, one question at a time. Run your next draft through all four, in order, with a rest between each; the self-editing checklist has the questions ready if you want them in copyable form.