Every story has two orders. There is the order you tell it in — where you open, what you withhold, when you flash back — which is one of the most powerful craft choices you have. And there is the order things actually happen, which is not a choice at all but a fact about your world. The first is narrative order; the second is the timeline. Confuse them, or let the second drift, and the story develops the quiet impossibilities readers feel even when they cannot name them: a character who reacts to news before receiving it, two events that cannot both be true on the dates given.
This guide covers how to build and keep a story timeline: why chronology matters underneath narrative order, how to track simultaneous threads and backstory on it, and how to use it to catch the continuity errors that hide in time. A timeline is a structural tool — it is what keeps the causal chain of your structure honest however you choose to present it.
Two orders, one story
Narrative order is where craft lives: opening in the middle of the action, withholding a key event until its reveal lands hardest, cutting between two threads to build tension, flashing back to recontextualize the present. These are deliberate manipulations of the reader's experience, and they are much of what makes storytelling an art rather than a report. None of them change what actually happened — they change only when the reader finds out.
Underneath all of it sits the timeline: the fixed chronological sequence of events, dates and ages included. Causality runs along this timeline, not along the narrative. A character can only know what they have learned by that point in story time, regardless of when the reader learns it; an effect must follow its cause in chronology even if the narrative shows the effect first. The more aggressively a story reorders its telling, the more it leans on a solid timeline to keep cause before effect — which is why the most structurally ambitious stories are the ones that most need their chronology pinned down.
Tracking simultaneous threads
The moment a story follows more than one thread — two protagonists, a split party, parallel storylines converging — time becomes a coordination problem. Each thread has its own sequence of events, but they share a single world clock, and the drama often depends on what is happening in one thread while another is occupied elsewhere. The error this breeds is threads drifting out of sync: an event in one storyline that should have reached another and did not, or two scenes the story treats as simultaneous that the stated dates make impossible.
The fix is to put every thread's events on one shared timeline rather than tracking each thread in isolation. When all events sit on the same axis, simultaneity becomes checkable — you can see that the messenger could not have arrived before the battle, that two characters were in different cities on the same day, that a thread's payoff lands after its setup in story time and not just in narrative time. Keeping threads on a common timeline is the same discipline that holds subplots together, viewed through the lens of time.
Backstory belongs on the timeline too
The timeline does not start on page one. The events that predate the story — a war a generation ago, a character's birth, an old betrayal, the founding of a city — are part of the same chronology and are where some of the most stubborn continuity errors live. Backstory feels safe because it is fixed and rarely revisited, which is exactly why its dates drift unnoticed: a mentor whose stated age makes him a child during the war he supposedly fought in, a feud that started after the people it supposedly divided had already died, a character born after an event they remember.
Putting backstory on the same timeline as the narrative present is what makes these impossibilities visible. Ages become positions relative to events rather than free-floating numbers, and the sequence of historical causes can be checked against the present they are supposed to explain. This is also where a timeline and a story bible meet: the bible records what is true, and the timeline records when it became true, and the two together are what let you catch a present that contradicts its own past.
Where CanonBoard fits
CanonBoard gives your story a real timeline as a first-class part of the canvas. Events are placed in chronological order — dated or simply sequenced — and linked to the characters, threads, and locations they involve, with backstory events sitting on the same axis as the narrative present. Multiple threads share one timeline, so what is simultaneous is something you can see rather than something you have to reconstruct in your head.
Because chronology is structured rather than implied, the impossibilities that hide in time become catchable. CanonBoard scans the story on demand and surfaces them with both sides quoted — an age the timeline will not allow, a character who acts on knowledge before they could have it, two events whose dates contradict their supposed order. It never writes your story or chooses your narrative order; it just keeps the chronology beneath it honest. Start free and give your story a timeline that catches what memory misses.
Frequently asked questions
- What is a story timeline?
- A story timeline is a chronological record of when events actually happen in your world, including backstory that predates the narrative — as distinct from the order in which you tell them. It exists to keep cause and effect straight underneath whatever narrative order you choose, so that characters learn things before they act on them and simultaneous events truly line up.
- What is the difference between story order and narrative order?
- Story order (or chronological order) is the real sequence in which events occur. Narrative order is the sequence in which the reader encounters them — which may use flashbacks, flash-forwards, or parallel threads. The two often differ on purpose, for effect. A timeline tracks story order so the causality holds no matter how you arrange the narrative.
- How do you keep a timeline consistent with multiple plot threads?
- Place every thread's events on the same shared timeline rather than tracking each thread separately, so you can see what is happening simultaneously across threads. Most multi-thread errors come from threads that drift out of sync — an event in one thread that should have affected another, or two 'simultaneous' scenes that the dates contradict. A single shared timeline makes those collisions visible.
CanonBoard scans your whole world and tells you where it disagrees with itself.
Start free