For legal, research and incident chronologies

Chronology software for legal, research and incident timelines

Build a chronology where every event cites its evidence, dates can count from a T-zero, and every change is reviewed and recorded. The timeline below counts a Falcon 9 launch from liftoff, from the countdown to the satellites deploying.

Evidence cited, not just listed

Keep each exhibit, statement or log in one source library and cite it from every event it supports. A reader sees the evidence under the fact.

  • Books, articles, archives, web pages and media, each with the right fields.
  • Add a source once, cite it from as many items as you like.
  • Give the timeline assistant a PDF, a spreadsheet or a pile of scans and it drafts the events it finds, each with the quote it rests on. Nothing is added until you have reviewed it.

Time counted from T-zero

Date an incident from the moment it began: T minus 38 minutes, T plus 2 minutes 13 seconds. Where the evidence is vague, say so, and the date keeps its margin.

  • Count from a moment of your own and name it; every date reads from it, in seconds, minutes, days or years.
  • Add a ± where a time is only roughly established, and the edge of its bar softens on the axis.
  • Write a date in the calendar a source uses, and let every reader see it in theirs.

Colleagues with the right access

Invite people as viewers or editors, or let a team own the chronology, so the work goes on beyond one person's account.

  • Editors add and change items; viewers read.
  • Hand a timeline over to someone else, or to a team.
  • Discuss the timeline, or any one item, right beside it. The discussion stays private, even on a public timeline.

Pro & TeamCollaborators come with Pro and Team, and a team with the Team plan.

Review before anything changes

Viewers you invite can suggest an edit: a corrected date, a new event or a removal, with a note. An editor reviews each one, and nothing changes until it is accepted.

  • A reviewer suggests an edit and says why.
  • Editors tick what to accept and can leave a note for the suggester. Nothing is overwritten silently.
  • Accepted edits land as the editor's own in the change history, and can be undone.

Pro & TeamLetting viewers suggest edits comes with Pro and Team.

An audit trail you don't have to keep

Every edit is recorded: who changed what, with the values before and after.

  • Filter by person, field or item.
  • Undo an edit straight from its line in the change history.
  • Deleted items and timelines can be restored for a while.

Pro & TeamPro and Team reach much further back through the change history than Free.

A booklet to file or hand in

Turn the chronology into a PDF to read, print or hand in, or a Word file to keep writing in, with every sourced item in date order.

  • Choose what goes in, from a full booklet to a compact list of items.
  • On A4 or US Letter, in any of six languages.
  • As a Word file, the sources come through as notes that renumber as you edit.

Pro & TeamExporting a booklet comes with Pro and Team, and also when you edit a timeline whose owner has one.

Coming from a spreadsheet or a document?

A spreadsheet of dates is the usual chronology, and its weakness is always the same: the evidence sits in another column or another file. Here each event carries its citation.

A document with a table has no memory of itself. When a time changes, you can't say who changed it or when. The change history can.

Emailing a file round the team ends with several chronologies. One timeline, with editors and reviewers, stays one.

More chronologies to read

Explore all

Ask AI

Answers come from the help centre and can be wrong.

Timescrolly does NOT keep your conversations.

See a chronology counted from T-zero

A Falcon 9 launch, from the go for propellant load to the second satellite deploying, every step at its second.

Open the Falcon 9 launch timeline