Building a Source-Linked Case Chronology

The chronology is the first thing a senior counsel asks for and the last thing a junior wants to be caught defending. When a bare list of dates goes into a brief and the other side produces a document that contradicts the sequence, the credibility of the entire case narrative takes the hit. A chronology is only as strong as the trail behind each line, so build it as an evidentiary instrument, not a summary.

Separate the event date from the record date

A great deal of confusion in litigation comes from collapsing two different dates into one. A letter dated 3 March may describe a meeting held on 27 February. Record the meeting on 27 February as the event, and cite the letter as the record that reports it. When a witness statement, an email, and a minute all touch the same incident, log them as separate rows pointing at one event. This is how you spot the moment two accounts diverge, which is usually where the dispute actually lives.

Anchor every row to a locatable source

Each entry should let a colleague reach the underlying page in one step. A workable row carries five fields:

• the event date, and whether it is stated in the record or inferred
• a one-line description in neutral language
• the document name and its bundle or exhibit reference
• the exact page or paragraph number
• the person who logged it and when

If a date rests on a phone call rather than a filed order, say so in the row. An inferred date presented as an established fact is the kind of small overstatement that a cross-examiner is trained to find.

Mark confidence honestly

Give yourself a plain vocabulary: confirmed, disputed, inferred, and approximate. A hearing date drawn from a certified order is confirmed; a delivery date reconstructed from surrounding correspondence is inferred. When you later convert the chronology into submissions, these labels tell you which sentences can be stated flatly and which need a qualifier. They also protect the junior who prepared it, because the reader can see exactly what was known at the time.

Hunt for the gaps before the narrative does

A chronology earns its keep when you read it against itself. Look for silent periods where an active matter suddenly has no entries, for two documents that fix the same event on different dates, and for a claimed sequence that a timestamp quietly contradicts. Note these as open questions in the chronology rather than smoothing them over. A visible gap is an instruction to go and find the missing document; a hidden gap is a surprise waiting for the hearing.

Keep it current as the file grows

Chronologies rot the moment the file moves on without them. Decide who updates it after every new order, disclosure, or witness statement, and make updating it part of closing out each task rather than a separate chore nobody owns. Tools built for legal work help here: a workspace such as Juniorlawyer that ties a timeline to the underlying documents keeps the link between an event and its proof intact as material accumulates, so the citation never drifts away from the fact.

Treated this way, the chronology stops being a decorative appendix and becomes the spine of the matter. When counsel asks where a date comes from, the answer is already on the page, complete with the document, the paragraph, and an honest note on how sure you are. That is what lets a timeline survive contact with the other side.