u/RegularWorking9861

I broke down the three documents a good developmentel editor actually hands you. The one that got the least love in the comments was the reverse outline, and I think that's backwards. So here's a longer take on just that one. Reader expectations is the lens I look through, so that's the angle. I'm not here to tell anyone how to write.

Fast version of what a reverse outline is, in case it's new: after the draft is done, you go back and write down what each scene actually does. Not what you meant it to do. What's on the page. Where the beat lands, whose head you're in, what changed by the end of it. You come out the other side holding the skeleton of the book you really wrote, which is almost never the book you think you wrote.

Plotter and pantser is a spectrume and nobody sits all the way at either end. But roughly: a plotter walks in with the map, so they can already see their structure whenever they want. A pantser flies without one. That freedom is where a ton of the best, most alive writing comes from and I'm genuinely not knocking it. The catch is that when you pants, you're inside the story the entire time. You never get to stand outside it and look at its shape. You finish the draft as the one person who can't see what you built.

Here's the part I keep chewing on. Nora Roberts is a pantser. She's said she just sits down and writes to find out what happens, straight through, and fixes it later "through a lot of experience." That last bit is the whole thing for me. She can pants safely because 200-something books have already put the reader's expectations in her head. She doesn't have to check the contract against the page, because the contract is already in her. Tia Williams plots. Different method, also works. Point is they both already know, cold, what their reader expects.

A newer writer pantsing the same way isn't doing anything wrong. They just haven't had the decade yet that turns that into instinct. So they're flying blind on a reader contract that lives in nobody's head, theirs included. And romance has a real contract. Readers expect certain beats to hit around certain places, and when they don't, the reader doesn't send you a tidy structural critique. They just quietly DNF and go find the next book.

This is the line I actually wanted to write the whole post around: the reverse outline is where a pantser gets to see how far they drifted from what readers expect. Not to beat yourself up over the drift. Some of your drift is the best thing in the book. But you cannot tell which part is the good kind and which part just wandered off, until you can see the shape, and the reverse outline is the cheapest way to see it without giving up pantsing at all. Write free. Then map what you made. Then you get to decide.

So don't skip it. And honestly, if you believe your best stuff comes out of pantsing, that's even more of a reason to embrace the reverse outline, because it's the thing that lets you keep writing that way and still catch the misses before a reader does.

That's my take. Editors, pantsers, plotters, tell me where I've got it wrong.

I spent the better part of a decade working closely with indie and self-published authors, on the publishing side rather than the writing side. One pattern I saw constantly: an author pays for a "developmental edit," a pile of files lands in their inbox a few weeks later, and they are not entirely sure what they are looking at or which document to act on first.

My aim here is narrow and practical: to give anyone weighing whether to hire a developmental editor a quick reference for what they should expect to get back, and how to judge whether it is worth the money. Editors differ widely in skill and in what they actually deliver, and price ranges with both. Most of the time the value you get tracks the price you pay. Not always. So it helps to go in knowing which of these documents you are paying for, how deep each one goes, and what might quietly be missing. Treat what follows as a checklist: something to confirm what is included, and to ask pointed questions about what is not.

So I want to lay this out as plainly as I can. A professional developmental edit is usually not one deliverable. It is typically three, and they are not three versions of the same thing. Each answers a different question, and the reason there are three is that no one of them can do the job of the other two. Understanding why tells you a lot about how editing actually works, and how to read the feedback you pay for.

I am posting this to be useful, and also because I would genuinely like to be corrected where I get it wrong. Editors here, push back.

1. The editorial letter. This is the big-picture document, often anywhere from five to forty pages of prose. Its defining move is synthesis: it takes everything the editor noticed and collapses it into a small number of patterns with priorities. If your protagonist behaves inconsistently in chapters three, seven, and twelve, a good letter does not list three problems. It names one character problem and tells you it matters more than the comma splices. The letter is where the editor says, in effect, here is how a reader experiences this book, here is what is working, and here is what to fix first. It answers the question: what does it mean, and what matters most.

2. The marked-up manuscript. This is your actual text with margin comments and queries anchored to specific lines. Where the letter generalizes, the markup points. "Your dialogue goes flat in emotional scenes" is a letter sentence. A margin note on page 142 that says "this exchange reads as small talk when the stakes should be highest" is the markup. It answers a question the letter cannot: where, exactly. You revise at the line, not at the level of a general tendency, so this is the document that makes the letter actionable.

3. The reverse outline, sometimes called a book map. This is the structural skeleton, scene by scene, usually as a grid: chapter and page range, point-of-view character, what happens, which subplot it serves, sometimes color-coded by thread. It exists to show you the shape of what you actually built, as opposed to what you think you built. It is the only one of the three that surfaces problems you literally cannot see any other way: a sagging middle, three action beats in a row, a viewpoint character who vanishes for five chapters, a midpoint that lands too late. Those are properties of the sequence as a whole. You cannot catch them reading line by line because you are inside the flow, and prose can assert "your pacing sags" but cannot show it to you. The map shows it as a visible gap in the grid. It answers: what is the actual shape of this book.

Why three and not one. Take any one away and a specific need goes unmet. A letter with no markup is a diagnosis with no X-ray: you nod along, then cannot find the instances. Markup with no letter is the opposite failure, two hundred equal-weight comments and no idea which five matter, which is why authors so often open the marked-up file and panic. And neither the letter nor the markup can do what the map does, because the structural problems the map reveals are invisible at the line level and unprovable in prose. Judgment without location is unactionable. Location without judgment is overwhelming. Structure is simply absent from the other two.

The part worth arguing about: how objective is any of this. The map feels like the objective one, just describe what exists. And the skeleton genuinely is: chapter count, page ranges, who is in a scene, those come back the same no matter who builds the map. But the rows that make a map useful, what is this scene doing, where is the conflict, what is its function, are interpretation, and two good editors will disagree on them. Even the choice of which columns to track is a quiet theory of what a story is made of. So a map is mostly objective with an interpretive layer baked in.

The letter is the openly subjective one, and that is not a flaw, it is the whole craft. What a developmental editor is really doing is running a mental model of your intended reader and projecting how that reader will receive your book. That projection is built from years of reading deeply in a genre, and it is exactly what you are paying for. It is also the honest limit of the work: it is one informed person's model of your readership, not the readership itself. The best editors are transparent about which notes are "this does not work" versus "this will not land with your particular readers," because those are different claims with different confidence behind them.

That last distinction is the one I think indie authors should internalize most, because it applies to every kind of feedback you will ever get, from an editor, a critique partner, a beta reader, or a tool. Always ask whether a piece of feedback is describing your book, or predicting your reader. Both are valuable. They are not the same thing.

If you have hired a developmental editor and gotten something different from this, I would like to hear it, the field uses these labels loosely and I am sure there is variation I have not seen.

Further reading (real editors showing real examples. I have more if you are still reading!):

• Rachelle Gardner, sentences pulled from actual editorial letters: https://rachellegardner.com/the-editorial-letter/
• KN Editorial, what margin comments on a real manuscript page look like: https://kneditorial.com/2025/05/09/working-with-an-editor-how-to-review-and-manage-track-changes/
• C.L. Polk, a visual walkthrough of an actual reverse outline grid: https://www.clpolk.com/a-visual-guide-to-a-reverse-outline/
• Jeni Chappelle, the per-scene columns an editor tracks in a book map: https://www.jenichappelleeditorial.com/post/evaluate-your-story-with-a-reverse-outline/
• The Literary Studio, sample manuscript assessment reports: https://theliterarystudio.co.uk/editorial-services/manuscript-assessment/samples-of-manuscript-assessment-reports/