What Should a Developmental Editing Report Include?

TL;DR: A good developmental editing report should give you a clear revision roadmap, not just a list of problems. Look for structure, manuscript-specific evidence, prioritised recommendations, and honest next steps before you pay.

A developmental editing report should work as a revision roadmap

A developmental editing report should not feel like a long list of everything that is wrong with your book.

Detailed feedback has its place, but detail on its own is not always useful. If you finish reading a report feeling bruised, confused, or unsure where to begin, the report has only done half the job. A good developmental edit should help you understand your manuscript more clearly and give you a practical way forward.

This is why I think of a developmental editing report as a revision roadmap. It should show you where your book is now, where it could be improved, and what you need to deal with first.

It is not there to rewrite the book for you. It is there to help you make better revision decisions.

At this stage, the editor is looking at the big-picture parts of the manuscript. For fiction, that might mean structure, plot, character development, pacing, viewpoint, tension, genre expectations, and the reader’s emotional journey. For nonfiction, it might mean argument, structure, clarity, audience, authority, chapter order, repetition, and whether the book delivers on its promise to the reader.

The exact focus will depend on the book, but the purpose is the same: to help you see the manuscript as a whole.

A useful report should identify the main issues, explain why they matter, and help you decide what to revise first.

1. It should separate the major revision work from the minor adjustments. Not every weakness in a manuscript matters equally. Some problems affect the whole reading experience, while others are smaller and easier to fix later.
2. It should show how each issue affects the reader. It is not enough to say that the opening is slow, the middle loses focus, or the argument is unclear. You need to understand why the issue matters and how fixing it will improve the book.
3. It should give you a sensible order for the work ahead. When feedback is presented as disconnected criticism, authors can end up trying to fix everything at once. That often leads to frustration. A better report gives you a sense of priority, so you can approach the revision in a more manageable way.

Length alone does not make a report useful. A very long report can still be vague. A shorter report can work well if it is clear, specific, and focused on the decisions you need to make next. What matters is whether the feedback helps you move from uncertainty to action.

So, when you are evaluating a developmental editing service, the question is not simply, “How many pages will the report be?”

A better question is: “Will this report help me revise, or will it simply tell me what is wrong?”

That distinction matters. Serious revision is demanding work, and you do not need a report that leaves you overwhelmed by criticism. You need one that gives you clarity, priorities, and a practical route into the next draft.

The report should have a clear structure, not a stream of vague comments

A useful developmental editing report should feel organised. It should not read like a loose collection of observations, margin notes, or personal reactions. If the report is there to help you revise, the way it is arranged matters.

In practical terms, this means the feedback is usually divided into clear sections. Different editors use different formats, but a strong report will often start with an overview of the manuscript as a whole, then move into the main areas that need attention. Depending on the type of book, these might include structure, character, plot, pacing, argument, content, reader experience, or positioning.

For fiction, you might see sections on story structure, character development, point of view, setting, tension, genre expectations, and the reader’s emotional journey. For nonfiction, the focus may be the central argument, chapter order, clarity of promise, audience fit, evidence, examples, tone, and how well the book delivers on its purpose.

The exact headings matter less than the thinking behind them. You are looking for a report that helps you understand the manuscript in layers. What is the editor’s overall view? What is working? What is not working yet? Which issues matter most? What should you tackle first?

This matters because developmental feedback can be demanding. Even an encouraging report may contain a lot of information. If that information arrives as a stream of vague comments, you can finish reading and think, “I know there are problems, but I don’t know what to do next.”

A well-structured report reduces that confusion. It gives you places to put the feedback. It separates big-picture issues from smaller concerns, helps you see patterns rather than isolated faults, and turns the editor’s response into something you can work through in stages.

You should also expect some kind of conclusion or next-steps section. It does not need to be a rigid checklist, but it should help you begin the revision. A report that identifies problems without helping you think about action is only doing half the job.

There is no single correct format. Some editors write formal reports with numbered sections. Others use a more conversational style. Some include summaries, bullet points, tables, or action lists. The format can vary, as long as the report is clear, organised, and useful.

Before booking, it is reasonable to ask the editor what their report usually includes. You can ask for a sample report, a redacted example, or at least a description of the deliverable. A professional editor should be able to explain how their feedback is structured and what you can expect to receive.

The goal is not to buy a report that looks impressive. The goal is to receive feedback you can understand, absorb, and use. A clear structure is what makes that possible.

It should diagnose the manuscript, not just list problems

A useful developmental editing report should do more than point out what is not working. It should explain why it is not working.

Any thoughtful reader can tell you that a section feels slow, confusing, or unconvincing. A good editor goes further. They look beneath the surface for the pattern causing that reaction.

For example, a weak report might say, “The pacing is slow in the middle.” That may be true, but it does not give you much to work with. Are there too many similar scenes? Is the central conflict unclear? Has the main character stopped making meaningful choices? Are chapters repeating the same emotional beat? Without that diagnosis, you are left guessing.

A stronger report might explain that the middle feels slow because the manuscript loses pressure after the opening act, or because the protagonist’s motivation becomes blurred, so the reader no longer understands what is driving the story forward. In non-fiction, the same idea applies. An argument may feel weak not because the writing is poor, but because important context is missing, the chapters arrive in the wrong order, or the same point is repeated without being developed.

Manuscript problems are rarely isolated. Slow pacing may be connected to structure. Reader confusion may come from missing context. A flat character arc may be rooted in unclear motivation. A book that feels “not quite right” for its market may have a genre expectation problem rather than a sentence-level problem.

A good report should help you see these connections, and it should tie each issue to the reader’s experience. Not simply, “This chapter is repetitive,” but something closer to, “Because this chapter repeats information the reader has already understood, it reduces momentum and delays the next meaningful development.” That helps you understand not just what to revise, but why the revision will improve the book.

The same is true of comments such as “the opening is confusing.” Confusing in what way? Does the reader lack enough context to understand the situation? Are too many names introduced too quickly? Is the point of view unclear? Is the book asking the reader to care before it has shown them what is at stake? Each diagnosis leads to a different kind of revision.

This is what separates a report from a list of complaints. A list of problems can leave you feeling overwhelmed. A diagnosis gives you a way in.

By the end of this section of the report, you should have a clearer understanding of the manuscript as a whole. You should be able to see the main things shaping the reader’s response: where the book builds momentum, where it loses focus, where it asks too much of the reader, and where the structure is working against your intentions.

That understanding allows you to revise the causes behind the problems, rather than fixing scattered issues one by one.

It should identify strengths as well as weaknesses

A useful developmental editing report should tell you what is not yet working in your book. It should also show you what is already strong.

Positive feedback is not there to soften the blow. Used properly, it becomes part of the revision plan. If you do not understand the strongest parts of your manuscript, you can damage them while trying to fix weaker areas.

Your report might point to an engaging narrative voice, a strong central premise, a main character with real emotional pull, or expertise that gives the book authority. In non-fiction, the strengths might lie in the clarity of your explanation, the originality of your angle, or the practical value of your advice. In fiction, they might lie in character, atmosphere, pacing, dialogue, or the emotional shape of the story.

These are not decorative comments. They show you what to protect.

Revision can be unsettling. Once you start moving chapters, cutting material, reshaping characters, or reworking your argument, it is easy to lose sight of what made the manuscript promising in the first place. A good report should make clear which elements should be preserved, strengthened, or used more deliberately.

That does not mean the report should hold back on weaknesses. Balance is not equal space for praise and criticism. It is a fair and useful view of the manuscript as a whole.

Weaknesses should be specific, constructive, and connected to the work ahead. Vague comments such as “the middle feels weak” or “the structure needs work” are not enough on their own. A stronger report explains why the middle loses momentum, how the structure is affecting the reader’s experience, and what kind of revision might help.

The best reports avoid both extremes. A praise-heavy report may feel encouraging, but it can leave you without a clear route forward. A criticism-heavy report may identify problems, but it can make revision feel bigger and more discouraging than it needs to be.

You want a balanced, practical assessment: what is working, what is not working yet, and how those two things interact. That balance helps you approach revision with focus rather than panic.

The next step is understanding which issues matter most, because not every problem deserves the same amount of time or energy.

It should prioritise the issues, not treat every problem as equal

A good developmental editing report should not leave you with a long list of problems and no clear sense of what matters most. At this stage, your real question is not just, “What is wrong with the manuscript?” It is, “What should I tackle first?”

Revision works best when it happens in the right order. Big-picture issues need attention before you spend too much energy on smaller fixes. There is little value in polishing a chapter sentence by sentence if that chapter may need to move, be rebuilt, or even be removed. Tightening dialogue will only take you so far if the character’s motivation is unclear or the plot logic does not hold together.

A strong report should show you which issues have the biggest effect on the reader’s experience. Some problems run through the whole book. Others are local and can be dealt with later. Both may matter, but they do not carry the same weight.

High-priority issues are usually the ones that decide whether the manuscript works as a complete reading experience. These might include structure, reader confusion, plot logic, argument flow, missing content, weak motivation, or problems with genre expectations. In fiction, this might mean a central conflict that arrives too late, a character decision that does not feel earned, or a plot thread that creates confusion rather than tension. In non-fiction, it might mean the argument does not build clearly, important information is missing, or chapters repeat points without moving the reader forward.

Lower-level issues still have a place. Style, wording, repetition, pacing within a scene, or moments of over-explanation can all affect the quality of the manuscript, but they should not pull your attention away from the larger revision decisions. A good developmental editor will usually flag when something is worth noting now but better handled later. That kind of guidance helps you avoid getting stuck in line-level improvements before the foundations are secure.

This is where a developmental editing report gives you a workable order for revision. It helps you understand what to fix first, what to keep in mind as you revise, and what can wait until the manuscript is structurally stronger.

Without prioritisation, feedback can quickly become overwhelming. You may feel as though everything needs fixing at once, which often leads to either panic or avoidance. A well-prioritised report reduces that pressure by giving you a clear starting point and helping you make steady progress, rather than trying to solve every problem in a single pass.

The aim is not to make revision effortless. Serious revision rarely is. The aim is to make it manageable and focused, so you can see the difference between the issues holding the book back and the refinements that will matter once the bigger work has been done.

It should use examples or evidence from the manuscript

A useful developmental editing report should not read like a set of abstract writing tips. General principles have their place, but they only become useful when they are connected to the manuscript in front of the editor.

If a report says the pacing is uneven, the author needs to understand where that happens and why. If it says the argument loses focus, the author needs to see that pattern on the page. Without this kind of evidence, the advice can feel vague, even when it is right. The author is left thinking, “Yes, but what does that mean for my book?”

Manuscript-specific examples are what make the feedback usable.

A strong report will usually point to chapters, scenes, sections, patterns, or repeated issues that help the author recognise the problem. In fiction, this might mean noting that several important turning points arrive too late, that a character makes a major choice without enough motivation, that the stakes disappear in the middle of the story, or that similar pacing issues appear across several chapters. In nonfiction, it might mean identifying a chapter order that weakens the reader’s path through the book, an unclear reader promise, an argument that needs more support, repeated material across sections, or a missing explanation that leaves the reader behind.

The point is not to embarrass the author or to prove the editor is right. It is to make the feedback useful.

When an editor shows you the pattern, you can begin to apply the lesson elsewhere. You are not simply being told, “This section is too slow.” You are being shown what slow pacing looks like in your own writing. You are not just hearing, “This chapter lacks focus.” You are seeing how that lack of focus affects the reader’s understanding.

Revision depends on recognition. Once you can see the issue clearly, you have a much better chance of fixing it across the manuscript.

The examples may appear in different places depending on the editing package. Some editors include most of the evidence directly in the report. Others use the report to explain the larger patterns and add more detailed examples in manuscript comments. Often, the two work together: the report gives the broad assessment, while the comments show how the issue plays out in specific places.

That does not mean every point needs a long list of examples. A developmental editing report is not meant to catalogue every sentence, page, or scene. Too much evidence can become overwhelming and can bury the main message. What matters is that there are enough examples to make the feedback clear, credible, and practical.

Good examples support the assessment and prepare the ground for the recommendations that follow. They help you see what needs attention and how the issue affects the reader’s experience. That is what turns a report from a set of opinions into a practical guide for revision.

It should explain recommendations and next steps

A useful developmental editing report should not simply tell you what is not working. Diagnosis matters, but it is only half the job. The other half is helping you understand what you might do next.

That does not mean the editor takes over the book or makes the creative decisions for you. A good editor guides. The author decides. Developmental editing should make your manuscript stronger while still leaving it clearly yours.

The best reports connect each recommendation back to the problem already identified. If the editor says the middle of the book loses momentum, the report should explain why this is happening and suggest practical ways to address it. That might mean reordering chapters, tightening repeated material, raising the stakes, clarifying a character’s motivation, or making the main argument clearer.

For fiction, the advice might focus on deepening a character arc, clarifying point of view, strengthening conflict, improving pacing, or making the ending feel more earned. For non-fiction, it might involve restructuring the argument, adding missing context, cutting repetition, improving chapter flow, or making the route through the book clearer for the reader.

The advice needs to be specific rather than vague. “Improve the structure” is not very helpful on its own. “Consider moving this chapter earlier, because it introduces the problem your reader needs to understand before the later case studies” gives you something you can think about and test.

A strong report should also leave room for choice. There is rarely only one correct way to revise a book. The editor might suggest two or three possible approaches, explain the likely effect of each, and help you choose the direction that best serves the manuscript.

It should also help you build a realistic revision plan. Not every issue carries the same weight, and not every change needs to happen at once. By linking recommendations to priorities, the editor helps you see what to tackle first, what depends on other decisions, and what can wait until a later draft.

A developmental edit can uncover a lot, and without clear next steps the feedback can feel overwhelming. Clear recommendations make that feedback easier to use. You can see the shape of the work ahead, understand why each change matters, and begin revising with more confidence.

Some packages may also include line-edit-style feedback

Some developmental editing packages include line-edit-style feedback. Others keep the line edit separate, or offer a combined package that gives you big-picture guidance alongside comments on the manuscript itself.

Check exactly what is included before you pay.

A developmental editing report and a line edit are not the same thing. A useful developmental report should focus on the big-picture work your book needs: structure, reader experience, argument or story, pacing, clarity, priorities, and the order in which to tackle your revisions. It gives you the roadmap.

Line-edit-style feedback works closer to the sentence and paragraph level. You are more likely to see it through tracked changes, margin comments, or annotations directly on the manuscript. These comments might point out unclear sentences, repeated phrasing, awkward transitions, over-explanation, tone issues, or places where the writing could be sharper or more precise.

Both types of feedback can be useful, but they do different jobs.

A developmental report might tell you that a chapter is trying to do too much, that the central argument is not yet clear, or that a scene is arriving too early in the story. A line-level comment might mark the exact sentence where the confusion begins, or the paragraph where rhythm, wording, or emphasis starts to weaken the reader’s experience.

There may also be some overlap. If sentence-level issues reveal a wider pattern, they may be summarised in the report. An editor might note that the prose often becomes abstract at the start of chapters, or that dialogue frequently explains emotions the reader could infer from action. At that point, the issue is not just one sentence. It is a repeated pattern that affects the book as a whole, so it belongs in the developmental discussion.

Tracked changes and margin comments should not replace a clear developmental roadmap. Local comments can show you examples in context and help you see the problem on the page. But if all you receive is a marked-up manuscript with scattered comments, you may still be left wondering what matters most, what order to revise in, and how the changes fit together.

That is the value of the report. It should turn the evidence into a clear plan.

When comparing developmental editing packages, look carefully at what you will receive. Ask whether you will get a written report, an annotated manuscript, tracked changes, a follow-up call, or some combination of these. Also ask what level of sentence-level feedback is included, if any.

A good editor should be clear about the difference. Developmental editing is not a substitute for a full line edit, and a line edit is not a substitute for developmental thinking. If a package includes both, that can be useful, but only if you understand what each part is doing.

The best result is not simply more comments. It is the right kind of feedback in the right format, so you can revise without feeling buried under notes.

It should explain what is different for fiction and nonfiction

A useful developmental editing report should not feel as if it has been copied from a general checklist. It needs to fit the kind of book being edited, because fiction and nonfiction ask different things of the reader.

For fiction, the report will usually spend time on story: plot, structure, character motivation, point of view, pacing, scene function, genre expectations, emotional impact, and reader engagement. In practical terms, the editor is asking whether the story holds together, whether the characters’ choices feel believable, whether the scenes earn their place, and whether the reader is being pulled through the book in the way the author intends.

For nonfiction, the focus shifts. The report may look more closely at the argument, structure, reader promise, authority, clarity, evidence, chapter progression, repetition, and practical usefulness. Here, the editor is asking whether the book delivers what it appears to offer, whether the chapters build in a logical order, whether the ideas are clearly supported, and whether the reader is likely to come away with the understanding, insight, or practical help they expected.

There is overlap, of course. Clarity matters in every book. So does structure. Pacing is not just a fiction issue; nonfiction can drag, repeat itself, or move too quickly over ideas the reader needs time to understand. Reader expectations matter in both as well. A thriller, a memoir, a business book, and a self-help guide all create different kinds of expectations, and the report should respond to those expectations.

This is why a developmental editing report should be shaped around the manuscript’s purpose and readership. It should not treat every novel as if it must follow the same formula, or every nonfiction book as if it is making the same kind of argument. A practical guide, a memoir, an academic-style book, and a thought-leadership book all need different editorial questions.

When you are choosing an editor, it is worth asking whether they understand your type of book. That does not mean they need to make sweeping claims about every genre or every nonfiction category. In fact, I would be cautious of anyone who overgeneralises. What matters is that they can explain the issues they will be looking for in your manuscript and why those issues matter for your intended reader.

A good report should leave you feeling that your book has been assessed on its own terms, not forced into a template designed for something else.

What a developmental editing report should not include or promise

A useful developmental editing report should be honest about its limits. It should give you a clear, practical way into revision. It should not sell you a fantasy.

Be wary of any report, or editing service, that promises publication, sales, reviews, bestseller status, agent interest, or guaranteed success. No editor can honestly offer those things. A strong edit can help you improve the manuscript, make better revision decisions, and present the book more professionally, but it cannot control the market, readers, publishers, agents, or reviewers.

A developmental editing report should not promise to make your book perfect, either. Books are built through choices, and many of those choices remain yours. The editor’s job is to show what is working, what is not working, and where revision is needed. Your job is to weigh that advice, make decisions, and do the rewriting.

Vagueness is another warning sign. If the report could apply to almost any manuscript, it is not doing enough. Comments such as “improve the pacing,” “develop the characters,” or “make the structure stronger” may be true, but they are not very useful on their own. You need to know where the problem appears, why it matters, and what kind of revision might solve it.

A weak report often hides behind broad statements. It may praise the manuscript without explaining what is genuinely effective, or criticise it without giving you a way forward. It may list issues but fail to prioritise them. It may focus on small surface details while avoiding the bigger questions of structure, argument, story, reader experience, or market fit.

Be cautious, too, if a service uses the language of developmental editing but does not clearly explain what you will receive. Developmental editing is not proofreading, formatting, ghostwriting, copyediting, or a simple reader reaction. Those services can all be useful, but they are different. The deliverables should be clear before you commit, so you know whether you are buying a strategic editorial report, manuscript comments, a full edit, or something else.

A good report is neither brutal nor flattering. It is specific, balanced, and useful. It does not frighten you into buying more help, and it does not pretend revision will be effortless. It gives you a grounded view of the manuscript as it stands and a realistic sense of what needs to happen next.

Report-only manuscript assessment versus fuller developmental editing

Before you pay for developmental editing, make sure you know what kind of support you are actually getting. Editors use different names for similar services, and the details can vary. One editor’s “manuscript assessment” might look quite different from another editor’s “developmental edit”, even when both focus on big-picture story or structure.

A report-only manuscript assessment usually means feedback in a written report. The editor reads the manuscript and comments on the main issues: structure, plot, character, pacing, point of view, genre expectations, argument, reader engagement, or whatever matters most for your book. The value is in the diagnosis. You get a clear view of what is working, what is not yet working, and where to focus your revision.

Fuller developmental editing may go further. Depending on the editor and the package, it might include a longer or more detailed report, comments placed directly in the manuscript, a follow-up discussion, revision planning, or extra guidance after you have had time to think through the feedback. This can help if you want a more guided process, or if your manuscript has several connected problems that are difficult to untangle from a single report alone.

Neither option is automatically better. A report-only assessment can be enough if you are at an earlier stage, want an overview, and feel confident turning feedback into a revision plan. A fuller developmental edit may suit you better if the manuscript is further along, the problems feel more complex, or you know you would benefit from more detailed guidance as you revise.

It is also worth being clear about what developmental editing does not usually include. Line editing is separate unless it is explicitly included in the package. Developmental feedback looks at the book’s foundations: the shape, logic, reader experience, and overall effectiveness. Line editing works at sentence and paragraph level. Both matter, but they are different skills and usually belong to different stages of editing.

So compare deliverables, not just service names. Ask what you will receive. Will there be a written report? How long and how detailed is it likely to be? Are manuscript comments included? Is there a call or follow-up? Will the editor comment on structure, character, argument, pacing, market fit, or genre expectations? The answers will tell you far more than the label on the service page.

If you mainly need direction, a strong assessment may be enough. If you need help seeing how the pieces connect, fuller developmental support may be the better fit.

Questions to ask an editor before paying for a report

Before you pay for a developmental editing report, ask a few direct questions. You are not trying to catch the editor out. You are making sure you both understand what will be delivered.

Start with the basics: what exactly will I receive? The word “report” can mean different things. For one editor, it might be a short overview. For another, it might be a detailed chapter-by-chapter assessment with a revision plan. You need to know what is included before you can decide whether the service is right for your book.

• How long or detailed is the report likely to be? This does not need to be an exact word count, but the editor should be able to explain the level of depth you can expect.
• Will it include a prioritised action plan? A useful report should help you understand what to fix first, what can wait, and which changes will have the biggest effect on the manuscript.
• Will the editor comment directly on the manuscript? Some reports are delivered as a separate document only. Others include margin comments, notes, or annotations alongside the report. Neither approach is automatically better, but you should know what you are buying.
• Are tracked changes included? If so, ask what kind of changes will be made. If not, check whether that is because the service is focused on big-picture structure rather than sentence-level editing.
• Is line editing included, offered separately, or not part of the service? Developmental editing is not the same as rewriting or polishing every sentence, and misunderstanding this point can lead to disappointment.

You should also ask whether the feedback will cover the issues that matter for your type of book. For fiction, that might include plot, character, pacing, viewpoint, dialogue, and genre expectations. For nonfiction, it might include argument, structure, reader promise, clarity, authority, examples, and practical value. The editor does not need to offer a perfect formula, but they should understand the kind of book you are writing.

If possible, ask to see a sample report or anonymised example. This can show you the editor’s style, the level of detail, and how useful the feedback is likely to be. You may also want to ask what happens after you receive the report. Is there a follow-up call? Can you ask clarification questions? Are further services available if you need them?

This is also a natural point to consider a free sample edit, where available. It can help you see how the editor thinks and whether their feedback feels useful before you commit.

Clear answers before payment protect both you and the editor. More importantly, they help you avoid paying for a report that sounds interesting but does not give you enough practical guidance when you sit down to revise.

The best report leaves you with clarity, not confusion

A good developmental editing report should not bury you in criticism. It should give you a practical way back into the manuscript.

By the time you finish reading it, you should understand what is working, where the main problems are, and which changes matter most. The report should do more than list opinions. It should explain what is happening on the page, put the issues in order, use clear examples from the text, and help you move into revision with purpose.

Most authors do not need more vague feedback. They need to know whether the problem is structure, character, pacing, argument, genre expectation, reader experience, or something else entirely. They also need to know what to tackle first, because trying to fix everything at once quickly becomes confusing.

The best reports are honest without being careless. They may be hard to read in places, especially when they point to problems you had not seen before, but they should never leave you feeling lost. Strong editorial feedback should feel organised, thoughtful, and useful. It should help you make better decisions about your book, not take the book out of your hands.

If you are comparing developmental editing services, look closely at what the report actually includes. Ask whether it will give you a clear overview, detailed analysis, examples from your manuscript, and practical next steps. That is what turns feedback into a plan.

If you are unsure what kind of support your manuscript needs, a free sample edit can be a useful first step. It shows you how the feedback works and whether developmental editing is the right fit for your book.

You should finish with a clear sense of what to revise next, and why.

Frequently Asked Questions