Guides · Revision

How to find plot holes in your manuscript.

The short answer: stop reading for plot holes chapter by chapter, and start reading for one kind of hole at a time — logic gaps, timeline slips, motivation gaps, dropped foreshadowing, broken world rules, and outright contradictions each hide differently, and each needs its own pass against your canon, not your memory of the book. Track what you find with the exact passages that clash, then decide, deliberately, whether to fix it or leave it. Do that and most of what a reader would catch surfaces before they ever do.

The method

Five steps, run in order.

Finding a plot hole for real isn't one long, paranoid reread. It's five smaller, more boring steps, done in sequence, every time you revise. Skip a step and you get the pass most manuscripts get: the obvious catches, and everything subtler left for a reader to find first.

1. Know the kinds of hole.

"Plot hole" isn't one failure — it's six, and naming them before you start turns a vague dread into a checklist:

  • Logic gaps. An effect with no cause, or two causes that can't both be true.
  • Timeline slips. An order of events that doesn't survive being put on an actual calendar.
  • Motivation gaps. A character acts against everything you've established about them, with nothing shown that changed their mind.
  • Unresolved setups. Foreshadowing planted with weight, then dropped — a promise to the reader the manuscript quietly stops keeping.
  • World-rule violations. Your magic, technology, law, or economy behaves one way in an early chapter and another way later.
  • Continuity contradictions. A fact — a name, an age, a scar, who knew what and when — that disagrees with itself across the book.

2. Read against your canon, not your memory.

Your memory of your own book isn't a reliable check — it's the thing that's failing. You remember what you meant to write, and a plot hole is exactly the gap between what you meant and what actually made it onto the page. Read against something external instead: a story bible, a timeline, a character sheet — structured canon that states, in writing, what's true, so a contradiction has something concrete to contradict.

3. Run one systematic pass per kind, not one pass for everything.

A single read-through asks you to catch six different failure modes at once, using six different kinds of attention — which is exactly why a single read-through catches so little. Read once for timeline alone, plotting every date and duration on an actual calendar. Read once for world rules alone, checking every scene against the rule you wrote down. Read once for foreshadowing alone, listing every planted setup and whether it paid off. The method is slower than one big read. It's also the only version that reliably works.

4. Track each finding with its evidence.

When you catch something, don't fix it in passing. Write it down with the two passages that clash — chapter and paragraph for each — then decide, deliberately: resolve it (change the prose, or change the canon it should have followed) or dismiss it (the contradiction is intentional, or too minor to matter). A hole fixed without a decision has a way of reopening in the next draft.

5. Get fresh eyes on the whole book at once.

Every pass above still runs through your own head, which is the one instrument that can't fully see its own blind spots. The reading that catches what you can't is one that holds the entire manuscript at once, with no memory of ever having written it — a beta reader, an editor, or a tool built to read every chapter against your canon in a single sweep.

Two examples

What a hole looks like once you're checking for it.

The demo manuscript below is Vellhark: a harbor city under an uneasy truce with the Korrith Order, bloodglass moving through customs sheds it isn't quite legal to search yet, and an account-keeper, Cael Marrow, whose ledgers only he is meant to read. Two findings from an early pass show two different kinds of hole — neither one a timeline slip.

Example one: a logic gap. In chapter eight, the customs warden Vessa Ondrin confronts Tarsil with a figure straight out of the Order's sealed ledger — the exact tonnage that never cleared the shed. It lands well on the page. The trouble is that chapter four established only Cael Marrow, the Order's reckoner, has ever opened that ledger, and Vessa has never been in the room with it. She is acting on knowledge the story never handed her. A pass that reads each scene against what a character could plausibly know catches it; a read-through, carried along by the confrontation, sails right past.

Example two: a broken world rule. The bible's very first fact about bloodglass is the tell that it isn't ordinary stone: it stays warm to the touch on the coldest nights. Chapter eleven, reaching for a bleak image, has a crate of it frozen fast to the dock in a hard frost. The scene reads fine on its own — but it contradicts the single property the whole plot is built on. Checking each scene against the world's own stated rules surfaces it; admiring the prose does not.

High
Logic

Vessa knows what she was never told

Ch. 8 has her quote the Order's sealed ledger; ch. 4 established only Cael Marrow has ever read it. She acts on knowledge the story never gave her.

§ ch. 4 ¶2 · ch. 8 ¶5
Low
World rule

Bloodglass freezes — but it can't

Established warm to the touch on the coldest nights (the tell it isn't stone), then iced fast to the dock in ch. 11.

§ canon · ch. 11 ¶3

Tracked with their evidence, the way step four asks for, two holes look like this.

Common pitfalls

The mistakes that let a hole through anyway.

Even writers who know to check for plot holes fall into a handful of traps that make the check hollow.

  • Rereading your own book for holes. You already know what's supposed to happen, so your memory fills the gap before you notice it's there — the single biggest reason a self-edit misses what a stranger catches immediately.
  • Catching only the obvious ones. A glaring contradiction on the same page gets caught by accident. The kind that survives — a fact planted forty chapters apart — needs the systematic pass, not luck.
  • Having no method at all. "I'll reread it and see" isn't a plan for six distinct failure modes. Without a pass per kind, you default to whichever kind you personally notice, and miss the rest every time.
  • Fixing a hole without checking the fix against canon. Change a date to resolve one contradiction and you can open a second one three chapters over. Every fix is itself a canon change — check it the same way you checked the original.

Where this fits

The check that runs this at manuscript scale.

The five steps above work with nothing but a notebook and patience — that's the whole point. Loreon's whole-manuscript validation runs the same kind of sweep on demand: it reads every chapter against your canon and hands you findings like the two above, each citing its passages, for you to resolve or dismiss. It's conservative by design — a contradiction that reads as intentional gets flagged lightly rather than rewritten outright, so the decision, and the prose, stay yours. Plot holes open widest at the two places memory is under the most strain: scene to scene as you draft, which maintaining continuity in a novel covers, and volume to volume once a story bible has to hold more than one book, which is the subject of planning a book series.

Loreon · The Writing Studio

Try the sweep on your own manuscript.

The editor is free, and welcome credits cover your first real agent work — no subscription, no card on file.