The Structural Pass

The instinct when you finish a draft is to open to page one and start fixing sentences. Resist it. Line-editing a scene that gets cut in the next pass is wasted work, and in a first draft, entire scenes get cut.

Revise in the right order

Structure first, then scenes, then sentences. A structural pass asks whether the story itself works before you spend a single minute polishing how it's written. Fixing commas in a chapter that shouldn't exist is effort in the wrong place.

How to actually do it

Reread the whole draft as fast as you can manage, ideally in a handful of days rather than weeks, so you can hold the shape of the whole thing in your head at once. Take one line of notes per chapter — a single sentence on what it's doing — and do not stop to fix anything. Editing while you reread is how structural problems hide behind sentence-level ones.

Three questions per chapter

Does this chapter still have the small goal it needs, the one from Chapters That Don't Sag, and does it resolve by the end? Do every character's actions here still make sense, or did an earlier revision change their motivation without you updating this scene to match? And does this chapter pay off something you promised the reader earlier, or set up something you'll actually deliver later? A chapter that fails all three isn't a chapter that needs better sentences. It's a chapter that needs to change shape, move, or go.

Flag, don't fix

Mark the chapters that don't earn their place and move on without touching them yet. You're mapping the problems in this pass, not solving them one at a time as you find them — fix the whole structure once you can see it all, then let the sentence-level polish come last, once you know which sentences will actually survive.