Worldbuilding craft · 4 min read

Timeline tracking for writers

Nothing loses a reader's trust faster than a history that does not add up — a character too young for a war they fought in, a winter that lasts most of a year. Here is a calm way to keep your timeline straight.

A reader will forgive a great deal. They will forgive a slow chapter, an unlikely coincidence, even a coast that faces the wrong way — for a while. The one thing they rarely forgive is a history that does not add up: a character who is thirty in book one and forty-five a year later, a war that ended before the general who won it was born, a winter that somehow lasts most of a year.

Timelines drift because time is invisible. Every other detail sits on the page where you can see it; the years between events live only in your head, and heads are where continuity goes to quietly unravel. Here is a calm way to keep your world's history honest.

Anchor everything to one calendar

Before you can track time, you need a zero — a single point that everything else is measured from. Pick one defining event and let your world count from it. Perhaps everything in your story is dated from the founding of the floating city of Vharn: the Concord forms in the year 210, Sera Auren is born in 388, the salt-coast accord is signed in 402.

It does not matter whether your world calls them years, cycles, or turns of the long tide. What matters is that there is one count, and every date you invent hangs from it. A single shared zero is the difference between a history you can check and a pile of ages you can only hope agree.

Track relative time, not just dates

Readers rarely feel raw dates. What they feel is relative time — how old a character was when something happened, how long ago the last war ended, how much time sits between two scenes. So track that directly.

For each major character, note their birth year on the one calendar. Now their age at any event is simple arithmetic instead of a guess, and the "thirty in one book, forty-five a year later" slip becomes almost impossible to make without noticing. Do the same for institutions and places: the Cartographers' Concord is a hundred and ninety years old when your story opens, which quietly tells you what it can and cannot yet have done.

Keep a single timeline of record

The heart of the whole practice is one rule: there is one timeline, and it is the timeline. Not a version in your draft, another in an old outline, and a third in your memory — one entry in your codex that every other mention must agree with.

When you invent a historical event mid-scene — a plague, a coronation, the loss of a fleet — you stop and add it to the timeline of record before you move on, dated on the one calendar. The timeline is not a thing you build once at the start; it grows every time your story reaches into the past, and it stays trustworthy precisely because you update it in the moment rather than promising to reconcile everything later.

Let the timeline catch contradictions

Once a single dated timeline exists, it starts doing your continuity work for you. Before you send a chapter out, you can run one quick pass: does every age, every "years ago," every reference to a past event match the record? Because the answer lives in one place, the check takes minutes, not an afternoon of hunting.

This is where a visual timeline earns its keep — seeing your history laid out on a line makes an impossible overlap obvious in a way a plain list never will. The Complete codex is built around exactly that view for long, branching sagas, and the wider habit it serves is the one in keeping your lore consistent. A timeline is really just consistency applied to time — and like every other part of a calm world, it starts the moment you give your history one organized home.

See the complete codex

The Complete system includes a visual timeline built for a long, branching saga — so book three never contradicts book one.

Timeline Tracking for Writers: FAQ

Do I need a full invented calendar with named months?

Not to stay consistent. A simple numbered count from one zero event is enough to catch every contradiction. Named months, festivals, and moons are a lovely flavour to add later, once the story asks for them — they are decoration on top of the count, not a substitute for it.

How much history should I work out before I start writing?

Only the handful of past events your opening actually leans on — a founding, a recent war, the reason two houses distrust each other. Invent the rest as the story reaches for it, dating each piece on your one calendar as you go. A history built entirely up front tends to be a history you never use.

Keep reading

Disclaimer: The Worldbuilder's Codex is a creative organizing tool. Your world and writing remain entirely yours; keep private account details out of your story notes.