Author Beta
Denne siden er maskinoversatt og kan inneholde feil. Rapporter en oversettelsesfeil · Vis på engelsk

Developmental editing: repair the story before the sentences

Developmental editing a novel yourself: build a causal outline, check the promises your opening makes, and compare three fixes for each structural flaw.

IntermediateAbout 45 minutes, plus writingGratisUpdated

By the end: Your reader contract in the Story Bible, a causal outline and a chosen revision plan in Ideas.
Helps to have: A complete draft. Lesson 1 helps.
A causal chainEach major event should cause or change the next one. Coincidence can start a story, but it shouldn’t keep it moving.BecauseEvent Ahappens…ChoosesCharacter Bdecides C…Which changesSituation DSo nextA new choiceis forcedLabel every link: causal, thematic, parallel, or deliberate coincidence.

What developmental editing looks at

Developmental editing is a broad review of how the whole manuscript works: the opening, the stakes, pacing, viewpoint, the promise of the genre, theme, motivation and the ending. Professional developmental editors bring experience that’s hard to replicate, but you can practise developmental editing a novel yourself using the same categories, and you’ll be a better client if you ever hire one.

A causal outline, not a list of chapters

Write each major event as a link in a chain: because A happened, B chooses C, which changes D. When the next event doesn’t follow, ask whether it’s a surprise that has been prepared for, or simply disconnected. A story driven by coincidence feels arbitrary even when every scene is well written.

Weak chain. Sarah discovers the property claim. A week later an unrelated storm wrecks the shop. Then a stranger reveals who really owns it. Stronger chain. Sarah challenges the claim, which starts a records search. The search exposes a forged survey, which leads someone to pressure her brother. His response changes what Sarah believes and forces a new choice. The inventions don’t matter; the cause and effect does.

The reader contract

Your opening and your genre make promises. A locked garage and a hostile developer promise a fight for the property, and probably an answer about who owns it. List the promises your first chapters make, then check each one: is it kept, deliberately overturned with enough setup, or knowingly left open for a sequel? An abandoned promise is one of the commonest reasons readers feel let down by an ending they can’t quite fault.

Three fixes, then choose

For each structural flaw, sketch three different solutions and count their cost: scenes to add, change, merge or cut. The first fix you think of is rarely the cheapest or the best. There’s no universal plot formula; three acts, five acts, episodes and non-linear structures are all options. Choose the plan that serves your book, and keep the current draft intact until you’re sure.

Common pitfalls

  • Events linked by “and then” instead of “because”.
  • Promises in the opening that the ending forgets.
  • Fixing the first idea that comes to mind without comparing costs.
  • Forcing the book into a structure template it doesn’t need.

Check your understanding

Which link is causal rather than coincidental?

Your turn

Map your story’s structure, check its promises, and compare fixes before choosing one.

Fills the boxes with the worked example, so you can see how it saves. Change anything.

What you type here stays in this browser until you save it to your Desk. It’s kept on this device if you leave and come back.

What this saves to your book
  • Your reader contract in the Story Bible
  • Your causal outline and revision plan in Ideas

Your chapters are not changed. When you start the plan, snapshot the chapters it affects. Encrypted in your browser first.

You’ll need a free account to save. Your answers wait here while you sign up.

Take it with you: Free for everyone. Made in your browser from what you typed above.

AI assistance optional, off

Off unless you switch it on. Ask about the lesson, get a hint, or have your exercise reviewed against this lesson’s checklist. It never writes the exercise for you. Questions and hints send only your question (we add the lesson). A review sends only the answers you copy into the box. Nothing from your Writing Desk or your books is ever sent, and every request shows you exactly what will leave, and to which AI service, before you send it. Don’t include anything private or confidential. Feedback is advice and may be wrong; it never changes your progress, and every lesson can be finished without AI.

Sign in to use AI assistance.

Check your work

These are prompts, not rules. Done when: A Story Bible entry or Ideas saved in one of your Writing Desk projects.

The Loom plot grid shows every thread against every chapter, so you can see where a promise was dropped. Story structures lays beats over your chapters.

Related: How to evaluate your first draft: diagnose before you polish · Revising characters, relationships and arcs: earn the change on the page · All of Revision & Editorial Lab

Sources and further reading

  1. Before You Hire a Developmental Editor: What You Need to Know, Sangeeta Mehta, on Jane Friedman’s site (December 15, 2022). Checked Nov 19, 2026. Three editors on what developmental editing covers, when it helps, and red flags.
  2. Editorial Service Definitions, Editorial Freelancers Association. Checked Nov 19, 2026. How professional editors describe developmental editing, line editing, copyediting and proofreading.

This lesson and its examples are original to Author Academy. Sources are cited for ideas and further reading; nothing is copied from them, and no institution endorses this course. Version 1.