She had green eyes in chapter three. They’re gray in chapter twenty-eight.
Nobody caught it. Not you, even though you’ve reread this manuscript six times. Not your beta reader, who read fast because the plot carried her along. Not your copyeditor, who was hunting commas.
But a reader will catch it. There’s always one. And the worst part isn’t that they see it. It’s what it sets off in their head: at that exact moment, they stop being inside your world and go back to being someone reading a text written by someone else. You’ve just lost the immersion it took you three hundred pages to build.
This article won’t promise you a magic button that finds all your inconsistencies. That button doesn’t exist, and I’ll explain why. It’ll give you something else: a method for hunting them down, and a way to produce far fewer of them.
Why you can’t see your own inconsistencies
It isn’t carelessness. It’s your brain betraying you, and it does so for good reasons.
When you reread your text, you don’t read it. You recognize it. You know what’s supposed to be written, so you see it. Your brain fills in the gaps, silently corrects, glides over what’s wrong. It’s the same mechanism that makes you reread a sentence with a typo ten times without seeing it, until a stranger points it out in three seconds.
On top of that, there’s a memory problem, and it’s structural. You don’t write your novel in three days. You write it over months, sometimes years. The you of chapter thirty-two no longer holds the memories of the you of chapter three. In between, you’ve changed your mind fourteen times, you’ve forgotten decisions, you’ve made new ones that contradict the old ones without you noticing.
You’re not rereading your novel. You’re rereading your memory of it.
The six families of inconsistencies
They aren’t hunted the same way, and that’s why you have to tell them apart.
Factual inconsistencies. Eye color, age, the name of a village, the number of siblings. The dumbest, the most visible, the easiest to fix. They almost always come from the same place: a piece of information invented on the fly, never written down.
Chronological inconsistencies. The most insidious ones. A character takes two days to get from one place to another in chapter five, and three hours in chapter nineteen. A pregnancy that lasts fourteen months. A child who’s eight in the spring and eleven the following fall. They hide in the cracks, and you only see them if you take the trouble to reconstruct the timeline.
Knowledge inconsistencies. Who knows what, and since when? A character uses information he wasn’t supposed to know. He reacts to an event he didn’t witness. He’s unaware of a secret revealed to him twelve chapters earlier. It’s the most destructive family, because it touches the plot itself.
Character inconsistencies. A character acts against his nature with nothing to justify it. The coward turns heroic because the scene needed it. The meticulous one slips up because the plan had to fail somehow. The reader won’t think “that’s inconsistent,” they’ll think “I don’t buy it,” which is worse.
Rules inconsistencies. Your magic can do this in chapter seven, but not in chapter twenty-one. Your technology works differently depending on what the scene needs. Every rule you set becomes a promise. Breaking it without justification is a betrayal.
Spatial inconsistencies. The bedroom is on the right going up, then on the left. The town is on the seashore, then three days’ walk from the coast. They seem minor, but they blur the mental map the reader is building.
Why no software detects them automatically
This is the moment to be honest, because it matters for what comes next.
You might think an AI could do this. It reads everything, it compares, it flags contradictions. In practice, it would produce so many false alarms that you’d turn the feature off within ten minutes.
Take a simple example. Your hero is wounded in the leg in chapter eight. In chapter twenty-four, he runs. Inconsistency? No: sixteen chapters and three months have passed, he’s healed. But to a machine, it’s a blatant contradiction. Temporary states are a nightmare to model: wounded, drunk, asleep, angry, dead (and sometimes not quite as dead as all that).
Add the problem of synonyms and labels. “The old man,” “Aldric,” “the mage,” “his father” can all refer to the same person. Or to four different people. A machine has to guess, and it guesses wrong.
And above all: you don’t re-describe your characters on every page. The information “she has green eyes” appears once, in chapter three. Nothing in the text of chapter twenty-eight lets a machine know that they should have been green. The inconsistency only exists relative to information absent from the immediate context.
A detector that cries wolf three times out of four isn’t a tool. It’s a nuisance. That’s why I didn’t put one in my own software, even though I badly wanted to.
The good news is that there’s a more effective approach. And it comes down to a single idea: it’s better not to produce the inconsistency than to hunt it down afterward.
The method: hunt in separate passes
Here’s how to hunt inconsistencies when they’re already there. The principle is simple and counterintuitive: look for only one thing at a time.
A “general” reread finds nothing, because your attention is spread across thirty criteria. A reread that hunts only one type of error finds plenty, because your brain knows what to look for.
Pass 1: the ID card. Take one character. Just one. Reread the manuscript looking only for him: every mention of his appearance, his age, his family, his past. Write it all down. The contradictions jump out when they’re lined up in a table. Start over with the next one. It’s tedious, and it’s devastatingly effective.
Pass 2: the chronology. Reconstruct the timeline. Every scene, its date, its duration. How much time between chapter nine and chapter ten? Is it compatible with the journey described? With the season mentioned? With the child’s age? It’s the most painful pass, and the one that pays off the most.
Pass 3: knowledge. For each major revelation in your plot, list who knows it and since when. Then check every scene where those characters appear. Do they act like someone who knows? Or like someone who doesn’t?
Pass 4: the rules. List all the rules of your world, including the ones you didn’t realize you’d set. Reread, checking that none are broken without justification.
Pass 5: the voice. Every character has a way of speaking. Reread one single character’s dialogue straight through, skipping everything else. Does he sound the same from beginning to end? A character whose voice drifts is a character you no longer believe in.
The fresh-eyes technique. Between two passes, change the form of the text: print it, change the font, export it to EPUB and read it on an e-reader. Your brain stops “recognizing” and starts reading again. It’s unsettlingly effective.
The real cure: don’t create them
All these passes are useful. They’re also exhausting, and they come too late.
The inconsistency almost always arises from the same situation. You’re writing. The text is flowing. You need a piece of information: this character’s age, that town’s color, what this one already knows. You know you wrote it down somewhere.
And there, you’re stuck choosing between two bad options.
Either you stop writing to go find it. You open the binder, you dig around, you lose five minutes, and above all you lose your momentum. By the time you come back to the text, the sentence you were about to write has evaporated.
Or you make it up, promising yourself you’ll check later. You won’t check. Nobody ever checks. And you’ve just created the inconsistency you’ll spend three hours hunting for six months from now.
The real problem isn’t detecting. It’s having the information in front of you at the moment you need it.
What I ended up doing
This exact problem is the one that led me to code Le Grimoire. So here’s how it approaches it, and above all what it doesn’t do. (How you end up coding your own software is behind the scenes.)
What it doesn’t do: it doesn’t automatically detect inconsistencies. For all the reasons explained above. I’d rather promise nothing than promise a detector that would lie to you one time out of three.
What it does is answer the real problem: the information in front of you, without leaving the text.
While you write, a panel called the Oracle sits beside the editor. It reads what you type and displays, in real time, the characters and locations it recognizes in it, the ones that already exist in your universe. One click, and the sheet opens. You see the age, the eye color, the biography, the way of speaking. You close it, and you keep writing your sentence. Three seconds, not five minutes. And above all, you never left your text.
It’s a silly thing, and it’s what changes everything. Because the inconsistency doesn’t come from laziness: it comes from the cost of going to check. Drop that cost to three seconds, and you check. Every time.
The rest serves the same logic. Your Character and Location sheets live next to the manuscript, not in a separate file you never open again. The Timeline holds the dated events, which makes the chronological pass workable instead of an ordeal. The Constellation shows your characters and their relationships in 3D, which surfaces at a glance connections you’d forgotten.
And when you finish a scene, the scene analysis rereads it and extracts what it contains: characters present, locations, relationships that changed, events to date. It offers to update the sheets. Nothing is saved without your approval, because it’s your universe, not its own.
The result is a story bible that stays true. It feeds on the text you actually write, not the one you’d planned to write.
A principle I set for myself on day one, and one I won’t budge on: Le Grimoire’s AI assists, it never writes in your place. It organizes, it connects, it shows you. Your prose stays entirely your own.
Le Grimoire runs locally on your machine. The trial is free, no strings attached.
To close
Inconsistencies aren’t a moral failing. Every novel contains some, including the ones you admire. The goal isn’t perfection, it’s not letting through the ones that break immersion.
Hunt them in separate passes, one thing at a time. Change the medium to get your fresh eyes back. And above all, arrange things so that checking a piece of information costs three seconds rather than five minutes.
Because at bottom, an inconsistency is almost always a check you didn’t have the courage to make.