You've spent two years on this book. You know your characters better than you know yourself. But somewhere around the 80,000-word mark, you notice something: your protagonist's sister's name is Maria on page 12 and Marie on page 340. A secondary character's eye color changes twice. A timeline contradiction means Chapter 22's flashback can't actually work the way Chapter 31 describes it.
These are the consistency errors that sneak in no matter how careful you are. They're not failures of craft — they're failures of memory across long projects. This post covers five practical methods for catching them before readers do.
Most consistency errors are fixable in revision. The problem is that the fixes require you to remember every detail you've established — and that gets harder as the word count grows. The solution isn't to remember better. It's to write things down where you can find them.
A project reference document doesn't have to be elaborate. What it needs is speed: you should be able to check whether a character's eye color is consistent in under a minute, without searching through 80,000 words of prose. One approach that works well for novel-length projects: maintain a running sheet with character attributes, key dates, world rules, and setting details. Update it as you write, not after. The overhead is small — thirty seconds at the end of a session — and it means you're never making decisions blind to what you've already established.
Drafts are almost always written in narrative order — you start at Chapter 1 and work forward. That's fine for writing, but it's a terrible order for revision. When you read forward through your draft, you only ever see events in the order they appear. You never see Chapter 47 next to Chapter 3.
Catching inconsistencies requires seeing the same information in different contexts. Read your draft in chronological order — which means starting with your prologue or flashback or wherever the story begins in terms of when events actually occur, not when the reader encounters them. This forces you to track the world as it evolves rather than as it's narrated, which is exactly where consistency errors hide.
When you add a new detail to your world — a character's hometown, a rule the magic system operates by, a relationship between two supporting characters — tag it immediately. The tag doesn't need to be formal. A comment in your project notes, a note at the top of the scene file, or a simple marker in whatever tool you're using. The goal is to create an index of what's been established so you can verify consistency before problems accumulate.
Conscriva's scene-tagging feature is built around this. When you tag a scene with the information it establishes — character attributes, world rules, relationship states — the tool shows you all instances where that information appears across the draft. This makes it practical to verify consistency in real time rather than only at the end.
The most consistent novels are usually written by authors who do a significant amount of world-building before writing, and who continue that work in parallel with drafting. Not as a separate phase — as an ongoing practice. They build the world and they write the story simultaneously, updating the world model as the story reveals new details about how things work.
The failure mode is writing first and building second: establishing world rules as you discover you need them, which means the rules change as you go and earlier chapters end up contradicting later discoveries. Separate the work. Not because it's a process rule, but because it prevents the specific failure mode where later drafts quietly break earlier ones.
Beta readers catch these things not because they're smarter but because they don't know what you meant to say — they only know what you wrote. You can approximate this by deliberately reading as a stranger to the manuscript: assume nothing, trust only what's on the page. When a character's motivation isn't clear, that's not a puzzle to solve — it's a consistency error to fix.
This gets easier with distance. A draft you finished last week is still too fresh; you read what you intended to write, not what's there. The closer you can approximate the experience of a first-time reader — the more you can come to the manuscript cold — the more you'll catch.
Conscriva's scene-tagging and project-reference tools help you catch consistency errors before they compound across 100,000 words.
Try it free →Consistency at novel scale is a different problem than consistency at short story scale. The density of details, the time span of writing, and the reader's expectation that the world behaves predictably — all of it compounds. The methods above don't add much overhead to the writing process. They do add a lot of certainty that the draft you're sending out is actually consistent. That's worth more than almost any other revision technique at this scale.