Recent chats

How do I keep a story timeline clear while drafting out of order?

Quick answer

Keep a separate timeline rather than relying on the order scenes appear in your draft. Give each event a time marker, a brief description, and a note about what each relevant character knows before and after it. Mark uncertain dates as provisional, and link each event to its scene. When you revise, check the timeline against the manuscript for cause and effect, knowledge, and time gaps.

LET’S WORK THROUGH IT

The question, the details, the next step.

Question

I’m drafting scenes in whatever order feels right, but now I can’t tell whether the story’s chronology still makes sense. What should I track?

Geez

Make a working timeline that is separate from your manuscript’s scene order. It can be a plain document or spreadsheet; the important thing is that every event has a place in chronological order, even if you write the scene much later.

For each event, record:

  1. A time marker, such as “Tuesday morning,” “three days later,” or “about a month before the opening.”
  2. A short description of what happens.
  3. The scene or draft location where it appears, using a chapter number, scene label, or placeholder.
  4. Which characters are present and what they learn.
  5. Any uncertainty you still need to resolve.

Use relative markers when you do not know exact dates. A consistent chain—“the next morning,” “two weeks later”—can be clearer than invented calendar precision. Keep the order of events distinct from the order in which readers encounter them.

Follow-up question

How do I track what each character knows? My scenes jump between different characters and time periods.

Geez

Add a knowledge note to events that change what a character knows. Think of it as a small ledger: before an event, what does the character believe or not know? Afterward, what information have they gained, and how did they get it? Include only details that matter to later choices, discoveries, or dialogue; you do not need to document every thought.

For example, suppose your story has a character named Mara. A continuity entry might look like this:

Event: The key is found in the garden. Time: Day 4, late afternoon (provisional). Present: Mara; Ivo arrives afterward. Knowledge change: Mara sees the key. Ivo does not see it and has not been told about it. Scene: Draft scene “Garden,” currently placed before the market scene. Check: Does Mara hide, carry, or leave the key before the next event?

This is an invented example, not a required plot pattern. The useful habit is to track how information travels: who witnesses an event, who is told, and when. That makes it easier to catch a character reacting to information before they could plausibly have learned it.

Follow-up question

Some dates are still fuzzy, and I have scenes that happen between major events. How can I show that without pretending I’ve decided everything?

Geez

Label uncertainty instead of hiding it. Use terms such as “approximate,” “before the festival,” or “within the same week,” and mark unresolved decisions with a short question. Do not assign a precise date just to make the table look finished; you can tighten it once the surrounding events are stable.

For scenes between major events, record the boundaries: “after Mara finds the key, before Ivo questions her.” If the length of the interval matters, note what the story requires—perhaps enough time for travel, recovery, or a change in plans—and flag that requirement for your own revision. Keep a “needs decision” marker for conflicts you have not settled. That lets you continue drafting while still seeing where chronology is provisional.

Follow-up question

What’s a practical way to check the timeline during revision, especially when the manuscript order is deliberately non-linear?

Geez

Check chronology and reading order separately. First, sort your timeline entries by story time and look for impossible sequences: an event happening before its cause, an unexplained gap, or a character knowing something too soon. Then read the manuscript in its intended order and ask whether each scene gives readers enough orientation to understand when they are, without accidentally revealing information too early.

A reusable entry is:

Event ID / scene: Story time (exact, relative, or approximate): What happens: Characters present: Knowledge before → after: Depends on / leads to: Open continuity question:

After changing a scene, update its entry and check any events that depend on it. You do not need a complete biography or a rigid calendar: keep the record focused on details that affect sequence, character knowledge, or the reader’s understanding of elapsed time.

A practical checklist

  • Give each event a time marker, using relative wording when exact dates are not settled.

  • Link each timeline entry to a scene label or draft location.

  • Record who is present and any important change in what a character knows.

  • Mark uncertain timing and unresolved continuity questions instead of guessing.

  • Check cause and effect, character knowledge, and time gaps after revising a scene.

  • Review story chronology separately from the order in which scenes appear to readers.

A few more useful answers

Do I need exact dates for every event?

No. Exact dates help only when they matter to the story. Relative markers such as “the next morning” or “before the trip” can keep events clear while leaving details undecided.

Should the timeline follow the chapter order?

Usually, keep the continuity timeline in story-time order and use a separate scene label to show where each event appears in the manuscript. That makes out-of-order drafting easier to review.

What if I change an event’s timing during revision?

Update its timeline entry, then review events that depend on it. Recheck character knowledge and any references to elapsed time, not just the date label.

YOUR QUESTION. YOUR DETAILS.

Let’s work through your situation.

Get a tailored answer or help with your next task. Starts at $1, with a quote before you pay.

Ask your own question
← Back to Geez at Work