A developmental edit is the single most misunderstood step in book publishing. Most first-time authors picture an editor with a red pen fixing commas. What actually arrives in your inbox is something else entirely: a multi-page editorial letter plus your manuscript covered in margin notes about structure, logic, and pacing — and barely a word about grammar.
If you are preparing a nonfiction book for professional editing, consider this post a developmental editing sample: an annotated walkthrough of each deliverable, showing you exactly what to expect, so nothing in the process surprises you.
What do you actually receive in a developmental edit?
You receive three things: an editorial letter, your manuscript back with tracked changes and margin notes, and — from thorough editors — a style sheet plus a clean reading file. The editorial letter is the centerpiece. It is a big-picture memo that explains what works, what does not, and how to revise, usually running two to eight pages according to BubbleCow's guide to editorial letters; editor Adam M. Rosen notes that a full nonfiction developmental letter often runs eight to twelve pages. The margin notes point at specific lines; the letter explains the larger reasons behind them.
| Deliverable | What it contains | What you do with it |
|---|---|---|
| Editorial letter | Strengths, prioritized big-picture issues, suggested revision order | Read it twice before touching the manuscript; it is your revision roadmap |
| Annotated manuscript | Margin queries, flagged repetitions, suggested cuts and moves | Work through note by note during revision |
| Style sheet + clean file | Recorded decisions on terms, names, and formatting | Keeps later rounds consistent and reduces churn |
An annotated sample: what the editorial letter looks like, section by section
Editorial letters follow a recognizable anatomy. Below is a composite sample built for this article from the issues developmental editors most commonly flag — this is an illustrative example, not a real client's manuscript — so you can see what each section does.
1. Overview and first impression
"The premise lands. A first-time founder reading chapter one will immediately recognize her own 2 a.m. spreadsheet panic. The voice is direct and credible — keep it. The book's core promise, though, hides until page 41. The reader bought a system; don't make her wait four chapters to see one."
What this tells you: the editor leads with what works (so you know what to protect) and names the single biggest structural finding up front. This matches the standard shape: brief overview of promise and audience, then strengths, then prioritized issues.
2. Prioritized big-picture issues
A good letter names three to five issues, ranked by payoff — not a laundry list of fifty. In our composite:
- Issue 1 — Buried promise: the core framework appears in chapter 4. Recommendation: move the framework reveal to chapter 1 and turn the current chapter 4 into a worked case study.
- Issue 2 — Repetition across chapters: chapters 3 and 5 teach the same pricing concept with different labels. Recommendation: merge into one chapter, pick one name for the concept, and add a summary table.
- Issue 3 — Sagging middle: chapters 6–8 are all theory with no application. Recommendation: end each with a one-page exercise so the reader practices before moving on.
3. Suggested order of operations
"Fix the structure first (issues 1–2), then the middle-chapter pacing (issue 3), and only then worry about sentence-level tightening. Do not copyedit yet — you'll be rewriting whole sections."
What this tells you: the letter sequences your revision so you don't polish sentences you're about to delete. This ordering — structure before sentences — is the whole point of doing developmental editing first.
What do the margin notes look like next to the letter?
While the letter handles strategy, the margin notes handle tactics. Each one ties back to a letter issue. Here are composite examples of what authors see in the manuscript file:
| Manuscript line (composite) | Margin note | Which letter issue it serves |
|---|---|---|
| "In this chapter, we will explore several facets of pricing psychology…" | "Consider opening with the framework diagram instead — the reader needs the map before the tour. (See letter, issue 1.)" | Buried promise |
| A three-page anecdote about a failed product launch, retold with new details | "This story already appeared in chapter 2. Keep the stronger version there; cut or compress here. (See letter, issue 2.)" | Repetition |
| "As previously stated, value-based pricing requires…" [third occurrence] | "Flag: concept name changes each chapter ('value pricing' / 'worth pricing'). Pick one term — see style sheet." | Consistency |
How are big-picture notes different from line notes?
Big-picture notes change what the book says; line notes change how a sentence reads. A developmental edit is almost entirely the former:
| Big-picture note (developmental) | Line note (copyediting) | |
|---|---|---|
| Acts on | Chapters, arguments, structure, pacing | Sentences, grammar, word choice |
| Example | "Merge chapters 3 and 5" | "Change 'utilize' to 'use'" |
| Who revises | You, the author, rewrite the sections | The editor can often fix it directly |
| When it happens | First, on the rough draft | Later, after structure is settled |
Reversing that order is the most expensive mistake in editing: paying for sentence polish on chapters you then restructure. The industry sequence is always structure first, sentences second, correctness third — a point made clearly in PaperTrue's guide to developmental editing.
What doesn't a developmental edit do?
Four things it is not, so your expectations stay accurate:
- It is not a copyedit or proofread. Typos and grammar get their own passes later.
- It does not rewrite your book for you. The editor diagnoses and recommends; you do the revising. As editor Kristen Stieffel puts it, doing the rewriting would be closer to ghostwriting — the guidance is the deliverable.
- It is not a guarantee of anything commercial. No honest editor promises sales, reviews, or a publishing deal.
- It cannot fix a missing premise. If the book has no clear reader and no clear promise, the letter will say so — and the fix is rethinking, not rewording.
How should you respond to a developmental edit?
Getting a multi-page critique of a manuscript you lived with for months stings. The authors who get the most from it follow the same process:
- Read the letter twice before opening the manuscript. First read: absorb scope and tone. Second read: start a list of questions. No markup yet.
- Sit with it for 48 hours. Defensiveness fades; the good notes get clearer. Almost every author disagrees with something on day one and agrees by day three.
- Triage the notes. Sort everything into must-fix (structural), should-fix (clarity and pacing), and consider (style and taste). Disagreeing with a "consider" note is fine; ignoring a "must-fix" rarely is.
- Ask the editor about contradictions. If two notes seem to pull in opposite directions, ask. A short call or email thread now saves a wasted revision cycle.
- Revise top-down. Restructure chapters first, then fix sections, then tighten sentences. Never start at the sentence level.
- Send a revision memo back. A short note listing what you changed, what you deliberately kept, and why. It closes the loop and makes any second round dramatically faster.
What mistakes do first-time authors make after a developmental edit?
- Treating every note as a command. The letter is expert advice, not law. But wholesale dismissal is just as bad — the notes you resist hardest are often the ones your readers needed most.
- Copyediting before revising. Paying for polish, then restructuring chapters, means paying twice. Structure first, always.
- Defending instead of revising. Long rebuttal emails feel productive and change nothing. Channel that energy into the revision memo.
- Trying to fix everything at once. Work the prioritized order the editor gave you. Issue one first; the smaller notes often resolve themselves once the structure is right.
- Skipping the second read-through. After revisions, read the full manuscript start to finish before it goes to copyediting. Structural fixes create new seams — chapter transitions, repeated setups — that only a full read catches.
Key takeaways
- A developmental edit delivers an editorial letter plus an annotated manuscript focused on structure, argument, and pacing — not grammar or typos.
- A typical editorial letter runs two to eight pages with three to five prioritized issues and a suggested revision order; full nonfiction letters often run longer.
- Margin notes point at specific lines, but the letter explains the larger reasoning — always read the letter before acting on the notes.
- The author does the revising, top-down: restructure first, tighten sentences later, and never copyedit before the structure is settled.
- A short revision memo back to the editor — what changed, what stayed, and why — makes any follow-up round faster and cheaper.
Frequently asked questions
How long does developmental editing take?
It scales with manuscript length and complexity. As a rough guide from industry sources, a manuscript up to 40,000 words typically takes two to eight weeks, while a standard 60,000–100,000-word book usually needs one to three months for the editing pass itself — before your revision time. Ask your editor for a schedule that separates their turnaround from your revision window.
How much does developmental editing cost?
Rates are commonly charged per word, per page, or as a flat project fee, and industry guides cite a typical range of $0.02 to $0.09 per word depending on length, complexity, and the editor's experience. Because it involves deep structural thinking, it costs more than copyediting. Get the scope in writing — what deliverables are included and how many revision rounds — before you commit.
Should I get a copyedit before or after a developmental edit?
After, always. Copyediting polishes sentences; developmental editing often moves, merges, or deletes whole chapters. Polishing first means paying to perfect sentences you may then cut. The correct sequence is developmental edit, author revision, then line editing and copyediting.
Will the editor rewrite my weak passages for me?
No. A developmental editor diagnoses problems and recommends fixes — sometimes with example rewrites of a sentence or two to demonstrate the direction — but the revision is yours. If you want someone to do the writing, that is a ghostwriting engagement, not an editing one.
Is a free sample edit the same as a developmental edit?
No. Sample edits usually cover a few pages and show you the editor's line-level style and communication. Developmental feedback is conceptual and depends on the whole manuscript — structure, pacing, and argument arc can't be judged from five pages. Use the sample to test fit, not to preview the full diagnosis.
A developmental edit can feel brutal on day one and invaluable by day thirty — it is the pass that turns a collection of chapters into a book that holds together. And it raises the question every author asks next: which type of editing does my manuscript actually need first? Our breakdown of the four types of book editing and which one you need answers exactly that. If you'd rather have a professional assess your draft and map the right editing path, take a look at our editing services or start with the self-editing checklist to tighten the manuscript before it ever reaches an editor — and if you're ready to talk through your book, book a free strategy session.