StoryHelm
Learn / Series Craft / How to Avoid Plot Holes in a Series
Guide · Series Craft

How to Avoid Plot Holes in a Series: Catch Them Before Readers Do

A plot hole is a break in your story’s own logic, not a contradicted fact: a problem the characters could solve in one obvious move but don’t, a clue a character uses before they could have learned it, an effect with no cause. In a series the worst ones span books, because the solution you wrote into Book 2 is still in the reader’s memory when Book 5 pretends it never existed. You close them by tracking the questions your plot must answer, and checking that every book actually answers them.

Plot hole vs continuity error: not the same problem

The two get lumped together, and fixing the wrong one wastes a revision. A continuity error is a contradicted fact: her eyes were gray in Book 1 and brown in Book 3, the siege was “three winters ago” in one book and “a decade” in another. The facts simply do not match. A plot hole is different in kind: the facts can all be correct and the story still breaks, because the events could not happen the way the book says. A locked door opens without a key. A character acts on a secret no one ever told them. A villain ignores the one move that would obviously win.

Put simply: a continuity error is a bookkeeping failure, a plot hole is a logic failure. You catch a continuity error by comparing facts; you catch a plot hole by asking whether the causal chain actually holds. Both sink a series, but they hide in different places, and a line edit that fixes spelling-of-the-facts will sail right past a hole in the logic.

The four plot holes a series breeds

Most holes in long fiction fall into four shapes. Each is invisible in the scene where it happens, because the scene is doing its job; the break only shows when you hold the whole arc up to the light.

The ignored solution
A problem the characters could end in one move they already have, but don’t, because the plot needs the problem to continue. The reader sees the easy exit even when the characters don’t.
The impossible knowledge
A character knows or uses information they were never given on the page: a name no one spoke to them, a plan they weren’t in the room for, a map they never saw.
The dropped setup
A gun on the mantel that never fires. A prophecy, a debt, a hidden heir planted with weight in an early book and then quietly forgotten. The promise is made; the payoff never comes.
The vanished capability
A power, ally, item, or skill that solved a problem once and then is conveniently unavailable when the same problem returns, with no reason given for why it can’t help now.

Notice how close the last two run to continuity, and how they are still distinct. A dropped setup is not a contradicted fact; it is a promise the plot’s logic leaves unkept. A vanished capability is not a trait that changed; it is the story declining to use a tool it told you was on the table. That is why a pure continuity pass can come back clean while the plot still has a hole in it.

Why a series makes them worse

A standalone gives a plot hole one book to hide in, and a reader one sitting to forget it. A series removes both protections. The setup you plant in Book 1 stays live in the reader’s mind for years; the solution your characters used in Book 2 is remembered as a tool they own. When Book 5 puts them in a corner the series already showed them how to escape, the reader does not think “I forgot.” They think “why don’t they just do the thing from Book 2?”

Scale makes it worse in a way no amount of care fully fixes. By Book 4 you have dozens of open questions in flight at once, every one a small contract with the reader: this debt will be called in, this enemy will return, this rule will matter. You wrote each promise months or years apart, and you cannot hold all of them in working memory while drafting a new chapter. The hole is rarely a failure of skill. It is a failure of recall across a body of work too large to keep in one head.

A plot hole is the question your story forgot it asked. In a standalone you have one book to remember it; in a series the reader remembers it for you.

Here is the cross-book shape, with the setup and the hole side by side the way they almost never appear to the author who wrote them two books apart:

Book 2, Chapter 5: “Keep the token,” the smuggler said, pressing the iron coin into Rell’s palm. “Show it at any harbor on the coast and they’ll hide you, no questions, no matter who’s hunting. That’s a promise older than the war.”
Book 5, Chapter 12: With nowhere left to run, Rell huddled in the alley as the patrol swept the docks. Every harbor on the coast was closed to her now, and there was no one left who would take her in.

Neither passage is wrong on its own. Book 5’s alley scene is tense and clean. But the reader who was handed that iron coin in Book 2 is shouting at the page: the token, use the token. The fix is a decision, not a deletion: either the coin has to fail for a reason the reader can see (the network is gone, the promise broken on the page), or the scene has to honor the tool the series already gave her.

How to close them before a reader finds them

You cannot out-discipline a memory problem at series scale, but you can make the open questions visible so none of them slips. The method is the same whether you track it by hand or have it read out of the prose.

  1. List the questions your plot must answer

    Every plot runs on questions: why doesn’t she just leave, how did he know, what stops them from using the artifact again. Write them down as you plant them. A question you never wrote down is a question you will never remember to answer.

  2. Trace each one across the whole series, not one book

    For every open question, find where it is raised and where it is answered. The dangerous ones are answered in a different book than they were asked, which is exactly where a single-book read-through loses them. If a question is raised and never resolved, that is a dropped setup. If it is answered in a way an earlier book already contradicted, that is a hole.

  3. Stress-test the easy exits

    For each crisis, ask what the obvious solution is, given everything the series has already established the characters can do. If the answer is “use the thing from Book 2” and they don’t, you have an ignored solution or a vanished capability. Close it by removing the tool on the page, or by giving a real reason it can’t help here.

  4. Decide, don’t delete

    A flagged hole is a choice, not a verdict. Sometimes the right fix is to pay off the setup; sometimes it is to cut the promise that started it. The point of finding the hole early is that in the draft it costs one rewrite. After the boxed set ships, it costs a reader’s trust and a one-star review that names the exact chapter.

How StoryHelm checks this

StoryHelm reads your whole series at once, the prose you wrote here and the books you imported from elsewhere, and surfaces the structural signals a plot hole leaves. The Foreshadowing agent tracks every setup you plant and flags the ones that are never paid off; the Narrative and World Rules agents read each established capability and rule and flag where a later book ignores or contradicts one. Every flag points to the exact book and chapter and sets the clashing passages side by side, the setup and the break, the way they never appear to you while drafting. StoryHelm reads and analyzes; it never drafts or rewrites a word, and it never decides whether a hole is real. It shows you the two passages that disagree; you choose the fix. For what this check does and does not catch, see What an AI Continuity Check Does (and Doesn’t).

Plot hole FAQ

Q. What is the difference between a plot hole and a continuity error?

A continuity error is a contradicted fact: an eye color that changes, a name that drifts, a date that no longer adds up. A plot hole is a break in the story’s own logic: a problem with an obvious solution the characters ignore, a piece of knowledge a character could not have, an effect with no cause. Continuity is about whether the facts match; a plot hole is about whether the events could actually happen the way the story says.

Q. Why are plot holes worse in a series than in a standalone?

In a standalone, a plot hole has one book to hide in. In a series, a solution you established in Book 2 sits in the reader’s memory through Book 5, so when your characters suffer through a crisis the earlier book already solved, the hole spans books. Series readers also have time and motive to compare, and they will: the longer the series, the more setups are live at once, and the more ways the plot can quietly contradict its own logic.

Q. How do I find plot holes in my own manuscript?

List the questions your plot has to answer: why doesn’t the character just do the obvious thing, how did they learn this, what stops the easy solution. Then trace each through the whole series and confirm the story answers it on the page. The hard part is doing it across books, because the setup and the hole are often hundreds of pages apart. An automated read can hold the whole series in view at once and flag where a setup is never paid off or a stated capability is later ignored.

Q. Can software actually detect a plot hole?

Software cannot judge whether a plot choice is satisfying, that is yours. What it can do is surface the structural signals a plot hole leaves: a thread planted and never resolved, a capability established and then contradicted, a piece of information a character uses before they were ever shown to have it. StoryHelm reads the whole series and flags those patterns with the exact passages, so you decide whether each is a real hole or a deliberate choice.

Keep reading

Find the question your plot forgot

Catch the token your hero forgot she was carrying.

StoryHelm reads your whole series, tracks every setup you planted, and flags the ones a later book never pays off, then points to the exact chapter where the easy solution went missing. Find the hole in the draft, when it costs one rewrite, not after the boxed set ships and a reader names the chapter for you.

Request a founding seat
Founding cohort forming now · No spam, unsubscribe anytime · It never writes your prose