A chronology is an argument under discipline
Litigation is full of lists of dates. A chronology becomes forensic work only when selection, description and source are handled consciously. What is included suggests what matters. The language used to describe an event may assume the very conclusion in dispute. The order of events may invite an inference of knowledge, reliance, delay or causation.
That does not make a chronology improper advocacy. It means its construction must be disciplined. The working chronology should be capable of holding facts that support the case, facts that resist it, and facts whose significance is not yet known. It is a place to test a narrative before presenting one.
Separate the dates that documents blur
One entry may involve several dates: when an event occurred, when a record was created, when it was sent, when it was received, and when a witness later described it. Treating these as one “date” can conceal the central issue.
Consider an email written on Friday that says a conversation occurred “earlier this week”, forwarded the next Monday, and exhibited years later to an affidavit. The email date is certain. The conversation date is a range reported by the writer. The forwarding date proves a later communication. The affidavit date proves when the witness adopted an account, not when the underlying event occurred. Each may matter for a different reason.
Record precision honestly. If the source establishes only a month, use the month. If two sources conflict, preserve both propositions until there is a reasoned basis to prefer one. False precision gives an attractive appearance of certainty while weakening the analysis beneath it.
Every event needs a source and a status
A robust entry answers at least four questions:
- When? The event date or best-supported range, with the document date kept separately where necessary.
- What? A neutral description specific enough to be useful.
- According to whom or what? A pinpoint reference to the document, page, paragraph, transcript line or instruction.
- With what status? Contemporaneous record, agreed fact, allegation, recollection, inference, disputed proposition or unresolved question.
“Meeting about contract” is too thin. “According to Lee's later statement, Lee and Patel discussed extending the delivery window” is better because it identifies the proposition and its character. If contemporaneous minutes say nothing about an extension, that belongs nearby rather than being silently reconciled.
The chronology should never make a contested account look agreed merely because both sides' propositions fit into the same date column.
Build broadly, then create issue views
The master chronology should be inclusive enough to preserve context. A hearing chronology should not. The mistake is to force one document to perform every task.
Begin with the material events and procedural history. Tag or otherwise mark entries by issue, actor, document type and confidence. That permits narrower views: the formation negotiations, the notice sequence, the history of a particular representation, the steps said to constitute delay, or the procedural events relevant to an application.
A filtered chronology is more useful than a prematurely shortened master. It lets counsel test whether a proposed narrative depends on excluding inconvenient events, and makes it easier to prepare a concise chronology for the court without losing the fuller analytical record.
Use sequence to test causation and knowledge
Sequence alone does not prove causation, but it often reveals what must be explained. Ask of each important event:
- What had already happened, and what had not?
- What could this person have known at the time?
- What decision or communication followed?
- Is the alleged cause earlier than the effect?
- Does the interval make the proposed inference stronger, weaker or merely possible?
This is particularly useful where later accounts compress time. A witness may honestly remember two connected events as consecutive when contemporaneous records show an intervening decision, warning or opportunity to act. The chronology does not decide credibility, but it identifies the proposition that cross-examination and submission must confront.
Silence can be an event, but handle it carefully
Absence matters only against an expectation. “No complaint recorded” is meaningful if the record is one in which a complaint would ordinarily appear, the relevant period has been searched, and the authors or custodians can be identified. It is much less meaningful if the collection is incomplete.
Mark gaps as questions: no document located between these dates; attachment referred to but absent; meeting alleged but no diary entry produced; response expected by a deadline but none presently found. A gap list generated from the chronology can drive further instructions, disclosure requests, subpoenas and conference questions. It should not be converted into a positive fact without an evidentiary foundation.
Keep procedural and evidentiary histories connected
The procedural chronology is often maintained separately, but the two histories interact. The date on which an allegation first appeared, particulars changed, a document was discovered, or a witness account was served may bear on the forensic significance of the evidence. Linking those events avoids the artificial picture in which the facts existed in a vacuum and the parties' cases never evolved.
Versions matter. If a pleading, expert report or statement is superseded, retain the relevant historical entry and identify the current document. Otherwise a search may surface language that is no longer relied upon without revealing when or why it changed.
Draft from the chronology, then test against the sources
A mature chronology can become the spine of an advice, opening, witness conference or cross-examination plan. It should not become a substitute for the evidence. When a paragraph of submission draws on a sequence, return to the underlying sources. Check the quoted words, the admissible use, the actor's knowledge and any competing entry nearby.
The final court chronology will usually be spare: agreed where possible, neutral in expression, and confined to events that assist. Its simplicity should be the result of deep work, not the absence of it.
Where software helps—and where it stops
Software can extract candidate dates, keep references attached, filter events by issue, and make it faster to move between an entry and its source. Those are meaningful gains, especially in a brief with many repeated dates. But a detected date is not yet an event, and an event is not yet relevant or proved.
Lexware's approach is to keep chronology work connected to the local brief and under review. Candidate dates can assist the first pass; counsel decides what enters the working chronology and how it is characterised. That division matters. The machine reduces clerical friction. The barrister supplies forensic purpose.