Can AI Catch Plot Holes in Your Novel?

You know that feeling when you're 200 pages into a revision and you realize your protagonist's eyes changed from brown to green somewhere around chapter twelve? Or that the coffee shop on Elm Street suddenly became a bar on Oak? Or that Tuesday somehow happened twice in the same week?

Yeah. That feeling.

Continuity errors are the quiet killers of otherwise solid manuscripts. They don't announce themselves. They hide in the cracks between scenes you wrote six months apart, in the gap between what you MEANT to establish and what you actually put on the page. And the worst part... you can read your own manuscript fifteen times and still miss them, because your brain auto-corrects what it already knows.

So can AI actually catch these things? The short answer is yes, with some important caveats I'm going to be honest about.

What "plot holes" actually means (because everyone uses the term differently)

When most writers say "plot holes," they're really talking about two very different problems.

The first is continuity errors. These are factual contradictions within your own story. A character's physical description changes. A timeline doesn't add up. A door that was locked in chapter three is mysteriously unlocked in chapter five with no explanation. A character references a conversation that hasn't happened yet. These are concrete, verifiable mistakes. You said X on page 30 and Y on page 180, and X and Y can't both be true.

The second is logical gaps. These are structural problems where the plot depends on something that doesn't quite make sense. Why didn't the character just call the police? How did they get from New York to London in an afternoon without any mention of travel? If the magic system requires a full moon, why is the climactic spell happening on a Tuesday afternoon?

AI is VERY good at the first category. The second... it depends.

What continuity analysis actually checks

A proper continuity pass across a full manuscript is tracking several things at once. Here's what the analysis looks for.

Character details. Names, physical descriptions, ages, relationships, occupations, habits. If your detective is left-handed in chapter two and shoots right-handed in chapter twenty, that's a flag. If a secondary character's name drifts from "Katherine" to "Catherine" to "Kathryn" across 300 pages (don't laugh, this happens ALL the time), the analysis catches it.

Timeline consistency. Days of the week, seasons, time of day, how long events take relative to each other. If your characters leave for a three-day journey and arrive the next morning, something's off. If it's autumn in chapter eight and summer in chapter ten with no time jump, that's a problem.

Setting details. Locations, physical layouts, distances between places. That coffee shop I mentioned? If you described it as being on the corner of Elm and Main in chapter four, and then your character walks past it on Park Avenue in chapter fifteen, a continuity checker will flag the discrepancy.

Established facts. Backstory, world-building rules, character knowledge. If a character is established as an only child and then mentions their brother, that's caught. If your fantasy world's magic system has clear rules you set up in act one, violations in act three get flagged.

This is the kind of work that a careful alpha reader does when they go through your manuscript for the first time. They're reading with fresh eyes, catching the things you've gone blind to. The difference is that an AI continuity checker doesn't get tired on page 200. It doesn't forget what happened in chapter three by the time it reaches chapter thirty. It's tracking ALL of these details simultaneously, across the entire manuscript, without the mental fatigue that makes human readers (including you) miss things.

Where this works really well

Continuity checking is one of the areas where AI analysis genuinely earns its keep. And it's worth being specific about why, because there's a lot of vague "AI is amazing" stuff out there. Here's what's actually happening.

The reason AI catches continuity errors reliably is that these are VERIFIABLE problems. The text says one thing in one place and a contradictory thing in another. You don't need taste or craft judgment to identify that. You need a system that can hold the entire manuscript in memory and cross-reference details across hundreds of pages.

That's exactly what a full-manuscript analysis does. It's not sampling a chapter here and there. It's processing the whole book, building a picture of your characters and settings and timeline, and then checking for internal contradictions.

This is also why the "just use ChatGPT" approach falls short for most novels. If you're pasting in chapters one at a time, the tool has no memory of what happened in previous chapters (or at best, a very compressed summary). Continuity checking only works when the system sees EVERYTHING. Your 90,000-word manuscript. All of it. At once.

FirstReader does exactly this. The continuity checker runs across the full manuscript, not chapter-by-chapter, tracking character details and timeline and setting and established facts from page one through the final chapter. It's the alpha reader who actually remembers every detail you wrote.

Where this gets harder

Here's where I need to pump the brakes, because if I pretended AI catches EVERYTHING related to plot holes, I'd be lying. And you'd figure that out the first time you used it.

Thematic coherence. Does your novel's central theme actually resolve? Does the protagonist's internal arc connect to the external plot in a way that feels earned? AI can tell you if your character literally contradicts themselves. It can't tell you if their emotional arc is thematically hollow. That requires the kind of interpretive judgment that... well, that's still very much a human skill.

Subtle foreshadowing payoff. If you plant a gun on the mantelpiece in act one (hello, Chekhov), a continuity checker can note that there's a gun and track whether it appears again. What it can't reliably assess is whether the payoff LANDS. Whether the reader will feel the satisfaction of that setup paying off, or whether it fizzles. The mechanics of foreshadowing are trackable. The emotional weight of the payoff is not.

Motivation logic. "Why didn't the character just leave?" That's a question about plausibility within the world you've built, and it requires understanding character psychology, social dynamics, genre conventions... all things that AI handles inconsistently. Sometimes it nails it. Sometimes it misses the obvious. I wouldn't trust it as the final word on whether your character's decisions make sense.

"Feeling" wrong. You know when you read a book and something bothers you but you can't put your finger on what? A good developmental editor can diagnose that. They can say, "The problem is that you've set up tension in this subplot and never resolved it, so the reader feels uneasy without knowing why." AI isn't there yet. It catches what's explicit. The implicit stuff... that's still territory for a human editor or a really sharp beta reader.

The key takeaway: AI continuity checking catches factual contradictions in your manuscript. It verifies what's on the page against what's elsewhere on the page. It does this faster and more thoroughly than any human reader, because it doesn't get tired and it doesn't forget. But it doesn't replace the interpretive, gut-level feedback that a skilled human gives you.

For a deeper look at what AI can and can't do in craft analysis more broadly, this piece covers the honest answer.

Why this matters more than you think

Writers tend to dramatically underestimate how many continuity errors are in their manuscripts. You assume that because YOU know the story, the story is consistent. But the you who wrote chapter three in January is not the same you who wrote chapter twenty-five in July. You changed things. You moved scenes around. You decided your character's backstory needed reworking, and you updated it in chapters fifteen through twenty but forgot about the reference in chapter six.

And readers notice. Maybe not every single one. But enough of them. A few eye-color changes probably won't tank your reviews. But a character who knows something they shouldn't, or a timeline that doesn't add up, or a setting that contradicts itself... those pull readers out of the story. And once a reader gets pulled out, getting them back is hard.

For indie authors especially (and if you're reading this, you probably are one), this matters because you might not have a full editorial team catching these things before publication. You might be working with beta readers who are great at telling you how the story FEELS but aren't tracking your protagonist's eye color across 350 pages. An alpha reader or a good continuity analysis is the safety net between your final revision and hitting "publish."

Try it yourself

FirstReader runs continuity analysis across your full manuscript as part of its craft report. Every finding traces back to specific passages and names the craft principle behind it. No vague "this felt off" comments. You get the exact contradiction, where it appears, and why it matters.

You can try it with a free chapter analysis to see the kind of detail it catches. Odds are pretty good it'll find something you missed. (It usually does. Don't feel bad about it... that's literally the point.)

Final words

Plot holes and continuity errors are different problems, and it's worth knowing which ones AI handles well and which ones still need human judgment. The factual stuff, the verifiable contradictions, the details that drift across a long manuscript... AI catches those reliably, and it catches them faster than you or any single human reader can. The interpretive stuff, the thematic questions, the "does this FEEL right" judgment calls... that's still on you and your editor.

Use both. That's the real answer. Get the continuity checked systematically so your human readers (your editor, your beta readers, your alpha readers) can focus on the stuff that actually requires human judgment. Don't make them waste their expensive time catching a character's eye color change on page 212.

If you enjoyed this and want more on the craft analysis side of things, stick around. And if you think I got something wrong... well, I'd like to hear about that too.