Building a litigation chronology with AI
By the ChamberOne team 5 minute read
A chronology is the spine of a litigation file. Every witness statement, every pleading and every argument leans on it. It is also the kind of work that eats a junior's week: reading hundreds of pages, noting every date, and trying to keep the sequence straight. AI can take the first pass at the reading. It cannot decide which events matter or whether two accounts of the same day agree. This article describes a method that uses the tool for what it does well and keeps the checking with people.
Key points
- Fix the chronology's columns and a convention for uncertain dates before extracting anything.
- Ask for events with exact wording and page references, one document or small batch at a time.
- Never keep an entry you cannot trace to a page.
- Watch for date-format confusion, relative dates, document dates versus event dates and misread scans.
- A lawyer decides which conflicts matter and what goes into any version used in court.
What a good chronology is for
A chronology records what happened, when, and where the evidence for it sits. It helps the team see the story, spot gaps and contradictions, prepare witnesses and cross-examination, and draft pleadings. Its value comes from being accurate and traceable. A chronology without sources is a story. With sources, it is a working tool.
Step one: decide the columns first
Before any extraction, fix the structure. A common layout has columns for date, event, source document, page or paragraph, who says so, and a note on relevance or issues. Add a column for status, such as checked or disputed.
Decide how to handle uncertain dates. Approximate dates, ranges and events known only by relation to others, such as the week after the meeting, need a convention, or the sequence will be unreliable.
Suppose a litigation team is preparing a chronology for a commercial dispute with around four hundred documents. They agree that every row carries a precision marker: exact, approximate or inferred. A row for an event known only from a witness statement is marked approximate. When the chronology is sorted, a reader can see which dates are firm and which are the team's best reading.
Step two: extract dated events from the documents
Ask the tool to list every dated event in each document with the exact wording that gives the date and the page it appears on. Work one document at a time, or in small batches, so you can trace each result.
Be specific in your instruction. Ask for events, not summaries. Ask it to include dates stated in different formats, and to flag where the document does not give a date for something that clearly happened.
Keep the instruction the same across documents so the output has a consistent shape. Save the wording that works, and note which tool and version you used, so another team member can repeat the exercise and get comparable results.
Step three: link every entry to its source
Every row needs a reference that a colleague can follow in thirty seconds: document name, page or paragraph, and ideally the words relied on. If the tool cannot supply the page, find it yourself before the entry goes into the chronology.
This is the rule that protects the work. An entry you cannot trace to a page is an entry you should not rely on.
Step four: check what the tool tends to get wrong
- Date formats. Day-month and month-day are easily confused in documents from different countries.
- Relative dates, such as last Tuesday or two weeks later, which depend on a date elsewhere in the document.
- Dates of documents against dates of events. A letter dated in March may describe something that happened in January.
- Poor scans, handwritten notes and stamps, which may be misread or skipped.
- Events that matter but are not dated, such as a conversation referred to in passing.
- Duplicates of the same event described in several documents.
Step five: merge, sort and look for conflicts
Once the entries are checked, merge them into a single sorted table. Now the useful work begins. Look for places where two documents give different dates for the same event, where a witness says something happened before a document shows it could have, and where there are unexplained gaps.
A tool can help by listing apparent inconsistencies, but each one needs a lawyer's reading. Some will be mistakes in extraction. Some will be real contradictions in the evidence, and those are the ones that matter.
It may help to read the sorted table aloud to a colleague, one row at a time. A sequence that sounds wrong when spoken, such as a reply dated before the letter it answers, is often an error you stopped seeing on the screen.
Mark each conflict in the chronology with a short note and an owner. Someone should decide whether it is an error to correct, an inconsistency to put to a witness or a point to raise with the other side. A conflict nobody owns tends to stay unresolved until the hearing.
Step six: decide what the chronology is for
A master chronology may contain everything. Versions for particular purposes, such as a short one for a hearing, or one limited to the issues in dispute, should be edited by a lawyer who knows what matters. Selection is an act of judgment about the case, and no tool can make it for you.
Keep the master and the version you use separate, and note the date of the last check on each.
Add new documents as they arrive, such as disclosure or witness statements, and repeat the checks on the new rows only. A chronology that is updated in small steps stays trustworthy, while one that is rebuilt before each hearing invites fresh mistakes.
Before anyone relies on a chronology in court, have a person who did not build it check a sample of entries against the sources. Fresh eyes find the date that was transposed or the page number that slipped by one.
- 1New documents arrive
- 2Extract dated events with the same instruction
- 3Link each row to its source
- 4Check the new rows only
- 5Merge, sort and look for conflicts
- Then back to step 1.
Confidentiality and record-keeping
Processing case documents means sending text to a tool. Find out where it goes and what is kept, and check the guidance from your regulator or bar on confidentiality. Note on the file that AI was used for the first pass, and who checked it. If the chronology is shared with the court or the other side, make sure it contains only what you intend to disclose.
This article is general information about the law, legal practice and technology, current when it was published. It is not legal advice. Laws and guidance change: check the sources linked above and take advice on your own circumstances from a lawyer qualified where you are.
Read next
India: arbitration, court intervention and awards, as the law stands in November 2026
The 1996 Act governs Indian arbitration; the Supreme Court has allowed limited modification of awards, and the 2024 amendment Bill is a draft.
6 minute readElectronic evidence under the Bharatiya Sakshya Adhiniyam
Section 63 of the BSA replaced Section 65B from 1 July 2024, adding a prescribed certificate format, mandatory hash values and an expert co-signature. This article explains every change that matters in practice.
6 minute readAI in Witness Bundle and Proof of Evidence Preparation: What to Automate and What Not To
A practical guide for litigators on which parts of witness bundle and proof of evidence preparation AI can handle, and which parts it must not touch.
6 minute read