A story timeline is a dated list of every scene in your novel, kept in the order events happen in the story's world, alongside the order readers meet them. To make one, pin the book to a calendar year, give each scene a row with a date, POV and summary, and record every character's birth date once so ages can be calculated rather than remembered. Then run a few date checks: ages, weekdays, moon phases, travel times and overlapping scenes.
That last step is where the timeline earns its keep. Most timeline errors are not dramatic. A brother is twenty-nine a month before his birthday. A Friday scene takes place on a Saturday. Each one takes a minute to fix and is easy for a reader to spot, which is exactly why they belong in a table, not in your memory.
The four timelines inside one novel
Before choosing a method, decide what you are tracking. A novel of any complexity has four overlapping timelines, and errors tend to sit where two of them meet.
Story chronology vs plot order
Story chronology is the sequence events happen in the world of the book. Plot order is the sequence the reader encounters them. In a straight linear thriller the two match. Add a prologue set ten years earlier, a mid-book flashback, or a frame story, and they split.
Track both in the same table: a "Reading order" column (chapter and scene number) and a "Story date" column. Sort by one and you see the book as written; sort by the other and you see what actually happened, in order. Many plot holes become visible only in the second view, such as a character reacting to news they have not yet received.
Character ages
Ages are the most common timeline slip because writers state them from memory. The fix is structural: record each character's birth date once, in one place, and compute their age on every scene date. Never type an age into the timeline by hand.
Parallel POVs
In a multi-POV novel each viewpoint has its own thread, and the threads must agree on shared events. If one POV character spends Friday night at the hospital, no other POV can have them at a dinner party at the same time. Put all POVs in one table with a POV column, so sorting by date and time puts simultaneous scenes next to each other.
Backstory
Backstory is the timeline before page one: a parent's death, a war, a first marriage, the founding of the town. It rarely gets dates because it is never dramatized, yet characters keep referring to it ("fifteen years ago," "the winter I turned twelve"). Give each backstory event its own dated row, marked as backstory, and the "years ago" lines become checkable.
Methods: spreadsheet, calendar, cards or software
There is no single right tool. The best choice depends on whether your hard problem is arithmetic, overview or structure.
Spreadsheet columns that do the work
A spreadsheet is the strongest free option because it can calculate. A practical column set:
| Column | Example | Why |
|---|---|---|
| Ch / Scene | 3.2 | Reading order |
| POV | Mara | Parallel thread check |
| Story date | 2019-10-19 | Chronology |
| Time | 21:00 | Same-day overlaps |
| Weekday | (formula) | Catches wrong weekday names |
| Location | Harbor | Travel checks |
| Summary | Mara finds the ledger | Quick scanning |
| Ages | (formula per character) | Age checks |
| Notes | "full moon" mentioned | Things to verify |
Two built-in functions do most of the arithmetic. Excel's DATEDIF(start_date,end_date,unit) with the unit "Y" returns "the number of complete years in the period", which is exactly a character's age on a scene date. Microsoft warns against the "MD" unit, which it says may give "a negative number, a zero, or an inaccurate result," so stick to "Y" for ages. Google Sheets has a DATEDIF function with the same syntax, including the "Y" unit. WEEKDAY returns the day of the week as a number, from 1 (Sunday) to 7 (Saturday) by default; formatting the date cell to show the day name works too.
Keep birth dates on a separate "Characters" tab and reference them, so a change to one birth date updates every age in the book.
Calendar tools
A calendar app shows weekdays and empty stretches at a glance, which a spreadsheet does not. In Google Calendar you can make a separate calendar for the novel (or one per POV), but Google's help page notes that you can only create new calendars from a browser, not the phone app. Go to the story year and enter scenes as events. The weakness: backstory spanning decades is clumsy, and nothing calculates ages.
Index cards
Cards (paper or digital) are best for plot order: one card per scene, laid out in reading order, with the story date written in the corner. Rearranging a flashback is a physical move. They do no math and can't be searched, so most authors who use cards also keep a date list somewhere else.
Timeline and story bible software
Dedicated tools add visual lanes, linked characters and, in some cases, custom calendars. Aeon Timeline, for example, describes itself as an app to help "manage complex stories" and lists a sync with Scrivener or Ulysses. Story bible tools keep the timeline next to character and place records. In BlurbBio the Story Bible holds characters, locations, items, relationships, a timeline and lore beside the manuscript. Software pays off on long books and series; for a single linear novel, a spreadsheet is often enough.
How to build the timeline, step by step
- Pick a real yearChoose the calendar year the story happens in, printed or not, so weekdays and moon phases can be checked.
- One row per sceneList every scene in reading order: chapter, scene, POV character, one-line summary.
- Date every sceneAdd a story date and, where it matters, a time of day. Sort by date to see chronology.
- Ages by formulaEnter each birth date once and let the spreadsheet compute ages on every scene date.
- Run the checksWeekdays, moon phases, seasons, travel times, overlapping POV scenes, backstory math.
- Fix both togetherChange the manuscript and the timeline at the same time, or the error comes back in the next draft.
A few notes on the steps that people skip.
Do it after the structure settles. A timeline built during a first draft is a planning tool; a timeline built after structural edits is a checking tool. You want both, but the checking version must reflect the scenes as they now stand, or you will "fix" scenes you have already cut.
Date every scene, even vague ones. If the text says "a few days later," pick a date and write "approx" next to it. A guessed date can still be checked; a blank can't.
Mark what the text actually says. Add a Notes column for every time-related detail on the page: a named weekday, the moon, the weather, "it was the first frost," a holiday. These are the claims a reader can check, so they are the ones you must check.
Worked example: an invented novel, The Salt Ledger
To show the checks, here is an invented novel. The Salt Ledger is not a real book; every name and scene below is made up for this tutorial. It is set in a fictional harbor town in October and November 2019, with two POV characters, siblings Mara and Tobin Quill.
Fixed facts in the character tab:
- Mara Quill, born March 3, 1987
- Tobin Quill, born November 20, 1990
- Their father died at sea "the winter Mara was twelve" (backstory)
Here are four lines from the draft and what the timeline found.
Check 1: an age stated from memory
Chapter 9, dated Thursday, October 24, 2019, calls Tobin "twenty-nine." With DATEDIF and the "Y" unit, Tobin's age on that date is 28: he was born November 20, 1990, and turns 29 on November 20, 2019, 27 days later. The fix is one word, but only a formula would have caught it, because "twenty-nine" feels right for a man born in 1990 and checked in 2019.
Check 2: backstory arithmetic
Chapter 14 has Mara say, "I left the summer I turned eighteen, fifteen years ago." She turned 18 on March 3, 2005, so that summer was 2005, and October 2019 is fourteen years later, not fifteen. The father's death passes the same test: Mara was twelve from March 1999 to March 2000, so "the winter Mara was twelve" is winter 1999 to 2000, roughly twenty years before the story. Give that event a backstory row and any later "twenty years ago" line can be checked against it.
Check 3: a weekday and a full moon
Chapter 3 is dated Saturday, October 19, and describes a full moon. The weekday is right: October 19, 2019 was a Saturday. The moon is not. The US Naval Observatory's moon phase data service, which covers the years 1700 to 2100, lists the October 2019 full moon on October 13 at 21:08 Universal Time, with the next new moon on October 28. By the 19th the moon was six days past full.
Note the time zone. The service gives Universal Time, so a full moon early in the UT day can fall on the previous local date in the Americas. Here 21:08 UT is 5:08 p.m. on the US East Coast (daylight time), still October 13. You can move the scene to Sunday, October 13, or keep the date and change the moon.
In 2019 the full moon fell on Sunday, October 13, so a scene on the 19th gets a waning moon; the image survives, the error doesn't.
Check 4: two POVs in one place
Chapter 1 (Tobin's POV) has him working a night shift on the trawler on Friday, October 18, from 8 p.m. Chapter 2 (Mara's POV) has Tobin knock on her door at 10 p.m. the same night. In reading order the chapters are adjacent and the overlap is easy to miss, because each scene is consistent within itself. Sorted by date and time in one table, the two rows sit next to each other and the contradiction is plain. One of them moves to Saturday, and the timeline row moves with it.
None of these four slips would sink the book. Together, in a review, they read as carelessness. The table found all four in minutes because each claim was a date, and dates can be computed.
Checks to run on every timeline
Weekdays and ages are the start. A full timeline pass also covers:
- Moon and daylight. Moon phases from the USNO service; sunrise and sunset matter for any scene at dusk or dawn, and change with latitude and season.
- Seasons and weather. Fall foliage, snow, school terms and harvests should match the place and the month.
- Holidays. Check every scene date against the public and religious holidays of the setting; a family that ignores a major holiday needs a reason.
- Travel time. If a journey takes two days going, it takes two days coming back unless the text says why not.
- Biology. Pregnancies, injuries, children's development and aging horses move at real speeds.
- Knowledge. Sort by chronology and check that no one acts on information before the scene where they learn it.
For the wider set of contradictions readers notice, from eye color drift to series canon, see our guide to continuity errors in novels.
Keep the timeline alive through revisions and series
A timeline that stops being updated becomes a source of errors, because you start trusting it after it has drifted from the text. Three habits help:
- Edit both at once. When you move a scene, change its row in the same sitting.
- Keep it with the rest of your canon. A timeline is one part of a story bible, alongside character and place records. Our guides on how to build a story bible and the story bible template show how the pieces fit.
- Carry it into the next book. In a series, book two's timeline starts where book one ends, and ages keep counting. Our guide to keeping a book series consistent covers series-level canon.
If you would rather not maintain the cross-checking by hand, software can help with the comparison step. BlurbBio's continuity checker compares new chapters against the canon in your Story Bible and flags contradictions for you to review. You still decide which version is right; the tool just makes sure you get asked.