How to Organise Your Fantasy Lore
Structure your world's lore before it gets out of hand.
Read →Most writers know they need a timeline. Far fewer actually build one that works. The typical approach — a document with a list of dates and events — is better than nothing, but it misses what a timeline is really for.
A fictional timeline isn't a filing system. It's a tool for understanding causality, spotting contradictions, and finding the story that lives inside your world's history. Here's how to build one that actually does all three.
Before getting into method, it's worth distinguishing between the two kinds of timeline a fiction writer needs:
World history timeline. The chronological record of your world's past — the events that happened before your story begins. Ages, eras, wars, discoveries, catastrophes, political shifts. This is the deep background that gives your world weight and explains why things are the way they are when your story starts.
Story/character timeline. The chronological order of events within your narrative — what happens to your characters, in what sequence, regardless of the order your story presents them. This is what prevents the classic confusion of non-linear narratives, parallel storylines, and multi-viewpoint stories.
Most writers need both. They serve different purposes and should probably be tracked separately.
Don't try to build a complete world history before you start. Begin with the events that directly shape your story's situation:
These are the anchors of your timeline. Everything else — the deeper world history — is built outward from these anchors as the world demands it.
Your world doesn't need to use our calendar. Many fantasy worlds use their own dating systems — years from a founding, ages defined by significant events, or entirely invented calendar structures. Whatever system you use, be consistent from the start.
The most common timeline mistake is mixing dating systems without realising it. "Three hundred years before the war" in one chapter becomes "Year 1200 of the Second Age" in another, and nobody — including you — is sure whether these refer to the same period or different ones.
Pick a reference point. Everything else is measured from it. Stick to it.
A timeline entry that says "Year 340: The Quiet Wars begin" is less useful than one that says "Year 340: The Quiet Wars begin — triggered by the assassination of King Aldric, orchestrated by House Vayne to destabilise the Treaty of Maren." The cause is as important as the event, because the cause is where the story lives.
When you record why something happened, you make your world's history feel like history — a chain of human (or inhuman) decisions with consequences — rather than a list of things that occurred. You also make it much easier to spot when a later event contradicts an earlier cause.
A timeline entry gains depth when it connects to the other elements of your world. The war on your timeline links to the characters who fought in it, the locations where it was fought, and the lore entries it produced — the treaties, the artefacts, the legends.
This is where dedicated worldbuilding software has a significant advantage over a document. In a connected platform, timeline events link directly to character profiles, location entries, and lore entries. Clicking an event shows you everything associated with it. In a document, those connections live only in your memory.
Here's the part most writers miss: a well-built timeline doesn't just record your world's history. It reveals the stories hidden inside it.
When you lay your timeline out fully, you'll notice things:
These observations generate story. A gap becomes a mystery. A coincidence becomes a conspiracy. An unfollowed consequence becomes a ticking clock. Your timeline is a source of plot, not just a fact-checker.
Update as you write, not after. When a new historical fact appears in your manuscript, add it to your timeline immediately. Waiting until the draft is finished means accumulating inconsistencies you'll have to unpick later.
Mark uncertain entries. Some dates will be rough estimates or placeholders. Mark them clearly so you know which parts of your chronology are settled and which are still in flux.
Check the timeline before any scene involving history. Before writing a scene where a character references the past, glances at your timeline first. This takes thirty seconds and prevents the kind of contradiction that takes hours to fix in revision.
Keep a "story timeline" separate from "world history." The order things happen in-story is different from the order you present them. Track both. Your world history is the objective chronology; your story timeline is the sequence of the reader's experience.
A timeline well-built is not a constraint on your storytelling. It's a foundation your story can stand on — and a map of the territory you haven't explored yet.
Your Own World includes a built-in timeline builder — connected to your characters, locations, and lore. Start mapping your world's history free.
Start building free →Structure your world's lore before it gets out of hand.
Read →Where plot holes come from and how to close them.
Read →Build a world that holds together across multiple books.
Read →