Fiction Developmental Editing

Gary Smailes | 3 November 2025

What developmental editing covers (and what it doesn’t)

Developmental editing looks at the spine of your story. Structure, logic, momentum, emotion. Grammar sits on the bench for now.

Here is the focus:

• Structure. Where the story turns. How scenes stack. Why this scene follows that scene.
• Plot logic. Cause and effect. Promises set up early, payoffs delivered later.
• Pacing. Acceleration, breath, then another push.
• Character arcs. Want, wound, misbelief, choice under pressure, change.
• Theme. The argument under the action.
• POV control. Who holds the camera and why, and how close the lens sits.
• Stakes. What goes wrong if failure wins, and for whom.
• Worldbuilding. Rules, costs, limits, and continuity across time and space.

No grammar. No commas. No typo hunts. Those arrive after the story holds.

The goal

A developmental round removes friction a reader feels but cannot name.

• Close plot holes. A lost heir does not forget royal protocol on page 280 without hint or reason.
• Clarify motivation. Give each choice a clear driver, fear, desire, duty, survival.
• Improve scene flow. Each scene alters the story state, forward momentum or new pressure.
• Align to genre conventions. Romance promises a HEA or HFN. Mystery rewards fair play. Thriller raises heat with each chapter. Fantasy respects rule costs. Horror lands dread with rhythm. Literary centers interiority without stalling.
• Meet reader expectations. Hook early, build pressure, twist with logic, finish with earned emotion.

A quick test:

• Open to page one. Mark the moment where normal life breaks. If nothing shifts by page five, start there.
• Flip to the midpoint. Name the irreversible shift. If no clear pivot, define one.
• Read the climax. State the protagonist’s choice in one sentence. If the choice reads fuzzy, motivation needs work.

What deliverables look like

You receive a plan, not a pile of nitpicks.

• Editorial letter. Big-picture diagnosis and priorities. Clear wins, major risks, and a plan for sequence of fixes.
• Margin comments. Scene-level questions and prompts inside the manuscript. “What outcome locks this door?” “Whose desire drives this beat?” “Where does the rule cost show on the page?”
• Scene map or beat sheet. A list of scenes with POV, goal, conflict, outcome, and notes on tension. Often framed in a familiar model, three-act, four-act, Save the Cat, or Story Grid.
• Revision plan. Step-by-step order. Structural surgery first, then character throughlines, then scene mechanics, then polish. Page targets and success checks.

What this gives you:

• A north star for revision.
• A place to log cuts and adds.
• Language to test new scenes against old goals.

Small exercise to prepare:

• Write a one-page synopsis before handing over pages. Do the same after revisions guided by the letter. The second summary should read leaner, clearer, and closer to the promise you want to make.

The reader promise

Readers buy a promise on page one. Delivery arrives at the end.

• Opening hook. A question, a need, a problem in motion.
• Midpoint shift. Stakes tilt or knowledge reframes the path.
• Climax. A decisive choice under peak pressure that flows from the arc.
• Resolution. Consequences land, wounds acknowledged, new normal formed, or door cracked for a series.

Developmental work tracks that promise. If the hook sells a caper comedy, the climax should not drift into tragedy unless the setup trained readers for that move. If the midpoint hints at betrayal, the finale honors that seed with payoff or a smart reversal.

Try this:

• Write the promise in one sentence on a sticky note. Place the note near your workspace. Read each revised scene and ask, does this scene push toward that promise.

What developmental editing is not

• Not line editing. No line music, no image tuning, no rhythm work. Your editor might flag a few sentences as examples, yet prose polish remains outside scope.
• Not copyediting. No style sheet enforcement, no hyphenation choices, no grammar or spelling sweeps.
• Not proofreading. No checks on widows, orphans, or layout on designed pages.

Mixing scopes muddies progress. Structure first, voice next, correctness last. Fix the bridge before painting the rail.

Examples from the trenches

• Structure. A heist novel opened with a long prison backstory. Moving the escape to page one gave the story a live wire. Backstory shrank to two sharp beats fed through action.
• Logic. A fantasy queen bent a magic rule during the finale. We added a cost seeded in chapter four, a scar on the palm that flares with use. Readers accepted the move because the bill arrived on time.
• Pacing. A thriller drifted after chapter ten. We set a 24-hour clock, added a midpoint failure, and trimmed a travel chapter. Tension returned.
• Character. A romance hero refused to apologize, then earned love. We traced pride to a family role, wrote one honest screwup fix during the dark moment, and the ending felt deserved.
• POV. A YA book hopped between four heads in one scene. We chose the one with the most to lose and tightened distance. Confusion vanished, tension rose.

How to know you are ready

• You have a complete draft from beginning to end.
• You feel unsure about scene order, stakes, or motivation.
• Beta readers say, “I felt lost in the middle,” or “I did not buy the choice.” Different notes, same root cause.

Send those pages. Ask for a sample pass on a chapter with a representative problem. Look for questions about goals, cause and effect, and reader promises.

Developmental editing serves the story’s backbone. Grammar waits. Voice waits. Nail structure, purpose, and payoff first. Then move to lines and commas with confidence.

Genre-specific priorities in developmental editing

Every genre asks for different proof on the page. Same toolset, different targets. Here is how I tune the work.

Romance

The relationship is the plot. Everything serves the arc from spark to commitment.

Nonnegotiables:

• Chemistry on-page. Shared scenes pulse with desire, humor, or friction.
• Conflict versus compatibility. Reasons to stay apart, plus clear reasons together makes sense.
• Trope execution. Proximity, enemies to lovers, grumpy sunshine. Pay the beats readers came for.
• Consent and heat-level consistency. Signals are clear. Intimacy tracks with your promise.
• Ending promise. HEA or HFN lands without hedging.

Quick checks:

• Two-scene test. One scene shows why they work, one shows why they fail. If both read flat, raise stakes or sharpen desires.
• Dialogue test. Strip stage directions. Read the lines out loud. Heat or tenderness should survive the cut.
• Dark moment audit. The breakup comes from a core belief, not a flimsy misunderstanding.

Mini fix:

• Write a single sentence for each lead. Want, fear, nonnegotiable. Pin those to your monitor. Revise scenes until choices match those anchors.

Mystery and Thriller

Readers want surprise that feels fair. Tension climbs. Time closes in.

Nonnegotiables:

• Fair-play clues. Evidence appears on the page before the reveal.
• Red herrings. Misleads point away without lying to the reader.
• Suspect arcs. Each suspect pursues a goal that crosses the case.
• Twist logic. Reversals read inevitable in hindsight.
• Timeline clarity. Clocks, travel, alibis, all aligned.
• Escalation. Pressure rises, options shrink.
• Credible stakes. Loss hits personal, professional, or public spheres.

Quick checks:

• Clue ledger. List clue, where placed, who knows, and how it pays off. Gaps tell you where to seed.
• Hour-by-hour strip. Map the case week or day. Alibi holes pop fast once you draw a line.
• Reveal audit. After the twist, re-read earlier chapters. Plant one visual or phrase in each that points toward truth.

Mini fix:

• Cap each chapter with a shove. A new threat, a fresh lead, or a cost paid for progress.

Sci‑Fi and Fantasy

The world has rules. Rules have costs. Story depends on both.

Nonnegotiables:

• Rule-based systems. Magic or tech has limits, prices, and failure modes.
• Info control. World lore enters through action, not lectures.
• Jargon clarity. Terms stay readable. Names easy to track.
• Maps, glossaries, series notes. Continuity lives somewhere reliable.
• Series arcs. Book one resolves its promise, while planting future threads with intent.

Quick checks:

• Rulebook one pager. List what the system does, where it fails, and what it costs the user. If the finale ignores this page, revise either the rule or the scene.
• First-chapter filter. Circle every invented term. Keep three. Push the rest to later scenes.
• Sandbox test. Give a clever side character ten minutes with your rules. Would they break the plot in one move. If yes, design a cost or guardrail.

Mini fix:

• Replace one exposition block with a consequence. A miscast spell, a shorted circuit, a public rule breach with fallout.

Historical

Readers trust you with time travel. Earn the trust.

Nonnegotiables:

• Anachronism control. Language, objects, and social norms fit the period.
• Period-accurate voice. Syntax and diction echo the era without choking flow.
• Research integration. Facts support scenes without dragging them down.
• Sensitivity for real figures and events. Respect, nuance, and source checks.

Quick checks:

• Idiom sweep. Flag modern phrases. Swap for period-appropriate beats or plain speech.
• Prop list by year. Clothes, transport, food, weapons. If an object arrives early, fix the date or change the prop.
• Source notes. Primary, secondary, expert. Keep a log for every loaded detail.

Mini fix:

• Turn a research paragraph into a lived moment. The draft says “rationing was severe.” The scene shows a baker watering dough and cutting the loaf unevenly.

Literary and Book Club

Interior life drives the engine. Form carries meaning. Momentum still matters.

Nonnegotiables:

• Interiority with intent. Thought and sensation reveal pressure, not fog.
• Subtext. Dialogue and action carry what lies under the surface.
• Thematic cohesion. A clear argument threads the book.
• Image systems and motifs. Repeated elements evolve, they do not repeat flat.
• Experimental structures. Pattern serves story, not the other way round.
• Purposeful ambiguity. Open questions enrich, core stakes stay legible.

Quick checks:

• Scene change test. For each scene, write what shifts. If nothing shifts, fold or cut.
• Motif ledger. List an image, where it recurs, and how it changes meaning. If it shows up three times unchanged, revise one beat.
• White space audit. Dense blocks earn their weight with payoff. Lighter passages place breath by design.

Mini fix:

• Add a concrete action after an abstract thought. Thought lands harder once grounded.

YA and MG

Voice leads. Agency belongs to the kid. Adults support without stealing the wheel.

Nonnegotiables:

• Age-appropriate voice. Syntax, references, humor, and slang fit the age band.
• Clear content boundaries. Romance heat, language, and harm matched to market norms.
• Focused stakes. School, family, friends, community. Big feelings, clear scope.
• Brisk pacing. Shorter chapters, on-page goals, quick turns.
• Adult presence with purpose. Mentors guide, they do not fix the climax.

Quick checks:

• Agency test. Name the person who solves the core problem. If the answer is an adult, rewrite the plan.
• Chapter breath test. Read one chapter aloud. If the voice trips over heavy description, cut or move detail into action.
• Gatekeeper pass. Note spots a teacher, librarian, or parent might flag. Align language and harm with your target shelf.

Mini fix:

• Replace a lecture with a peer moment. A friend shares a secret, a dare, or a joke that shifts the plan.

One more tool

Build a genre checklist on a single page. Put your book’s promise at the top. List five must-haves from your category. During revision, tick each item with page numbers. No guesswork. Proof on the page.

The developmental editing workflow

A clear process lowers stress and lifts the work. Here is how a thorough developmental edit usually runs.

Discovery

We start with context. Genre, comps, word count, goals, audience, pain points. Give me your pitch in two lines. Name three books your reader loves. Tell me where beta readers stalled or bailed.

Ask for a sample edit on ten pages. You want to see margin notes in action. Tone, clarity, and practical value. Also ask how I deliver tough notes. You need honesty, not whiplash.

Quick prep:

• Write two promises your book makes to a reader.
• List three scenes you love and three you fear.
• Note hard limits. Voice, theme, representation pillars.

Scope and agreement

We set the frame. Level of edit. Deliverables. Number of passes. Timeline. Fee. No fog.

Typical package:

• Editorial letter, big-picture through scene dynamics.
• Tracked comments in the document.
• Beat sheet or scene map.
• A follow-up call to walk the plan.

We also agree on response times and file handling. When questions arise, do we use comments or email. One weekly call or only milestone check-ins. Clarity saves time and nerves.

Diagnostic read

I read once for experience. No tinkering. Then I map story moves. Opening image, inciting incident, first plot turn, midpoint shift, dark night, climax, resolution. I note pacing pockets and logic risks. I sketch character wants and misbeliefs. I flag world rules and costs.

Example beat slice:

• Hook: page 1 to 3, a theft during a wedding.
• Inciting incident: page 18, the suspect is a sibling.
• First turn: page 60, proof points to the wrong sibling.
• Midpoint: page 150, the hero hides evidence to protect family.

Risk list might include travel scenes with no new pressure, a villain who enters too late, or a rule which breaks during the finale.

Mini exercise for you:

• Write one sentence per act. If the line wobbles, structure needs reinforcement.

Editorial letter

This is the blueprint. From macro to micro, with examples and options. You will see what works, what blocks momentum, and where readers will question motive or logic. I propose fixes, offer choices, and note trade-offs. No vague advice.

A sample block might look like this:

• Issue: a flat middle which slows momentum.
• Symptoms: repeated searching scenes, no shift in power.
• Goal: raise stakes and narrow options by midpoint.
• Options:
  1. Compress travel into a montage with one costly setback.
  2. Move reveal A to end of act two, swap reveal B to midpoint.
  3. Merge two sidekicks, free page count for a direct clash with the antagonist.
• Example on page 142 to 147: revise beat where the hero bargains with the fence, add a price which haunts act three.

You also get a scene map with columns for goal, conflict, outcome, and POV. Empty columns signal cuts or rebuilds.

Revision phase

You run the plan. Not all at once. Triage first.

Set three buckets:

• Must fix: structural issues which block reader trust.
• Likely fix: improvements which support pace or motive.
• Later: items for line edit or copy pass.

Test changes on two or three chapters before scaling. Send those pages for a quick pulse check if included. Keep a change log, one line per move, page range, reason. When a margin query needs a decision, answer in the doc so the chain of thought survives version churn.

Two small tools:

• The “because” test. After each scene outcome, write “because” and finish the sentence. If logic snaps, revise motive or action.
• The “state change” tag. At the top of each scene, note start state and end state in five words or fewer. If nothing shifts, fold or repurpose.

Schedule a midpoint call to solve snags. Bring examples. Bring questions that start with “If we move X, what breaks.” We fix at the level with the highest leverage.

Beta and sensitivity readers

Once the spine holds, recruit targeted readers. Match goals to readers. Pacing and clue fairness for mystery. Heat level and consent clarity for romance. Representation for cultural or identity aspects. Technical accuracy for medicine, law, or aviation.

Give a short brief:

• Book promise and genre.
• What to focus on.
• Three to five questions with page hooks. Example: “Did the midpoint twist surprise and still feel earned. Page range 140 to 160.”

For sensitivity work, pay readers, agree on scope, and ask for sources if they reference guidance. Treat notes with respect and privacy.

Final verification

After revisions, I review key changes or a refreshed outline. We check pressure at act turns, motive chains, world rules, and continuity. If a fix solved one problem and introduced a new hole, we patch now.

Quick checklist before you move to line work:

• Opening hook aligns with genre promise.
• Midpoint changes the game, not the mood.
• Climax forces a decisive choice, not a coincidence.
• Resolution honors the promise on page one.
• Word count sits within market norms for your shelf.

Lock the structure. Then line editing will sing, and copyediting will not fight story logic. Clean bones first, polish later.

Self-editing checklist to maximize your developmental edit

A smart self-pass raises the value of any developmental edit. Fewer blind spots. Sharper questions. Stronger pages. Use this checklist before you hand over the manuscript.

Reverse outline

Map every scene. One line per scene with four fields: goal, conflict, outcome, POV.

Example entries:

• Ch 4. Goal: steal the ledger. Conflict: guard blocks exit. Outcome: escape without ledger. POV: Mara.
• Ch 5. Goal: regroup with ally. Conflict: ally demands proof. Outcome: plan stalls. POV: Mara.

Scan the list. If a scene leaves the story in the same state, cut or combine. If two scenes chase the same goal, merge and raise pressure.

Quick exercise:

• Highlight outcomes in one color. You want visible change from scene to scene. No change means low priority or a cut.
• Add a column for time of day. Look for three breakfast scenes in a row. Collapse repetition.

Character arcs

Define core drivers for the protagonist and key players. Use a simple template.

• Goal: what the character wants on page one.
• Motivation: why that goal matters.
• Conflict: forces in the way, internal and external.
• Misbelief: false story the character lives by.
• Transformation: the new belief after the climax.

Snapshot example:

• Before: Mara believes loyalty means silence.
• After: Mara learns loyalty means honest risk.

Now stress-test. At the climax, does the protagonist make a decisive choice that reflects new belief. If a side character steals the final move, reassign agency.

Two checks:

• Track three moments where the misbelief causes harm. Without harm, no reason to change.
• Write the final choice in one sentence. If the line wobbles, the arc needs work.

Pacing

Anchor the inciting incident early. Aim for within the first 10 percent of word count. Mark act turns, midpoint, and climax. Every turn should raise stakes and narrow options.

Tools that help:

• Chapter length audit. List word counts for each chapter. Long, long, long often signals a sag. Vary rhythm. Alternate breathers with pressure.
• Time markers. Add a clock or a deadline when useful. A clear countdown focuses choices.
• Scene purpose test. Label scenes as gain, loss, or reveal. Long runs of reveal drain energy. Mix gains and losses.

Speed tune-up:

• Compress travel. One sentence can replace four pages unless pressure shifts during the trip.
• Collapse redundant beats. Three meetings to share the same news equals one meeting with a wrinkle.

POV control

Choose the right eyes for each scene. Stakes must land hardest on the POV holder. If a scene needs secret thoughts from two people, split the scene or move the switch to a clean break.

Distance matters. Decide how close the camera sits. Deep interiority uses fewer filter words. Watch for these: saw, noticed, felt, thought, realized. Replace with the thing itself.

Example:

• Weak: Mara realized the room smelled of smoke.
• Stronger: Smoke scorched the back of Mara’s throat.

Keep tense and person consistent. Head-hopping breaks trust. One POV per scene keeps focus.

Anchor trick:

• Add one sensory detail only the POV holder would notice. A scar twitch, a family smell, a private nickname. One line locks the frame.

Dialogue and exposition

Cut filler. Trim greetings, weather, and throat-clearing. Remove “as you know” lines. Subtext carries more weight than lectures.

Replace info dumps with dramatized revelation. Give a need, a price, and a choice.

Example shift:

• Dump: “Our magic drains life force. The council banned it in 1642 after three deaths.”
• Dramatized: The healer saves a child, then coughs blood into a cloth. A council notice lists three names and a date. A fine lands on the table.

Tighten speech:

• Shorten long monologues. Break with beats that show action.
• Give each speaker a distinct agenda. Want, tactic, obstacle.
• Read dialog aloud. Stumbles point to unnatural phrasing.

Two quick cuts:

• Remove one “well” or “so” from each page.
• Delete any line that repeats information from the previous five pages.

Worldbuilding continuity

Keep a living log for names, places, rules, and costs. A spreadsheet works. So does a document with quick headings.

Core lists:

• Timeline by day or week.
• Map or travel notes with distance and travel time.
• Rulebook for magic or tech with limits and costs.
• Naming patterns and honorifics.
• Research sources with page or link.

Continuity checks:

• Flag first use of each proper noun. Cross-check spelling and capitalization across the book.
• Verify time math. A three-day trek should not finish before lunch unless transport changes.
• Apply costs. Every use of a power draws the same price, unless the story shows a change with a reason.

For historical work, run a pass for anachronisms. Clothing, slang, food, transport, law. If a historical figure appears, log sources for each scene.

Market alignment

Match the book to reader promise for your shelf. Word count, structure, and ending expectations matter.

Guidelines, not handcuffs:

• Romance: central couple on-page, consent and heat level consistent, HEA or HFN. Word count often 70k to 100k.
• Mystery and thriller: fair clues on-page, red herrings, rising tension, clear timeline. Word count often 75k to 100k.
• Sci fi and fantasy: rules with limits and costs, jargon clarity, no early glossary dump. Word count often 90k to 120k.
• Historical: period voice, no modern idiom without cause, research woven into action. Word count often 80k to 110k.
• Literary and book club: strong interiority, image systems, purposeful ambiguity with forward motion. Word count varies, often 70k to 100k.
• YA and MG: age-appropriate voice, focused stakes, brisk pace, meaningful adult presence without takeover. Word count often 50k to 85k for YA, 30k to 50k for MG.

Pick three comp titles from the last five years. Note tone, structure, and trope use. List two reader promises those books keep. Check your manuscript against the same promises.

Final sweep:

• Opening signals genre promise.
• Midpoint shifts power or knowledge.
• Climax forces a choice with consequences.
• Resolution honors the opening promise.

Run this checklist. Then hand your editor a draft with clear goals, clean logic, and evidence of hard thinking. That groundwork invites deeper notes and a sharper plan.

Collaborating effectively with a developmental editor

Think of this as a partnership. You bring the story. The editor brings a trained eye and a process. A little prep turns that mix into momentum.

Set the brief

Give your editor a clear frame before they open page one.

• Non‑negotiables. Voice, theme, representation, tone lines you will not cross.
• Success metrics. How you will measure a strong result.
• Comps. Recent books or shows with a similar promise.
• Known friction. Where critique partners got lost or bored.

Sample brief you can paste into an email:

• Non‑negotiables: First‑person present stays. Bisexual rep stays. No sexual violence on page.
• Success metrics: Cleaner midpoint turn. Clearer villain plan. Beta readers report no confusion in the final heist.
• Comps: The Sun Down Motel for tone. Ninth House for structure.
• Known friction: Readers ask why Lina forgives Ben. Confusion about the timeline in Act Two.

One quick exercise. Write three things you refuse to lose. Then write two risks you want to take. Hand both lists to your editor.

Agree on communication

Decide how the work will happen, not only what will happen.

• Queries. Will notes arrive in a Word file with tracked comments, a Google Doc, or a separate memo. Agree on how you will answer questions in the margins.
• Call cadence. Book dates now. One kickoff call. One midpoint check. One debrief. Put them on a calendar.
• Response time. Set a normal window for replies. For example, two business days for short questions. A week for heavier asks.
• Follow‑up support. Ask what comes after the letter. One round of email Q&A. A one‑hour call. A read of a revised outline. Confirm in writing.

Margin etiquette saves time. If you ask a question, mark it with a Q. If you want a decision, mark it with a D. Sample note:

• Q: Does this reveal belong here or at the midpoint.
• D: Pick one motive for the aunt here. Grief or greed.

Manage feedback without drowning

Notes will conflict at times. That is normal. Your job is triage.

Use a simple three‑tier system:

• Tier 1. Breaks the book. Plot hole, missing motive, wrong POV, broken timeline.
• Tier 2. Strength move. Sharper scene purpose, cleaner arc beat, tighter setup for a twist.
• Tier 3. Preference. Line‑level phrasing, minor world flavor, small continuity nits you plan to fix later.

Start with Tier 1. Fix two or three scenes that carry the most load. Prove the approach on a sample chapter. Share that sample if you want a quick gut check before scaling.

Keep a change log. Nothing fancy. A list keeps your brain clear.

Change log example:

• 2025‑02‑10. Moved inciting incident to Chapter 2. Result, faster hook, cleaner setup for the mentor.
• 2025‑02‑12. Cut banker POV in Act Two. Result, tighter tension and less head‑hopping.
• 2025‑02‑15. Reworked Lina’s apology scene. Consequence now visible on page.

Give yourself a short cooling period before big choices. A day helps. Then return to the notes with a steady head.

Version control that protects your work

Protect the draft. Future you will thank you.

• File names. Include title, stage, version, and date. Example: Title_v3_DEV_2025‑02‑10.docx. For the next pass, bump the version number.
• Backups. Keep a live copy in the cloud and one on an external drive. Save at the end of each session.
• Tracked changes. Turn them on. Add a brief comment near large cuts or moves. Example: Moved scene to Ch 12 for fallout timing.
• Snapshots. Before you accept all changes, duplicate the file. Keep the old version on hand for comparison.

When you share a new version, include a short note on what changed and where to look. Editors read faster with a map.

Build support artifacts

A light set of documents speeds every pass and keeps continuity sane.

Style sheet. A running list for choices and rules.

• Spelling and hyphenation. email vs e‑mail. copyeditor vs copy editor.
• Capitalization choices. The Circle, the Order.
• Character data. Names, ages, pronouns, pet names, relationship links.
• Diction notes. Slang limits, regional terms, languages on page.
• Formatting. Inner thoughts in italics or not. Phone texts as block quotes or inline.

Story bible. The world and the timeline in one place.

• Calendar of events with day and time.
• Maps or travel notes with distances and routes.
• Magic or tech rules with costs and limits.
• Laws, customs, and taboo zones.
• Research sources with links or page numbers.

Scene list. The bird’s‑eye view.

• Columns for chapter, scene goal, conflict, outcome, POV, time of day, and setting.
• One line notes on turns. Reveal, gain, loss.

Share these with your editor or keep them internal. Up to you. Update them when you revise. If a rule shifts, add the reason. Future scenes must pay the same price.

Treat the collaboration like rehearsal, not a verdict. Show your intent, define the playbook, and track choices. You will get sharper notes and a steadier path to a stronger book.

From developmental edit to publication

You have a stronger story. Do not lose speed now. The next steps turn a solid structure into a finished book readers trust.

Sequence the next stages

Think in layers. Each stage fixes a different problem. Start at the top and move down.

• Structure lock. If scenes still shift or a subplot still wobbles, hold. Line work will get shredded by new cuts. Run a quick test. Summarize each act in one sentence. If those four sentences read clean, move on.
• Line editing. Focus on voice, rhythm, and clarity at sentence and paragraph level. Trim repetition. Sharpen beats inside scenes. Align tone across POVs.
• Copyediting. Fix grammar, spelling, punctuation, and style consistency. Apply your style sheet. Check continuity for names, timelines, and terms.
• Proofreading on designed pages. Read the book in pages that look like the final product. Catch dropped words, bad line breaks, widows and orphans, and odd hyphenation. This is not the time to move a scene.

A quick yardstick. If a note affects a chapter summary, it belongs before line editing. If a note affects a sentence, it belongs in line editing. If a note affects a comma, it belongs in copyediting or proof.

Querying vs. self‑publishing

Pick a lane. Tailor your work to fit the lane’s finish line.

Querying

You are pitching a promise. Your editorial letter holds the language for that promise. Use it.

• Query letter. One paragraph for the hook. One paragraph for the key conflict and stakes. One short bio line with relevant credits or comps.
• Synopsis. Two pages. Present tense. Spoil the ending. Hit the inciting incident, midpoint shift, climax, and resolution.
• Opening pages. Clean, precise, in line with the genre. No throat clearing. Anchor POV by paragraph two. Stakes on the page early.

Mini exercise. Write a one‑sentence logline. Character, goal, obstacle, consequence. Read it out loud. If you stumble, simplify. This sentence guides the query and the first page.

Send only once you have those three pieces tight. Agents read fast. Clarity wins.

Self‑publishing

You are running a production. Set your crew and your dates.

• Cover design. Brief with genre comps, tone, and core image systems from your edit. Supply a one‑line hook for the back cover.
• Formatting. Decide on print sizes and ebook formats. Ask for chapter openers, scene break marks, and text treatment for messages or spells in line with your style sheet.
• Metadata. BISAC codes, keywords, series name, series number, tagline, and back cover copy. Keep terms from your editorial letter’s positioning notes.
• Distribution. Pick stores and aggregators. Set preorder dates with enough room for proof, ARC, and upload buffers.
• ISBNs and copyright. Assign ISBNs per format. Deposit files where required in your country.

Set a light launch calendar. ARC send date. Final proof date. Upload deadline. Street date. Put those on a wall where you see them.

The beta loop, late stage

Run one more pass with targeted readers. Aim for five to eight people who read your genre. Not family.

Give them a tight brief. One page is plenty.

• What did you feel at the midpoint.
• Where did attention drop.
• Which twist felt earned. Which felt thin.
• Any lines or terms you had to read twice.
• One thing you loved. One thing you wanted more of.

Time box the read. Ten to fourteen days. Gather answers in a form or a shared doc. Do not rebuild the book here. Fix clarity and pacing only. If two or more readers flag the same scene, address it. If feedback conflicts, return to your goal and comps.

Sensitivity and subject‑matter checks

Bring in experts before line editing to avoid big rewrites later. Two common cases.

• Sensitivity readers. For culture and identity on the page. Share character sheets, key scenes, and any moments with potential harm. Ask for notes on stereotypes, language choices, and power dynamics. Pay them. Credit them if they agree.
• Subject‑matter experts. For technical accuracy. Medicine, law, guns, hacking, aviation, forensics, or any field with rules. Provide the scenes where the knowledge drives outcomes. Ask for plausible adjustments that preserve story stakes.

Give readers a clear scope, a deadline, and a way to mark issues by severity. Must fix. Strongly advised. Optional. Fold must‑fix notes in before line work.

Production readiness

Before you move to design, assemble the pieces that keep you sane.

Front matter

• Title page with author name and imprint.
• Copyright page with year, ISBNs, and rights line.
• Dedication and epigraph if you use them.
• Series list if this book sits between others.

Back matter

• Acknowledgments.
• Author note if context helps the read.
• About the author with website and newsletter link.
• Teaser chapter or link to the next book.
• Book club questions if that suits the genre.

Carry your style sheet and story bible into every handoff. Give the formatter rules for quotes, italics, small caps, scene breaks, and special text. Give the proofreader the style sheet and a list of known quirks, like foreign phrases, dialect, or invented terms.

Before upload, run a page check.

• Open the PDF or print proof. Scan chapter starts, page numbers, headers, and scene breaks.
• Flip through for odd hyphenation and rivers.
• Read the first thirty pages and the last thirty pages line by line. Error rates spike there.

If you plan ARCs, output clean files after copyedit and one proof pass. Send with a feedback form deadline and clear guidance on where to report issues. Final files lock after the proofread on designed pages.

Take a breath. You moved from a messy draft to a book with a spine, clean prose, and a plan to reach readers. Keep the discipline you built during the dev edit. It carries through launch and the next book too.

Frequently Asked Questions

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

Leave this empty

Get free book