Editors for science fiction novels: what an edit covers

A science fiction edit looks hardest at six things: how many invented things chapter one asks the reader to hold, where the exposition comes from, which assumptions will date the book, whether competence has drained the tension, whether scale stays consistent, and whether anyone in the book would still want anything if the central idea were removed. Every genre fails in its own way. Romance fails at want, mystery fails at fairness, and science fiction fails at load-bearing exposition, because the reader has to carry your world and your plot at the same time and most drafts hand over both at once.

I edit a lot of science fiction, and I write it, so a fair chunk of what follows is me describing mistakes I've made on the page and then watched somebody else make three months later. Here's what a sci-fi manuscript needs from an edit that a generalist editor will usually miss.

1. Worldbuilding load is a budget, and most drafts blow it in chapter one

A reader can hold a limited number of unfamiliar things in working memory before the prose turns into noise. Not zero, because science fiction readers are unusually tolerant and that's why they read it, but limited. Call it a budget.

Chapter one of a typical draft spends that budget on an invented place name, an invented political body, an invented unit of time, an invented job title, two invented pieces of hardware, and a protagonist whose name is also unfamiliar. That's seven withdrawals before anything happens. The reader has no plot yet to hang those seven things on, so they hang on nothing and are gone by page four.

An editor should be counting, literally. A good developmental pass on sci-fi marks every novel noun in the first twenty pages and asks, one at a time, whether the reader needs this now or when it matters. The fix is almost never cutting the worldbuilding. It's moving it to the scene where it does work.

2. Exposition management: who is allowed to not know things

The oldest trick in the genre is the ignorant viewpoint: the new recruit, the outsider, the kid. It works, it's overused, and writers reach for it because they haven't found the other options:

• Disagreement. Two experts who both know the thing but disagree about it can explain it completely while arguing. Nobody has to be dumb.
• Failure. A system explained while it's working is a lecture. The same system explained while it's failing is a scene.
• Procedure. Characters running a checklist reveal how a thing works and how they feel about it, so competence and exposition share a paragraph.
• Absence. Sometimes the right amount of explanation is none, and the reader infers. Trusting the reader is a technique, not laziness, but it has to be chosen, and most drafts confuse "I trusted the reader" with "I forgot to write it."

When I mark up a sci-fi draft, exposition notes are usually the largest single category. There isn't too much of it, it's just in the wrong container. (Our glossary has a short entry on motivated exposition if you want the basic idea.)

3. The technology will date, and there's a craft answer to that

Every writer worries about this, and most worry about the wrong half. Your invented technology won't date. Your assumptions about the present will. Stories go stale because of the phone in the character's pocket, the way people search for information, what a job is, what surveillance feels like. It's the unexamined furniture that goes stale, not the ray guns.

Two practical moves:

Describe function, not interface. "She pulled up the manifest" ages slowly. "She swiped left twice on the holo-pane and tapped the third glyph" ages faster and stops the scene dead. Interface detail is the most expensive prose in science fiction per unit of story value. Spend it once, on the one interface that's thematically load-bearing, and describe everything else by what it accomplishes.

Date the culture on purpose. If your society's relationship to a technology is stated, with characters who have opinions about it, argue about it and resent it, then it reads as a choice rather than an oversight, even decades later. Unexamined tech dates badly, and tech people argue about turns into period texture.

4. The competence trap

Science fiction's most reliable pleasure is watching a smart person solve a hard problem with correct procedure. Andy Weir's The Martian is the obvious example, and the hard-SF shelf is full of others. It works because the reader gets to feel competent by proxy.

It's also a trap, and here's the mechanism: competence removes doubt, and doubt is what makes a scene a scene. If your protagonist is the best engineer on the ship and the problem is an engineering problem, the reader knows the outcome on the first page of the sequence. The prose can still be pleasurable, because process is pleasurable, but there's interest without tension. A novel can run on interest for a while, and not for four hundred pages.

Symptoms I flag in a manuscript:

• The protagonist is never wrong about a technical matter, only about a personal one.
• Every problem is solved by the discipline the protagonist already has.
• Failures are budget failures (not enough time, not enough parts) rather than judgment failures.
• Long stretches of correct procedure with no scene goal underneath, where the character is doing their job and not pursuing anything.

The fix is usually not "make them dumber." Put the cost somewhere their competence can't reach, and make the correct technical answer the wrong human answer. Now competence is a choice with a price, and the sequence has a spine.

5. Scale drift

Space is big, and manuscripts lose track of it. Distances, populations, travel times and the consequences of an event stop agreeing with each other somewhere around the middle. A fleet that took four months to arrive retreats in a chapter. A colony of two thousand fields a standing army. A continent-scale disaster has the emotional footprint of a house fire.

This is a continuity job, but a developmental one. A copy editor won't catch it, because no single sentence is wrong. It takes an editor holding the whole book in their head, which is one argument for a developmental read before you pay anyone to polish sentences.

6. The idea-to-story ratio

The last one is the hardest to hear. Plenty of sci-fi drafts are an idea wearing a plot as a disguise. The idea is good, which is why the writer wrote four hundred pages, but the characters exist to walk the reader through it, and the ending resolves the idea rather than the people. A good puzzle is the opposite: a few fixed rules, one surprise, and an answer that feels inevitable once you see it. Our guide to the best daily logic puzzles is a quick way to study that shape.

The diagnostic question: if the central science-fictional idea were removed, would anyone in this book still want anything? If the answer is no, the manuscript needs a developmental edit, not a line edit, and no amount of polish will fix it. If the answer is yes, you probably have a book and the notes will be about structure and pacing.

What we've worked on

For transparency, since a lot of editing sites are vague about this: we've done live development edits on science fiction drafts on stream, including The Life Interstellar. On the writing side, our science-fantasy novel The Distributor was published by The Story Plant, and our cyberpunk short story The Last Fare of M1S-3 ran in Write Ahead / The Future Looms. The full list is on the publications page.

That matters for one reason: an editor who has been through a science fiction submission process knows which of your problems are craft problems and which are market problems, and those get different notes.

Where to start

If you're not sure whether your manuscript needs structure work or sentence work, read the breakdown of developmental, line, copy and proofread first. Picking the wrong one is the most common way writers waste money on editing. When you're ready, the Get Edits page has the options, including free live edits on Twitch if you don't mind your draft being discussed in public.