Character inconsistency almost never comes from a writer forgetting who their character is. It comes from a filing error: the detail that was supposed to change got frozen, or the detail that was supposed to stay fixed quietly drifted. Once you see character consistency as a filing problem rather than a memory problem, it becomes something you can actually control — with four buckets and a rule for each.
The four buckets that keep a character straight
Everything true of a character belongs in one of four buckets, and each bucket has a different rule. Immutable facts are true for the whole book and should never move — a birthplace, a handedness, a fundamental fear. Changeable states are true right now and are supposed to move — an injury, a rank, who a character trusts this week. Open questions are things you have not decided yet and must not let a draft decide for you by accident. And deliberate exceptions are intentional inconsistencies — a lie, a disguise, an unreliable narrator — that must never be "corrected."
The drift you are trying to prevent is almost always a bucket error. A burned hand (a state) gets treated as permanent and is still burned three books later. A false name (an exception) gets "reconciled" into a continuity mistake. A birthplace (a fact) drifts because it was only ever mentioned once. Sort the details correctly and most inconsistency simply stops happening.
A worked example: a changing injury and a deceptive name
Take Mara. She was born in the salt marshes and is left-handed — immutable facts; if a draft ever makes her right-handed, that is a flag. In chapter three she burns her left hand — a state, with a current value that keeps evolving; by chapter nine it is healing, and a continuity check should know the difference between "burned" and "was burned." From chapters four to nine she travels under the false name Sera — a deliberate exception; a naive consistency pass would see "Mara" and "Sera" as a contradiction and try to fix it, which would wreck the disguise.
Notice what a good process does here. It does not silently rewrite anything. It flags that chapter eleven still describes the burn as fresh, cites the two passages, and asks you whether the hand should have healed by now. It leaves "Sera" alone because you told it that inconsistency is on purpose. Every decision stays yours; the tool’s job is to surface evidence, not to overrule the author.
A continuity check should cite the evidence and ask for a decision. The moment a tool silently "corrects" your prose, it can no longer tell a mistake apart from a choice — and your deliberate exceptions are the first casualties.
Build a Canon Card that records time, source, and authority—not a personality résumé
A useful Canon Card is small enough to consult and precise enough to resolve a disagreement. Give every entry six fields: the detail, its bucket, the point in the story when it becomes true, the chapter or scene that establishes it, its current value, and whether the author has locked it. “Mara has a scar” is weak. “Left palm burn; changeable state; begins chapter three; established in scene 3.4; healing but grip still limited after chapter nine; author locked” can govern later prose.
Do not fill the card with generic adjectives such as brave, sarcastic, or complicated unless the manuscript gives them an observable rule. Record behavior instead: avoids direct apologies, answers fear with a practical task, never uses contractions with authority figures. Observable rules can be checked against a scene. Labels invite a tool to flatten the character into a stereotype.
Open questions belong on the card too. If you have not decided whether Mara recognizes the antagonist’s voice, write “undecided through chapter ten” rather than leaving the field empty. An empty field looks like permission to invent. A named open question tells every future drafting session to preserve the uncertainty until you decide.
- Detail: the exact fact, state, question, or deliberate exception.
- Effective point: the chapter or scene where it becomes true.
- Evidence: the accepted passage that established it.
- Current value: what is true at the manuscript’s present position.
- Authority: proposed, accepted, locked, or intentionally unresolved.
Run continuity as a point-in-time check before accepting a chapter
Check the draft against the canon that was true at that exact point in the story, not against the character’s final state. First list every named character in the chapter. Then compare identity facts, physical states, knowledge, relationships, location, possessions, and public aliases against their effective dates. A detail can be correct for chapter twelve and wrong for chapter four even when both sentences are individually plausible.
For every conflict, produce an evidence pair: the draft sentence and the accepted passage or Canon Card entry it may contradict. Classify the issue before editing—clear contradiction, possible timing problem, intentional exception, or open author decision. Only a clear contradiction should receive a proposed minimal patch. The other three should become questions, because guessing at them can erase foreshadowing, deception, or a change you intended to reveal later.
After any accepted correction, re-check dependent scenes and update the Canon Card only if the correction changed the authoritative fact. Keep the current writing position unchanged. A continuity repair is finished when the contradiction is resolved and downstream state still agrees—not when an AI has produced a smoother paragraph.
Keep the canon where the whole book can see it
A Canon Card in a notebook is better than nothing, but it only helps if it is checked. The reason character drift is so common in long AI-assisted books is that the canon lives in a chat that scrolls away, so nothing is actually comparing chapter eleven against the facts you set in chapter three. Canon has to be somewhere durable, and it has to be consulted as you write.
That is what a blueprint in BookWriter is for: the immutable facts, the states, and the exceptions live as approved rules the manuscript is checked against, not as a message you hope to find later. When the connected continuity review is verified live, it reads that canon and proposes evidence-backed, smallest-possible corrections for you to decide on — one chapter at a time, never a silent rewrite.
Track relationships and knowledge as directional state
Many apparent character errors are really relationship or knowledge errors. Mara trusts Iven in chapter five, but Iven does not yet trust Mara. Mara knows the map is forged, but the reader and the guard do not. A single global field such as “Mara and Iven are allies” destroys those distinctions. Record directional state: who feels what toward whom, who knows which fact, when they learned it, and whether they are willing to reveal it.
Update these ledgers only when an accepted scene changes them. For knowledge, store the fact, the character, the acquiring scene, the evidence available to them, and any false belief it replaced. For relationships, store the direction, current state, cause, public performance, and private truth. A character may publicly obey a commander while privately planning betrayal; that is not inconsistency unless the manuscript forgets which layer a scene can access.
Before accepting a scene, run a knowledge-access check. For every revelation or inference, ask whether the point-of-view character could know it at that moment and how. Then run a relationship check: does the action fit the current directional state, or does the scene need a visible turning beat? The goal is not to forbid surprise. It is to make the causal bridge appear on the page when a state changes.
Also distinguish author knowledge, reader knowledge, and character knowledge. The outline may reveal the murderer while the reader is still meant to suspect two people and the detective knows less than both. A drafting assistant given the full blueprint can leak that privileged knowledge through narration, metaphor, or an improbably accurate guess. Record disclosure boundaries and check the prose, not only dialogue, for information the active viewpoint has not earned.
When a revelation is accepted, update every affected ledger in one bounded review: who learned the fact, which false belief ended, which relationship changed, what the reader now knows, and which future scenes may rely on it. Preserve the establishing passage as evidence. That makes later continuity checks temporal—correct for this chapter—rather than a flat comparison against everything the author knows by the ending.
Review those updates before saving them as canon. A draft can propose a revelation; only the accepted scene establishes it. Rejected alternatives must not advance knowledge or relationships merely because they appeared in a conversation.
| Ledger field | Example |
|---|
| Knowledge holder | Mara |
| Known fact | The archive map is forged |
| Effective scene | 8.3, after comparing the seal |
| Disclosure boundary | Has not told Iven through chapter nine |
| Relationship direction | Mara trusts Iven; Iven remains suspicious of Mara |
Directional records prevent a scene from treating shared history, trust, or information as automatically mutual.