There's a particular kind of revision pain that comes from spending two weeks tightening prose in a chapter you eventually cut. You sharpen every sentence, nail the rhythm, get the dialogue snapping, and then realize the whole chapter is doing the wrong job. That's not a line-editing failure. That's what happens when you skip structural revision.
The order matters more than most writing advice admits. Developmental editing, whether you hire someone or do it yourself, always comes before line editing. Structure before sentences. Every time.
Why Structure Must Come Before Sentence-Level Edits
Line editing is expensive, time-consuming, and emotionally draining. It demands a different kind of attention than drafting: slow, granular, almost musical. You don't want to spend that energy on material that might move, shrink, or disappear.
Structural problems don't get fixed by better prose. A chapter that arrives too early in the story will still arrive too early, no matter how elegantly it's written. A subplot that never pays off will still feel hollow after you've polished every paragraph. Big-picture revision catches those problems first, so your line edits land on stable ground.
Think of structural revision as triage. You're not making things pretty; you're making sure the right things are in the right places, doing the right work.
Step 1: Evaluate Your Narrative Arc
Before anything else, read your draft for shape. Not sentences, not scenes, just the overall arc. Ask yourself:
- Does the story open with a situation that creates genuine forward pressure?
- Is there a clear midpoint shift that raises the stakes or reframes the central conflict?
- Does the climax actually resolve what the story set up, or does it resolve something adjacent?
- Is the ending earned by what came before it, or does it arrive by authorial convenience?
If you can't answer those questions from memory after reading, your arc probably needs work before anything else does.
One practical move: write a one-paragraph summary of your novel as it currently exists, not as you intended it. What actually happens, in order, at the level of major events. If that summary feels wobbly or vague, that's your diagnostic.
Step 2: Check Chapter and Scene Logic
Once the arc holds, zoom in one level. Every chapter and every scene needs a reason to exist in the specific position it occupies. This is where a lot of structural revision checklist work gets done.
For each chapter, ask: what changes between the first page and the last? If nothing changes, the chapter is probably stalling. For each scene, ask: whose goal drives this scene, what opposes it, and what's the outcome? A scene that can't answer those three questions in a sentence or two is usually either doing too little or doing the wrong thing entirely.
This is also where you catch sequencing problems. A revelation that lands in chapter twelve might need to move to chapter eight because the reader needs that information to understand what's happening in chapters nine through eleven. You can't see that problem at the sentence level.
Step 3: Audit Pacing and Transitions
Pacing is structural, not stylistic. A slow chapter isn't slow because the sentences are long; it's slow because the scene has no tension, or because three scenes in a row all end with the protagonist retreating and regrouping. The fix is structural: cut a scene, raise the stakes in another, or reorder so that pressure and release alternate rather than stack.
Transitions between chapters and sections deserve specific attention during structural revision. Ask whether the reader has enough context to follow the jump, and whether the jump creates momentum or interrupts it. A jarring transition might mean two scenes need a bridge; it might also mean one of them belongs somewhere else.
Step 4: Confirm Each Scene's Purpose Before You Polish
This is the last structural gate before line edits. Go scene by scene and confirm that each one is doing at least one of the following: advancing plot, deepening character, building tension, or delivering information the reader needs. Ideally two of those. A scene doing none of them is a candidate for cutting or merging, regardless of how well it's written.
This is also where subplots get audited. Does the subplot connect to the main conflict thematically or causally? Does it resolve, or does it just stop? If it stops, that's a structural gap, and no amount of line editing will fill it.
A note on using Nexa during structural revision: If you're working on Writing Nexus, Nexa is the in-app story coach built for exactly this stage. She's not a ghostwriter; she works more like a developmental editor in your corner. You can bring her your plot outline, a scene you're unsure about, or a question like "does my act two actually build toward my climax?" and she'll work through the structure with you, ask the right questions, and offer specific suggestions based on your actual project. During structural revision, that kind of targeted feedback is more useful than general advice, because the problems are always specific to your story. She can also help you draft a one-paragraph arc summary, which is one of the most clarifying exercises in this whole process.
When You're Ready to Move to Line Edits
You're ready when you can say, with some confidence: the arc holds, every chapter earns its position, the pacing creates forward pressure, and no scene is doing nothing. You don't need perfection at the structural level, but you need stability. Shaky foundations don't improve under decoration.
Once the structure is solid, line editing becomes a pleasure rather than a trap. You're refining something that works, not propping up something that doesn't.
If you're mid-draft or staring down a finished first draft that needs serious revision, start your structural pass on Writing Nexus. Nexa can work through the big-picture questions with you before you touch a single sentence.
