developmental editing fiction

Developmental Editing Fiction

Developmental Editing for Fiction: Scope and Timing

Developmental editing looks at the story engine. Structure, plot, pacing, character arcs, POV, theme, market fit. Not grammar. Not style. Save commas for later.

Here is the work in plain terms. A developmental editor asks whether the premise holds, whether scenes cause consequences, whether stakes rise, and whether readers will feel what the pitch promises. The focus stays on the book’s spine and organs, not its clothing.

What falls inside scope

Expect scrutiny on:

Off the table for now:

Those belong to line editing and copyediting. Developmental work shapes the book so those later passes pay off.

Typical deliverables

Most editors offer a mix of these:

A short debrief call often accompanies delivery. Use that call to confirm priorities and next steps.

Mini example:

Best timing

Book developmental work after a complete draft or a substantial revision. The editor needs a full view of the arc. Partial drafts hide problems, which leads to vague advice.

A simple path that works:

Short on budget or time. Start with a manuscript assessment or a partial pass on the opening and outline. Apply guidance to the full draft before a deeper round.

How editors read a novel

Editors read with promises in mind. A romance promises an emotionally satisfying ending. A mystery promises fair-play clues and a credible reveal. A thriller promises escalating danger and a deadline. Break the promise, readers walk.

A few quick lenses:

Red flag examples:

Prep that raises quality and lowers cost

Bring a tight briefing pack. Quotes improve. Feedback lands faster.

Include:

Prep tips:

A tiny exercise before you book:

Those five lines sharpen the edit and your choices.

What to ask your editor to answer

An editorial letter works best when guided by your goals. Give questions that target your pain points.

Examples to include in your brief:

Add one success question. For example, Which elements feel strong enough to leave alone for now. This protects working parts while you rebuild weak ones.

A quick checklist before you hit send

Developmental editing shapes story. Respect the order, and the rest of the process becomes smoother. Get the scope right, bring the right materials, and ask sharp questions. Your future line editor will thank you. Your readers will too.

Plot and Narrative Structure

Plot carries readers through the book. Structure orders events so tension grows, reveals land, and payoffs make sense. When those pieces work, readers stop checking the time.

Start with a core promise

Name the promise. Who drives the story, what goal sits on the table, and what change rides on the outcome. Add a feeling target for the reader.

Try this quick frame:

Mini exercise:

Tape those lines above your desk. Every structural choice serves that promise.

Build a clean causal chain

Scenes need to trigger consequences. Each event sets off the next event. No random errands.

Weak chain:

Stronger chain:

Use a simple test. Between any two scenes, write Because X, therefore Y. Or But X, so Y. If the link reads And then, rethink.

Common leaks:

Hit the structural beats with purpose

Every genre bends beats, yet a backbone helps.

Spot checks for each:

Tiny blueprint example, mystery:

Weave subplots to raise pressure

Subplots serve the main arc, not the other way around. Treat each thread as a lever. Pull, and pressure rises.

Test every subplot with three questions:

If a thread fails two questions, merge with a stronger thread or cut. Two weak friends in a cast often become one sharp friend who forces change. Romance, rivalry, mentorship, family tension. All fair game, as long as those threads squeeze the central choice.

Tame timelines and reveals

Chronology carries more weight than grammar at this stage. Track time, place, and logistics so revelations land where impact peaks.

Practical moves:

Watch for timeline hitches:

Tools that make structure visible

Clarity comes faster when the skeleton sits on the table.

A quick case:

Action steps for a structural pass

One last test before moving on. Pitch the story to a friend in four beats. Setup. Disruption. Reversal. Decision and payoff. If the pitch sounds like a sequence of causes and effects with rising stakes, structure likely holds. If the pitch meanders, go back to the chain. The draft will thank you, and readers will feel the difference.

Character Arcs and Relationship Dynamics

Plot moves bodies. Character arcs move hearts. Desire, choice, and pressure give a story a spine readers feel.

Agency and desire

Give the protagonist a goal that would keep a real person up at night. Tie every major choice to that goal. Then throw credible obstacles in the way.

Quick frame:

Exercise:

Agency test for scenes:

If any answer reads no, raise the stakes or cut the scene.

Arc types tied to theme

Arcs grow from misbelief. Name the lie the protagonist starts with, then design moments that confront that lie.

Three common paths:

Theme alignment:

Prompt:

Antagonistic forces with logic

Pressure shapes change. Build opposition with human logic, not cartoon villainy.

Four sources to mix:

Give the opposing force a reason that makes sense within that worldview. The rival wants the same promotion. The aunt thinks wealth equals stability. The storm arrives during peak season. The hero self-sabotages under stress.

Checklist:

Cast design with intent

Redundant characters blunt momentum. Fold roles where overlap appears.

Audit steps:

Give side characters mini-arcs that intersect the main arc.

Cross-check with the protagonist’s growth. Side arcs should collide with turning points, adding pressure or relief at planned moments.

Relationships as engines of change

Relationships shape choices. Treat each bond as a pressure point.

Mentorship:

Friendship:

Romance:

Rivalry:

On-page cues that show growth:

Practical steps for a character pass

Build GMC sheets:

Beat the arc per act:

Root out passenger characters:

Scene turns for character state:

Map interactions:

Line check for agency:

Dry run test

Pitch the arc in four beats:

If the pitch lands clean and causal, the spine holds. If the pitch wanders, return to GMC, prune the cast, and raise relationship pressure where the heart of the story lives.

Pacing, Scenes, and Narrative Tension

Readers turn pages for answers. Each page should plant a question. Each scene should move the story from one state to another.

Scene craft

Build scenes on three legs, goal, conflict, change.

Example:

Quick check for any scene:

If nothing turns, compress, combine, or cut.

Exercise, write a one-line log for five scenes using this form. Want. Obstacle. Turn.

Entrances and exits

Start late. End early. Skip warm-up. Skip cooldown. Land in motion, leave on tension or relief.

Use hooks or mini-questions to propel readers across breaks.

Trim exit fluff. No long goodbyes. No travel unless travel alters stakes.

Microtension

Microtension lives inside lines. Curiosity at the sentence level keeps attention even during quiet moments.

Tools,

Try this pass on a slow page. For each paragraph, add one friction point. A withheld name. A wrong assumption. A minor lie. Watch energy rise.

Exposition control

Backstory and facts serve story, not the other way around. Readers want what helps the current problem.

Principles,

A test line to try, “She knew three things,” then deliver three relevant facts, each linked to the current goal.

Rhythm variety

Monotony drains momentum. Vary scene length, mode, and heat.

A rhythm pattern to try across a chapter, pressure, breath, push. Repeat with rising stakes.

Sequel beats

After major events, lock in forward motion with a compact sequel.

Example, the heist fails. Reaction, fear and shame. Dilemma, run now or rescue the partner. Decision, rescue, which shifts the next goal and scene setup.

Practical pacing tools

Build a simple spreadsheet. Chapter by chapter, or scene by scene.

Columns to include,

Scan for trouble,

Front-load crucial questions early in acts and at chapter starts. Name the chase. Name the fear. Name the clock.

Quick drills

Pacing grows from choices, not tricks. Clear goals, smart conflict, frequent turns. Relationships add pressure. Voice adds flavor. Structure sets the climb. Keep readers asking, “What happens next,” then answer with consequence and a new question. Repeat, with purpose and heart.

POV, Voice, and Genre Conventions

POV controls access. Voice shapes experience. Genre sets the contract with your reader. Nail these, and the story breathes.

Choosing and managing POV

Pick your viewpoint with intent. First person gives direct access. Strong intimacy. Close third offers similar access with more range for tone. Omniscient steps back, offers breadth, and invites commentary from the narrator.

Keep tense and psychic distance stable unless a clear reason exists to shift. Psychic distance means how close we sit inside a mind. Closer reads like raw thought. Farther feels cooler, more observational. Choose a default and stick to it scene by scene.

No head-hopping. One viewpoint per scene or per chapter. Signal switches with a scene break and a clear identifier in the opening line. Location, name, or a unique filter on the first paragraph.

Quick drill:

Create a simple POV charter:

Keeping voices distinct

Voice grows from word choice, rhythm, focus, and bias. Two characters in the same city will notice different details. A surgeon clocks symptoms. A pickpocket clocks exits.

Build a short voice profile for each viewpoint:

Align dialogue with interiority. A character who swears in thought should not sound prim in speech unless hiding something. If you want a mask, show the slippage.

Spot-check a chapter. Cover names and dialogue tags. Read a random page out loud. Could you tell who speaks from sound alone. If not, raise contrast. Swap three words for each viewpoint, ones only they would use. Keep a list on your desk.

Show vs tell with intent

You do not need to dramatize every minute. Show turning points. Tell transitions and low-stakes business with clean summary.

Told:

Shown:

Use summary to leap over dead air. One line will handle travel, setup, or repetitive tasks. Deploy one or two vivid specifics inside summary to keep texture.

Use interiority for judgment and meaning. Action without thought reads thin. Thought without action stalls. Pair them.

Genre promises and how to meet them

Each shelf comes with expectations. Meet them, then surprise within fair bounds.

Crossing streams. Blend away, but choose one primary promise. Market copy, cover, and early chapters should signal that promise without confusion.

The reader promise

Tone and reading level must match your audience and comps. A snarky teen voice suits YA urban fantasy. A meditative voice suits literary family drama. Align word count and heat level with reader expectations for the niche you plan to pursue.

Voice should reinforce theme and mood. If your theme explores trust, let diction show openness or guardedness. If mood leans eerie, avoid wisecracks in life-or-death moments unless the point is dissonance.

Test this. Pick two comps. Read five pages from each. Then read your first five pages. Do the vibes sit on the same shelf. If not, adjust tone, pacing, or line choices.

Action steps

Worldbuilding and Continuity

Readers forgive dragons and time portals. They do not forgive broken rules. Your world earns trust by setting limits, then keeping receipts.

Rules and constraints

Define how things work. Then show the price.

Edge cases bring drama. Who is allowed to break the rule. What happens when they do. If there is no consequence, there was no rule.

Quick drill:

Setting as function

Place should squeeze choices, not sit like wallpaper.

Anchor each scene with one sensory fact that affects behavior. The generator coughs every time the lights flick. The alley smells of bleach. Snow piles against the door. Pick details that force action or color mood. Skip the tourist brochure.

Test yourself. Open three scenes. In the first paragraph of each, add:

Build a continuity bible

Memory lies. Your book needs a log.

Keep a simple tracker. Spreadsheet, notebook, or a notes app. Use columns you will update, not ones that look fancy and gather dust.

Track:

Add a style sheet for capitalization, hyphenation, and invented terms. Decide once. Keep it consistent.

Red flag examples:

Fix these before line edit. Continuity errors multiply once prose tightens.

Research and representation

Facts are texture and guardrails. Skimp here and readers will email you.

Representation needs care. Give characters from any group a specific job, desire, and flaw that are not tokens. Avoid assigning all harm or all virtue to one identity. If you write outside your lived experience, bring in sensitivity readers. Pay them. Listen.

Build a research log:

Plausibility and logistics

Your reality, your rules. Still, bodies, tools, and distances behave. Honor that.

When you need an exception, seed it early. If a character reaches the capital in a day, explain the courier hawk or the tunnel in chapter three, not at the finish line.

Map your timeline. A simple row of days with morning, afternoon, night can reveal overlap and gaps. Mark travel, injuries, weather, and major beats. Do the clocks line up.

Sanity check trick. Write the story of your story from the point of view of a logistics officer. How did they move, eat, sleep, and hide. Where did resources come from. Bored yet. Good. Fix the holes.

Action steps

Frequently Asked Questions

What does a developmental edit for fiction actually cover and what is out of scope?

A developmental edit for fiction examines the story engine: premise and promise, causal chain between scenes, stakes and escalation, subplots, theme and genre fit. The editor tests whether scenes cause consequences and whether readers will get the experience your pitch promises.

Line-level concerns—sentence rhythm, word choice, commas and fine continuity fixes—are normally off the table and handled in later line editing or copyediting passes so the structural work can land first.

When is the best time to book a developmental edit?

Book a developmental edit after you have a complete draft and have done at least one self-revise—use a reverse outline for fiction and a short synopsis to surface major gaps. Editors need the full arc to diagnose midpoint issues, subplots and theme alignment.

If budget or time is tight, start with a manuscript assessment or a partial pass on the opening 30–50 pages plus your outline so you can apply directional fixes before a full pass.

Which materials should I include to get accurate quotes and faster, cheaper feedback?

Send a tidy briefing pack: a 1–2 page present‑tense synopsis, a reverse outline for fiction (one line per scene noting purpose and change), a character GMC sheet for key roles, two to three comps, an audience statement and current plus target word count. Label any sensitivity or research concerns up front.

Clean .docx files with clear scene breaks, a simple style sheet and a list of your top questions let editors price accurately and spend reading time on the work that truly needs diagnosis.

How do editors test structure—what is a useful way to audit scenes and beats?

Editors use scene-by-scene audits and beat sheets to check causality and pacing. A simple test between any two scenes is “Because X, therefore Y” (or “But X, so Y”); if the link reads “and then,” the chain needs work. They also map the inciting incident, midpoint shift, crisis and climax against word ranges to locate sagging middles or late reveals.

Tools such as a beat sheet for the midpoint, index cards or a visual story map make mis-timed turns obvious and speed editorial diagnosis.

How should I prepare characters and relationship dynamics for a character pass?

Prepare concise character GMC sheets (Goal, Motivation, Conflict) for protagonist and major players, and a simple relationship grid that maps ruptures and repairs against plot turns. For each scene, note the state change—“Hopeful to doubtful,” “Ashamed to defiant”—so an editor can see whether interior arcs align with external beats.

Audit side characters by function: if two serve the same purpose, merge or retask one. That keeps the cast tight and ensures relationships drive choices rather than act as filler.

How should I handle POV, head-hopping and tense before the edit?

Create a POV charter that assigns who holds viewpoint in each scene, your default tense and allowed psychic distance. One viewpoint per scene is the rule; signal any switch with a scene break and an anchor line (name, location or time) so the reader is not disoriented.

Run a head‑hop audit: highlight thought verbs and interior cues. If two minds leak into the same paragraph, split the scene or choose a single head. Fixing POV consistency before a developmental pass reduces confusion and sharpens editorial feedback.

What practical steps protect worldbuilding and continuity during a developmental pass?

Build a continuity bible for your novel—a single spreadsheet or document tracking names, spellings, dates, ages, locations, tech or magic rules and any costs for breaking those rules. Colour-code timelines and dual threads so mirrored beats align and travel or injury windows make sense.

Seed any planned exceptions early and record sources for technical facts. Editors will flag plausibility issues, but a clear continuity bible saves time and prevents small errors multiplying during later line edits.

Writing Manual Cover

Download FREE ebook

Claim your free eBook today and join over 25,000 writers who have read and benefited from this ebook.

'It is probably one of the best books on writing I've read so far.' Miz Bent

Get free book