Developmentalediting

Usually when you can feel something isn't working but can't put your finger on what. Maybe beta readers drift off halfway through, or you're getting rejections that mention vague 'structural issues', or the story just doesn't land the way you meant it to. A developmental edit is where we work out exactly what's missing from the reading experience and why. You don't have to be in trouble to book one, though. Plenty of writers use a developmental edit simply to take a manuscript they already like and push it as far as it can go.

Once you have a complete draft and you've revised it as far as you can on your own. A developmental edit works best on a manuscript you've already taken seriously, so any self-editing and beta reader or critique feedback beforehand only makes it more useful, and the better shape the draft is in, the higher-level the feedback can be. When you book, it helps to tell me a bit about what you're going for: your goals for the book, who it's for, and anything you already suspect isn't working. If you're several drafts in and still feel something fundamental is off, that's usually a good sign it's time.

Both are thorough reads that evaluate all of the big elements: structure, pacing, character, worldbuilding, whether the story is doing what you want it to, etc.

A manuscript assessment only provides a report, while developmental editing also has comments written throughout the manuscript so you can see how the feedback applies to exact points on the page. An assessment is usually enough if you just want big-picture direction, but if you want detailed advice on revising your story structure closely, developmental editing is the choice.

Two ways, side by side. You get comments and tracked changes throughout the manuscript itself, pointing out specific moments where something is working or could be developed, alongside a separate, detailed editorial report that steps back and covers each element of the story and what I see overall. Once you've had time to read through everything, there's an optional follow-up call to answer questions and talk through how to tackle the trickier spots.

No. Keeping your voice intact is the whole point. A developmental edit works through comments and suggestions on your own manuscript, so every change is yours to make or ignore. My job is to help you tell your story more clearly and effectively, not to smooth it into sounding like me. If anything, the aim is to get more of your voice onto the page, not less.

It depends on the length and complexity of the manuscript, but I usually aim for around four to eight weeks, and you'll have a confirmed delivery date before you commit. A developmental edit is thorough, so it takes longer than a lighter pass: a close read, detailed feedback throughout, and the follow-up call. If you're working to a deadline, let me know early and I'll be honest about what's realistic.

Revision, mostly. The edit gives you a clear picture of what to change and why, and then the work of reshaping the manuscript is yours. It's a big job, so it helps to have support: some writers lean on a critique partner or writing group to stay accountable while they work through the notes. Once your revisions are done, the manuscript is usually ready for the lighter, later stages like copyediting and proofreading.

No. AI tools can hand you generic structural advice, and some can flag things like length or an obvious pacing dip. What they can't do is feel a story. They can't tell you why an ending doesn't feel earned, read the emotional current of a scene, or tell the difference between a genre expectation you're breaking on purpose and one you've broken by accident.

That's the whole point of a developmental edit: judgment about your particular book, from a person who has actually read it and cares whether it works. I never put your manuscript into an AI tool, and the reading and the thinking are always my own.