How to keep a story timeline

6 min read · Updated October 23, 2026

A story timeline is a list of what happens in your book, in the order it happens in the world, with an in-story date on each event. It is different from your outline, which follows the order of chapters. Most timeline mistakes come from mixing the two up.

Keep a timeline from the first draft if you can, and build one from the manuscript if you can't. It is the fastest way to catch characters who age too slowly, journeys that take no time, and flashbacks that contradict the present.

Story order vs. chapter order

Every scene has two positions: where it sits in the book, and when it happens in the story. In a straight linear novel they match. As soon as you add a prologue set twenty years earlier, a second viewpoint running a few days behind the first, or a flashback in chapter 14, they don't.

Record both for every event:

Sorted by date, this is your timeline. Sorted by chapter, it is your reading order. You need both views. The first tells you whether the world makes sense; the second tells you what the reader knows at each point, which matters for reveals and for anything you publish for readers.

What to record for each event

Keep entries short. A useful timeline event has:

• A title in plain words: "Death of Lord Aldric," not "Ch1 climax."
• A date, as precise as the text commits to. "Spring, 388" is a fine date if that's all the book says.
• An end date for anything that lasts: a siege, a voyage, an illness.
• Who was there and where it happened. These two fields catch most timeline errors.
• The chapter where the reader learns of it.

Don't invent precision. If the book only ever says "the winter Mara turned eighteen," record that, and don't make up a day of the month you'll later contradict.

Ages: the most common timeline error

Readers do arithmetic. If a character is "nineteen" in chapter one and was "born in the spring of 388," someone will check.

The fix is to store a birth date and work ages out from it, rather than storing ages directly. When the text states an age, note the in-story date that age applies to. Then any age claim can be checked against the birth date.

In The Ashen Crown, the first chapter calls Kael Varn "nineteen years old" on the night of the burning, 3 Ashmoon 412 AS. Chapter three says he was born in the spring of 388. That makes him about 24. One of those has to change, and it's far easier to find before the book is printed.

Watch for these too:

• Siblings and parents. A mother who is 30 can't have a 17-year-old and a 15-year-old if she married at 20, unless the book explains it.
• "Years ago" phrases. "Ten years ago" in book one and "ten years ago" for the same event in book three is a mistake if two years passed between them.
• Long-lived species. If elves age differently, write down the rule once and do the conversion every time.

Travel time

Distances fix the timeline more than people expect. Once you write "three days' ride," every journey on that road takes about three days, forever.

For each route your characters use, note the distance and how long it takes on foot, by horse, by ship or by whatever your world uses. Then check that characters don't arrive faster than the road allows, or appear in two places too close together.

The Ashen Crown has a planted example. Varrow is three days' ride south of Thornwatch. Kael is at the vigil in Thornwatch on 5 Ashmoon and only then rides for Varrow. But a later chapter has him holding the Varrow gate from 4 to 6 Ashmoon. He would have to be in both cities on the 5th, and he couldn't have reached Varrow by the 4th anyway.

A good rule: an event on the same day in two places can be ordinary travel. A stay of several days that overlaps a stay somewhere else is not.

Flashbacks, prologues and memory

Flashbacks are where story order and chapter order separate the most, so they're where timelines earn their keep.

• Date the flashback, not the chapter. A memory in book two of something that happened in 409 belongs at 409 on the timeline.
• Check what the character knew then. If a flashback shows a character using knowledge they only gain later, that's a contradiction even if every date is right.
• Keep remembered details consistent. If the same flashback appears twice, the weather, the words and the people present should match, unless the point is that memory is unreliable. If it is, note that in the bible so you don't "fix" it later.

Invented calendars

Fantasy and science fiction often need their own calendar. You don't need to build an elaborate system, but you do need to write down the parts you use:

• Month names and lengths. The Ashen Crown uses the Reckoning of the Flame: ten months, from Frostmoon to Deepwinter, of 30 or 31 days each.
• Days in a year. Ten months of 30 or 31 days gives a year of 304 days. That changes ages: a character who is "20 years old" has lived fewer Earth days than a 20-year-old reader.
• Eras and year zero. "412 AS" means 412 years After Sundering. If your world has more than one era, note when each starts.
• Seasons and festivals. If midsummer is always in Highsun, a midsummer feast in Thawmoon is a mistake.
• Weeks, moons and other cycles, if the plot depends on them.

Write dates in one consistent format everywhere in your notes, such as "3 Ashmoon, 412 AS." Mixed formats ("the third of Ashmoon," "Ash 3," "412.9.3") make errors much harder to see.

Facts that change over time

A timeline isn't only events. Facts change: titles are gained, eyes are lost, alliances flip. A fact without a date is a fact that will eventually look like a contradiction.

Give changeable facts a range. "Mara Thorne: title, Lady of Thornwatch, from 4 Ashmoon 412" is true from the day after her father dies, and not before. A scene earlier in the book that calls her Lady of Thornwatch is then clearly wrong, and a scene later that does so is clearly right.

How to build a timeline from a finished draft

If you're working backward from a manuscript:

1. Read through once and list every event with a date or a time phrase ("the next morning," "two winters later").
2. Pin one event to an absolute date. Everything else is relative to it.
3. Convert each relative phrase into a date. Where the text is vague, keep it vague.
4. Sort by date and read the list straight through. Gaps, pileups and impossible journeys show up quickly.
5. Add births and deaths, then check every age and every event a character appears in after their death.

For a longer method, see building a story bible for a finished book.

A timeline is a tool, not a cage

You don't need dates for every scene, and you don't need to show readers your calendar. The timeline exists so you can make choices on purpose. If a character is younger than the math says because a curse took a year from her, that's a story. If she's younger because nobody checked, that's a mistake. The timeline tells you which one you have.