"The wound was in the shoulder—no wait, the leg." Arthur Conan Doyle never noticed. A hundred and thirty years later, every single book about Sherlock Holmes still brings it up.
Watson's war injury migrated from shoulder to shin across the original stories. Scholars call it "Watson's Wandering Wound," and it became more famous than half the mysteries Doyle actually solved on paper. No timeline document. No character database. One background detail, left unchecked, permanently scarred one of the most beloved series in literary history.
Timeline errors don't destroy great work. But they leave marks that outlast everything else.
Four Types of Timeline Errors
The problem has four faces, and each one hides differently.
Absolute time errors are the friendly ones. A story set in 2020 where characters use a phone model released in 2022. A historical novel where someone makes a phone call decades before Alexander Graham Bell's patent. Any reader who knows the era catches these immediately. Almost too easy.
Relative time errors -- sneakier by a mile. Chapter 5 says "that summer three years ago." Chapter 20 says "that summer five years ago." Same event. Or a character described as thirty-five, except her birth year and the story's year put her at thirty-three. These demand cross-referencing. Dedicated readers absolutely do that math.
Causal time errors break physics and logic. A character in Chapter 10 mentions something that hasn't happened until Chapter 15. Someone drives between two cities in an hour when the trip takes four. Readers don't just notice -- they get ejected from the story. The contract between writer and reader says the world follows rules. Causal errors tear up that contract.
Parallel time errors haunt multi-POV novels. Two storylines running simultaneously, except the details betray them. Character A calls Character B on Friday in Chapter 3. Character B's chapter shows that day was Wednesday. Nearly every writer juggling multiple viewpoints has tripped on this.
Here's what all four share: they almost never appear in first drafts. They breed during revision. Move a date, forget to update the seven passages referencing it. Delete a scene, leave behind dialogue that points to it. The culprit isn't carelessness -- it's the nature of revision itself.
That's why this requires a system. Not a better memory.
Building Your Timeline Document
Inside Slima's Writing Studio, the File Tree has an "Outlines and Plans" folder. That's where timeline.md belongs. This file becomes the single source of truth for every time-related detail in the story.
Three sections. That's all it needs.
Story Time Range -- the boundaries. Start date, end date, total span. These parameters cascade into everything: what season it is, whether holidays fall inside the story, what the weather's doing, what characters wear. Get these wrong and downstream errors multiply.
Core Events Table splits into two halves. First, the backstory events -- the past that shaped characters before page one. Second, the main timeline during the story itself. Each entry records the date, what happened, which characters were involved, and which chapters reference it. When a single event needs adjusting, every affected passage is visible at a glance.
Character Age Reference -- the section most writers skip, and most regret skipping. When a character reminisces, how old were they? When two characters discuss a shared memory, do their ages actually line up? A table mapping birth years to ages at key story moments catches contradictions before readers do.
Split View (Cmd+ or Ctrl+) earns its keep here. Timeline on the left, current chapter on the right. Every time-related sentence gets an instant cross-check -- just glance left. No switching windows, no hunting through tabs.
Quick Open (Cmd+P) makes it faster still. Type "timeline" and jump straight to the file. No clicking through folder hierarchies.
Let AI Be Your Timeline Guardian
A hundred thousand words. Dozens of time references scattered across them. Manually cross-checking every single one? That's not diligence. That's a recipe for missed errors and wasted afternoons.
Open the AI Chat Panel with Cmd+Shift+A (Mac) or Ctrl+Shift+A (Windows). Let the machine do what machines do best -- scan, compare, calculate.
Step one: time mention scan.
Feed the AI Assistant this prompt:
Please scan all chapters in the "Drafts" folder and find every time-related mention. Include:
- Specific dates or years (e.g., "March 2024," "that summer")
- Relative time expressions (e.g., "three days ago," "next month," "last winter")
- Season or weather descriptions (e.g., "snow was falling heavily," "cherry blossoms were blooming")
- Character age mentions (e.g., "when he was thirty," "she was still a child")
- Historical events or era markers (e.g., "during the dot-com bubble," "after the pandemic")
Please organize into a table, noting chapter location and original text excerpts.
That inventory is the foundation. Without it, everything downstream is guesswork.
Step two: consistency cross-check.
Based on the following timeline document and time mention list, please check for any contradictions:
[reference timeline file]
Focus on:
- Whether relative times point to the correct absolute times
- Whether character ages are consistent at various time points
- Whether the event sequence is logical
- Whether season descriptions match the dates
Please list all contradictions found, noting specific locations.
Step three: scene interval math.
Sometimes the question is narrow and specific --
The scene in Chapter 5 takes place on Friday night. The scene in Chapter 8 is described as "three days later."
Please calculate:
- What day of the week should Chapter 8 be?
- When do Chapters 6 and 7 take place?
- Is this consistent with other time clues?
If you find contradictions, please suggest how to correct them.
The principle underneath all of this: AI handles calculation and comparison. The writer handles judgment. AI won't miss that "Tuesday in Chapter 7" contradicts "Monday in Chapter 8." But it can't tell the difference between a genuine mistake and an unreliable narrator lying on purpose. That distinction -- error versus intent -- stays with the author.
Handling Complex Time Structures
Linear storytelling is already hard to manage. Non-linear? That's the deep end.
Multi-timeline stories -- the kind that alternate between "now" and "thirty years ago" -- run two independent chronologies simultaneously. Each has its own event sequence, its own internal logic. But the correspondence between them matters just as much. Which "present" chapter aligns with which "past" moment? Miss that mapping and the timelines drift apart without anyone noticing until a reader points it out.
In Slima's File Tree, create separate documents: timeline-present.md, timeline-past.md, and a timeline-crossref.md for tracking where the two intersect. Separate management, instant cross-reference.
Non-linear narratives face a different beast. "Reading order" and "story time" are two completely separate sequences. Readers encounter an ending fragment first, then the beginning, then somewhere in the middle -- but the story has an objective chronology underneath. Both sequences need tracking. Logic must hold from every angle.
Christopher Nolan's Memento is the canonical example. One thread moves forward, one moves backward. The production team tracked every scene's position in both "film order" and "story order," ensuring causality held even when viewed in reverse. Writing a novel with this structure is arguably harder -- prose doesn't have camera language to signal temporal jumps.
When Timelines Need Revision
Chapter fifteen. Sudden realization: the story works better spanning six months instead of a year. Or a key event needs to shift three months earlier. Or -- the painful one -- the entire timeline needs compression.
Changing one date is easy. But how many passages reference that date? How many chapters contain "three months ago" or "last summer" pointing back to it? Change the source, and every downstream reference needs updating. This is where new errors breed fastest.
Slima's Branches feature exists for exactly this moment. Create a branch -- call it timeline-revision. Make every change there. Run a full AI consistency check. Confirm everything lines up. Then merge back to the main branch.
The safety net: if the revision spirals into unexpected complexity, abandon the branch entirely. Walk away. The main branch sits there untouched, exactly as it was.
In the Version Control panel (Cmd+Shift+G), every major timeline change deserves a snapshot with a clear label: "Timeline compression: story span changed from one year to six months." Three months later, that label is a lifeline.
Keep a change log inside the timeline file too. Why is this event on this date? What got modified and when? Future-you will be grateful for those thirty seconds of documentation.
Stories Without Specific Years Still Need Timelines
"My novel is set in a vague 'contemporary' period. No specific years. So I don't need a timeline, right?"
Wrong. Possibly even more wrong than for a story with explicit dates.
No specific years doesn't mean time doesn't exist. How many days pass between events? How old is the character during that flashback? After a winter scene, the next chapter can't suddenly have cicadas. If characters have jobs, the day of the week matters.
Relative time references are actually more treacherous than absolute ones. "Three days ago" and "last week" both need to point somewhere definite, even if that somewhere never appears on the page. Vague is not the same as careless.
The timeline can use relative markers: Day 1, Day 15, Week 3. No need for "March 15, 2024." But every "three days ago" and "last month" and "that winter" needs a reference point to anchor against.
Watson's wound wandered from shoulder to leg, and Conan Doyle probably never knew. A hundred and thirty years on, the mistake is more widely cited than most of his correct details.
Not every error gets remembered for a century. But the tools to prevent them are sitting in Writing Studio right now -- timeline documents, AI-powered consistency checks, Version Control snapshots. What's left is the thirty minutes it takes to set them up.
In the next article, we'll tackle research material organization -- all those reference materials that keep expanding during the creative process, and how to collect, manage, and locate them in three seconds flat.