Common Plot Holes (And How To Fix Them)

Gary Smailes | 5 November 2025

What Counts as a Plot Hole (and Why It Breaks Immersion)

A plot hole is a break in story logic. A link goes missing, a rule gets bent when it suits the moment, or a character acts in a way that clashes with established motives. Readers trip over these breaks. Once trust slips, tension drops with it.

Common signs:

• Missing cause. A door is locked in one chapter, open in the next, with no change shown.
• Broken rules. The magic needs blood once, then works for free later.
• Motivation mismatch. The hardline prosecutor lets the villain walk with no pressure on the page.

Readers forgive mystery. They do not forgive confusion. If a reader cannot answer three questions, why this, why now, why them, belief slides into doubt. You feel the wobble, because scenes lose weight when purpose blurs.

Suspense vs. a gap

Suspense withholds information on purpose. The withholding is prepared with signals, then paid off at a meaningful moment. A gap is a missing step you forgot to show.

• Suspense example. A masked caller warns the hero. We see a silhouette with a limp twice. At the climax, the hero unmasks the ally, the mentor with the old knee injury. The reveal pays a seed, so readers nod.
• Gap example. The hero knows the bomb code with no setup. No prior access. No clue chain. That is a hole.

Simple test. If you reveal the answer, does the reader say, of course, or wait, since when. Aim for the first.

Write a one-page story logic brief

Before drafting or during revision, write a tight brief to hold your rules and promises. One page, plain language. Keep it near your keyboard.

Include:

• Genre promises. What readers expect from your shelf. Example, locked-room puzzle, fair clues. Heist, a team with specialties, a twist on the plan.
• Protagonist goal and stakes. One sentence each. Goal, recover the stolen ledger. Stakes, if she fails, her sister goes to prison and the syndicate erases the town records.
• Non‑negotiable rules. Tech, magic, legal, social. Limits and costs. Magic needs a named relic and exacting focus. City cameras store footage for 48 hours. Police require a warrant for phone dumps. A duke outranks a merchant in court.
• Antagonist constraints. What stops the villain twice before the midpoint. What price they pay to escalate later.
• Red lines. No time travel. No perfect hacks. No last‑minute witnesses from nowhere.

Mini exercise, write five rules for your world, two costs, and one exception you will never cross. Then add one example scene that shows a rule in action before you rely on it for a big turn.

Build a cause‑and‑effect chain

Map the spine with a simple formula, Because X, therefore Y. But Z. This forces causality onto the page and exposes weak links.

Example, thriller:

• Because the hero’s source vanishes, therefore she raids his locker for leads. But security tags her badge.
• Because security flags her, therefore Internal Affairs watches her calls. But she uses a pay phone and tips the whistleblower.
• Because the whistleblower names a shell firm, therefore she stakes out the warehouse. But the firm is a front for her captain.

Notice the push and pull. Each step grows from the prior outcome. Each step adds pressure. If you write your core beats this way and hit an and then, mark it. And then means no cause, no consequence, or a missing obstacle.

Quick drill, write five lines for your own story using because, therefore, but. If line three reads, and then they go to the cabin, ask why. What forces the cabin. Add a reason on the page before you go there.

Why holes break immersion

Readers build a mental contract with you. They invest time, attention, and hope. They expect fairness and coherence. When a hole appears, the contract thins. Attention drifts to the author’s hand rather than the scene. That little voice says, the writer needed this to happen, so it did. Tough to recover once that voice wakes up.

You stop that voice with groundwork:

• Show costs before you spend power.
• Show access before you reveal knowledge.
• Show pressure before a big choice.
• Show limits before you bend one.

Two practical tools to catch trouble early

• Story logic brief session. Set a timer for 40 minutes. Fill the brief. Highlight any soft spot you feel tempted to wave away. No waving. Solve or reduce.
• Cause‑and‑effect pass. Take your beat sheet. Write because, therefore, but lines for Inciting Incident, First Plot Point, Midpoint, Crisis, and Climax. If any beat lacks a clean because, re‑sequence or add setup one scene earlier.

One last tip. When you ooze toward explanations in dialogue, pause. Explanations smell like patchwork. Prefer plants that do the same job with action on the page. A single scene where the spell sputters under stress teaches more than a paragraph of lore.

Mystery thrills when readers trust the floor. Keep logic tight, pay promises, and suspense will do honest work for you.

The Usual Suspects: Common Plot Hole Types

You know these culprits. They sneak in during fast drafts and survive into late revisions. Spot them early, and you save yourself three chapters of mopping up.

Weak or missing motivation

A choice without a clear want, need, or pressure reads hollow. The detective quits the case because she is tired. The prince forgives the traitor because plot. Readers shrug.

Fix it on the page. Show stakes and constraints before the choice. Give the moment a forcing function. A deadline. Leverage. Risk to someone the hero cares about.

Example. The hacker refuses to hand over the drive. Flat scene. Add pressure. The kid sister waits in the car, feverish. A text arrives, two hours until the buyer leaves the country. Now the refusal or surrender carries weight.

Quick drill. Before any major choice, write one line each for want, fear, timer, and cost. If one box stays empty, build a scene to fill it.

Deus ex machina and convenient rescues

Luck solves the problem. A sniper appears on a rooftop. A spell shows up in a footnote. A long-lost aunt pays the ransom. Readers feel the strings.

Solutions need set-up or a choice. Plant tools and knowledge early. Or flip coincidence into a complication, not a fix. A character decision must turn the outcome.

Example. The bridge collapses and the hero falls into a passing boat. Coincidence. Reframe. The boat breaks ribs and exposes the hero to patrols, which forces a new plan. Luck hit, then cost followed, and a decision guides the next step.

Plant better. If a lockpick saves the day at the midpoint, show it in a pocket in chapter two. Or show a failed lockpick attempt earlier, which both sets a rule and makes the later success feel earned.

Timeline and continuity errors

People teleport. Night flips to noon. A gun returns after being tossed off a cliff. Trust erodes when time and objects wobble.

Fix with a simple timeline. Scene by scene. List date, time, location, elapsed time. Add travel, rest, recovery. If a character crosses town, add traffic. If a wound heals, respect healing windows.

Example. Your hero gets stabbed on Tuesday, runs a rooftop chase on Wednesday, then swims a mile on Thursday. Adjust. Give Wednesday to morphine and fallout. Move the chase to Friday with a brace.

Line-level aids help. Time-stamps in chapter headers. A text that reads, meet at 23:40. A sunrise described in hard terms, not vibes.

Worldbuilding and rule violations

Magic works with blood once, then with a wink later. Law enforcement roars in one scene, then forgets to exist in the next. Readers do not forgive sliding rules.

Write a rules-and-costs page. Limits and prices. Clarify power ranges, failure modes, legal boundaries, social hierarchies. Then add a calibration scene early. Show a boundary before the midpoint.

Example. Teleportation needs a fixed anchor and drains the caster for an hour. Show a small hop that leaves the mage gasping. Later, when a long jump saves lives, readers know the price and wait to see who pays.

Institutions need shape. If calling the police would end the story, add a warrant delay, a jurisdiction fight, or a credible reason the hero avoids them, such as corruption with names and evidence.

Clue logic and knowledge leaps

Mystery and thriller readers track fairness. When the sleuth “knows” without access or a clue appears from thin air, the contract breaks.

Build a clue lattice. Setup, discoverable clue, interpretation, consequence. Make access plausible. Make misdirection fair.

Example. Setup, the victim loved old films. Discoverable clue, a bookmarked clip on a home computer. Interpretation, a line quoted in the ransom note points to a film buff. Consequence, the suspect list narrows to the projectionist and the cousin who runs a cinema club.

Avoid knowledge leaps. If the code phrase requires Latin, give the protagonist a reason to read Latin. A class. A parent. Or put a translator in the scene and pay with time or risk.

Chekhov’s gun and dangling threads

You show a knife on the mantel, then forget it. Or a payoff arrives with no seed. Readers notice. You taught them to watch. Deliver or remove.

Run a promise and payoff audit. List every promise in Act I, plot, clue, relationship beat, emotional arc. Confirm delivery or intentional subversion by the end.

Example. In chapter three, the mentor warns, never cross the river after dark. If no crossing matters later, cut the warning. If a crossing matters, plant a reason in Act I, a ferry schedule or a folk tale with a cost, then pay it in Act III.

Prune without guilt. Removing a stray setup often sharpens focus and reduces noise.

Power creep and antagonist inconsistency

Abilities change from scene to scene. The villain hacks any system on Monday, then fails to open a garage door on Friday. Heroes level up without cost. Stakes go mushy.

Define capability ranges for both sides. Add costs for high-power actions. Show escalation with trade-offs on page.

Example. The telepath reads crowds for surface thoughts, but deep dives burn memory. Early scenes show headaches after short probes. At the climax, a deep dive saves a life and erases a childhood memory. Power, price, consequence. Readers feel the weight.

Keep the antagonist honest. Give them a plan, resources, blind spots. If they fail, show why, not because the hero needed a win.

Two quick diagnostics to run this week

• Label each scene with G, C, O. Goal, conflict, outcome. Add a line for new information. Missing goal, no engine. Missing conflict, flat scene. Outcome without a cause, red flag for a hole.
• Circle any moment solved by luck. Then rewrite so a choice or sacrifice earns the result. A bruise, exposure, a burned bridge. Tie the price to the character arc.

One last reminder. Readers love to work. They lean forward when cause and effect stays tight and rules hold under pressure. Give them fair play, honest stakes, and choices that hurt. The story will hold. The holes will not.

Diagnose Plot Holes Before Readers Do

Readers spot logic gaps fast. Do the forensics before they do.

Reverse outline

Write one line per scene. State who wants what, the obstacle, and the turn. Then note how this scene triggers the next one. Use because, therefore, or but. If you hit an “and then,” flag it.

Mini-check. Pull three scenes from the middle. Summarize each in one sentence. Draw arrows between them. If the arrow says “and then,” either add a cause or cut the scene.

Example. Scene 12, Maya steals the keycard. Therefore, Scene 13, she enters the vault. But, Scene 14, the vault triggers an alarm, which forces a choice.

Beat sheet audit

Holes love act breaks. Verify your Inciting Incident, First Plot Point, Midpoint, Crisis, and Climax. Each beat must change the story’s direction and lock in new stakes.

Questions to ask:

• Does the Inciting Incident force a response, not a mood shift?
• Does the First Plot Point close the door on the old plan?
• Does the Midpoint reveal new information that raises stakes?
• Does the Crisis corner the protagonist into a hard choice?
• Does the Climax resolve the central goal on-page?

If a beat feels thin, strengthen cause and effect before and after it.

Promise-and-payoff tracker

List every promise made in Act I. Plot hooks, clues, warnings, emotional vows. Next to each, note where the payoff lands or how you subvert it. If no delivery, prune or plant.

Example entries:

• Aunt’s locket with a hidden hinge, promised in ch. 2. Payoff in ch. 24, holds the map shard.
• “Never cross the marsh after dusk,” warned in ch. 3. Payoff in ch. 18, crossing costs an ally.

Do a pass looking only for promises. Readers remember them. So should you.

Timeline and map

Build a calendar. Put days and times on scenes. Add travel durations, sleep, recovery, meal breaks, fuel, and weather. Draw simple maps for key locations, even a napkin sketch helps. Test movement and line of sight.

Reality check. A six-hour drive eats daylight. A stab wound needs rest and care. A storm delays the ferry. Respect physics and logistics, and readers relax into the story.

Line tools help. Chapter headers with time stamps. A text thread with time stamps. A sunrise described with specifics, not vibes.

Style sheet and story bible

Track names, ages, eye color, jobs, vehicles, pets, rules for tech or magic, currency, slang, food, laws. Keep a page for each system. Note limits and costs.

Use it during revision. If Nora’s car is a blue Civic in ch. 1 and a red Jeep in ch. 10, fix the outlier. If healing magic works once per day in chapter two, hold that line later when pressure rises.

Pro tip. Add a “known unknowns” page. Questions you still need to answer. Fill those before line edits.

Reader testing

Target your beta readers. A nurse for medical scenes. A parent for school politics. A mystery lover for clue fairness. Give a clear brief.

Ask focused questions:

• Where did confusion kick in?
• Which moment felt too easy?
• When did you doubt a choice or motive?
• What solution would you try first in the hero’s shoes?

Do not defend on the spot. Note patterns. Three readers stumbling in the same place points to a hole.

Expert and sensitivity review

Bring in subject-matter experts for plausibility. A lawyer for warrants and hearings. A climber for anchor points. A coder for network access. Bring in sensitivity readers for culture, identity, history, and community norms.

Give context, not your whole draft. Provide the scene, your current rules, and the intended effect. Ask where reality would push back. Fix on-page with limits, process, and consequence.

Actionable: keep a hole log

Start during draft one. Keep it simple.

• Page or scene number
• Issue type, motivation, clue logic, timeline, rule, continuity
• Suspected cause, missing setup, wrong sequence, weak stakes, broken rule
• Proposed fix, cut, plant, reorder, rewrite choice
• Status, parked, in progress, solved

Batch similar fixes. All timeline tweaks in one pass. All rule calibrations in one pass. Saves time and reduces new errors.

Actionable: run the simpler solution test

For each major problem, ask the obvious question. Why not call the police. Why not use the spell again. Why not take the train. If a simpler path exists, add constraints on-page.

Examples of credible constraints:

• Legal, no warrant, gag order, probation risk
• Technical, no signal, dead battery, rate limit on magic
• Social, trust risk, witness in danger, family vow
• Physical, injury, distance, weather, locked door with alarms

Put the constraint where the reader will look for it, before the decision point. A single line often covers it. “No signal. Tower down since the storm.” Or, “We have one charge left. After this, nothing until sunrise.”

Do these checks, and your story tightens. Cause leads to effect. Rules hold under pressure. Readers lean in, not back.

Repair Strategies That Don’t Break Something Else

Fix the logic without tearing new holes. Work small, aim true, and let the story carry the weight.

Start with the root cause

Before tinkering, label the problem. Missing setup, wrong sequence, weak stakes, or broken rules. Symptoms look similar. Causes do not.

Quick test:

• Missing setup. A skill or tool appears late with no plant.
• Wrong sequence. Information arrives after the choice it should guide.
• Weak stakes. A “big” decision with no on-page pressure.
• Broken rules. The world behaves differently when pressure hits.

Example. Your thief cracks a biometric safe on sight. Root cause, missing setup. Fix, show prior access, a copied print, or a workaround introduced earlier. Do not explain with a paragraph. Show the plant where readers expect it.

Add setup or remove payoff

An unsupported payoff begs for a wall of explanation. Resist. Plant early, or cut the payoff.

Example. The poison antidote shows up in chapter 28. Option one, seed a clinic visit in chapter 6 where the doctor mentions that antidote stock exists in limited doses. Option two, remove the antidote, force a different choice, perhaps a sacrifice or detour that costs time.

Rule of thumb. If adding a graceful plant takes fewer lines than explaining late, plant. If not, rip the payoff and build a cleaner outcome.

Mini-exercise. Circle every late-stage solution. For each, write a two-line plant in Act I or early Act II. If no elegant plant fits, consider a new outcome.

Re-sequence events

Sometimes events are fine, order is not. Move revelations earlier or later so choices feel earned. Information must arrive before the moment it influences.

Example. The suspect’s confession comes after your detective accuses the wrong person. Flip them. Let the confession hit first. Now the accusation lands with bite, or the detective changes course, which shows growth.

Try this. Take your last act. Write each reveal on a sticky note. Shuffle and test three orders. Read the sequence out loud. Keep the order where motive and pressure align.

Convert convenience into consequence

Luck saved the hero. Readers feel cheated. Charge a price and tie it to the arc.

Example. A random blackout lets your protagonist slip past guards. Turn the blackout into a threat. Alarms trip, the backup generator fails, oxygen levels drop in the lab. The escape works, but now an injured ally needs help, or the break-in exposes a secret, which fuels the next scene.

Ask, what price fits the theme. Injury for someone who fears weakness. Public exposure for someone who hides. The bill must come due.

Gate knowledge

Who knows what, when. Access needs groundwork. Foreshadow, build clue chains, and add “checks” scenes where a process becomes credible on the page.

Example. A hacker guesses a password on the first try. Thin. Fix one, show the phishing attempt two chapters earlier. Fix two, make the hacker an ex-employee who kept a backdoor, introduced in Act I. Fix three, restrict knowledge, give the password to a side character, and make the trade costly.

Ask before each leap. Do they have access. Do they have time. Do they have reason to look there. If one answer is no, supply a plant or change the plan.

Merge or refocus subplots

Redundant threads breed contradictions. Collapse or trim to clarify stakes.

Example. Two mentors offer advice in different scenes, one gentle, one harsh. Merge into one mentor with a sharp edge and a soft history. Now motive aligns, and you cut a scene with no turn.

Another move. Shift a subplot’s goal so it serves the main spine. The office rivalry becomes the reason the hero loses a key resource at Midpoint. Same scenes, clearer purpose.

Exercise. List every subplot with its function, reveal, turn, and payoff. Cross out any line with no turn or no consequence to the main plot. Either fold into another thread or cut.

Calibrate rules on the page

Readers will accept limits if they appear before crisis. Show costs and failure modes.

Example. Teleportation drains glucose and memory. Two jumps in an hour lead to migraines and lost nouns. Show that cost in a low-stakes scene early. When the hero refuses a third jump to save a friend, readers accept the limit.

Add a calibration scene before the midpoint. A teacher, a manual, a failed test. Keep it brief. One page of action beats one page of exposition.

Line-level anchoring

Sometimes the hole lives in the glue. Add time, place, and causal links at the sentence level.

Tools:

• Time stamps. “Tuesday, 6 a.m.”
• Location tags. “Outside the courthouse.”
• Causal connectors. “Because the alarm blared, she cut the wire.”
• Micro-foreshadowing. “He pockets the bent paperclip.”

Example. “He walks out of the bar. Next scene, he wakes on a train.” Add a line. “The last bus left at eleven. He watches the taillights fade, then buys a midnight ticket.” Now the move reads as a choice, not a teleport.

Choose the smallest effective fix

Avoid nuclear solutions. Start small.

Order of operations:

1. Cut or merge. Remove the thread that causes conflict or confusion.
2. Plant or foreshadow. Add a line or beat to set up a later move.
3. Reorder. Move a reveal earlier or later to support a choice.
4. Rewrite the choice. Only if the first three fail.

Test ripple effects after each change. A small plant in Act I touches Act III. Note any new edges and smooth them before moving on.

Test the repair

Run a targeted read of the affected sequence only, setup to payoff. No skimming. Mark where your eye trips. Then do a fast read of the whole act for clarity and pace. If you slow down to explain to yourself, the fix needs one more pass.

One more tip. Read aloud. Your ear hears gaps your eye forgives.

Do this work, and patches disappear into the fabric. Cause leads to effect. Stakes rise in clean lines. Readers feel safe in your hands, which means they lean forward and stay there.

Prevention: A Plot Consistency Toolkit

Prevention beats patching. Put a few guardrails in place, and your draft stops fighting you.

Prewrite guardrails

Build a one-page brief before pages pile up. Nothing fancy. One screen, tight.

Include:

• Premise in one sentence.
• Protagonist’s goal and what fails if they miss it.
• Antagonist’s plan and the pressure it applies.
• Non‑negotiable rules for tech, magic, law, and social norms.
• Scope limits, travel, communications, recovery time.

Example, brief lines:

• Premise. A paramedic hides a whistleblower after a hospital cover-up.
• Goal. Get the witness to the state investigator by Friday.
• Stakes. If she fails, more patients die and she loses custody.
• Antagonist plan. Hospital security controls cameras and pays a bounty.
• Rules. No real-time hacking. Citywide blackouts last at least two hours. Ambulances require logs.

Print it. Keep it next to the keyboard. When a scene fights the page, check the brief first.

Scene cards

One card per scene. Five fields, done.

• Goal. What the viewpoint character tries to get.
• Opposition. Who or what pushes back.
• Immediate stakes. Loss today, not someday.
• Turn. The beat that shifts power or knowledge.
• New question. The appetite for the next scene.

If a card lacks a turn, redesign before writing.

Sample card:

• Location. Rooftop handoff, 2 a.m.
• Goal. Nina takes the drive from the courier.
• Opposition. Private security scans rooftops. Partner late.
• Stakes. Lose the proof, lose her license.
• Turn. Partner arrives with two uniformed cops.
• New question. Who tipped the cops.

Tape the cards in order. If three in a row repeat the same goal or lack turns, fold or merge.

Reveal calendar

Schedule your plants and payoffs so tension rises cleanly. Use a simple grid.

Columns:

• Setup. The moment a tool, rule, or name enters the story.
• Development. A reminder or twist that keeps it warm.
• Payoff. The scene where it matters.

Aim for rhythm. Plant early. Touch it mid-act. Pay it off under pressure.

Small example:

• Setup. Chapter 3, the hero notices the spare key under the dragon planter.
• Development. Chapter 9, the planter appears in a background line.
• Payoff. Chapter 22, the hero grabs the key while the alarm blares.

If a payoff lacks a setup, write a two-line plant or cut the payoff.

Constraint checks

Stop “why don’t they” questions before they start. Define frictions early and show them in action.

Common constraints:

• Communications. No signal in elevators, traceable calls within city limits, encrypted messages take hours to decode.
• Travel. Ferries stop at midnight, checkpoints add thirty minutes, horses tire after twenty miles.
• Money and resources. Ammo scarce, fuel rationed, visas required, rare herbs spoil in heat.
• Law and institutions. Warrants take a day, bail denied for violent charges, security audits log every badge swipe.
• Power limits. Magic drains stamina, AI access restricted to public terminals, drones need line of sight.

Put one small scene on the page that proves each constraint. Readers learn the rules by watching the rule bite.

Version control and change log

Memory lies. Keep a log of changes so the story bible stays current.

Create a simple document named CHANGELOG.

Use this format:

• Date.
• Chapters affected.
• Change summary.
• Reason.
• Follow‑ups required.

Sample entry:

• 2025‑03‑12. Ch 12, 17. Moved the lab break‑in before the confession.
• Reason. Confession must drive the decision, not explain it.
• Follow‑ups. Update timeline. Add a line in Ch 10 foreshadowing new camera coverage.

Review the log weekly. Update names, ages, rules, and maps to match.

Feedback pipeline

Use the right reader at the right time.

• Alpha reader. Tests the concept and promise. Ask, what grabbed you, what feels thin, where did your attention wander.
• Developmental editor. Structure and causality. Ask, where logic fails, where stakes sag, where order fights motive.
• Beta readers. Narrative consistency and emotional truth. Ask, where confusion hit, what felt easy, which choice rang false.
• Copyeditor. Continuity polish, time of day, names, ages, props, spelling.

Send focused questions. Limit each round to the layer you are testing.

Tools worth using

Pick a few. Keep them light.

• Beat sheet or spreadsheet tracker. One line per scene with goal, turn, word count, and notes.
• Aeon Timeline or a similar app. Dates, travel times, age math, moon phases.
• Style sheet. Names, spellings, titles, terms, capitalization, pet phrases.
• Worldbuilding bible. Rules and costs, maps, social order, economy, tech limits.
• Tension heat map. List scenes and rate tension from 1 to 5. Look for long cold patches.

Tools help, but habits do the work.

Two checklists

Pre‑draft checklist:

• Premise sentence approved.
• Protagonist goal and stakes clear.
• Antagonist plan mapped across acts.
• Non‑negotiable rules listed with costs.
• Constraint scenes scheduled.
• Reveal calendar sketched for key plants and payoffs.

Pre‑revision checklist:

• Beat audit complete for Inciting, First Plot Point, Midpoint, Crisis, Climax.
• Reverse outline built with cause, effect, and “and then” flags.
• Promise and payoff tracker updated.
• Timeline verified with travel and recovery windows.
• Style sheet and bible synced to the draft.
• Hole log pruned, fixes prioritized by smallest effective change.

Print the lists. Check them off with ink. Your future self will thank you.

The final logic pass

Do this after line edits sit for a day. Read fast, eyes on logic only. Mark three things in the margin.

• C for causality.
• R for rules.
• M for motivation.

If a scene lacks one of those letters, it needs a tweak. Fix only those marks, then read the whole act cold for pace.

One quiet habit, huge payoff. Your story holds water. Your readers stop looking for leaks and start turning pages.

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