What You Should Know About Working with a Developmental Editor

You’ve reached the point where your manuscript feels like a book — but you also sense something’s missing. You can’t quite put your finger on it. You’ve re-read it so many times that you can recite it by heart, and you’re wondering: “Is there actually a problem here, or am I just too close to see it?”

This is the moment when friendly beta readers won’t be enough, and a developmental editor steps in. Let me walk you through what developmental editing actually means—and why it’s quite different (and much more impactful) than getting feedback from friends or beta readers.

What Is Developmental Editing, Anyway?

Developmental editing, also called substantive, structural, or content editing, happens before copyediting or proofreading. It’s the stage where someone helps you shape the story itself: plot structure, narrative flow, character arcs, pacing, emotional stakes… all the big-picture stuff. Usually, it’s a serious story makeover.

What to Expect: The Editorial Letter

Most developmental editors will give you an in-depth editorial letter or critique. Some keep it brief — a tidy 2–3 pages. Personally? I’ve never mastered the art of being concise when it comes to editorial letters. I like to over-explain, over-analyze, and make sure you understand not just what needs adjusting, but why. So my editorial letters tend to be 10+ pages of deep-dive feedback.

That letter will break down why certain parts of your story may not be landing as you hoped — and more importantly, how to fix them. We’ll look at structure, emotional arcs, pacing, tone, and all the little threads that need to weave together to make your narrative stronger. In addition to the letter, some developmental editors (myself included) will also provide in-line comments directly in your manuscript.

What we won’t do is rewrite your book. Our role is to guide you toward the parts that need rethinking, but you’ll be the one steering the revision, making choices in the way that feels right for your story.

Timing Is Everything

You don’t want to bring in a developmental editor too soon, when you’re still brainstorming. But you also don’t want to wait too late. The general sweet spot is after you’ve gone through several rounds of self-revision—when you’ve done everything you can on your own, and maybe even had a few friends or beta readers give it a read.

But always, always bring in a developmental editor before copyediting and proofreading. Developmental editing often leads to significant changes — new scenes, deleted chapters, restructured arcs. It’s not unusual to do some heavy rewrites. And there’s no point polishing the grammar on paragraphs that might not even survive the next draft. First, make sure your story itself is solid. The grammar check comes later.

Communication and Mindset Matter

Working with developmental editors should feel like a collaboration. In my experience, trust, honesty, and clear goals are key. But the most important requirement from you as an author is to stay open-minded about the changes your editor might suggest.

You don’t have to implement everything. Some suggestions might not resonate with you, and that’s perfectly fine. But you should remember that you and your editor share the same goal: to make the best book possible.

My advice? Talk through your vision in advance. Ask for a free sample edit, or at least have an introductory call. You need to get a sense of their editing style, how they think, and the direction they might take your story. This step will save you a lot of second-guessing later on.

What a Developmental Editor Can and Can’t Do

They can:

• Diagnose why your story isn’t working and suggest structural fixes.

• Offer ideas on pacing, character arcs, and theme development.

• Mentor and raise your craft along the way.

They can’t:

• Rewrite your book.

• Turn your draft into an instant bestseller — editing alone won’t guarantee a publishing deal or five-star reviews (but it significantly increases you chances).

• Replace your voice. Any suggestion is just a suggestion; you’re still the author.