Fantasy Book Editing

Gary Smailes | 1 November 2025

Why Fantasy Manuscripts Need Genre‑Savvy Editing

Fantasy multiplies risk. New worlds, new rules, new histories. Every layer introduces places for cracks to form. A spell works one way on page 40, a different way on page 240. A city faces east in the prologue, then a sunset shines through the same gate. Readers track these details with hawk eyes. An editor with fantasy mileage keeps the whole machine aligned.

Reader expectations steer the work from the first read to the last proof. Maps, appendices, coherent rules, and payoffs that honor promises. Developmental feedback checks rule logic, cost of magic, and plant‑payoff chains. Line editing trims lore that clogs a scene, sharpens terms, and keeps tone aligned with subgenre. Copyediting locks capitalization for Orders and Artifacts, firms up spelling for invented words, and catches that stray “High Priest” versus “high priest.” All three stages serve the same goal, trust. Readers feel safe when the rules hold.

Subgenre choice shapes every decision. A quick tour:

• Epic fantasy. Big casts, wide geography, long arcs. Often longer word counts, think 120k to 180k.
• Grimdark. Moral gray, graphic stakes, iron laws with ugly costs. Tighter hope budget.
• Sword and sorcery. Focused quests, fast pacing, monster‑of‑the‑week energy. Often 70k to 100k.
• Urban fantasy. Contemporary settings, snappy voice, series‑friendly hooks. Often 80k to 110k.
• Portal fantasy. Outsider learns rules on page, careful with tutorials, strong sense of wonder.
• Gaslamp. Victorian‑adjacent tech, manners, and occult. Period voice without museum dust.
• YA fantasy. Teen lens, interior stakes, brisk momentum. Often 75k to 100k, plus content guidelines.

Pick with intention. A grimdark tone glued to a whimsical quest reads false. A 180k portal debut faces extra friction in queries. Subgenre alignment gives you a target and an editor a playbook.

Continuity sits at the core. Magic needs laws, limits, and costs. No freebies in the climax after chapters of caution. Politics and logistics need weight. Who feeds the army. How long a raven message takes. What a week looks like on a thirteen‑month calendar. Even names need rules. Decide on honorifics, apostrophes, and diacritics early, then keep those choices stable. A style sheet and a world bible turn guesswork into consistency.

Series planning starts on page one. Seeds, arcs, and rules must survive growth over multiple books. A throwaway “last winter’s plague” becomes a timeline trap two books later. A prophecy line boxes your ending if phrased too tight. Plant with care. Pay off with precision. Keep a ledger for core laws, historical milestones, lunar cycles, and invented units. Series readers re‑read, then cross‑check. Respect that investment.

Two quick snapshots of problems editors see every week:

• A duel shows fire magic burning out at three blasts, then a siege runs twenty blasts without fallout. Fix at the rule level, then hunt every battle for similar leaks.
• A map shows two rivers crossing, then the text sends a barge upstream across both in one day. Fix the map or the travel plan, then align every time check.

Action for this week:

• Pick 3 to 5 current comps from your shelf, same subgenre and audience.
• Name your subgenre with confidence.
• Set a target word count that matches that shelf.
• Write a one‑sentence magic promise. State power and cost in one breath.

Examples:

• Blood magic buys one hour of strength per cut, and shortens the user’s life by one day.
• Names bind spirits only once, and the name‑giver loses the sound from memory forever.
• Light sigils remake matter, and each sigil burns a permanent scar in the caster’s skin.

Tape that promise above the desk. Share it with your editor. Every scene should honor the rules or show a price for breaking them. That discipline builds trust, then trust carries readers through the strangest parts of your world.

Developmental Editing Priorities for Fantasy

Fantasy rewards ambition, then punishes sloppiness. New rules invite new loopholes. Strong developmental work closes those gaps and lifts the story where readers feel most picky, magic and meaning.

Structure and stakes

Start with a clear goal for the protagonist, something visible and pressing. Stack rising complications. Mark a midpoint shift where pursuit changes form. Drive toward a darkest moment that forces a new price. End with a climax that honors the world’s rules. No deus ex machina. If blood magic drains a year of life in chapter five, the same cost applies during the final duel.

Quick exercise:

• Write the protagonist’s external goal in ten words or fewer.
• Name the consequence for failure in one line.
• Describe the midpoint decision in one sentence, not plot, choice.
• Define the final price paid at the climax.

If any box feels vague, the story wobbles. Tune before line work.

Exposition control

Readers love lore, then bail when a scene stops for a lecture. Share information only when a character’s choice hangs on that information. Present discovery on the page.

Swap this:

• “The Seven Guilds once ruled the city. Guild marks on the wrist track debt going back four hundred years...”

For this:

• A bouncer scans a glowing tattoo, blocks the hero, and says, “Debt holders queue in the alley.”

Now the rule lives in action. The scene still moves.

Audit pass:

• Highlight any paragraph of backstory longer than three lines.
• For each highlight, write the choice affected in the scene.
• No linked choice, move that lore later or fold into behavior or setting detail.

POV and scope

Pick single or multiple POV with intention. One POV offers focus and tight intimacy. Multiple POV widens the map, yet risks repetition. No head hopping. Readers should always know whose skin they occupy.

Test for multiple POV:

• For each POV character, write one line with desire, lie, and a decision only this character makes.
• Duplicate roles, merge or drop a lens.
• Each POV earns unique settings, relationships, and thematic weight.

Scope ties to subgenre. Epic often uses several threads across distance. Sword and sorcery thrives with a lean lens. Urban leans voicey and close. Match scope to promise.

Antagonism and conflict

Villains and systems deserve competence. Guards learn after a first break‑in. Wards adjust. Rivals plan two moves ahead. Conflict grows through consequences, not louder shouting.

Raise costs of magic over time. Each use should mark the user, body, reputation, or alliances. Add moral pressure. Save one child or the city. Take power and lose trust. A choice that bites harder than a new spell level lands with readers.

Practical ladder:

• After every win, add a scar, a debt, or a public setback.
• After every loss, add new knowledge or a narrow path forward.
• Repeat with increasing stakes.

Prologues and prophecy

Prologues work when they spark tension for chapter one. A murder viewed by the future antagonist. A forbidden ritual witnessed by a child who appears in scene two. No centuries‑long history lecture in a robe.

Prophecy should increase pressure, not erase choice. Vague lines invite interpretation and missteps. Hyper‑specific lines chain the finale to a single trick.

Tests:

• Prologue relevance visible by the end of chapter two.
• Prophecy creates new problems for the hero, not answers.

Series scaffolding

Plan seeds that sprout over volumes, while finishing a book‑level arc with a clean yes or no. Tease a wider war, yet resolve this campaign. Plant and payoff require a ledger.

Trackers to build now:

• Chekhov’s guns, who saw them, where they reappear.
• Magic laws and costs, with scene references.
• Historical dates, rulers, wars, moons, holidays.
• Name lists for Orders, Houses, and artifacts, with capitalization choices.

Series risks: throwaway lines turn into traps later. “Last winter’s plague” locks timelines. “No one crosses the Frostmere” blocks a future plot unless groundwork shows a rare way through. Flag these lines during revision and confirm support before book two.

Action steps

Scene‑by‑scene purpose test:

• Write a one‑line answer for each scene, “What changes?”
• No change, combine with a neighbor or replace with a beat that triggers a new problem, decision, or revelation.

Beat sheet:

• Map inciting incident, first doorway, midpoint, second doorway, darkest moment, and climax.
• For fantasy romance, add beats for meet, push‑pull, break‑up, and grand gesture.

Travel control:

• Compress or cut campsites and road days without new conflict.
• If the journey matters, bake in a challenge or a choice. New terrain, a toll, a betrayal, a clue.

Strong developmental work saves months later. Fewer rewrites. Cleaner promises. A world that holds pressure from first page to last.

Worldbuilding, Magic, and Continuity Systems

Fantasy asks readers to trust a made world. Earn that trust with rules, receipts, and a paper trail. Dream big, then document.

Magic systems

Magic needs laws, limits, and costs. No free wish list. If a spell heals, what goes unpaid elsewhere? Time, stamina, memory, reputation, rare materials, a favor owed. Pick a cost with teeth and stick to it across chapters.

Hard magic, rule bound, invites clever puzzles. Readers expect solutions to grow from known rules. Soft magic, mysterious, suits awe and dread. Use for tone and trouble, not last‑minute rescues. Align the story’s big turns with the approach you promise.

Examples:

• Teleportation: works only to marked rooms, leaves nausea, burns rare incense. No mark, no jump.
• Necromancy: wakes the dead for one question, steals a day of the caster’s life. Abuse leaves visible aging.
• Firecalling: draws heat from nearby sources, chills allies, cracks stone floors. A win warms no camp.

Mini exercise:

• Write three laws your magic never violates.
• List one hard limit.
• Pick one cost that escalates with overuse.
• Name two plot problems solved by magic. Note the paid cost on the page, not in notes.

If a late chapter breaks a rule, raise a flag. Either seed support earlier or remove the cheat.

Societies and logistics

Readers track wagons, coins, and seasons without trying. Give the story plausible scaffolding.

Sketch:

• Economy: who farms, mines, trades, taxes. What shortages shape choices.
• Politics: rulers, councils, guilds, who enforces law.
• Religion: public rites, private taboos, feast days that interrupt plans.
• Ecology: climate, crops, beasts, migration, storm seasons.
• Tech level: roads, boats, siege engines, printing, medical care.
• Calendars and time: months, week names, holidays, leap logic.
• Distances and travel: road quality, river routes, mountain passes. Travel time on foot, horse, wagon, air.

Quick plausibility check:

• Mark two towns on a map. Note river direction, prevailing wind, and terrain.
• Estimate travel for a trader, a messenger, an army. Select different speeds. Adjust plot beats to match.
• Where supply lines break, add a new problem. Food runs low. A bridge toll drains purse and patience.

Small details earn trust. A night market at harvest. A curfew after a riot. Wet boots after a bog.

Naming and language

Names carry tone and cohesion. Pick rules, then follow them.

Guidelines:

• Set phonetic patterns by region or culture. Three or four letter clusters used across a family line hint at shared roots.
• Keep titles and honorifics consistent. Decide on King vs king, High Priest vs high priest, Sir vs Ser, then log choices.
• Keep apostrophes and diacritics rare. Readability beats flourish. Save marks for a language with purpose on the page.
• For conlangs: limit to key terms with context. Gloss in dialogue or action, not a footnote mid‑scene.

Mini test:

• Read ten names out loud. Mix nobles, commoners, cities, Orders.
• If your tongue trips or patterns clash, revise the list before deeper edits.

Consistency controls

Memory lies. A system remembers.

Build a world bible:

• Geography: maps, climate zones, trade routes, border disputes.
• Society: government terms, ranks, currency, legal punishments.
• Magic: laws, costs, exceptions seeded, limits by location or season.
• Lore: myths, folktales, holidays, insults, swears.
• Creatures: behavior, diet, tracks, weaknesses.

Create a glossary and timeline:

• Glossary: invented terms, artifacts, Orders, place names, plural forms.
• Timeline: births, reigns, wars, treaties, migrations, natural disasters. Scene dates as you draft.

Style sheet:

• Capitalization choices, hyphenation, preferred spellings, numerals, units.
• Notes for typography: italics for incantations, small caps for ancient script, bracket style for telepathy.

Use search tools:

• Build a list of risky pairs: daemon vs demon, gray vs grey, adviser vs advisor.
• Run checks before copyediting begins.

Sensitivity and authenticity

Cultures breathe. Avoid one‑note portrayals. No single trait defines a people. Food, music, clothing, law, quarrels, humor, grief, and joy, all sit together.

Credit inspirations. If you borrow from a real history or living culture, say so in acknowledgments. Better, invite guidance.

Bring in readers with lived experience:

• Sensitivity readers for culture, disability, queerness, faith, or trauma themes.
• Subject experts for history, ecology, weaponry, sailing, language.

Common red flags:

• Exoticized names only for outsiders.
• Villainy linked to skin tone or facial features.
• Spiritual systems lifted whole without context.
• Gender roles frozen without internal debate.

Aim for nuance. Mixed neighborhoods. Intermarriage. Regional slang. Minor holidays nobody agrees on.

Paratext

Support the story with useful extras, not crutches.

• Maps: match river flow, mountain ranges, scale, and travel claims in the text. Place a compass rose. Label only what readers meet.
• Dramatis personae: core cast, houses, roles. Keep it crisp.
• Pronunciation guide: only where needed. Use simple hints.
• Appendices: magic rules, Orders, short timelines. No spoilers. No replacement for on‑page drama.

Print and ebook need to survive together. Ornaments, glyphs, and special characters should render cleanly across devices. Keep access in mind for screen readers.

Action steps

Rule break audit:

• List every scene where magic solves a problem.
• Next to each, write the cost paid in scene.
• No cost logged, fix the scene or revise the system.

Searchable records from draft one:

• Maintain a living glossary, timeline, and style sheet.
• Update after each session.
• Back up in two places.

Two quick passes before feedback:

• Logistics pass: mark travel times, supply issues, weather shifts.
• Naming pass: highlight first mentions of invented terms. Add context within two sentences.

Worldbuilding earns applause when readers forget they are tracking rules. Give them a world that stands up to questions, then invite those questions with confidence.

Line Editing for Immersion and Readability

Line edits are where readers fall in or fall out. Scene by scene, sentence by sentence, you either guide them forward or leave them squinting in the dark. Aim for grip and glide. No haze.

Clarity first

Anchor who, where, and when in the first two lines of every scene. If readers wonder whose head they are in, they are not in the story.

Before:

Moonlight pooled on old stones as footsteps approached.

After:

Moonlight pooled on the east wall of Blackfen Keep. Mara crouched behind the cistern as two guards clanked past the arch at midnight.

Name the space. Name the actor. Give a time cue. If a character’s goal is live in the scene, drop a hint of it.

Prune purple fog. Flowery clauses that slow action or bury emotion help no one.

Before:

A serpentine ribbon of dawn, kissed by the benediction of ages, unfurled upon the hallowed city as her soul danced with ineffable destiny.

After:

Dawn bled into the city. Her hands shook. Today she would face the council.

Quick test:

• Highlight the first two sentences of each scene. Mark who, where, when, and goal.
• If any box stays blank, revise until filled.

Description with intent

Description earns its keep when it alters decisions, tone, or stakes. Lists of banners and brocade only burn pages.

Before:

The hall boasted seven tapestries, four chandeliers, and a dozen marble busts, each rendered with uncanny artistry.

After:

Seven tapestries hung heavy in stale air, all stags, antlers gold. The new stag bore a crown. The rebels had lost this city.

Tie detail to pressure. Use senses that change choices. Smoke that stings eyes. Stone that steals heat. Bells that force a halt to hide.

Mini exercise:

• In one scene, underline every descriptive noun. Circle three that shape a decision. Cut three that do not.
• Replace one static sentence with a sensory beat tied to goal. Example: Instead of describing the market, have a fishmonger shove a salted cod into the protagonist’s hands, staining a letter she needs to present clean.

Combat and choreography

Fights reward clarity over coolness. Keep space, time, and cause and effect in a clean line.

Before:

He pivoted, stepped, punched, pivoted again, grabbed, twisted, stepped, leaned, spun, sliced, ducked, raised, brought his arm down with a mighty cry.

After:

Tomas slid left, steel scraping stone. The ogre’s club smashed the pillar. Dust blinded him, and he dropped to one knee. When the swing came back, he drove his knife into the exposed wrist.

Map the scene on a sticky note. Where is everyone at the start. Where are they after each major beat. If a character teleports between lines without on‑page movement, fix the gap.

Checks:

• Who can threaten whom right now.
• What changes after each beat.
• One sentence per meaningful action. Remove micromotions. Blinked. Turned. Adjusted grip. Save those for rhythm, not as a running tally.

Read fights aloud. If you run out of breath, the reader runs out of patience.

POV integrity, voice, and diction

Stay inside the chosen skull. Keep language aligned with the character’s age, background, and mood.

Filter words drain immediacy. Consider trimming saw, heard, felt, noticed, realized when the focus stays clear without them.

Before:

She saw the hawk dive and felt fear rise.

After:

The hawk dropped. Her throat went dry.

Do not exile every filter word. Use one when needed to guide distance or avoid confusion.

Invented terms belong, but only with context close by. Supply the meaning within two sentences.

First use example:

The akhar bells tolled, thin and sour. By dusk, every shop would shutter, and the watch would drag debtors to the square.

Match register to subgenre and setting. A street thief should not sound like a court historian unless pretending to. If slang appears, build it from the world, not from modern memes.

Mini exercise:

• Pick one chapter. Mark any word a twelve‑year‑old outside your world would not know. Check that the surrounding text grounds it fast.
• Swap one grandiose sentence for ten plain words that punch.

Dialogue and tags

Readers skim tags, so keep them simple. Said does the job. Action beats carry weight.

Before:

“By the frozen stars of the Ancients,” the Captain snarled viciously, “you cur, you’ll rue this day.”

After:

“By the frozen stars,” the captain said. He pulled on his glove. “You’ll rue this day.”

Limit invented swears and titles. One or two signature oaths per culture read sharper than a grab bag. Capitalize titles by rule, not by mood, and log the decision.

Handle dialect with a light hand. A hint in syntax or one repeated vowel reads better than wholesale phonetic spelling.

Dialogue checks:

• Each speaker sounds distinct without name tags in every line.
• Beats reflect culture and status. A prince does not shrug through a council. A mercenary does not bow like clergy.
• No speech dumps that tell lore the speaker would not share in that moment. Put knowledge where it belongs.

Typography choices

Make typography serve story and readability.

• Italics: pick one use for telepathy or incantations and stick to it.
• Foreign or old tongue: italics on first use only, or not at all. Decide and record.
• Orders, Houses, Artifacts: choose capitalization rules. The Order of Embers, but order when used generically.
• Sound cues and onomatopoeia: sparing use. Screen readers need clear text.

Style sheet snippet to record:

• Telepathy in italics. Spoken spells in roman type.
• King capitalized when used with a name or as address. Lowercase as a role in general use.
• Compass points lowercase, except for The North as a region name.

Action steps

Readability pass on lore‑heavy chapters:

• First three paragraphs. Confirm who, where, when, and goal live on the page.
• Underline each invented term. Add a context clue within two sentences if missing.
• Replace one encyclopedia sentence with an action that reveals the same fact.

Action scenes aloud:

• Read with a metronome or clap the beats. Cut any motion that does not change advantage, injury, or position.
• Track pronouns. If you lose the subject, the reader will too.

Highlight to trim:

• Filters in clusters: saw, heard, felt, noticed, realized.
• Micromotions in clusters: blinked, sighed, turned, nodded, smiled, began to, started to.
• Adjective stacks: pick one strong noun or verb instead.

Finalize typography and capitalization:

• Decide on italics rules for magic and telepathy.
• Pick capitalization for Orders, Houses, Artifacts, and titles.
• Add every choice to a living style sheet.

Line editing is hospitality. You open the door, hang up the coat, and lead readers to the seat with the best view. Give them a clear path, and they will follow you anywhere.

Copyediting, Proofreading, and Production Extras for Fantasy

Copyediting keeps your book clean, consistent, and readable. Fantasy adds invented words, map labels, runes, and wonky plurals. So the rules need to be clear and written down. Then you follow them to the last page.

Build a real editorial style sheet

Make decisions once. Record them. Hand the sheet to every helper on your team.

What to include:

• Spelling and plurals for invented words. Drak, draks. Aezir, Aeziri.
• Capitalization rules. The Order of Ash. An order of spies.
• Titles. High Priest as address. The high priest as a role.
• Numerals and units. Spell out one to nine, then digits. Leagues, spans, moons. Coin denominations and symbols.
• Hyphenation. Half blood, half-blood, halfblood. Pick one.
• Diacritics. Aréne every time, not Arene on Tuesdays.
• Foreign words and old tongue. Italicize on first use or never. Decide.
• Formatting for magic. Spells in small caps or roman. Telepathy in italics or roman.

Note special typography needs:

• Runes or sigils. Vector art or a font with full licensing. Record the size, weight, and placement rules.
• Scene break glyphs. Which glyph, what size, and how it behaves in print and ebook.

A quick snippet might look like this:

• Demon, not daemon.
• King capitalized before a name or as address. Lowercase otherwise.
• The North as a region, capitalized. Directions lowercase.

Map and lore alignment

Your text and your map must agree. Readers will check.

Run a simple audit:

• Spelling of place names matches the map labels.
• Rivers flow downhill. Mountain chains look like real geology, not a fence of triangles.
• Compass rose matches the story. If the harbor faces east, we need sun on the water at dawn, not dusk.
• Travel math holds. If a party covers two hundred miles in three days on foot, the terrain must explain the pace. Or the text must.
• Weather and seasons line up with latitude and altitude. Snow on the pass in summer needs a line to sell it.

Map scale tip:

Take a journey you describe. Measure it against the scale bar. If your time in days does not match your words in miles, adjust one of them. Do not hope no one notices. Someone will.

Glossary and back matter

Back matter helps, but it is not a rescue boat for weak scenes. Keep it lean and useful.

Glossary:

• Define terms in one clean line. No spoilers. Mage-seal, a red wax mark used by court mages to bind contracts.
• Pick a pronunciation style. Simple respelling beats jargon. Ay-zer, not IPA strings few readers can parse.
• Cross-reference sparingly. House Ember, see Orders.

Dramatis personae:

• List major players with one tag each. Name, role, one anchor fact. Liora Maren, smuggler, twin to the captain.

Timeline:

• Hit the big beats. Founding of the city, the plague year, the treaty. Date format consistent with the world’s calendar.

Appendices:

• Rules for magic if the plot hinges on them. One page. Do not dump a manual.

Consistency passes

Small errors break trust fast. Run targeted checks.

Common traps:

• Variant spellings. Demon or daemon. Grey or gray. Pick and police.
• Name drift. Is it Liora or Leora in chapter 18.
• Titles. High Priest of Embers on first reference, the high priest after. Log exceptions, like formal letters.
• Weapons and gear. Saber in one scene, sabre in the next. Ironwood vs iron-wood.
• Numbers. Ten thousand or 10,000. Pick a rule and stick to it.

Painful homophones:

• Reign, rein, rain.
• Hoard, horde.
• Peal, peel.
• Palate, palette, pallet.
• Brake, break.
• Vial, vile.

Set a search list and sweep your files.

Series alignment:

• Keep a second sheet for series rules. Ages, scars, eye color, mount names, signature spells, dates. Add a page for oath words and hand signs if your world uses them.

Proofreading on designed pages

Proof on the design. Do not rely on the Word doc. Layout changes introduce new errors.

Print book checks:

• Page headers and footers correct on recto and verso.
• Scene break glyphs appear where intended. No missing breaks.
• Chapter ornaments render cleanly at print size.
• Ligatures work. fi and fl do not drop out.
• Widows and orphans flagged for the designer. One-word last lines patched.
• Quotation marks and apostrophes curly, not straight. No stray doubles in dialogue.
• Dashes and hyphens consistent with your style sheet. No double spaces after periods.

Ebook checks:

• Test EPUB and MOBI on multiple devices and apps. Phone, tablet, dedicated e-reader.
• Scene breaks survive reflow. No blank-page deserts.
• Special characters and diacritics display across platforms.
• Small caps, if used, render as true small caps or fall back gracefully.
• Linked table of contents works. Back matter links jump to the right place.
• No images used to display important text. That includes runes with plot value.

Accessibility

Make choices that help every reader.

• Do not bury key lore in images. Describe in text or provide alt text.
• Use ornaments that have a text fallback. Asterisks or a blank line with role markers in the EPUB.
• Contrast and size. Pale gray text on black looks cool and reads poorly. Keep body text legible.
• Avoid long blocks of italics. They can strain readers. Use sparingly for telepathy or incantations.
• Keep hyperlink colors readable against both light and dark modes.

Quick test:

• Run your EPUB with a screen reader. If it trips over an image break or a spell, add proper tags or a text cue.
• Zoom to 200 percent on a phone. If the layout breaks, adjust CSS or font choices.

Action steps

Before copyediting:

• Assemble a master term list and map labels. Pull from the manuscript and the art files.
• Lock your capitalization and numerals rules. Put them on page one of the style sheet.

During copyediting:

• Run a dedicated search for homophones and name variants. Use wildcard and regex if needed.
• Mark every place name and title on first use. Check against the style sheet.

Before proof:

• Export a PDF from the typesetter and proof on paper with a ruler. Then proof the EPUB on three devices.
• Verify every scene break, ornament, diacritic, and special glyph in both formats.

After proof:

• Fix the files, then spot check those fixes. Do not trust a global change.
• Update the style sheet with any new decisions. Save it for book two.

Copyediting and proof are the last hands on the baton before you pass it to readers. Do the dull work with care. The magic reads sharper when nothing else gets in the way.

Workflow, Tools, and Team for Fantasy Authors

Fantasy editing is not a straight line. You need the right sequence, the right tools, and the right people. Get these wrong and you will pay in time, money, and reader trust.

The editing sequence that works

Start here: manuscript assessment (optional but wise) → developmental edit → line edit → copyediting → typesetting/ebook formatting → proofreading.

Manuscript assessment gives you the big picture before you commit. A good assessor reads your full manuscript and delivers a 3-5 page letter identifying the strongest elements and the problems that need fixing. Think of it as a map before the journey. Skip it if you are confident about structure and pacing. Do not skip it if this is your first fantasy novel or if beta readers gave conflicting feedback.

Developmental editing fixes story problems. Structure, character arcs, pacing, worldbuilding gaps, magic system holes. Your editor reads for the forest, not the trees. Expect an editorial letter (5-10 pages) plus margin comments. Plan for major revisions. This stage hurts but it saves your book.

Line editing polishes prose and flow. Sentence rhythm, word choice, clarity, voice consistency. Your editor reads paragraph by paragraph, fixing clunky transitions and purple prose. Moderate revisions expected.

Copyediting catches grammar, spelling, punctuation, and consistency errors. Your editor creates a style sheet and flags every variant spelling of "grey/gray" and "daemon/demon." Light revisions only. Do not add new scenes here or you create ripple errors.

Typesetting and ebook formatting happens after copyediting. The designer lays out your print book and builds your ebook files. They handle fonts, margins, chapter breaks, and special characters.

Proofreading finds the errors that survived everything else. Missing quotation marks, bad page breaks, typos introduced during layout. Your proofreader works on the designed pages, not your Word file.

Do these steps in order. Do not skip copyediting to save money. Do not combine line editing and developmental editing to save time. Each stage has a job. Let it do that job.

Tools that scale with your ambitions

Scrivener beats Word for fantasy manuscripts. Use collections to group scenes by POV, timeline, or magic use. The research folder holds character sheets, maps, and world notes. Compile to different formats without losing your structure.

Plottr or Aeon Timeline handles complex chronologies. Fantasy authors juggle multiple character arcs, prophecies with long payoffs, and political events that span decades. A visual timeline prevents you from aging your characters backward or having winter last eighteen months.

World Anvil organizes everything about your world. Characters, locations, cultures, religions, magic systems, timelines. The free tier handles most indie projects. Pay for more storage if you plan a long series. Alternative: a well-organized Google Drive folder with spreadsheets. Less pretty but cheaper and more portable.

Search and regex lists catch consistency errors. Build a list of variant spellings, character names, and invented terms. Run searches before each editing pass. Example list: gray/grey, advisor/adviser, towards/toward, Liora/Leora, mage-born/mageborn, traveling/travelling.

Version control prevents disasters. Save a dated draft before major revisions. Keep a change log: "Draft 3.2: Cut the prophecy subplot, added Kael's backstory, revised the magic system costs." Google Drive, Dropbox, or GitHub for Writers work. The method matters less than using one consistently.

Style sheets grow with your series. Start with book one. Track capitalization rules, character descriptions, place name spellings, magic system terminology. Hand this sheet to every editor you hire. Update it after each book. By book five, this sheet is gold.

Specialist help that prevents late rewrites

Sensitivity readers review your manuscript for harmful stereotypes and cultural missteps. Hire them after developmental editing but before line editing. Pay them. Give clear deadlines and guidelines about what you want feedback on. Do not hire one person to represent an entire culture or identity. Get multiple perspectives.

Subject matter experts check your research. Medieval warfare, horseback travel, blacksmithing, sailing, astronomy, linguistics. Find them through writing organizations, university departments, or professional associations. A historian who specializes in medieval warfare costs less than rewriting three battle scenes after publication.

Cartographers create maps that support your story instead of confusing readers. Rough sketches work for early drafts. Professional maps matter for publication. Budget $200-800 depending on complexity and style. Brief your cartographer on the key locations, travel routes, and scale requirements before they start.

Conlang consultants design constructed languages that feel authentic. You do not need a full language for most fantasy. You need consistent naming patterns, plausible grammar rules, and a few dozen vocabulary words. Budget $300-1500 depending on scope. Alternative: study real languages that match the feel you want and adapt their patterns.

Beta readers test your story on actual readers. Recruit 5-8 people who read your subgenre. Give them a deadline and specific questions. "Did the magic system make sense? Which POV character felt strongest? Where did you get confused?" Thank them publicly and send advance review copies when the book launches.

Hiring editors who get fantasy

Genre experience matters more than credentials. An editor who has worked on fifty contemporary novels might miss the worldbuilding gaps that tank your fantasy. Ask for their fantasy client list. Read samples of their work. Check if they understand magic systems, multi-POV structure, and series arcs.

Request a sample edit of 1500-3000 words. Pay for it. This sample shows you their editing style, communication approach, and understanding of your story. A good sample edit catches real problems and suggests workable solutions. A bad one nitpicks commas while missing plot holes.

Clarify deliverables upfront. What format will you receive? Editorial letter plus annotated manuscript? How detailed will the margin comments be? Do you get a second pass to review your revisions? What happens if you need an extra week to complete revisions? Pin down these details before you sign.

Budget for multiple rounds. Developmental editing often requires revision and a follow-up review. Line editing might need a light second pass. Copyediting always needs proofreading after typesetting. Plan for these costs from the start. A $2000 developmental edit that includes revision review beats a $1200 edit that leaves you hanging.

Check references and reviews. Ask editors for client references. Look for reviews on Reedsy, ALLi, or other professional platforms. Red flags: no references provided, only glowing testimonials, promises that sound too good to be true.

Project management for multi-book series

Build a milestone calendar. Mark when you need the editorial letter, how long you have for revisions, when the follow-up check happens. Buffer time for unexpected problems. Life happens. Characters decide to do things you did not plan. Magic systems reveal plot holes. Build slack into your schedule.

Budget for extra rounds. Developmental editing often needs a second pass after major revisions. Copyediting might need updates after late changes. Proofreading sometimes catches errors that require typesetting fixes. Budget 20-30% more than the base editing cost to handle these extras.

Maintain a living series style sheet. Start with book one. Track character ages, physical descriptions, relationships, world rules, magic costs, place name spellings. Update after each editing round. By book three, this sheet prevents continuity errors that take weeks to fix.

Lock major decisions early. Magic system rules, world geography, character backstories, political structures. Change these after book two and you create series-wide continuity problems. Small adjustments are fine. Major retcons require editing all previous books.

Plan series arcs during book one editing. Your developmental editor should help you identify which threads need to continue, which characters need future growth, and which world elements require deeper exploration. This planning prevents you from writing yourself into corners or dropping plot threads readers expect you to resolve.

The editing process for fantasy is longer and more complex than for contemporary fiction. Plan accordingly. Budget accordingly. The payoff is a book that works on every level and a series that keeps readers coming back.

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