Last month a friend printed her 2,000-word article, uncapped a red pen, and started fixing things at the top. Page one needed a comma. Page two had an introduction that didn't fit, so she rewrote it. The new introduction promised something the middle never delivered, so she patched the middle, which broke a transition, which sent her back to page one. Three hours in, she called me. She had a shredded first page and had never once looked at pages five through nine.
She wasn't careless. She was doing four jobs at once, and every job kept undoing the others.
The fix isn't willpower or a longer list of checks. It's running the same checks in the right order, one kind of problem at a time. That is what this checklist does: four passes down the page, each answerable in a single sitting.
Why the order matters more than the list
Most self-editing checklists fail for a boring reason: they're one giant undifferentiated list, followed in whatever order your eye lands. The chaos is where the process breaks.
Editing problems live at different altitudes, and the altitude decides the sequence. Cut a section during the structure pass, and every sentence you would have polished inside it is effort saved. Polish first, and that same cut throws the work away. Professional editors keep editing and proofreading separate for exactly this reason: merged passes are slower and worse, not faster and cheaper.
The four passes, in order:
- Structure. Does each section earn its place?
- Argument. Do the claims hold up?
- Line. Do the sentences work?
- Polish. Is everything clean and consistent?
Give each pass its own sitting, with a night between when you can manage it. The rest isn't sentimentality; it's the difference between reading the draft and remembering it, and you can only notice problems in the one you're reading.
Pass one: structure
The structure pass asks one question: does this section earn its place? Notice what it doesn't ask. Not "is it well written." The well-written section that serves no purpose is the hardest cut there is.
The margin summary. Read the whole draft without fixing anything, writing a one-line summary beside each section. Two adjacent summaries saying the same thing mean two sections doing one job. A summary you struggle to write means the section has no job, and a summary that surprises you has found your first cut.
The promise test. Underline the sentence where the piece tells the reader what it's about. Every section after it either pays that promise off or wanders off the property. This is also why a vague opening paragraph is an editing problem in disguise: when the promise is fuzzy, every section looks like it fits.
The shuffle test. Ask whether the piece improves if section three goes first, because drafts solve problems in the writer's order, rarely the reader's. A piece that spends 600 words warming up needs its point moved to the top and the warm-up compressed to two sentences. Paragraph order is cheap to fix when you aren't also fixing commas.
Pass two: argument
Structure asks where things are. The argument pass asks whether they hold weight. Read for claims and evidence only, ignoring style so completely that an ugly sentence passes without comment.
Give every claim its evidence. Highlight each sentence asserting something: "the process fails under load," "readers scan before they read." Every highlighted claim needs a reason, an example, or a source behind it. A claim with none of the three is an opinion in a fact's clothing, and readers can tell.
Run the "so what" test. At the end of each section, ask what changes for a reader who believed it. Sections that pass demonstrate their own importance. Sections that fail were written for your sense of completeness, and completeness is not a reader need.
Audit the hedges. "Arguably." "Perhaps." "Probably the best." "One of the most." Find them one by one and decide whether the claim stands without the cushion. A claim that collapses when you remove "arguably" was never standing. When something is genuinely uncertain, say so plainly and say what would settle it; readers forgive that far more readily than confidence they can hear wobbling.
Pass three: the line
Now the sentences. This is where rhythm gets fixed and where most of the cutting happens, because a draft can be structurally sound and still flabby.
Read it aloud. The ear catches what the eye forgives: sentences that refuse to end, accidental rhymes in the cadence, same-length sentences landing like a metronome. Running out of breath is the body's way of requesting a period.
Interrogate the longest sentences. A readability checker will list them for you. Some long sentences earn their length by doing one job with room to breathe. More often, a long sentence is three sentences holding hands, and each would be stronger alone. Rhythm comes from variety, and sentence length is the raw material of rhythm.
Hunt filler. "Very," "really," "in order to," "due to the fact that." A focused hunt pays off immediately; our catalog of filler words to cut lists thirty with before-and-after rewrites.
Pass four: polish
Typos, formatting, consistency: the small stuff, which is why it goes last. It's also the only pass where automated tools do real work: a grammar checker catches the agreement errors you've gone blind to, and a final word count tells you whether the piece landed where you aimed.
Consistency beats correctness here. Choose "email" over "e-mail" and hold the line. Pick a number style and apply it everywhere. A piece with consistent unconventional choices reads as intentional. A piece with mixed correct ones reads as careless.
The polish pass also sweeps formatting debris: double spaces, headings that jump from H2 to H4. And it's the last defense against the typos that survive repeated readings, which is a separate problem with its own bag of tricks.
The whole checklist in one table
| Pass | Core question | Quick tests | Typical cuts |
|---|---|---|---|
| 1. Structure | Does each section earn its place? | Margin summaries, promise test, shuffle test | Whole sections, duplicated points, warm-up paragraphs |
| 2. Argument | Do the claims hold up? | Claim highlighting, "so what" test, hedge audit | Unsupported assertions, borrowed confidence, unearned superlatives |
| 3. Line | Do the sentences work? | Read aloud, longest-sentence audit, filler hunt | Filler words, throat-clearing openers, tangled clauses |
| 4. Polish | Is everything clean and consistent? | Tool pass, error log, formatting sweep | Typos, mixed conventions, stray formatting |
Copy the table into the top of your draft as a scratchpad and tick each pass as you finish it. The tick marks matter more than they look: editing fatigue is real, and the visible record of a finished pass stops you re-running it out of anxiety.
One honest caveat: the table compresses a lot of judgment into four rows. The hard part of editing isn't noticing problems; it's deciding that the section you loved on Monday is the one that has to go. The passes make that decision final, so you make it once.
Frequently Asked Questions
How many editing rounds does a draft need?
Four structured passes plus one final read-through is plenty for articles, essays, and most business writing. Past that, diminishing returns set in, and the piece needs readers more than it needs you. If it still feels wrong after a full cycle, the problem is structural: run another structure pass, not more polish.
Should I edit on screen or on paper?
Structure and argument passes work well on paper, because the slow medium discourages fiddling with sentences you shouldn't be touching yet. Line and polish passes belong on screen, where the tools live. The hybrid is the point: change something between passes so the text stops feeling like furniture.
How long should each pass take?
The line pass usually runs longest, because it touches every sentence. The polish pass should be quick, and if it isn't, the mess got pushed downhill from earlier passes. For a worked-out budget, the four-pass editing workflow attaches minutes to each pass.
What if I only have time for one pass?
Run the structure pass. A well-organized piece with rough sentences beats a polished shambles every time, and readers forgive clunky phrasing far more readily than they forgive not knowing why they're reading.
The one rule to keep
If everything else evaporates, keep this: never fix a sentence you haven't decided to keep. Every pass in the checklist exists to enforce that order, big questions before small ones. Run it on your next draft, one pass per sitting, and notice how much editing time stops being wasted.