What Does a Developmental Editor Actually Look For?

You know you need developmental editing. You've probably already looked at what it costs and felt that familiar tightening in your chest. But here's a question that doesn't get asked enough... what exactly are they LOOKING for when they read your manuscript?

Because "big-picture feedback" is vague. "Structural issues" is vague. And if you're going to spend $3,000 to $5,000 on an editorial letter, you should know what you're paying for. More importantly, if you're going to self-edit before sending it out (and you should), you need to know what to look for yourself.

So let's walk through the actual craft dimensions a developmental editor evaluates. The vocabulary here matters. Once you know these terms, you can talk to editors, critique partners, and alpha readers with real precision instead of gesturing at "something feels off in the middle."

Plot structure

This is the skeleton. A developmental editor looks at whether your story has a discernible shape... whether the major turning points land where they should, whether the inciting incident actually incites something, whether the climax pays off what the setup promised.

Craft frameworks call this the "quest" structure. Does your protagonist want something specific enough to drive two hundred pages of story? Does the pressure escalate? Are there genuine reversals, or does the plot just... proceed?

Most first drafts have a plot. Fewer have a plot STRUCTURE. The difference is the thing a dev editor is trained to spot.

Character arcs

Every major character should be different at the end of the book than they were at the beginning. That's the arc. A developmental editor evaluates whether that transformation is earned, whether it's visible on the page (not just in your head), and whether the events of the story actually cause the change.

The common failure here is the "sudden epiphany" problem. The character spends 280 pages being stubborn, then realizes they were wrong in a single paragraph on page 281. A dev editor will catch that and tell you WHERE the turning points need to go so the arc feels gradual and believable.

They'll also flag characters who don't arc at all. Sometimes that's intentional (flat-arc protagonists exist, and they're valid). But usually it means the character is reactive instead of active, and the editor needs to tell you which it is.

Pacing

This is the one everybody thinks they understand and almost nobody does. Pacing isn't speed. A slow-burn literary novel can have excellent pacing. A thriller can have terrible pacing despite a car chase every thirty pages.

Pacing is about TURNS. Every scene should contain a value shift (something changes between the opening and closing of the scene). When too many scenes in a row lack a turn, the story stalls. When every scene is high-octane with no breathing room, the reader goes numb.

A developmental editor reads for the rhythm of tension and release across chapters. They'll tell you the middle drags, yes, but they'll also tell you WHY. Maybe you've stacked three consecutive scenes of internal reflection with no external conflict. Maybe a subplot disappears for sixty pages and the reader loses the thread.

If you want to dig into this one on your own, I wrote a separate piece on diagnosing pacing problems that goes deeper.

Scene construction

Scenes are the unit of storytelling. A developmental editor evaluates each scene against a basic set of craft questions. Does the scene have a goal (what the POV character wants in THIS scene, not in the book generally)? Does it have conflict (opposition to that goal)? Does it end with a disaster, a setback, or at minimum a change in value?

The scene-sequel structure is the classic framework here. Not every editor uses the same terminology, but they're all looking at the same thing... does each scene WORK as a unit? Or are there scenes that exist only to move a character from point A to point B, convey backstory, or set up a later payoff without doing any dramatic work themselves?

Those "bridge" scenes are the ones that get flagged. They're the ones your beta readers are vaguely gesturing at when they say "the middle was slow."

Point of view

POV is one of the most technical dimensions a dev editor evaluates, and it's where a lot of writers have invisible habits they can't see on their own. The editor is looking at POV consistency (do you stay in one character's head per scene?), narrative distance (how close the prose gets to the character's thoughts), and whether the POV choices serve the story.

A head-hop in chapter seven isn't just a "mistake." It breaks the reader's immersion, and the reader usually can't articulate why. They just feel pulled out of the story. A developmental editor will catch every instance and explain the pattern.

They'll also evaluate whether you chose the RIGHT POV for the book. First person when third limited would serve the story better. Third omniscient when the story is too intimate for that distance. These are judgment calls, but informed ones.

Dialogue

A developmental editor reads dialogue for several specific craft problems. Are characters differentiable by voice alone (could you tell who's speaking without the dialogue tags)? Is there subtext, or are characters saying exactly what they mean in every conversation? Is the dialogue doing double duty (advancing plot while revealing character), or is it just exchanging information?

They'll also flag the "talking heads" problem: extended dialogue with no action beats, no grounding in the physical scene, no sense of where the characters are or what they're doing while they talk. Two floating voices in a void. It happens more than you'd think, especially in revision when you've cut surrounding description and left the dialogue hanging in space.

Narrative voice and prose tendencies

Voice is slippery. A developmental editor isn't going to tell you what your voice SHOULD be (that's your job as the artist). But they will flag when the voice is inconsistent, when the register shifts without reason, or when prose habits are undermining the storytelling.

Show vs. tell is the big one here. Entire craft books have been written about it, and for good reason. A dev editor will find the passages where you're telling the reader what to feel instead of showing the evidence and letting them feel it. They'll also flag overwriting (purple prose that calls attention to itself) and underwriting (scenes that needed more sensory grounding and got none).

World-building consistency

This applies to every genre, not just fantasy and sci-fi. Even a contemporary novel set in a real city has world-building rules. A developmental editor checks whether those rules stay consistent. Does the geography of your fictional town contradict itself in chapter fifteen? Did the magic system you established in act one get quietly violated in act three because you needed the plot to work?

Continuity falls here too. Character eye colors that change. Timeline contradictions. A character who "never drinks" ordering a beer on page 200. These feel small individually, but they compound. Every inconsistency costs the reader a small amount of trust, and trust is cumulative. Lose enough of it and the reader checks out.

Theme and stakes

Most developmental editors will evaluate whether your book is ABOUT something beyond the surface plot. Theme isn't a message or a moral (please don't write those). It's the question the book keeps circling. The pattern that emerges from the choices your characters make.

A dev editor won't tell you what your theme should be. But they'll notice if the book doesn't seem to be about anything, or if the thematic throughline gets muddled by subplots that pull in unrelated directions.

Stakes are related. The editor evaluates whether the reader has a reason to care about the outcome. What does the protagonist lose if they fail? Is that loss meaningful enough to sustain the story? Stakes that are too abstract ("the fate of the world") can be just as weak as stakes that are too small ("whether to attend the party"), because abstract stakes don't land emotionally.

Tension and conflict

Distinct from pacing, though related. A developmental editor looks at whether every scene contains genuine opposition. Not explosions. Not arguments (though arguments count). Opposition to whatever the POV character wants in that moment.

When tension disappears, the reader's engagement disappears with it. The editor maps this across your manuscript and shows you the dead zones. Chapters where everybody agrees, where problems get solved too easily, where the protagonist faces no resistance. Those are the chapters readers skim.

Why knowing this vocabulary matters

Here's the practical payoff. When you understand these ten dimensions, you become a better self-editor. Instead of rereading your manuscript and feeling vaguely uneasy about "the middle," you can run through each dimension systematically. Is pacing the problem, or is it a POV issue masquerading as pacing? Is the dialogue flat, or is the real issue that the scenes lack conflict and the dialogue has nothing to push against?

You also become a better client. When you hire an editor (and you probably should, at some point), knowing these terms means you can ask specific questions. "Can you pay particular attention to my POV consistency?" is a better brief than "tell me what's wrong."

And you can use interim tools more effectively. An alpha reader (human or automated) evaluating your manuscript at the craft level can give you targeted feedback on these exact dimensions BEFORE you invest in a full developmental edit. That's the workflow gap most writers don't realize exists... the space between finishing your draft and handing it to a professional.

What a developmental editor does that can't be automated

Honesty matters more than a sales pitch here.

The ten dimensions above are structural. They follow established craft doctrine. They can be evaluated against specific, documented principles. And that means a chunk of this work CAN be done by rules-based analysis tools that apply those same principles.

FirstReader does exactly that. It evaluates your manuscript across these craft dimensions, scene by scene and chapter by chapter, and ties every finding to a named craft principle. It's an alpha reader for your manuscript... principle-based feedback before you spend thousands on a human editor.

But a developmental editor also brings things that can't be reduced to rules. Subjective taste. Market awareness ("this is beautifully written but won't sell in your genre"). Intuition from reading thousands of manuscripts. The ability to say "this works even though it breaks every rule" or "this follows every rule and still doesn't work." That's human judgment. FirstReader doesn't pretend to replace it.

What it DOES replace is the tedious structural analysis that eats half an editor's time. The POV consistency check. The scene-by-scene turn analysis. The pacing map. The show-vs-tell flagging. The stuff that follows rules and can be measured against documented craft principles.

Use the tool for the structural work. Save the human for the judgment calls. Your editor will thank you (and charge you less, because you'll show up with a cleaner manuscript).

Try it on a chapter

If you want to see what rules-based craft analysis looks like on YOUR writing, FirstReader offers a free chapter analysis. Upload one chapter. See the craft report. Decide for yourself whether the feedback is useful before you commit to the full manuscript.

No subscription. No account required for the free chapter. Just your prose and the craft principles it gets measured against.

At the end of the day, knowing what a developmental editor looks for makes you a better writer whether you hire one or not. The vocabulary isn't gatekept knowledge. It's just craft. And the more precisely you can name what's working and what isn't in your manuscript, the faster you'll fix it.

If you found this useful, leave a comment to let me know. And if you didn't... well, I'd like to hear that too.