What this skill does
Chronology Builder is one of the most time-consuming tasks in litigation and dispute work, now reduced to minutes. You feed the skill a collection of documents — emails, letters, contracts, court filings, transcripts, internal notes — and it extracts every date-anchored event, organises them in chronological order, and presents a structured timeline with the source document referenced against each entry.
The skill handles messy real-world inputs: dates in multiple formats, implied timelines ("three weeks after the notice was sent"), events described across several documents that need to be reconciled, and gaps in the record that suggest missing documents. It flags conflicts — where two documents give different dates for the same event — and notes entries where the date is approximate or inferred rather than explicit.
The output chronology serves directly as the factual backbone for pleadings, witness statements, and litigation strategy documents. It is the same task that associates spend hours on before a big arbitration hearing, done automatically so they can focus on the analysis.
When to use it
- Preparing a case for litigation or arbitration, where a reliable chronology is the foundation for all pleadings
- Conducting an internal investigation, where you need to establish a clear sequence of events from email and document trails
- Advising on a breach of contract claim, where the timeline of performance and default is central to liability
- Preparing witness statements and needing to brief witnesses on the chronological sequence of events they participated in
What you get
A structured chronology table with columns for Date (explicit or inferred), Event Description, Parties Involved, Source Document (with reference), and Notes (flagging conflicts, gaps, or inferences). The skill also produces a brief Narrative Summary — two to three paragraphs that tell the story of the chronology in prose form — and a Gaps & Conflicts section identifying missing documents or inconsistencies that need further investigation.
Example prompt inputs
- "20 emails between a contractor and a developer over an 18-month construction project. Build me a chronology of the key events and disputes"
- "A case file containing a contract, three amendment letters, several performance notices, and the termination letter. What is the timeline?"
- "Transcript from a client interview about a shareholder dispute — extract the dates and events in chronological order"
- "Internal investigation into an employee conduct issue — please extract the timeline from these HR emails and incident reports"
Why legal-specific AI matters here
Chronology work requires more than extracting dates from text. It requires understanding what counts as a legally significant event (a formal notice, a deadline missed, a payment made late) versus what is background noise. It requires recognising when a document implies a date without stating it, and when two accounts of the same event are inconsistent in a way that matters. Whisperit's Chronology Builder applies legal reasoning to this task — it knows what a notice period is, what triggers a breach, and what kind of date discrepancy is legally material versus merely administrative.