Guides · Revision
How to find timeline errors in a manuscript.
By Daniel Bentes · Published 27 July 2026
The short answer: stop reading and start counting. Extract every time marker onto one line, anchor them to a single day zero, convert every relative marker to a day number, then test the durations against travel, healing and how fast news moves in your world. Timeline errors survive read-throughs that catch everything else because they are contradictions between calculations, and prose is very good at hiding arithmetic.
Why they survive
Timeline errors are arithmetic wearing prose.
Every other continuity class is a contradiction between two statements, and reading carefully can surface it. Timeline errors are different: they are contradictions between two calculations, and prose is very good at hiding arithmetic.
"Three days later" reads as a phrase, not a number. Nobody adds while they read — not your beta readers, not your editor, and least of all you, because you already believe the schedule. That is why timeline errors survive read-throughs that catch everything else, and why the only reliable method is to stop reading and start counting.
The method
Build a spine, then test it.
1. Extract every time marker onto one line
Go through the manuscript and pull out anything that fixes or moves time: dates, seasons, "the next morning", "a fortnight later", ages, festivals, moon phases, pregnancies, how long a wound takes to heal. One row each, in reading order, with the chapter. Do not interpret yet — transcribe.
2. Anchor it
Pick one event as day zero. It does not matter which; it matters that there is one. Convert every relative marker into a day number from the anchor. Most contradictions surface right here, in the conversion, before you have tested anything — because two relative markers that both sounded fine cannot both produce the same day number.
3. Test durations against the world
A spine can be internally consistent and still impossible. Check travel against distance and method, healing against injury, messages against how fast news moves in your world, and gestation and growth against biology. This is where fantasy and historical fiction quietly break: the schedule works, but only if the horse never sleeps.
4. Check the seasonal and celestial layer separately
Weather, daylight, harvest, festivals and moons move on their own schedule and are easy to write by mood rather than by calendar. Lay them against the spine as a second pass. A scene set at dusk with the sun high is not a timeline error a duration check will ever find.
5. Run each character's own line
The book's timeline can be sound while a single character's is impossible — present in two places, or crossing a distance the spine does not allow. Trace each major character's movements as their own sequence.
Worked example
Where the arithmetic breaks.
Chapter one
They came ashore at the Long Quay two days after midwinter, in a grey that never quite became morning.
Chapter nine · the deposition
"I left Vellhark four days after midwinter," she said, "and I have not set foot there since."
On the spine: arrival at day +2, departure at day +4. She arrives two days before she leaves. Read as prose, eight chapters apart, this is nearly invisible — both lines are ordinary, and "four days after midwinter" in a deposition sounds like precision rather than a claim to check. Written as two numbers on one line, it takes a second.
Note also what the spine does not tell you: whether she is lying. A deposition that contradicts the narrative is a timeline error or a witness perjuring herself, and the arithmetic looks identical either way.
Limits
What counting will not settle.
- Intentional unreliability. Lying characters, faulty memory, and deliberately disordered narration all produce contradictions on the spine that are not errors.
- Deliberately vague time. Some books work by not committing. Forcing a spine onto a dreamlike chronology can damage the thing that makes it work.
- Whether the pacing is right. A spine tells you the schedule is possible, not that the middle sags.
- Non-linear structure. Flashbacks and braided timelines need two axes — story order and telling order — and conflating them creates errors that do not exist.
Related: the continuity checklist, what each character knows (time and information constrain each other constantly), and how to find plot holes.
Loreon · The Writing Studio
Or let the software read it.
Everything above works with a spreadsheet and patience. Loreon does the same reading against a structured story bible and hands you the findings, with the passages cited.