Keeping Your Story Timeline Straight
A character sets off in autumn, travels "for a few days," and arrives in deep winter with snow on the ground; then travels back in the same time and finds the fields in bloom. Errors like this don't show up while writing: they only show up when you put the events in a row on a timeline.
What it's for
The timeline is the clock inside the story, distinct from the order the reader meets the events in. It's for three things:
- Consistent durations. How long that trip, that siege, that pregnancy, that investigation actually takes.
- Ages and anniversaries. How old each character is in each scene, how many years separate two siblings, how much time has passed since the backstory.
- Setting. Season, hours of daylight, weather, holidays: details the reader uses to orient themselves, and that disorient them if they skip.
Absolute dates or relative days?
It depends on the kind of book, but the most flexible solution is keeping both.
| Method | When it helps |
|---|---|
| Days since the start ("Day 1, Day 6, Day 40") | always: fastest way to compute durations |
| Real dates (March 12, April 3…) | if the book names them, or if season matters |
| Character ages in a column | if there are minors who grow, or time jumps |
The base record is a table: one row per scene or chapter, columns for "day since the start," "date," "place," "who's there," "how long since the previous scene."
How to build it
- At the end of the first draft, not before: skim the chapters and assign each a "day since the start," even roughly.
- Mark the explicit intervals: every time the text says "three weeks later," "the next morning," "that summer."
- Compute trip durations and compare them: two routes over the same distance should take the same, barring a reason.
- Add the age column and run it forward: if a character is 16 in chapter 2 and the story lasts eight months, by chapter 40 they're still 16 or 17, not 15.
- Overlay the seasons: if you start in September and the story lasts four months, the last act is in winter. The landscape should know.
Flashbacks and parallel plotlines
- Flashbacks go on the timeline at their real time, with a note on where the reader meets them. This checks that what the character remembers is consistent with their age back then.
- Parallel plotlines (two groups of characters in different places) go on the same "days since the start" axis: it's the only way to notice that, when the two threads reunite, ten days have passed for one and twenty for the other.
When story time isn't linear
In a novel with chapters out of order, or with several timelines, the timeline becomes the main working tool: you write the real sequence of events first, then decide what order to present them in. Without the first, the second becomes unmanageable by the third revision.
Frequently asked questions
Should I build the timeline before or after writing?
The minimum is after the first draft, as a revision tool. Outliners can sketch it earlier, but it still has to be re-checked against the actual text: drafting always shifts a few durations.
How precise does it need to be?
As precise as the book. If the text never names dates and doesn't count seasons, "days since the start" is enough to check durations. If the book is historical or mentions holidays, anniversaries, real events, you need real dates.
How do I handle a novel spanning thirty years?
With two levels: a "wide" timeline by year (what happens in 1971, in 1978…) and "tight" timelines by day only for the stretches the book covers in detail. You don't need to date the gaps between blocks to the day.
Should the timeline be shown to the reader?
Usually not: it's an internal tool. Some novels with many timelines include a small chronology in an appendix, but that's an editorial choice, not a requirement.
What if I find a time error after the book is finished?
Almost always you fix it by changing a vague reference rather than a precise one: turning "three days later" into "a few days later" resolves most conflicts without touching the scenes.