A plot hole is rarely a big mistake. It is a small fact from chapter four that chapter twenty-two forgot. Authrot keeps the facts each chapter establishes, tied to the words that established them, and points to the line that breaks one.
Free account, no card. Includes 50 AI credits to try the assistant.
Contradictions
Flagged against the fact it breaks.
When a chapter is read, a line that contradicts an earlier fact or one of your anchors is flagged with both sides shown: what the book said before, where it said it, and what this chapter says now.
0
plot holes
2
promises due or stalled
11
brief lines this chapter changed
20
facts recorded
Needs attention
Problems the scan found, and promises this chapter should deliver on, move forward, or leave alone.
Due nowPromise
The palace burned with the king inside, and no one saw it lit.
The ember keyHighcairn
DueBefore midwinter
Pay it off here, or give the reader a reason it waits.planted ch 1 · open 5 chapters
StalledPromise
The hooded knight names a price for his silence that Ilsa cannot pay yet.
The hooded knight
Give it a sign of life before the reader forgets it.planted ch 1 · untouched since ch 2
The brief
Anchored4
Details anchored in the story and truths reconciled with it. Never contradict these.
Anchored
Ilsa DanvarCharacter · 1 anchored
Fear
Cannot ride, and won't say why
The chapter brief
What’s fixed, what’s true now.
As a chapter opens you see what can’t change, what is true at this point in the story, what is planned, and what is overdue. It is the page an editor’s continuity notes would be, kept for you.
Due nowPromise
The regent would wear the crown before the year turned, and everyone in the Marches knew what that meant.
The crownThe Marches
DueBefore midwinter
Pay it off here, or give the reader a reason it waits.planted ch 1 · open 5 chapters
character6. SnowmeltIlsa Danvar
Ilsa rides out to the gate conflicts with Ilsa can’t ride
“Ilsa rode out to the Salt Gate before the others were awake.”
Established earlier: Ilsa doesn’t ride.
FixedNot a problem
Anchored facts
The facts the book must never contradict.
Anchor a fact on a character, a place or a rule of the world: her eyes are grey, the bridge fell in the war, iron burns the fae. Readings check every chapter against it.
Character No. 01 / 14
[ PORTRAIT ]
Ilsa Danvar
aka the smith’s girl, Ils
41Refs6Links9/12Chapters
Nineteen, a smith’s apprentice, and the only one in Emberford who won’t go near a horse.
3 unlinked mentions: where the text writes Ilsa Danvar and nothing links it Link all
The Smith’s Girl
Ilsa found the key where the fire had left it, deep in the ash below Highcairn.
named found by the assistant
What the Ashguard Knows
The lock gave under the key, and she was through before the vault door could decide against her.
the scene depends on it found by the assistant
Suggest a fix
A proposed edit, not a lecture.
For any continuity issue, ask for a fix and get an exact edit to the line in question. You read it, apply it or discard it. Your text doesn’t change until you say so.
Corin shouldn’t know about the key yet. Make him only suspect.
Reading a document
Looking up the story bible
Proposal1 change
Let Corin suspect, not know
1¶ 5· inline
Corin asked her outright about the key where she had been. She told him the truth, or most of it.
Discard ApplyApplied
NowCorin suspects Ilsa is hiding somethingch 2
What a plot hole actually is
Most of what readers call plot holes fall into a few families. A fact that changes without a reason: the scar on the left cheek moves to the right. A character who knows something they were never told. A rule of the world that holds until the plot needs it not to. An object that is in two places at once, or a wound that heals between one page and the next. And the quiet one: a thing the story set up and never used, which a reader feels as a hole even if nothing was contradicted.
What these share is that each one is a disagreement between two parts of the book. That matters, because it means a plot hole can only be found by holding the earlier part in mind while reading the later one. That is exactly what gets harder as a manuscript grows. At thirty thousand words you can keep it all in your head. At a hundred and twenty thousand, across a series, nobody can.
Why rereading doesn’t catch them
Writers reread constantly, and still miss holes, because rereading is reading. You follow the story, you enjoy the scene, and the detail from eleven chapters ago is gone. Professional continuity editors work differently: they build a sheet of every fact as it is established (eye colours, dates, who was in the room) and check each new page against the sheet, not against memory.
Authrot works the same way. When a chapter is read, it records who appears, what happens, where things stand as the chapter ends, and the setups planted, each tied to the words that established it. The next chapter is checked against that record. The difference from a hand-kept sheet is that nobody has to type it, and it is never three chapters behind.
Events and facts, each tied to the passage it came from
Who has met whom, one direction at a time
Facts that change over time, kept apart from the ones that never do
Optional: a chapter is read automatically after you stop typing
The holes that come from people
Many of the hardest holes to spot are about knowledge, not facts. A character mentions the stolen ring before anyone told her it was stolen. A detective acts on a clue he hasn’t found yet. The villain knows where the heroes are hiding without a scene that shows how. These slips happen because the writer knows everything, and it is easy to let a character borrow what only the author should know.
Authrot doesn’t keep a list of what each character has been told, so this kind of slip is still yours to catch. What it gives you is the record: events in order, each tied to its words, so a reveal sits in the chapter where it happens and you can look it up instead of trusting memory. Relationships are kept too. Every tie in Connections knows the chapter it starts in and the one it ends in, so you can slide back to any chapter and check that the alliance, the engagement or the feud actually holds by then.
Absence causes holes too. A character who disappears for fifteen chapters and returns without comment leaves readers wondering what happened to them. Characters who have gone quiet too long are flagged as due back, which is often the first sign that a storyline has been dropped rather than paused.
Reveals: the chapter where each one happens, on the record
Ties: who is allied, married or feuding at this point
Presence: who is on the page, and who has been gone too long
Anchors: the facts you decide are true
Some facts matter more than others. The colour of a minor character’s coat can drift without much harm; the rule that the dead never come back cannot. Anchoring is how you tell the studio which is which. Anchor a fact on a bible entry, or lock a decision in your Foundations, and it becomes a fixed point that every reading checks against.
Anchors also protect your plan from the AI. The Co-writer never redrafts an anchored field, and every suggestion it makes is checked against your anchors. So if you’ve decided the villain is the narrator’s sister, a suggestion that quietly makes her a stranger is caught before it lands.
Flashbacks, story time and the order things happened
A surprising number of false alarms in any checker come from flashbacks. A chapter set twenty years earlier will naturally contradict the present: the dead are alive, the castle is still standing. Authrot keeps story time apart from reading order, so a flashback sees the right past and is checked against what was true then, not what the reader has already read.
The same separation helps with real timeline holes. If chapter nine says the journey took three days and chapter twelve has them arrive the next morning, a reading can flag the later line against the earlier fact, with both passages a click away.
From finding to fixing
A list of problems is only useful if you can work through it. Checks gathers every open continuity issue (and any duplicate bible entries) into one list, so you can take them in order. Each one shows the earlier fact and the line that breaks it. For any of them, Suggest a fix proposes an exact edit, shown word by word, that you apply or discard.
Not every contradiction is a mistake. An unreliable narrator lies, a character misremembers, a rumour turns out wrong. A finding is a question, not a verdict: dismiss the ones you meant, resolve the ones you’ve fixed, and the list stays honest. Drift checks go one step further and tell you when a chapter strays from its arc, your writing rules or its anchors, which is often how a hole starts.
Questions writers ask
Can software find plot holes in my novel?
It can find the most common kind: a line that contradicts something the book already established. Authrot reads each chapter, keeps the facts it sets up tied to their words, and flags a later line that breaks one, with both sides shown.
Does the plot hole checker use AI?
Yes. Chapter readings and Suggest a fix use the AI, and each shows its cost before it runs. Anchors, the story bible and linking names by hand all work without it.
What if the contradiction is on purpose?
Dismiss it. An unreliable narrator or a lie told in dialogue is a choice, and a dismissed finding stays out of your list.
Will it fix the plot hole for me?
Only if you ask, and only as a proposal. Suggest a fix offers an exact edit for you to review; nothing changes in your text until you apply it.
Does it understand flashbacks?
Yes. Story time is kept apart from reading order, so a flashback is checked against what was true when it happens, not against the present of the book.
Can it check my whole manuscript at once?
Import the manuscript and have the chapters read into the bible. Each chapter is checked against the ones before it, and every open issue collects in Checks.
Does it catch setups that never pay off?
Yes. Setups are tracked as promises, grouped by when they should pay off, and the ones left hanging are listed with the line that planted them.