Story Timeline Software
Keep the chronology of your story visible and connected.
Place events on a narrative timeline, connect the people and locations involved, and move from chronology to the manuscript or story bible without maintaining a separate spreadsheet.
Try Lokee’s connected workspace →What a connected timeline looks like
A sample sequence: two characters converge on the same night, in different places, with a direct path back to the chapter and entity behind each event.
Night of the Eastern Curfew — Duskhollow
Rowan Ashe crosses the rooftops to the Gilded Lantern to meet Sera Nightingale. Referenced by Chapter 1.
Night of the Eastern Curfew — Varnhold Manor
Lady Iseult Varnhold reviews the Circle’s ledger in the manor cellar, the same night, across the city. Referenced by Chapter 2.
Following morning — Crown Watch Barracks
Magistrate Ophelia Crane connects both nights’ reports. Involves Ophelia Crane, Captain Aldric Thorne.
The public demo currently covers Writer, entities, the relationship graph, and the plot board — timeline is available in the full app and is being added to the demo in a future update.
Why chronology becomes difficult in complex fiction
Once a story has more than a couple of characters moving independently, keeping ages, locations, and event order consistent by memory stops being realistic — a spreadsheet helps until it silently falls out of date.
Events as structured story objects
Each timeline event is its own record — a title, a description, and links to the characters and locations involved — not a row of loose text in a spreadsheet.
Link characters, locations, and chapters
An event can reference multiple characters, a location, and the chapter that depicts it, so you can move from a date on the timeline straight to the entity or manuscript context behind it.
See simultaneous events and character paths
Because events carry structured dates and participants rather than plain text, overlapping or simultaneous events across different characters or locations become visible instead of buried in separate notes.
Canonical and alternative timelines
Branch a new timeline from any event to explore a possibility, a draft direction, or an alternate-history thread without disturbing your canonical chronology. Mark one timeline canonical, and Lokee flags contradictions within a branch’s own inherited history automatically — cross-branch differences are expected and never flagged.
Extract timeline candidates from existing prose
Run AI extraction on an imported or written chapter to propose timeline events from your own text — dates, participants, and locations inferred from what you actually wrote.
Review and approve before committing events
Every AI-proposed event is shown for review. You accept, reject, or edit each one — nothing is added to your timeline automatically.
Use the timeline beside Writer
The timeline shares the same vault as your manuscript and entity cards, so chronology stays connected to the story you’re actually writing rather than living in a separate document.
FAQ
How do writers track fictional chronology?
By recording events as structured records — with dates, participants, and locations — instead of prose notes, so the chronology can be queried and cross-checked rather than just read.
Can I connect timeline events to characters?
Yes. Each event can link any number of characters and a location, and can reference the chapter that depicts it.
Can I use fictional dates?
Yes — the timeline is built for fictional calendars and eras, not just real-world dates.
Can Lokee detect events in a manuscript?
Yes — AI extraction can propose timeline event candidates from imported or written text, which you review before they’re added.
Does Lokee support parallel timelines?
Yes — branch a new timeline from any event to track a possibility or draft direction, mark one canonical, and Lokee automatically flags contradictions within a branch’s own inherited history.
Can I export the timeline data?
Timeline data lives in your vault’s local files alongside entities and the manuscript — readable and exportable, not locked into a proprietary format.