Bookshaper
FeaturesPricingCompareFree Tools
Download Bookshaper
Guides/Reading Your Manuscript

Timeline & Chronology

The order events happen, not the order you tell them

Two Orders, One Manuscript ↓Where the Dates Come From ↓Reading the Timeline ↓What to Look For ↓When Your Manuscript Has No Dates ↓What Review Buys You ↓

Two Orders, One Manuscript

Every novel has two sequences running through it. There is the order the reader meets the scenes — chapter one, then chapter two — and there is the order the events actually happened in the world of the story. For a strictly linear book the two are the same, and the distinction never comes up. The moment you write a flashback, open with a prologue set decades earlier, or braid two timelines together, they come apart.

The Timeline view — Structure → Timeline — is where you see both. It groups your scenes by the dates they carry and lays them out on a chronological axis, so the true sequence of events is visible as a shape rather than something you reconstruct in your head while reading. Switch it to reading order and the same scenes re-sort into manuscript order. Every place the two disagree is a moment where you have moved the reader through time.

That is not a defect to be corrected. Flashbacks and non-linear structures are craft choices, and the view takes no position on them. What it gives you is the ability to see how many of them there are, where they cluster, and whether the pattern you intended is the pattern you wrote.

Above the timeline, a line states how many date groups move between the two orders and out of how many — for example, twelve of thirty-eight. The denominator is the point: a book with three crossings out of forty is doing something very different from one with thirty out of forty, and the raw number alone would not tell you which you have.

Where the Dates Come From

A scene's position on the chronological axis comes from its timeline date. You can set that yourself on any scene, and the manuscript analysis will also propose dates it reads out of the prose — a scene that opens on the morning after the funeral, a chapter that names a month and a year.

An inferred date is a proposal, not a fact, and it is held apart until you accept it. Scenes carrying values still awaiting review are counted in a chip on the toolbar, which opens a review drawer where you can read each proposal against its scene and approve it. Until you do, the value is excluded from your exported book and from the deterministic checks that read chapter dates.

Scenes with no date of their own inherit the last date set before them, which is what lets you date the first scene of a sequence and have the rest of the sequence follow. Inherited positions are marked as inherited rather than shown as though the scene asserted a date itself. The distinction matters when you are hunting a contradiction: a date the scene states is evidence, and a date it merely continues is not.

Reading the Timeline

The Timeline splits into two tabs, and they answer different questions. Above the chronology sits a small toolbar of toggles that change what the axis is made of.

  • Chronological / Reading order: the same scenes, sorted two ways. Chronological is the default because it is the thing you cannot get by scrolling your manuscript.
  • Refined Labels / Original Labels: refined labels are Bookshaper's parsed reading of each date, with values that mean the same period merged into one group. Original labels show the raw text exactly as it appears on the scene, unparsed and unmerged, so you can check what the parse did rather than take it on trust.
  • Years / Characters: Years gives you a plain calendar axis. Characters replaces it with point-of-view threads running across the same date groups, so you can follow whose story is being told when, and see where a thread goes quiet.
Chronology
The chronological layout itself — a year axis or a set of character threads, with a drill-in below showing the scenes in the period you have selected. Clicking any scene opens it in the editor, so you can move from noticing something to fixing it without losing your place.
Dates
The entry table: every scene in reading order, with its date and timeline label editable in place. It is how the Timeline gets built rather than only read, and it needs no analysis run at all — it works with AI switched off.

What to Look For

The value of a chronological view is that it makes certain problems obvious that are nearly invisible when reading forward. These are worth a deliberate pass.

  • Crossings you did not intend. Switch between the two orders and watch which groups move. A flashback you planned will move; a scene that moves because you mis-dated it is a bug you would otherwise find in copyedit.
  • A character who acts before they arrive. With the Characters lens on, a thread that starts earlier in chronological order than the scene which introduces that character is either a deliberate reveal or a continuity error.
  • Empty stretches on the calendar. In chronological order the year axis includes years nothing happens in. A three-year gap in the middle of your book is a fact about your story, and worth confirming you meant it.
  • Clusters where everything happens at once. Several date groups collapsing into a single short window can mean your story is denser than the narration implies — characters crossing a country in an afternoon, or a subplot given weeks it does not have.
  • Dates that look wrong once parsed. If a group's refined label does not match what you meant, switch to original labels and read the raw value on the scene. It is usually the scene's text, not the parse.

When Your Manuscript Has No Dates

A manuscript where no scene carries a date has no axis to lay out, so the Timeline falls back to grouping scenes by chapter and says so in the header — naming which of the two it is, nothing entered yet or a run that found none. This is a missing input rather than a missing feature: the view is waiting for dates, not broken. Its Dates tab is where you supply them by hand, one row per scene, with no analysis involved.

You have two ways to supply them. Set timeline dates by hand on the scenes that anchor your sequence and let the rest inherit, or run the manuscript analysis and review the dates it proposes. Contemporary novels that never name a date are perfectly normal — if yours is one of them, the chapter-grouped fallback is the correct view of it, and the Characters and POV information is still there to read.

What Review Buys You

Accepting an inferred date — or simply typing over it on the Dates tab, which makes it yours — does more than tidy the Timeline. The Timeline under Structure orders chapters by the dates they assert, and an unapproved AI inference does not count as asserted — so the chronology you read there is only as complete as the dates you have made yours.

So the review step is what makes the Timeline's chronology complete for the chapters it covers. Approve the dates you agree with, and the Timeline orders those chapters by what you have made yours — chronology you read for yourself there. Contradictions that live in the prose rather than in a date field are a manual continuity pass's job (see the Continuity & Timeline guide) or a point question for Lume.

Related guides

Continuity & Timeline

Catching contradictions before your readers do

Character Presence & Arcs

Tracking characters across your manuscript

POV Consistency

Maintaining point-of-view discipline across your manuscript

← All guidesDocumentationFAQ

Bookshaper

Write, organize, style, and publish your manuscript in one place.

Product

  • Features
  • Pricing
  • Documentation
  • Writing Guides
  • Blog
  • Comparisons
  • Free Pacing Analyzer
  • FAQ
  • Support
  • About
  • Press Kit
  • Affiliate Program

Help

  • Protecting Your Work
  • Windows Performance
  • System Status

Legal

  • Terms of Service
  • Privacy Policy
  • Licensing Agreement
  • Affiliate Terms
  • Open-Source Licenses

Bookshaper uses AI for proofreading, revision, line editing, expansion, dialogue analysis, and select generation features (such as back-cover blurbs and cover concepts). Your manuscripts are stored locally. We do not authorize AI providers to train on your manuscripts, and we configure available no-retention controls on every request; because these features run on third-party AI platforms, this protection relies on each provider honoring its default API terms.

© 2026 Bookshaper. All rights reserved.