How to Find Plot Holes in Your Novel, and the Ones That Span a Series
To find plot holes in your novel, list the questions your plot must answer and find the page where the book answers each one; trace every clue back to the scene where the character learned it; and test the easy exits your characters ignore. In a series, run the same pass across every book, not one at a time.
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 five continuity errors readers catch most is the other list; Watson’s wandering wound is a continuity error that really shipped, and shows how a fact slips without the logic breaking; for a mystery’s clue trail there is the clue and plot-thread tracker.
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.
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.
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.
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.
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. Two of these have their own guides: the knowledge ledger for the impossible knowledge, and the resurrection error for the dead, broken or burned things a plot quietly reuses. For software that reads a book against its own logic, see the AI plot hole checker.
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:
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 software track the setups for you.
-
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.
-
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.
-
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.
-
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.
StoryHelm reads one book at a time, the prose you wrote here or a book you imported from elsewhere, and surfaces some of the structural signals a plot hole leaves. The Foreshadowing pass, which runs in a Full read or from its own page, pairs each setup with its payoff and lists the setups that never pay off, with the chapter where each was planted; once two or more books in a series have been through it, the series Books page also lists setups no later book pays off. In a Full read, the Coherence Guardian can flag a scene that breaks a rule the same book set up, such as a power used past its stated limit, or a character acting on knowledge they were never given. Neither compares rules or capabilities from book to book, and neither spots an ignored solution, so the easy-exit test in step 3 stays yours. StoryHelm reads and analyzes; it never drafts or rewrites a word of your manuscript, and it never decides whether a hole is real. It shows you what does not line up; 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
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.
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.
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 go through each book in your series and flag a setup that is never paid off, or a scene that breaks a rule the same book set up.
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. In a Full read, StoryHelm reads one book at a time and can flag those patterns within it, usually naming the chapter and often quoting a short line. Across a series, it also lists setups an earlier book planted that no later book pays off, matched by name. You decide whether each is a real hole or a deliberate choice.
By writing down the questions the plot has to answer as they draft (why doesn’t she just tell him, how did he get the key, what stops the obvious exit) and answering each one on the page before the book ships; by keeping a ledger of who knows what and when they learned it; and, in a series, by reading each new book against the earlier ones rather than against memory. Most holes are not invented; they are inherited from a draft that changed.
The four types above, in illustrative form: the token your hero forgot she was carrying while she picks a lock by hand; the villain who could have ended the story in chapter two with the power he uses in chapter thirty; the character who acts on a letter no scene showed him reading; and the solution Book 2 established that Book 5’s crisis ignores. None of these is from a published novel; they are the shapes to look for.
Keep reading
Craft for the Long Game
The full pillar: pacing, voice, foreshadowing, and structure, held together across a whole series rather than one book.
ReadSeries Continuity, End to End
The other half of holding a series together: names, timelines, geography, and the facts that have to stay true across every book.
ReadCatch the token your hero forgot she was carrying.
StoryHelm reads each book in your series, tracks the setups you planted, and flags the ones a later book never pays off, then points to the book that planted each one, with a quoted line or a short description of the moment. 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.
Get the free Self-Audit