How Do I Know If I Need A Developmental Editor

Gary Smailes | 3 November 2025

What developmental editing actually covers

Developmental editing looks at the bones of a book. Structure. Plot. Pacing. Character arcs. Point of view. Theme. Stakes. Reader journey.
For nonfiction, think argument flow, table of contents logic, and learning outcomes. The promise to the reader must make sense from page one to the final chapter.

This work sits early in the publishing path. Self‑revision and beta reads. Then a developmental edit. Next comes line editing. Then copyediting. Then typesetting. Proofreading lands last. Each stage depends on the one before. Move the big blocks first, polish later.

Also known as structural or substantive editing, this is shaping the book. Not polishing sentences. A developmental editor studies intention and effect. What promise does the opening make. Where tension builds. Where momentum stalls. How characters change. How ideas stack, prove, and stick.

Here is what a pro checks and questions.

• Story structure. Does the setup create a clear desire line. Does the middle escalate pressure. Does the ending pay off the opening image and promise.
  Nonfiction version. Does the introduction name a problem and a result. Do chapters move from problem to solution to outcome in a sensible order.
• Plot and pacing. Are beats landing at the right time. Are scenes episodic or linked by cause and effect. Do quiet moments earn their space.
• Character arcs. Who wants what and why. What belief must change. Where does the shift happen, and does the story earn it.
• Point of view. One head per scene, or a deliberate pattern. Are switches clear. Does voice stay consistent with knowledge and tone.
• Theme and stakes. What truth runs under the scenes. What goes wrong if the protagonist fails. Are those stakes visible on the page.
• Reader journey. What questions arise and when answers arrive. Where curiosity spikes. Where attention drifts.
• For nonfiction. Promise, proof, and practice. Are claims backed by data or story. Do examples serve the thesis, not distract from it. Do chapters end with a clear takeaway or next step.

Two quick snapshots.

• Fiction. A thriller opens with a chase. Pages move fast, yet the goal feels vague. A developmental edit asks for clarity in scene one. Who is after whom. Why today. What happens if the hero fails now. The fix might move a reveal to page two, merge two chases, and sharpen the consequence. The scene reads shorter and stronger, because purpose drives action.
• Nonfiction. A leadership book promises a repeatable method. Chapters bounce between memoir and tips. Readers lose the thread. A developmental edit maps the promise, then reorders chapters into a sequence. Problem. Principle. Practice. Proof. Case studies shift to match claims. One chapter becomes a sidebar. Another splits into two cleaner steps. Readers now move through the method without whiplash.

Notice what did not happen in those examples. No one spent hours fixing commas. That comes later. Copyediting handles grammar, agreement, hyphenation, numbers, citations, and consistency once structure holds. Proofreading catches last-minute errors on laid-out pages. Those stages require a settled draft. Move chapters after copyediting and money goes in the bin.

If the work sounds abstract, here are concrete tools a developmental editor uses.

• A beat or chapter map. One line per scene or section with goal, conflict, and outcome for fiction. Promise, proof, and takeaway for nonfiction. Empty boxes reveal weak scenes. Duplicates point to cuts.
• A timeline and POV chart. Color blocks for each character or thread. Overlaps and gaps jump out.
• Opening and ending mirror test. First image versus last image. First claim versus final result. The book should close the loop it opens.
• An argument ladder for nonfiction. Claim, support, counter, conclusion. Steps must climb, not circle.

A brief caution. Developmental editing often asks for bold moves. Cut a chapter. Combine two. Add a scene that turns the story. Drop an anecdote that repeats a point. This feels brutal on a polished paragraph. Save the pretty sentence in a scraps file. Resurrect it later if it earns a place.

A small field test for your draft.

• Write one sentence that sums up the book. For fiction, name protagonist, goal, major obstacle, and stakes. For nonfiction, name the problem you solve and the result for the reader.
  If that sentence wobbles, structure likely wobbles too.
• List every scene or section in a spreadsheet. One purpose per row. If the purpose sounds like vibes, the scene likely lacks direction.
• Mark scenes or chapters you plan to move, merge, or delete. More than a couple, and you are still in developmental territory.
• Ask five beta readers three focused questions. Where did you skim. Where did you feel lost. Where did you feel hooked. Patterns point to structural work, not line fixes.

What arrives from a strong developmental round. An editorial letter with a ranked list of issues and fixes. Margin notes on key pages that show patterns. A revised outline or scene order. A plan for your next draft, not a sea of red on commas. Some editors include a follow‑up call or a light check of your revision to confirm progress.

Who does this work well. Editors with genre fluency and a clear method. A romance editor should talk beats, heat level, and reader expectations. A fantasy editor should talk world rules and payoff of setups across books. A business editor should talk promise, case study selection, and outcome language. Ask for a sample of feedback on a few pages. Look for questions that improve thinking, not line tweaks that flatter the surface.

One last rule of thumb. If major scenes or whole chapters still feel mobile, you are in the developmental stage. Line editing waits. Copyediting waits. Proofreading waits. Move the furniture before hanging pictures.

Signs your manuscript needs a developmental edit

You feel uneasy about the draft, not because of commas, because of shape. If structure slips, a line edit will not rescue it. Here is how to spot the big stuff early.

Fiction red flags

• A sagging middle. Scenes shuffle along without higher stakes. The hero wants something, then wanders. Quick test. List scenes in order and link them with therefore or because of this. If you reach and then, momentum is missing.
• Episodic scenes. Each chapter entertains, yet nothing compounds. Ask why this scene must follow the last one. No cause, no story.
• Unclear protagonist goal. Readers should name the goal in one sentence. If friends say, I think they want freedom, or closure, or revenge, the spine is weak.
• Flat character change. The hero starts stubborn and ends stubborn. Track belief at the start versus belief at the end. Note where the shift begins. No beat, no arc.
• POV drift. One scene, one mind. If thoughts from three heads appear in one paragraph, readers slide out of the dream.
• Timeline scrambles. Holidays out of order. Sunsets after midnight. Ages that do not line up. Build a simple timeline and watch for gaps.
• An ending that shrugs. The payoff ignores the setup. A twist with no seed feels cheap. Revisit the first three chapters and plant what the ending spends.

A quick example. You wrote a heist. Team gathers, argues, trains, argues again. Fun banter, no drive. A developmental edit presses for a clock, a cost, a leak inside the team. One training scene stays, two merge, one becomes a reveal. Now pressure builds instead of circling.

Nonfiction red flags

• A muddled promise. The book opens with a story, a quote, a stat, then no clear result for the reader. Write one sentence that names the problem and the outcome. If this feels slippery, structure likely is too.
• Repetitive chapters. Three chapters teach the same idea with new examples. Fold them, or let each chapter serve a different step toward the result.
• Unclear transformation. Readers finish a chapter and do not know what changed for them. End sections with a takeaway, a step, or a question to apply.
• Weak scaffolding. The table of contents reads like a grab bag. Ask a friend to summarize the flow in two lines. If they stall, reorder.
• Case studies that miss the point. A good story, no link to the thesis. Trim or refocus. Each example should prove a claim.
• A TOC that resists summary. If the sequence does not fit Problem, Solution, Outcome, or another clean pattern, your argument may wander.

Example. A leadership book promises a method for first-time managers. Chapters bounce among hiring, conflict, personal burnout, and feedback. A developmental edit groups content into a path. First 90 days. One-on-ones. Feedback. Team health. Now readers find steps, not a maze.

What beta readers keep saying

Listen for patterns, not volume. When three people with different reading tastes echo the same note, pay attention.

• Slow start.
• Lost in the middle.
• Confusing motivations.
• I skimmed.
• I do not know who this is for.

Those are structural signals. If a note says, loved the sentences, but I drifted, the problem sits above the line level. Resist tinkering with prose until the big pieces lock.

Market feedback worth heeding

• Agents or editors say, voice strong, structure not ready. That means hold the query until you fix the spine.
• Your comp titles move faster, hit key beats sooner, or honor genre rules you ignore. Study where comps place major turns or insights. Note page ranges. If your big moments land far later, you know where work waits.

Your own process is sending signals

• A one-sentence premise refuses to gel. You try version after version, each one vague. The story does not know itself yet.
• The synopsis balloons or collapses. Two pages become eight, then shrink to a paragraph with holes. Structure lacks hierarchy.
• You keep rewriting the first three chapters. The rest sits untouched. That loop often means a shaky map, not weak sentences.
• You avoid the ending. Not out of fear, out of not knowing what earns it. Time to shore up the promise and the turn.

Actionable: run a focused beta survey

Pick five to seven readers who match your target audience. Give them a short brief and four to six pointed questions. Keep answers short and specific.

Suggested questions for fiction:

• What is the protagonist’s goal by page 30.
• Where did your attention dip, list page ranges.
• What did you believe would happen at the midpoint, and what happened.
• What goes wrong if the hero fails, in one sentence.
• Which scene felt out of order or unnecessary.

Suggested questions for nonfiction:

• What result did the book promise in the opening.
• Where did you skim, list chapters.
• Which claim felt weak, and why.
• After each chapter, what would you do next, if anything.
• Does the TOC read as a path, say it back in two lines.

Collect responses in one document. Highlight repeated notes. If three or more readers cite the same big-picture issue, move a scene, merge chapters, or rethink order. That is developmental work. Line edits wait until those fixes hold.

A final gut check. If you hear yourself say, I think I need someone to tell me where this goes, you are describing a developmental edit. The goal is clarity, flow, and payoff. Once the book stands straight, polish away.

When you might not need a developmental editor

Sometimes the bones already hold. If story or argument runs clean, a structural overhaul would waste time and money. Here is how to tell, and where to focus instead.

Signs the structure holds

• Beats or argument map cleanly. Try this five-line check.
  1. Who wants what by page 30.
  2. What interrupts the plan at the quarter mark.
  3. What reverses expectations at the midpoint.
  4. What cost rises at the three-quarter mark.
  5. How the ending pays off the opening promise.
  If those five lines come fast and stay specific, the spine looks strong.
• Each chapter moves the goal forward. Open a scene list or TOC. Beside each entry, write one clause, so what. If the answer differs each time and builds pressure or insight, momentum exists.
• Readers finish without confusion or skimming. Two or three beta readers, not your mother, report clear stakes, rising tension, and a satisfying landing. Notes focus on lines, humor, or style, not on order or purpose.
• A friend retells the book in two sentences. Ask for a one-breath pitch from someone who read the draft. If that person is able to state the premise and outcome without hedging, the throughline reads.

A quick picture. A cozy mystery with an inciting death by chapter two, a midpoint reveal that flips suspicion, a black moment where the sleuth loses access to a key source, and a final reveal seeded in chapter one. Readers report smooth flow, no head-scratching. That book moves to line and copy.

When issues sit at the sentence level

Not every problem is structural. Some drafts sing on shape and stumble on prose.

• Clunky phrasing, bumpy rhythm, or mixed tone point to line editing. Do a read-aloud test. Mark every spot where breath runs short, diction feels off, or voice wobbles. If margin notes pile up on wording, not on order, hire a line editor.
• Grammar, consistency, and style-sheet gaps point to copyediting. Run a few pages and look for subject–verb errors, comma splices, hyphenation drift, number formatting, capitalization rules, and continuity of names or terms. If the story holds and the issue list looks mechanical, schedule copyediting.

When guidance beats a full rebuild

You want a seasoned eye to confirm direction, not a blowtorch to the foundation. A manuscript assessment suits that goal. You receive an editorial letter that lays out strengths, risks, and next steps, without in-text changes. Lower cost, faster timeline, clear to-do list.

What to include for best results:

• One to three chapters, plus a synopsis for fiction.
• TOC, intro, and one middle chapter for nonfiction.
• A one-sentence premise or value promise.
• Target reader, comps, and top three questions.

Use the assessment to decide next moves. If the report flags minor order tweaks and line-level work, skip a full dev edit. If the report points to missing beats or chapters with no clear job, plan deeper revision.

Short or prescriptive projects

Some books follow a tight outline by design. Workbooks, checklists, step-by-step playbooks. A light structural review keeps sequence clear and outcomes measurable. After that, go straight to line and copy.

A quick filter. If each section begins with a promise, delivers one tool, and ends with a short action, structure already does the heavy lifting.

Actionable next steps

• Request a paid sample assessment. Send 2–3k words plus an outline or TOC. Include audience, goals, comps, and your top concerns. Ask the editor to advise on full dev work versus a lighter assessment or line edit.
• Review the sample response for clarity and fit. Look for specific notes on beats or argument, a ranked issue list, and a proposed path forward. Vague praise helps no one.
• Freeze the draft before handing pages to a pro. No tinkering while the sample sits in review. Clear version control saves time and money.

One last gut check. If scene order feels solid, readers follow without tripping, and your questions circle style, cadence, or grammar, a developmental edit is not the next step. Move to the right level of support and keep going.

Self-diagnosis tests for structure and narrative

Before you pay for a deep structural edit, stress test the spine yourself. Give yourself clear tasks, short time limits, and honest notes. You are looking for missing jobs, weak links, and places where readers stumble.

Premise check

Write one sentence.

• Fiction: Protagonist, goal, stakes, obstacle.
• Nonfiction: Audience, promise, proof, outcome.

Examples:

• Fiction: A burned-out paramedic must win back custody of his son by exposing abuse in his father’s care home, but a corrupt director blocks every move.
• Nonfiction: For new managers, a 12‑week plan to run one‑on‑ones, set team norms, and hold fair reviews that improve performance.

Read it aloud in one breath. If you stall, the core is fuzzy. Ask four blunt questions.

• Who drives the story or argument.
• What do they want or need to learn.
• What stands in the way.
• What breaks if they fail.

If answers wobble, structure likely does too.

Mini-exercise, five minutes:

• Write the sentence.
• Cut filler words.
• Swap vague nouns for concrete ones.
• Test on a friend. Ask for a one-line repeat. If they add pieces you never wrote, your draft sends mixed signals.

Scene or section audit

Open a spreadsheet. One row per scene or chapter.

Fiction columns:

• Scene number and location
• POV
• Goal
• Conflict
• Outcome
• Next beat

Nonfiction columns:

• Chapter title
• Promise
• Proof, example, or case
• Takeaway or tool
• Next step

Fill every row. No blanks.

Flag rows where Goal or Promise reads thin. These rows often repeat work from other chapters or stall momentum. Combine, delete, or rewrite.

Tiny samples:

• Fiction, Scene 12, Rooftop, POV Lina, Goal steal the drive, Conflict security drone patrol moved, Outcome escape with decoy, Next beat rival finds her glove.
• Nonfiction, Chapter 4, Promise set up a weekly scorecard, Proof case study of a cafe chain, Takeaway use the five‑metric template, Next step download the worksheet.

Two quick checks:

• Does Outcome trigger the next scene’s Goal. If not, you have an orphan.
• Does each Takeaway ladder toward the book promise. If not, you have side quests.

Beat or TOC alignment

Compare your draft to a known framework. You are not married to one map, but timing signals health.

Fiction, rough guideposts:

• Hook and setup by 10 to 15 percent.
• First plot turn around 25 percent.
• Midpoint reversal near 50 percent.
• Crisis near 75 percent.
• Climax in the final stretch.

Nonfiction, simple spine:

• Problem, stakes, and audience promise upfront.
• Solution parts in a logical sequence.
• Proof through cases, data, or stories.
• Outcomes and next steps near the end.

Mark where each beat or module lands. If a major beat arrives a third of the book late, tension will sag. If two big moments sit on top of each other, readers miss one. Move units until rhythm breathes.

Arc mapping

Fiction:

• List the protagonist’s visible want.
• List the deeper need, often a belief shift.
• Mark scenes where behavior or belief changes.
• Note reversals, costs, and a moment of no return.

If the need sits unchanged until the last chapter, the arc reads thin. If the need flips back and forth without cause, readers lose faith.

Nonfiction:

• Define the reader’s starting state.
• Break the transformation into steps.
• Tag each chapter with a step number.
• Check for gaps, duplicates, and leaps.

If steps jump from 1 to 4 with no bridge, insert a chapter or a section. If two chapters do the same job, merge.

Continuity and POV

Open your draft and color‑code.

• For fiction, color by POV. Keep one color per scene. If two colors bleed into one scene, you are head‑hopping. Choose a center.
• Create a simple calendar. Day and time for each scene. Mark travel and recovery windows. Mismatch signals a timeline snarl.
• Track names, places, ages, jobs, and rules in a separate tab. Update as you revise.

For nonfiction with research:

• Log sources per chapter.
• Note quotes and paraphrases.
• List figures and tables.
• Mark open research gaps in red.

Continuity is invisible when it works. When it breaks, readers put the book down.

The 90‑minute audit

Set a timer. Work fast and without polish.

• Minute 0 to 10. Write your one‑line premise or value promise. No throat clearing. One sentence.
• Minute 10 to 50. Build the scene or section map. Use the columns above. Force yourself to fill every row.
• Minute 50 to 80. Run the framework check. Mark where beats or modules land.
• Minute 80 to 90. List the top five issues. Rank by impact, not by ease.

Common big‑ticket issues:

• No clear inciting event.
• Midpoint does not change the game.
• Stakes do not rise.
• Repetitive chapters.
• Unclear or missing takeaways.
• POV drift.
• Timeline knots.
• Thin or absent proof.

What your results mean:

• If fixes require moving or rewriting several scenes or chapters, plan for developmental editing.
• If notes focus on word choice, rhythm, or tone, move to line editing.
• If errors cluster in punctuation, capitalization, and consistency, book a copyedit.

Two last tips:

• Print the five‑issue list and keep it visible during revision.
• Repeat the 90‑minute audit after a pass. You should see fewer big‑picture flags and more line‑level notes. That shift tells you structure now holds.

How to prepare and work with a developmental editor

Developmental editing lands early, so preparation pays off. Freeze the draft, sharpen your goals, and choose a partner who fits your book and your process. Here is how to set up the work and get full value from every note.

What you will receive

Most projects include a few core deliverables.

• Editorial letter. A big-picture analysis with priorities, risks, and a clear revision path. Expect sections on structure, pacing, character or argument flow, and stakes or takeaway.
• Margin comments on key pages. Line-level notes where structure meets sentences, often on the opening, turning points, and the end.
• Scene or chapter map. A grid which shows what each unit does, how units link, and where momentum drops.
• Revision plan. A step-by-step order for changes, with a proposed schedule.
• Follow-up support. Many editors offer a call to walk through the plan. Some offer a second-pass check once revisions are in.

Ask for a sample of each item. Style varies by editor, and you want materials which match how you learn.

Choosing the right editor

Look for fit on three fronts.

• Genre and category experience. Ask for titles in your lane, plus outcomes. For fiction, match on subgenre and audience age. For nonfiction, match on purpose, such as trade how-to, memoir, or academic crossover.
• Feedback style. Request a paid sample on 2 to 3k words plus an outline or table of contents. Study the clarity, tone, and practicality of the notes. You want sharp and specific, never vague or cruel.
• Alignment on goals. Share your purpose and success criteria. Query-ready in six months. Self-publish with a launch plan. Series potential. You want an editor who agrees on direction before work starts.

Questions to ask during a short call:

• What problems do you see in the sample and outline.
• Which three fixes would move the needle fastest.
• How will we decide what to cut.
• Which framework or methodology do you use, and why.
• What does success look like for this round.

Trust your gut. If you leave the call energized and clear, you likely found your partner.

Scope and timeline

Document the scope before you sign.

• Word count and file format.
• Level of edit, full developmental edit or a lighter manuscript assessment.
• Number of passes.
• Deliverables, letter, margin notes, map, plan, follow-up.
• Communication cadence, weekly email, shared doc, or calls.
• Delivery dates for each piece.

Developmental edits often span several weeks. Protect that time on your calendar as well, since questions will surface and quick replies keep momentum.

Budget and options

Pricing often runs per word or as a flat fee based on complexity and turn time. A full developmental edit suits drafts which need reordering, new scenes or chapters, and deeper stakes or payoff. For early-stage work, a manuscript assessment gives a diagnostic view without in-text edits, which lowers cost and speeds turnaround.

Ask for:

• A written quote with scope, dates, and payment schedule.
• A sample or mini assessment before a larger commitment.
• A clause for a short follow-up check after revisions, if needed.

Collaboration best practices

Strong outcomes follow strong process.

• Freeze the draft before handoff. No new chapters during the edit. Changes midstream blur targets and invite chaos.
• Share comps and target readers. Three to five comparable books, plus a short note on audience and promise.
• List your top questions. Where do readers stall. Which character or concept confuses people. Where do you want more heat.
• Resist line edits during structural work. No polish on paragraphs which might move or vanish.
• Keep decisions in writing. A short recap after each call saves time and stress.

One more habit, name owners for tasks. You own new scenes and research. The editor owns the map and the plan. Shared clarity prevents drift.

Your pre-handoff packet

Give your editor a tidy packet. Aim for brief and focused.

• One-sentence premise or value promise.
• One-paragraph summary of the book, start to finish.
• Table of contents or a scene list with a single line per unit.
• Comps, three to five titles with a note on fit.
• Audience, who they are and what they want from this book.
• Goals, query-ready or self-publishing, plus any deadlines.
• Top three concerns.
• Questions you want answered.
• Any constraints, legal, ethical, employer approvals, or privacy issues.

Label files clearly, BookTitle_Draft_Date.docx, TOC, Summary, Sample. Editors love clean handoffs.

A short request email

Subject: Dev edit inquiry for Book Title, 85k, upmarket mystery

Hello [Editor Name],

I am seeking a developmental edit for Book Title, 85k words, upmarket mystery. Target readers love Louise Penny and Jane Harper. Draft is frozen. I attached a one-page summary, table of contents, and the first 3k words.

Goals:

• Query agents in four months
• Strengthen the midpoint and finale
• Tighten POV and timeline

Would you share availability, a quote, and whether a sample edit or assessment suits this stage.

Thanks,

[Your Name]

Tweak details for nonfiction, swap in audience, promise, and learning outcomes.

How to use the edit once delivered

Start with the letter. Read once without marking. Walk away for a day. Read again and highlight the top priorities. Build a simple plan with three columns, task, effort, impact. Tackle high-impact work first. Merge or cut scenes and chapters before adding new pages. Save line polish for later.

Bring questions to the follow-up call. Pin down order of operations. Confirm success criteria for this pass. Book a short second check only after structural shifts settle.

Red flags

Watch for trouble before you sign or during the work.

• Vague promises without samples.
• Guarantees of bestseller status.
• An edit which focuses on commas while core beats wobble.
• An editor who avoids calls or refuses to explain methods.
• Scope creep without a clear change order.

One last nudge. Preparation lowers cost and stress. A clear brief, a frozen draft, and a matched editor turn a rough stack of pages into a book readers finish and recommend.

Frequently Asked Questions

Download FREE ebook

Claim your free eBook today and join over 25,000 writers who have read and benefited from this ebook.

'It is probably one of the best books on writing I've read so far.' Miz Bent

Leave this empty

Get free book