How to Find Plot Holes in Your Novel (Before Your Editor Does)

A plot hole is the moment a careful reader stops reading and goes back two pages because something didn't fit. They might keep going. They might not. Either way, the spell is broken.

The good news is that almost every plot hole in a finished manuscript is catchable before publication if you know how to look. The trick is that you can't catch them by reading the book again. You wrote the book. Your brain fills in what's not on the page. You'll re-read your own manuscript twelve times and miss the plot hole that the average beta reader catches in chapter three.

This post is the seven-pass system I've watched working novelists use to find plot holes in their own manuscripts before sending the book to an editor or to readers.

What "plot hole" actually covers

The term gets used loosely. For a working revision, separate it into four distinct kinds of breaks, because you catch them with different techniques:

1. Causal breaks. Event B is supposed to follow from event A and doesn't. The protagonist makes a choice that doesn't actually proceed from anything in the previous 50 pages.
2. Continuity breaks. Eye colors change. Place names change. Someone is in two cities on the same day. Someone knows a thing they shouldn't know yet.
3. Logical breaks. The world's rules contradict themselves. A magic system that worked one way in chapter 4 works a different way in chapter 18 with no explanation.
4. Motivational breaks. A character does something the character has no reason to do, except that the plot needed it.

The seven-pass system below catches all four, in roughly the order they're easiest to see.

Pass 1: Print the manuscript. Read on paper.

Cheap pass, expensive insight. Print your novel one-sided, sit somewhere you don't normally sit (a coffee shop, a park bench, anywhere your "writing chair" instincts don't fire), and read with a red pen.

You will see things on paper that are invisible on screen. Your brain reads the screen too fluently. It's familiar with the text. Paper, somehow, breaks the familiarity. Two-thirds of the obvious mistakes you've been missing show up here.

What to mark, in this pass:

• Anywhere a sentence makes you stop and re-read.
• Anywhere a chapter ending feels too easy.
• Anywhere you suddenly can't remember why the protagonist made the previous decision.

Don't try to fix anything. Just mark. Three to five hours, depending on book length.

Pass 2: Build a chapter-by-chapter scene grid

This is the pass that catches the most plot holes. It's also the most boring.

Open a spreadsheet. One row per chapter (or one row per scene, if your chapters have multiple scenes). Columns:

• Chapter / scene number
• POV character
• Timeline (specific date, day-of-arc, or "next morning")
• Location
• Who's in the scene
• What does the POV character want in this scene? (one sentence)
• What's the conflict? (one sentence)
• What changes by end of scene? (one sentence)
• What does the reader learn that they didn't know before?
• Plot threads active in this scene (label each thread with a one-word name)

Fill it in scene by scene, not from memory. From the manuscript. This will take 6 to 12 hours on an 80,000-word novel. There is no shortcut. The grid is the point.

When you're done, read down each column.

• The timeline column will surface continuity breaks. "Scene 14 is Tuesday morning. Scene 15 is Wednesday afternoon. Scene 16 is also Tuesday afternoon." Every novelist has this. Catch it now.
• The want column will surface motivational breaks. If a character has no want in three consecutive scenes, those scenes are coasting. The book sags. If the want is unchanged for ten scenes, the arc has stopped moving.
• The changes by end of scene column will surface causal breaks. If three scenes in a row "nothing changes", you have padding. If a scene "changes everything" but the next scene doesn't proceed from that change, you have a causal hole.
• The plot threads column will surface dropped threads. If thread "the lighthouse" appears in chapters 3, 7, 9, and then disappears, ask whether you finished it.

Spreadsheets are dull. They are also the single highest-leverage tool for catching structural plot holes in your own work.

Pass 3: The character knowledge audit

A specific subset of plot holes that's hard to see during writing: what does each character know, and when do they learn it?

For each significant character, build a small knowledge timeline:

• Character name
• The 5 to 10 important pieces of information in your book (e.g. "the antagonist is the protagonist's brother", "the magic system requires blood")
• For each, write the chapter where this character learns it

Then read your manuscript and check whether characters ever act on knowledge they shouldn't yet have, or fail to act on knowledge they already do.

A common version of this break: in chapter 18, your protagonist references the antagonist's identity in dialogue. But the reveal scene is in chapter 22. They couldn't have known yet. This kind of break is almost invisible during writing because you know, and the character feels like an extension of you.

Romance writers know this one too. The "we're not officially together but they know" trope is a fertile ground for accidentally giving a character information they wouldn't have at a given moment.

Pass 4: Cause-and-effect read

Open the manuscript. For every chapter, write down in the margin: "This chapter happens because of: ___", with the answer being a previous chapter or scene.

A finished novel has a cause-and-effect chain. Each chapter (after the first) is the consequence of something earlier.

If you can't fill in the answer for a chapter, that chapter is disconnected. It might still be a good chapter. But if the only reason it's there is "and then this happened next", you have a structural hole between chapters that's worse than any continuity error.

The fix is usually one of:

• Add a setup scene earlier so this chapter is a payoff
• Replace this chapter with a different one that does follow causally
• Cut the chapter and merge what's load-bearing into adjacent chapters

This pass is brutal on a first novel. It often kills 5,000 to 10,000 words. The book that comes out the other side is a much tighter book.

Pass 5: The reverse read

Read your novel from the last chapter backwards to the first. Not paragraph-by-paragraph backwards, just chapter-by-chapter.

This breaks the plot momentum that lets you skim. You're reading each chapter cold, without the build-up that the previous chapters created.

What you'll catch:

• Foreshadowing that's missing (you reach a climax that the earlier chapters didn't set up)
• Foreshadowing that's hammered too hard (you reach a "twist" you've been telegraphing since chapter 4)
• Chapters that don't independently make sense without the lead-up
• Pacing that felt fast forward, but going backward, you can see was just a list of things happening

The reverse read is uncomfortable. It is also the pass that surfaces the structural problems your forward reads have been hiding.

Pass 6: Beta readers, with the right brief

Generic beta readers give you generic feedback. ("It was great! The middle felt slow.") Useful for vibes. Useless for plot holes.

For a plot-hole-targeted beta read, brief your readers with three specific asks:

1. "At any point, did you stop reading and go back? Tell me where and why." This catches continuity breaks and causal breaks the reader noticed.
2. "Was there ever a moment a character did something that didn't make sense to you?" This catches motivational breaks.
3. "Did anything contradict itself? Magic rules, geography, dates, character knowledge?" This catches logical and continuity breaks.

Three to five readers, all in your genre, ideally writers themselves. Do not ask "did you like it." That's a different conversation that you can have after you've fixed what's broken.

When the reader feedback comes in, look for convergence. One reader catching one thing might be the reader, not the book. Two readers catching the same thing is the book.

Pass 7: The AI developmental read

This is new in 2026 and it's a real pass. AI tooling can run a structural analysis on a finished manuscript and produce three things humans struggle to do:

• A chapter-by-chapter scene grid like the one in Pass 2, but auto-generated. Saves the 6 to 12 hours.
• Continuity flags across the whole manuscript. The AI catches "Marcus has brown eyes in ch. 2 and blue eyes in ch. 17" or "the timeline says Tuesday in ch. 14 and Tuesday again in ch. 16, both as 'today'".
• Voice drift detection. Where does chapter 18 sound like a different writer than chapter 4? This isn't strictly plot hole territory, but it correlates with chapters that were written months apart, which is often where causal breaks live.

A good AI pass doesn't replace beta readers. It catches the mechanical layer (continuity, structure, scene-level pacing) so the humans can spend their attention on the judgment layer (does this chapter belong, is this scene the right scene to spend 4,000 words on).

This is what Inkett Editor is built for. It runs a developmental read on a finished manuscript and returns the same shape of letter and notes a freelance editor would write. It's the layer below the human read, not the replacement for it.

What to do after you've found the holes

Catching the holes is the first half. Fixing them is harder.

A few principles that keep the fix from creating new holes:

• Fix structural breaks before continuity breaks. If you're going to rewrite chapter 14, don't waste time fixing the eye color in chapter 14. The chapter might not survive.
• Make a list of every fix before changing anything. New writers fix one hole, the fix breaks two scenes, they fix those, those break three more, and the manuscript drifts. Plan the cascade.
• Read the fixed scenes in context with the unchanged scenes around them. Sometimes a fixed scene reads as fixed in isolation but doesn't sit right next to its neighbors.
• Run another scene grid pass after substantial fixes. Yes, again. Yes, it's painful. The grid will surface fixes that broke other things.

A short list of plot holes I've seen working novelists ship anyway

Not every plot hole is fatal. Some are nitpicks. The threshold for "must fix" is roughly:

• Always fix: breaks in the cause-and-effect chain. Breaks where a character knows something they shouldn't. Breaks in the established rules of your world. Timeline impossibilities.
• Usually fix: continuity errors (eye colors, place names). Readers notice and review accordingly. Cheap to fix. No reason to leave them.
• Sometimes fix: "this character would never do this" if the moment is dramatically essential and you can plant a setup scene earlier. If you can't make it earn, cut it.
• Don't fix: plot conveniences in genre fiction that are conventions of the genre. (The romantasy heroine surviving the explosion. The thriller protagonist getting one good break. Genre forgives these. Don't twist your book in knots fixing what readers won't notice.)

---

A novel without plot holes isn't a novel without holes the reader could imagine; it's a novel where the reader doesn't trip on the holes that are there. Your job in revision is making sure no reader stops reading because something didn't fit.

If you've gone through the seven passes and you want a structural read that catches what you missed, Inkett Editor runs the developmental and continuity layers on a finished manuscript and returns chapter-anchored notes the same way a freelance editor would. The Editor is live for founding writers today. See also How Much Does a Developmental Edit Cost in 2026? for the full picture of when the AI pass is enough vs when you'd want a human editor on top of it.