Genre Specific Editing: What Fantasy And Sci Fi Writers Should Know

Gary Smailes | 5 November 2025

What SFF Editing Prioritizes

You build two machines at once. A world and a story. Editing lines them up. If rules, timelines, or terms drift, readers stop trusting the page. They forgive oddness. They do not forgive wobble.

Keep world, character, and promise aligned

Worldbuilding gives limits. Character arc gives need. Genre promise gives shape. Editing keeps those three in sync.

Examples fix things faster than theory:

• Teleporters require fuel in chapter two, then work free in chapter eight. Add a refill scene, or show a hack with a cost.
• A blood oath binds speech early on, then a prince lies with no fallout. Insert the telltale sting on his tongue or show a loophole you seeded before.
• A colony spans two suns, yet school runs eight-to-three, Earth style. Adjust bell times, sleep cycles, and street light cues.

Quick check:

• List top five rules for magic or tech. Add costs and failure modes for each. Tie at least two plot turns to those costs.
• Track the hero’s need across acts. Where does the world block it. Where does the world help. If the world never pushes back, stakes feel hollow.
• Name your promise in one line. Example: A rogue linguist saves a fleet using banned grammar. Every edit choice should serve that promise.

Subgenre yardsticks

Different shelves invite different tests.

Hard science fiction

• Plausibility with receipts. Numbers, models, constraints. Orbits honor physics. Energy budgets keep power in check.
• Ask: Where does heat go. What breaks first. What tradeoff hurts the most.

Epic fantasy

• Internally consistent systems. Magic with limits. Geopolitics with supply lines and culture. Power shifts ripple through guilds, faiths, and borders.
• Ask: Who feeds the army. What ritual fails during drought. Which law binds a king.

Space opera and urban fantasy

• Pace and voice do the heavy lifting. Big hearts, big set pieces, clean through-lines. Quips earn space only when they move motive or plot.
• Ask: Does every scene drive momentum. Does the voice guide without snark fatigue. Do reveals land clean.

Stand in the reader’s shoes. A physics grad will stress-test thrust equations. A fantasy lifer will sniff out coinage, calendars, and court etiquette. A thriller fan in space wants sleek chapters and clear stakes. Edit with that lens.

Onboard readers without dumping

Early pages must teach terms, stakes, and social order, but no lectures. No “as you know, Captain” chats. No four-page history prologue before anyone wants it.

Better moves:

• Anchor first. Give who, where, and goal in the first paragraph. Then layer one alien term, not five. Show meaning in use.
• Use status play. A rookie breaks a taboo. A veteran corrects them with a few words and an action. Lesson learned in motion.
• Lean on concrete nouns. Oxygen ration chit. Hex-key seal. Salt circle. Readers read through jargon when context carries weight.
• Time explanations with need. Put a short explainer at a decision point. One or two lines. Then let consequences teach the rest.

A trick from the edit room: print your first chapter. Highlight sentences that teach the world. Another color for sentences that move plot or reveal character. If teaching outweighs story, cut or move some info to moments where a choice depends on it.

Red flags:

• Glossary front-loaded with three pages of terms. Move it to back matter if you include one at all.
• Scene built to deliver a lecture. Replace with a problem scene where knowledge alters the outcome.
• A hero who narrates their own expertise in big blocks. Have someone challenge them. Let resistance shape the lesson.

Action: Draft an editorial brief

Give your future self a map. A one-page brief saves months of churn. Fill this out before revisions.

• Target reader. Name an age range, genre habits, tolerance for jargon, favorite vibes.
• Subgenre. Epic fantasy, space opera, cyberpunk, climate SF, gaslamp fantasy, or another clear lane.
• Tone. Hopeful, bleak, sardonic, lyrical, punchy.
• Promise. One line on what readers will follow and care about.
• Science or magic hardness. Where you sit on the hard-to-soft spectrum. State non-negotiables.
• World pillars. Power sources, travel, economy, social order, faith, flora, fauna, or tech families.
• Off-limits moves. No time travel. No prophecy. Or list twists you refuse.
• Series intent. Standalone or book one. Threads left open by design.
• Content notes. Violence level, body horror, medical detail, bigotry on page, romance heat.
• Success test. Three signs you delivered. Example: Climax uses rule X at full cost. Antagonist motive stays legible. Readers never stall in chapter one.

Sample snippet

• Subgenre: Hard SF salvage thriller
• Promise: A diver recovers a cursed drive from a derelict near Venus, then weighs profit against crew survival
• Hardness: Physics obeyed, speculative materials flagged as unknown

Action: List three comps and map their beats

Pick three recent titles on your shelf. One close cousin, one aspirational hit, one outlier with a tone you love. Map their core beats to calibrate pace and scope.

Do this for each:

• Opening signal. What promise lands by page ten.
• Onboarding method. How terms roll out without dumps.
• Midpoint shift. What truth or cost flips the plan.
• Climax engine. Which rule or limit bites. What choice seals fate.
• Scene length and chapter rhythm. Short, long, or mixed. How cliffhangers work.
• Voice notes. Humor level, metaphor use, sentence length, slang.

Example

• The Expanse, Leviathan Wakes. Promise by page ten: noir in space, big stakes. Onboarding through jobs in motion. Midpoint ties plague to politics. Chapters fast, voice straight.
• Mistborn. Promise: heist plus fresh magic rules with hard costs. Teaching via fights and training with purpose. Midpoint reveals empire depth. Stakes rise through resource scarcity.
• Rivers of London. Promise: police procedural with sorcery. Onboarding through banter and casework. Pace favors voice, not math.

Now reflect. Where does your book sit among those rhythms. If your chapters run twice as long, own it or adjust. If your midpoint drifts, sharpen it. Use comps to guide choice, not to copy.

A final mindset for priority edits

Every revision protects immersion. World rules stay stable. Character need drives choices. Subgenre promise stays visible. Teach early pages with appetite and restraint. Use a brief and comps to aim decisions. Edit for the reader you named, on the shelf you chose.

Developmental Editing: Worldbuilding, Plot, and Stakes

You owe readers a story only your world makes possible. Developmental work aligns world, plot, and stakes so each page feels inevitable and earned.

Systems behave like characters

Magic and technology need personality. Rules. Limits. Costs. Without those, a surprise rescue feels cheap. With those, choices gain weight.

Examples help:

• Warp drive needs coolant. Overuse warps hull plating. A captain pushes once, loses shielding in the next fight.
• Blood magic buys truth for a day. Price equals a scar and a memory erased.
• Telepathy works through skin contact. Gloves block signals. Court scenes twist around a handshake.

Link a rule to a turn:

• Early win becomes a loss when the fuel tax spikes.
• Midpoint forces a taboo breach for a greater goal.
• Climax spends the last resource seeded in chapter two.

Try this:

• System sheet in four lines. Input. Output. Limit. Failure mode. Keep copies for each system. Pin one above your desk.
• Two plot turns must hinge on those limits. Not flavor. Engine.

Red flags:

• Power grows across chapters with no new cost.
• A fix arrives from offstage with no setup.
• Rules only hem in side characters while the lead slips free.

World pressure grows plot

Laws, geography, economy, language, and history shape goals and obstacles. Prophecy, guilds, AI, empires, all need cause and effect readers accept.

Quick sketches:

• A desert trade network relies on beetle resin for water storage. Raiders torch resin farms. Supply lines fail. The hero must choose between defending farms or escorting pilgrims.
• A city bans private spells. A mother hides a healer mark, avoids hospitals, and joins a smuggling ring.
• An empire taxes starship mass. Crews jettison furniture to outrun inspectors. One heirlooms box goes overboard, and with it a clue.

Three questions per scene:

• Which rule pinches here.
• Which norm raises the price here.
• What resource runs short.

Stakes rise when the world bites back. A mountain pass closes during thaw. A guild strikes over unpaid fees. A translation error misroutes a convoy. No random storms. Cause, then effect.

Manage scope with structure

Big canvases beg for discipline. Multi POV, braided timelines, quest parties, political intrigue, all ask for clear purpose and controlled reveals.

Tools that save sanity:

• Job assignments for each POV. Investigation. Survival. Reform. Romance. Each viewpoint needs a lane, plus a private stake.
• Scene labels with time and place. First line does the anchoring. No one hunts for bearings.
• Rotation with intent. Alternate threads when a question hangs, not after a reveal lands.
• Bread crumb foreshadowing. One strange detail now, a payoff three chapters later.

Practical setups:

• Index cards, one per scene. Color by thread. Mark goal, conflict, outcome on each card. Shuffle until escalations stack clean.
• Braided timeline notes with two columns. Era A on the left, Era B on the right. Each shift raises tension rather than hiding cause until after effect.
• Quest party sheets with domain tags. Lock puzzles belong to the scholar. Frontier travel belongs to the ranger. Final sequences then feel earned.

Clarity tests:

• Strip any scene to one line. If the line reads recap or transport, fold that material into a stronger scene.
• Count how many scenes pass without a change in risk, knowledge, or plan. Trim or combine.

Avoid exposition dumps

Readers want to learn, but not in lectures. Keep classrooms offstage unless drama breaks the chalkboard.

Better methods:

• Teach through problems. A rookie misdraws a ward, alarms snap shut, a veteran fixes the line while swearing about iron content. Lesson delivered, stakes intact.
• Use objects with meaning. Oxygen ration chit. Hex-key seal. Salt circle around a cradle. Concrete nouns outwork adjective stacks.
• Let status dynamics speak. A guard checks a permit, pauses on a sigil, then waves a bribe through. Power explained in a gesture and a line.
• Time micro explainers to choices. One or two sentences at decision points. Then let consequences teach the rest.

Try this highlight pass:

• Print chapter one. Yellow for world teaching. Blue for plot or character motion. If yellow swamps blue in five pages, move some lines to later moments where a choice depends on the info.

Common culprits:

• “As you know” dialogue. Delete.
• Front-loaded history prologues. Store in back matter, or better, scatter seeds through scenes of need.
• A hero monologues expertise in blocks. Add a challenger. Force a test.

Action: build a worldbuilding dossier and series bible

A living dossier pays rent during revision.

Include:

• Maps with scale, compass, borders, and travel paths.
• Calendars with weekdays, lunar cycles, seasons, and holidays.
• Ranks, honorifics, and how people address rivals or elders.
• Currency with denominations and buying power. Price of bread. Price of a bribe.
• Flora and fauna, or tech specs. Inputs, outputs, energy source, maintenance.
• Names with pronunciation and diacritics.
• Laws, taboos, and enforcement reality.
• Supply chains for food, fuel, medicine, and data.

Keep a series bible for threads, rules, and seeds:

• Prophecies quoted in full, plus who heard them and where.
• Rule log with costs and examples by page.
• Factions with motives, resources, and grudges.
• Loose ends saved for later volumes.

Update after each draft. Add page references each time a rule evolves. Share with early readers or editors for alignment.

Action: create a scene list and a discovery plan

Build a list that shows the spine.

For each scene, note:

• Goal. What the viewpoint wants now.
• Conflict. Who or what blocks progress.
• Outcome. Win, loss, draw, or twist, plus new info or risk.

Then a discovery plan:

• First mention of each key term or rule, with page numbers.
• Reinforcement moments, with context. Training, failure, folklore, or a joke.
• Overlap markers. If two scenes teach the same thing, combine or cut one.

Read through the list. Look for repeated beats. A chase followed by another chase with no fresh risk equals fatigue. Swap in a negotiation, a betrayal, or a discovery that resets the board.

Action: run a prophecy or tech audit

Every promise or capability shapes ethics and stakes. Track each one from debut to finale.

Checklist:

• Statement. The promise or tech in one line.
• Limits. Range, duration, energy cost, failure modes.
• Visibility. Who knows, who believes, who doubts.
• Social effects. Law, custom, black markets, faith, and crime patterns.
• Plot touchpoints. Where the rule blocks a plan. Where the rule saves a plan. Where the rule backfires.
• Payoff. Scene number where the highest cost arrives.

Examples:

• Resurrection exists, so grief customs shift. Murder investigations treat corpses as witnesses. Courts regulate soul contracts. Your climax then pressures those systems hard.
• FTL needs entanglement keys. Piracy targets key vaults. Nav officers earn priest-level status. A mutiny plot must account for key control.

Final sweep questions:

• Does every major system extract a price at the moment of triumph.
• Does a late twist rely on a rule readers never saw.
• Do side characters live under the same rules as the lead.

Developmental editing rewards rigor. Systems with teeth. A world that squeezes desire into decisions. Scenes that escalate because rules close doors. Do this work, and readers stop seeing gears. They feel story.

Line Editing for Clarity, Wonder, and Jargon

Line edits turn a good draft into a book readers press into friends’ hands. You tune sentences for sense, rhythm, and delight. You remove noise. You protect wonder.

Action scenes need choreography and cadence

Readers track bodies in space. Give them anchors.

• Who stands where. Use a compass point, a landmark, a doorway.
• What the viewpoint sees, hears, feels. One sense per beat beats a list.
• Why each move matters. Stakes belong inside the swing.

Short lines speed fights. Longer lines set up moves or cost.

Before:

She spun as the drone fired, trying to see who shot first while the corridor filled with smoke and someone screamed behind her as her pistol skittered across the tiles.

After:

The drone fired. Heat grazed her cheek. She spun. Smoke bloomed. A scream from behind. Her pistol skittered across tile.

Clear verbs help. Avoid glue words like “as” or “while” when actions happen in sequence. Break them apart. Track hands, weapons, and injuries. If a sword falls, leave it down until someone picks it up on the page.

Orientation tricks:

• First sentence names place and threat. “South gate. Two guards. One horn.”
• Paragraph breaks show shifts. New attacker, new line.
• Scene focus rides on goal language. “Reach the console.” “Hold the line.” “Get the child out.”

Balance wonder with readability

Big ideas thrive in clean prose. Concrete nouns carry weight. Strong verbs do more than stacks of adjectives.

Before:

The extremely ancient, beautiful, awe-inspiring spire rose above the remarkably bustling, lively market.

After:

An obsidian spire rose over the market. Fish hissed on griddles. Criers hawked salt and silk.

Trim filter verbs. Words like knew, saw, heard, felt, noticed, realized, thought, seemed, decided, began, started, manage distance. Cut when context makes the filter obvious.

Before:

She felt the ship shudder and realized the jump had failed.

After:

The ship shuddered. The jump failed.

Kill throat-clearing. Phrases like “there was” or “it was” slow a line without reward.

Before:

There was a sense of wrongness in the room that made him uneasy.

After:

The room felt wrong. His jaw clenched.

Pick one fresh sensory detail instead of four bland ones. Let the reader breathe inside the scene.

Dialogue carries culture and subtext

No lectures. No “as you know.” People talk for goals, not for backstory.

Use status cues and slang. Code-switch when power shifts. Let idiom reveal place and history.

• High court: “Your Grace, the levy falls short again.”
• Dockside: “Boss, coffers run dry. Half pay if we’re lucky.”
• AI with old code: “Query. Payroll integrity compromised.”

Mix tags and beats. Said, asked, whispered cover most needs. Beats show action and tone.

Before:

“As you know, the Order of the First Flame has ruled for centuries,” he explained.

After:

“The Order set the rules centuries ago.” He spread a palm over the inked charter. Scars crossed three fingers.

Keep clashes on the line. People interrupt. Talk past each other. Drop a withheld answer. The gap holds more tension than a speech.

Test for lecture:

• Delete any line that exists to brief the reader. Does the scene still move. If yes, leave it out.
• Move an explanation to the moment a decision depends on it.

Neologisms and conlang, handled with care

Readers enjoy new terms when context earns trust. Use sparingly. Seed meaning inside action.

• First use, plain-language cue nearby. “He slid a chigkey into the lock, two-prong, copper teeth bent.”
• Second use, no gloss, same context. The reader confirms the guess.
• Third use, new context to show range.

Morphology should hold steady. If plural in your world takes “-in,” keep it consistent. Titles, ranks, orders, ships, all need one form of capitalization and spacing.

Typography choices matter. All caps read as shouting. Italics work for foreign terms or emphasis, not entire sentences. Small caps for AI or system messages only if style stays uniform from page one.

Pronunciation guides belong in story only when mishearing matters. Otherwise, trust pattern.

Targeted passes that pay off

Do separate sweeps. One focus per pass. Fewer dropped balls.

1. Action clarity
   • Mark who holds what at scene start and end.
   • Highlight “as,” “while,” “before,” “after.” Break false simultaneity.
   • Check line of sight and distance words. Across, behind, within reach.
2. Exposition trimming
   • Bracket every sentence that explains. Then ask, needed now or later.
   • Move facts to choice points.
   • Replace abstract nouns with objects or actions.
3. Dialogue authenticity
   • Read aloud. Cut formal grammar where characters would not use it.
   • Reduce tags to said, asked, whispered. Use beats for tone.
   • Check insult ladders, honorifics, and oath words for each culture. Keep them consistent.
4. Sensory specificity
   • One strong sensory hit per paragraph during high load scenes. Heat stink of coolant. Grit on a molar. Ozone after a spell snaps.
   • Replace general color words with material or light. Bronze in torchlight. Oil-slick sheen.
   • Remove duplicate descriptors within ten lines.

Put high-load scenes through a voice recorder. Fights, chases, tech reveals, ritual sequences. Stumbles on playback signal muddle.

Build a terms list and keep it close

A living lexicon protects continuity and saves time for everyone who touches the book.

Set up entries like this:

• Term. Part of speech. One-line definition. Plural form.
• First appearance page.
• Allowed shorthand or acronym.
• Notes on capitalization and morphology.

Sample entries:

• jump key, noun. Entangled crystal array used to initiate FTL. Plural jump keys. First on p. 14. Shorthand key. Lowercase.
• the Order of First Flame, proper noun. Religious ruling body in the capital. First on p. 3. Short form the Order. Caps on Order when full title implied.
• shard-speech, noun. Telepathic protocol enabled by bonded glass. Plural shard-speech forms. First on p. 62. Hyphen always.

Include ships, units, currencies, ranks, provinces, holidays, spell names, AI models, bot types, creature species. Add example sentences for terms that invite confusion.

Keep a short rule block at the top:

• Numerals and units. Metric in text, imperial in dialogue when character would use it.
• Titles and honorifics. Sir Rowe, Captain Huang, Mother Prior. Lowercase when generic.
• Hyphenation patterns. Star-charts, warp-sick, blood-born. Lock these early.

Update the list after each pass. Share with beta readers and editors. Use it during proof checks.

Line edits respect your reader’s time and attention. Clean scaffolding lets wonder stand. Clear beats, sharp detail, honest talk, and disciplined terms, and your pages read faster and cut deeper.

Copyediting and Continuity: Style Sheets, Maps, and Timelines

Readers forgive typos. They do not forgive drift. Copyediting in SFF protects the spell. Names stay spelled. Rules stay true. Time moves in a way that makes sense. You build that reliability with a style sheet, a timeline, and a habit of checking the boring things before they bite you.

Build a style sheet that does real work

Your style sheet is a simple document that answers the same questions every time. It saves you from reinventing a comma on page 312.

Decide on:

• Names and diacritics. Kól stays Kól. No Kol in chapter nine.
• Capitalization. the Order vs the order. the Empire, but imperial troops.
• Hyphenation. star chart or star-chart. Choose once.
• Numerals and units. Three meters or 3 m. Light-year or lightyear.
• Dates and calendars. 12 Frostfall, Year 4, or Fourth Frost, 4 YR. Pick a format.
• Titles and honorifics. Sir Hal vs sir when used generically. Mother Prior or the mother prior.
• Common variants. Grey or gray. Okay or OK.

Give each entry a home:

• Term, part of speech, definition in one line.
• First appearance page and chapter.
• Plural form or short form.
• Caps rule.

Sample entries:

• Order, proper noun. Religious council ruling the capital. First on p. 5. Short form the Order. Cap Order when implied.
• jump key, noun. Crystal device used to initiate FTL. First on p. 18. Plural jump keys. Lowercase.
• Frostfall, proper noun. Month 11 in the royal calendar. 30 days. First on p. 2. Abbrev Frf. Never Frst.

Set house references. Chicago Manual of Style for punctuation and capitalization. Merriam-Webster for spelling. Note any deviations. If you prefer email over e-mail, write it down.

Mini exercise:

• Open your latest chapter. Pull every capitalized word that is not at a sentence start. Add to the sheet. Mark any wobble.

Make space and time obey

If your map says the city sits on the north bank, the sun cannot set over water on the same side unless your planet tilts like a carnival ride. Readers notice.

Check spatial logic:

• Distances on maps align with travel times in scenes.
• Rivers flow downhill. Branches join downstream, not upstream.
• Mountains cast rain shadows. That dry valley should not hold a lush jungle without a reason.
• Ship decks, corridors, and bays remain in the same relative order across scenes.

Check temporal logic:

• Travel speeds. On foot 20–30 km per day. Horse 30–50 with rest days. Airship faster, but fuel and weather still bind you.
• Spaceflight. State your FTL rules. Jump range, cool down, fuel cost. Then stick to them.
• Moons and tides. Two moons mean varied tide cycles. Coastal scenes should reflect that.
• Time dilation or portal lag. If one week passes on station and one day on planet, show the mismatch in age and logistics.

Do the math once. Put results in your bible. You do not need equations on the page. You need to avoid a hero racing across a continent in an afternoon because you forgot the map scale.

Mini exercise:

• Pick one journey in your book. Write departure time, distance, speed, rest. Do the totals. Adjust scenes or the map to fit.

Keep visuals and back matter honest

Maps and charts are promises. If your map shows three villages on the east road, do not send the caravan past four. If you change a border in revision, change the map label too.

Back matter checks:

• Map scale matches travel claims in the text.
• Place names match capitalization and accents on the page and in the map.
• Star charts use the same ship names, registry numbers, and class tags as the chapters.
• Glossary entries match how terms work in scenes. No secret meanings that contradict usage.
• Dramatis personae list aligns with names and honorifics in dialogue.
• Appendix data, timelines, and tables reflect the latest draft.
• Epigraphs have accurate attributions and permissions where needed.

Test a glossary entry by pointing to a scene. If shard-speech in the glossary says line-of-sight only, the big finale cannot include a mountain-to-mountain chat unless a new rule enters the story and costs something.

Mini exercise:

• Print your map and a high-churn chapter. Highlight every place named in the text. Trace it on the map. Any mismatch gets a sticky note.

Track a series like a pro

Series continuity is where readers bring receipts. They remember the scar you forgot. They remember who swore never to board a ship again, then boarded a ship with no mention of fear.

Build a continuity table. Keep it open while you write.

• Character: age by book and by chapter range, hair and eye, scars, dominant hand, notable speech patterns, first and last seen.
• Objects: artifact name, owner, status, location, last known appearance.
• Oaths and laws: exact text, scope, penalties, exceptions.
• Ships and units: captain, registry, crew count, armament, damage history.
• Borders and factions: alliances, treaties, dates of change.

Sample lines:

• Aerin. 17 at start B1, 18 after Spring Fair B2. Scar under left collarbone, knife wound B1 ch 23. Afraid of open water after river raid B1 ch 12.
• Kyr, sword. Broken B2 ch 12. Shards stored in temple vault, capital, shelf C. No reforge yet.
• Falcon, frigate. Registry F-442. Captain Huang. Lost port engine B1 ch 8. Repaired B1 ch 14 with spare coils.

Time stamps help. Use a simple timeline with dated beats or clean relative markers.

• Day 1: Departure from Kett. Noon, river crossing fails.
• Day 2: Camp in Black Pine. Scout injured.
• Day 10: Arrive at Malin Gate. Festival eve.

Update after structural changes. When you move a siege up three weeks, birthdays, crop cycles, and travel windows shift. Fix references to weather, harvest, and moon phase.

Do the boring sweeps that save you

Adopt Chicago and Merriam-Webster. Maintain one style sheet across drafts and books. Share it with every editor and proofreader.

Run these sweeps per draft:

• Variant spellings. Search pairs, then settle. grey, gray. armor, armour. adviser, advisor. okay, OK.
• Titles and ranks. captain vs Captain Huang. sir vs Sir Rowe. the duke vs Duke Harrow. Make rules and apply them.
• Hyphenation drift. set up vs setup. time skip vs time-skip. light-year vs lightyear. Pick your form.
• Left and right swaps. Search left hand, right hand, left eye, right eye. Make sure wounds and scars stay put.
• Numerals and units. 3 m vs three meters. ly vs light-year. Standardize for narrative and for dialogue by character voice.
• Calendar checks. Day name consistency. Month lengths. Leap days if your world has them.
• Page proofs. After typesetting, spot-check breaks that split names, lists, and maps. Image captions match text terms.

Read any scene with distance, direction, or time aloud while pointing at your map or chart. If you trip, the reader will too.

Copyediting is the unglamorous guard at the gate. Keep the rules clear and the doors aligned, and your reader walks straight into wonder without snags.

Science, Magic, and Ethics: Plausibility and Sensitivity

Readers buy a promise. Physics holds or spells hold, within clear lines. Break the promise and trust leaks away. Keep the frame honest, and wonder feels earned.

Calibrate plausibility to the promise

Hard SF leans on physics, engineering, biology. Numbers rule. Softer SF or fantasy keeps to internal logic and steady consequences.

Set scope at the start, then hold the line.

• Railguns and delta‑v, or psionics and prophecy. Pick constraints that fit subgenre.
• If FTL requires a rare isotope, show acquisition, theft risk, or rationing.
• If teleportation exists, show energy cost, range, cool‑down, and failure modes.
• If a healing spell closes wounds, scars remain, fatigue follows, or materials run out.

Readers track cost. Power without price breaks tension.

Mini exercise:

• Pick one system, tech or magic. Write five lines: input, output, limit, cost, failure. Keep that card on your desk. Revise scenes until every use matches those five lines.

Social worldbuilding echoes real life

Cultures on the page reflect cultures off the page. Simple buckets flatten people. Complexity builds credibility.

Run checks on:

• Monolithic “races.” Add regional, class, and belief variation. Language shifts across valleys and courts.
• Colonial analogues. If an empire extracts resources, show trade terms, resistance, collaborators, and propaganda.
• Coded discrimination. Clothing rules, surname laws, permit checks, border rituals, school tracking. Show mechanics, not labels alone.
• Gender, disability, neurodiversity, queerness. Avoid pain as sole identity. Give goals beyond trauma.
• Religion. Rituals, schisms, holidays, food rules. Faith produces conflict and comfort, both.

Naming matters. Slurs or near‑slurs wound readers. Terms held by insiders differ from outsider usage. Record usage rules in the bible and honor them in dialogue and narration.

Mini exercise:

• Write a street scene in the capital, then rewrite from the viewpoint of a dockworker from a minority district. No speeches. Small frictions only. Who pays extra. Who gets stopped. Which door leads to service stairs.

Ethics and stakes are story engines

Technology and magic shift power. Power invites moral choice. Readers notice who pays and who decides.

Test common hotspots:

• Consent. Love draughts, memory edits, truth serum. If a character removes choice, story logic must treat that as violation, not romance shortcut.
• Privacy. Telepathy, surveillance swarms, predictive AI. Show laws, countermeasures, cultural norms.
• Personhood. AI, uplifted animals, golems. Define rights, property status, and emancipation paths. Keep language consistent. “Who” versus “which” signals stance.
• Collateral damage. City battles, orbital strikes, volcano magic. Track casualties, aid, political fallout.
• Autonomy. Prophecy, geas, binding oaths. Clarify scope and loopholes. Breaking an oath carries penalties beyond scolding.

A quick rule, harm on the page deserves response on the page. Silence reads as approval.

Mini exercise:

• List three moments where your protagonist uses leverage over another being. For each, note consent, alternatives, and aftermath. Add one on‑page consequence where silence currently sits.

Bring in experts and sensitivity readers

Subject‑matter experts save you from public math. Sensitivity readers protect people on both sides of the page.

Where to seek help:

• Orbital mechanics, materials science, biotech, weapons systems, military logistics.
• Linguistics, historical law, religious studies, anthropology.
• Lived experience across cultures, disabilities, gender identities, sexual orientations, faith backgrounds.

Give context. Share premises, system rules, and what you want readers to feel. Ask for accuracy risks, trope landmines, and dead language. Log every decision in the series bible, with sources.

Plan early. Early input adjusts foundations. Late input patches ceilings and leaves cracks.

Mini exercise:

• Pick one high‑risk element. Draft three precise questions for an expert. Example for portals, “Energy cost per jump, storage medium, and failure residue on surroundings.” Then email or post in a vetted forum.

Action tools

Build a plausibility checklist per system. Keep it short. Use it.

For each system, note:

• Inputs. Fuel, mana, focus, materials, social permission.
• Outputs. Range, force, bandwidth, resolution.
• Limits. Range caps, weather sensitivity, shielding, wards.
• Costs. Energy drain, injury, rare components, social penalty.
• Failure modes. Misfires, side effects, blowback, contamination.
• Externalities. Noise, heat, light, EM signature, environmental damage.

Test scenes against the checklist. If a fight ignores heat signature, later stealth scenes collapse. Adjust sooner, not after ARC reviews.

Engage experts and sensitivity readers early for high‑risk zones, then record outcomes.

• Medicine. Dosage, recovery windows, triage, blood loss.
• Linguistics. Phonology, morphology, orthography for conlangs. Loanwords, register.
• Cultures and history. Foodways, humor, naming patterns, etiquette.
• Military tactics. Unit sizes, supply lines, casualty rates, terrain use.

Onboarding plan for terms and concepts keeps readers upright.

• First mention in plain language. “The slip is a short jump between anchor points.”
• Second use with a light reminder. “The slip burned fuel faster near mass.”
• Later shorthand once context sticks. “Slip window at 0400.”
• If a glossary appears, definitions match usage. No surprises.

Mini exercise:

• Take five key terms. Write a first‑mention sentence in clean prose. Then mark page numbers where shorthand takes over. If shorthand arrives before context lands, move an explainer to a decision point.

Good science or good sorcery feels earned. Choices carry cost. Cultures feel mixed and alive. Readers feel safe in knowledgeable hands, so the story can take risks.

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