What a Developmental Editor Looks For
The big-picture issues a structural edit evaluates — and what software can and can't do.
What a developmental editor evaluates
A developmental edit is an examination of your manuscript's structural and narrative foundations. The editor reads the full manuscript and delivers a report — typically 10 to 20 pages — covering the major elements of craft.
- Pacing
- Is the story moving at the right speed? Are there stretches where nothing happens? Are action sequences so compressed that the reader can't breathe? Pacing isn't just about speed — it's about variation. A thriller that runs at full speed for 300 pages is as exhausting as a literary novel that meanders for 300 pages. A developmental editor identifies where the pacing works, where it stalls, and where it rushes past moments that need room to land.
- Character arcs
- Do your characters change? Is the change earned? A developmental editor tracks each major character's emotional trajectory across the full manuscript. They'll notice if your protagonist's transformation happens too abruptly, if a secondary character is more compelling than your lead, or if a character's motivations shift without explanation between chapters.
- Plot structure
- Does the story have a clear dramatic question? Does it build toward a climax? Are the turning points in the right places? A developmental editor evaluates whether the structural bones of your plot support the story you're trying to tell. This includes subplot management — tracking which threads are active, which have been dropped, and which resolve too neatly or too abruptly.
- Theme and motif
- What is your book about, beneath the plot? A developmental editor identifies the thematic threads running through your manuscript and tells you whether they're consistent, contradictory, or underdeveloped. They'll notice if a theme you introduced in Act One never pays off, or if competing themes are diluting each other.
- Point of view
- Is the POV consistent? Are head-hops distracting? In multi-POV novels, is each perspective earning its place? A developmental editor evaluates whether your POV choices serve the story and whether the execution is clean.
- Emotional beats
- Does the reader feel what you want them to feel, when you want them to feel it? This is one of the subtlest and most important things a developmental editor assesses. They'll identify scenes that should be emotional but land flat, moments where the emotional register doesn't match the content, and places where you're telling the reader how to feel instead of creating the conditions for them to feel it.
- Continuity
- Do the details hold up across 300 pages? Timeline consistency, character descriptions, world rules, seasonal references, geographical accuracy — a developmental editor catches the things you've lost track of after months of revision. The character who was left-handed in Chapter 3 and right-handed in Chapter 20. The road trip that takes two hours in one scene and six hours in another.
What software can't do
The limitations matter as much as the capabilities, and being honest about them is important.
- Subjective quality
- Software can tell you that a scene is slow. It can't tell you whether that slowness is a flaw or a deliberate, effective choice. A quiet scene after a major revelation might be exactly what the reader needs. Only a human editor — one who understands pacing as an art, not just a metric — can make that judgment.
- Emotional resonance
- Software can identify scenes with high emotional language. It can't tell you whether those scenes actually make a reader feel something. The difference between a scene that describes sadness and a scene that evokes sadness is one of the most important distinctions in fiction, and it's entirely beyond what an algorithm can assess.
- Market awareness
- A developmental editor brings knowledge of genre conventions, reader expectations, and what's working in the current market. They know that the pacing expectations for a cozy mystery are different from a psychological thriller. Software analyzes text; it doesn't read books for pleasure or track market trends.
- Creative judgment
- "This subplot isn't working" is something software might flag based on structural data. "Here's what would make it work" requires creative insight that only a human editor can provide. Software can identify problems; it generally can't propose solutions that require narrative imagination.
When you still need a human editor
Always, if you can afford one.
Software is a tool for self-diagnosis. A developmental editor is a creative partner. They bring experience across hundreds of manuscripts, an understanding of what makes stories work at an emotional level, and the ability to articulate problems and solutions in ways that help you grow as a writer.
If your budget allows a developmental edit, get one. Use software to prepare your manuscript first so you get the most value from every dollar you spend on human editing. If your budget doesn't allow an editor right now, structural analysis software gives you a level of insight into your own manuscript that simply wasn't available to authors five years ago.
The goal isn't to replace editors. The goal is to make sure no author has to publish a book with structural problems they didn't know about, simply because they couldn't afford someone to point them out.