By the time a novel is finished, no author can hold all of it in their head at once. A character’s eyes change colour between chapter 3 and chapter 28. A journey that took two days in one scene takes a week in another. A house that burned down is still standing forty pages later. None of this is bad writing. It is the predictable cost of writing something too long to re-read in one sitting.
A novel consistency checker is the tool built for exactly that gap. Its job is to read the whole manuscript and catch the contradictions you can no longer see, because you wrote them too far apart to notice. This guide explains what that job really involves, why self-checking and generic chatbots fall short, what to look for in a tool, and how the main options compare.
Short answer: a good novel consistency checker reads your entire manuscript, remembers what happened in early chapters while it reads later ones, and flags contradictions in character, timeline, world and plot across the whole book. Most tools that claim “consistency” only check spelling or formatting, and almost all of them are English-only. Vellam is the dedicated option built around whole-book consistency, and it works in Polish, English, German and Spanish.
What a consistency checker actually does for a novel
The word “consistency” gets used loosely. A grammar tool will tell you that you spelled a name two different ways, and call that a consistency check. That is real, but it is the smallest version of the problem. The hard kind of inconsistency lives across chapters, and it comes in four shapes.
- Character drift. A trait, a backstory detail, or a physical description that quietly changes. Someone who was an only child gets a sister. A scar moves sides. A character who hates the sea is sailing for pleasure two hundred pages later.
- Timeline and continuity. Events that do not line up in time. A pregnancy that lasts four months. A character at two places at once. A season that skips or repeats. An age that does not add up against a stated birth year.
- World and location contradictions. The physical or rule-based world changing without reason. A town described as coastal becoming landlocked. A magic system that forbids something in chapter 5 and allows it in chapter 22.
- Dropped plot threads. A promise the book makes and never keeps. A mysterious letter that is opened and never mentioned again. A villain who vanishes. A subplot that simply stops.
Catching these is not a spelling problem. It is a memory problem. The tool has to read the whole book, hold every earlier chapter in mind while it reads the next one, and notice when a later page contradicts an earlier one. That is the real definition of a novel consistency checker, and most tools that use the phrase are not doing it.
Why manual self-checking and generic chatbots fail at scale
The instinct is to do it yourself, or to paste chapters into a chatbot. Both break down for the same underlying reason: scale.
Self-checking fails because you are too close to the book. You know what you meant, so you read what you intended instead of what is on the page. You also cannot keep eighty thousand words in working memory. The contradictions that survive into a finished draft are precisely the ones spread too far apart for a human to catch on a linear read. A spreadsheet helps, but only as much as you keep it updated, and most authors stop updating it around chapter ten.
Generic chatbots fail because of context and consistency of attention. Even when a model can technically accept a long manuscript, it does not read all of it with even attention, and it tends to be agreeable rather than rigorous. Ask it whether your timeline holds and it will often reassure you. It has no persistent map of your book, no per-chapter record to check a later claim against, and no structured output you can audit. There is a deeper reason a raw language model is not enough for this, and it is worth understanding before you trust one with continuity.
A real consistency checker is built around the manuscript, not around a chat window. It reads chapter by chapter, keeps a record of what it found, and checks each new chapter against that record.
What to look for in a consistency checker
Four things separate a tool that genuinely checks novel consistency from one that just markets the word.
- It reads the whole manuscript, in order, remembering what came before. Per-document grammar passes do not count. The tool has to carry chapter 2 into chapter 30.
- It detects cross-chapter contradictions, not just in-sentence errors. The value is in the distance between the two facts that disagree.
- It works in the language you write in. Continuity logic that only runs on English is useless for a Polish, German or Spanish manuscript.
- It builds its map from your text automatically. If you have to type every character and fact into a form first, the tool is only as complete as your data entry, and you are back to the spreadsheet problem.
How the main options compare
Here is how the tools authors actually reach for stack up against those four requirements. The honest summary up front: most of them are strong at something else and weak at cross-chapter consistency specifically.
| Tool | Reads whole manuscript | Cross-chapter contradictions | Works in your language | Auto-built from your text |
|---|---|---|---|---|
| Vellam | Vellam only | |||
| AutoCrit | ||||
| ProWritingAid | ||||
| Marlowe | ||||
| Manual spreadsheet |
A manual spreadsheet ties on language, because it holds whatever you type, and AutoCrit and Marlowe genuinely read whole manuscripts. The gap is cross-chapter contradiction detection in your own language, built automatically from your text.
A few honest notes on each, using only what each tool actually claims.
AutoCrit analyses full manuscripts and markets contradiction and timeline tracking, which is more than most. The limits are that it is English-only and it does not build an automatic, per-chapter map of your story for you to inspect, so its consistency findings are harder to trace back to where they come from. If you write in English, it is a credible option. If you write in any other language, it does not apply.
ProWritingAid is an excellent line and grammar editor, and that is the honest framing. Its “consistency” feature is about formatting: spelling variants, hyphenation, spacing, dialogue punctuation. That is genuinely useful, and it is not the same as catching a character whose eye colour changes across the book. It is also English-only for this work. Use it for the sentence-level pass, not for continuity.
Marlowe produces a useful structural report on a whole manuscript: pacing, dialogue ratios, plot beats. On granular consistency it does not really compete, and it is English-only. It answers “how is my book shaped” more than “where does my book contradict itself.”
A manual spreadsheet is the honest baseline. It works in any language, because it is just your typing, and a disciplined author can track real continuity with one. The catch is that it is entirely manual: nothing is read for you, nothing is flagged for you, and it is only as current as the last time you updated it. Most drafts outgrow the spreadsheet.
What Vellam does that the others do not
A whole-book consistency check
Vellam reads your manuscript chapter by chapter, the way a reader does, keeping every earlier chapter in mind as it reads the next. From that it runs a whole-book consistency check that flags four kinds of contradiction: a character trait, a character’s state of mind, a location description, and a plot status that stops adding up. This is the cross-chapter work that grammar tools and structural reports do not attempt.
A Story Atlas built automatically from your text
After each chapter, Vellam generates per-chapter cards for every character, location and thread, pulled from what you actually wrote, with heatmaps that show where someone disappears for a stretch. You do not fill in a form first. The map is built from the manuscript, which means it is complete by default and you can trace any consistency flag back to the chapters it came from. If you have ever kept a story bible by hand, this is that, generated and kept current for you.
An AI-writing detector, in the same place
Vellam also includes a built-in AI-writing detector. Run it on a chapter or the whole book and it scores how machine-like the prose reads, with the lowest-scoring sentences highlighted. It is the same kind of scan a publisher or a contest might run, so you see it before they do. None of the consistency tools above ship anything like it.
Sentence-level analysis, for free
A rule-based analysis layer marks cliches, weak verbs, filler, passive narration and repetition, and it costs no credits. This is the line-level pass that overlaps with what ProWritingAid does well, included alongside the continuity work rather than sold as a separate product.
An idea generator, not a prose generator
It is worth being precise about Vellam’s AI, because the category is full of tools that write for you. Vellam’s assistant is a thinking partner, not a ghostwriter. It brainstorms plot, talks through a character, and points at a line that could be sharper. What it does not do is hand you finished prose to drop into your book. There is no insert button, nothing is written into your manuscript, and the whole design assumes you write every line in your own words. A consistency checker should help you find what is wrong with the book you wrote, not quietly rewrite it into a different one.
Built with authors and publishers, and it moves fast
Vellam is built in the open with the people who use it. There is a public feedback board where authors and publishers post requests, vote, and watch them ship, and we read and act on all of it. The roadmap is shaped by working novelists and by publishing houses at the same time, which is rare in this category, and features land quickly. Consistency checking in particular keeps getting sharper because real manuscripts keep surfacing real edge cases.
Works in your language
This is where the category thins out fast. Vellam’s interface is fully localized in Polish, English, German and Spanish, and its analysis is built for manuscripts in those languages. AutoCrit, ProWritingAid and Marlowe are English-only for consistency work. A manual spreadsheet handles any language but does none of the detection. If you write in Polish, German or Spanish, the practical choice for automated cross-chapter consistency is narrow, and that is not a marketing line, it is just where the tools are.
You stay in control
Vellam never changes your text on its own. Its AI help is opt-in, sits in a side panel, and your text is not used to train any model. A consistency check reads your book and reports back. It does not touch a word of it.
Choose another tool if
- ProWritingAid: you want the strongest line and grammar editor and your idea of consistency is spelling, hyphenation and formatting, in English.
- AutoCrit: you write in English and want manuscript analysis with timeline tracking, and you do not need an inspectable per-chapter map or non-English support.
- Marlowe: you want a structural report on pacing and plot shape for an English manuscript, more than granular continuity.
- A manual spreadsheet: your book is short enough to track by hand and you are disciplined about keeping it current.
Choose Vellam if
- You want a true whole-book consistency check that flags character, location and plot contradictions across the entire manuscript.
- You want a Story Atlas built automatically from your text, not a form to fill in.
- You write in Polish, German, Spanish or English and want a fully localized tool.
- You want consistency, an AI-writing detector and sentence-level analysis in one place.
- You prefer a one-time payment with credits that do not expire.
Can you use both?
Yes, and for many authors the sensible stack is two tools. Run ProWritingAid or your editor of choice for the line-level pass, then run the whole manuscript through Vellam for cross-chapter consistency, a Story Atlas and an AI-detection scan before it reaches a beta reader or an editor. They solve different halves of the problem, and the continuity half is the part most easily missed when you self-edit.
Frequently asked questions
What is a novel consistency checker?
It is a tool that reads your whole manuscript and flags contradictions that span chapters: a character trait that changes, a timeline that does not line up, a location that contradicts an earlier description, a plot thread that gets dropped. It is different from a grammar checker, which works sentence by sentence, and different from a formatting consistency feature, which only checks things like spelling variants and hyphenation.
Can ChatGPT or another chatbot check my novel for consistency?
Not reliably. A general chatbot does not keep a persistent, per-chapter map of your book, does not read a long manuscript with even attention, and tends to reassure rather than audit. A dedicated checker reads chapter by chapter, records what it finds, and checks each new chapter against that record.
Does a consistency checker work for novels written in Polish, German or Spanish?
Most do not. AutoCrit, ProWritingAid and Marlowe are English-only for this work. Vellam’s interface and analysis are built for Polish, English, German and Spanish, so the cross-chapter consistency check runs in the language you actually wrote in.
Will my consistency checker rewrite my book?
Vellam will not. It reads your manuscript and reports contradictions back to you. Its AI help is opt-in, lives in a side panel, never inserts prose into your text, and your manuscript is never used to train any model. You fix what it finds, in your own words.