To build a case chronology that lawyers can trust, treat it as an evidence index with a time dimension. Each entry should state what happened, identify who says so, link to the supporting passage, and expose uncertainty. A long list of dates copied from documents may look complete while hiding contradictions and missing proof.
The useful chronology is built for a purpose. It helps a team test a pleaded narrative, investigate limitation, prepare a witness, trace compliance with an order, or find the record needed for a hearing.
What question should the case chronology answer?
Write the chronology's purpose at the top of the working instructions. A master factual chronology and a procedural chronology may share events but answer different questions. A witness chronology may include only events that person observed or discussed. A limitation chronology may require trigger events, acknowledgements, exclusions, and filing dates.
Define the date range, issues, parties, document set, and standard for inclusion. Decide whether allegations are included and how they will be labelled. Never present a pleading assertion as an established fact merely because it has a precise date.
| Chronology type | Primary question | Typical sources |
|---|---|---|
| Factual | What happened and in what sequence? | Contracts, messages, records, witness material |
| Procedural | What has happened in the proceeding? | Pleadings, filings, orders, hearing records |
| Issue-specific | What evidence bears on one disputed question? | Selected documents, testimony, expert material |
| Witness | What did this witness do, see, receive, or say? | Statements, communications, contemporaneous records |
| Limitation | Which events may start, pause, extend, or affect time? | Transactions, notices, acknowledgements, filings, orders |
The companion guide to litigation chronology software explains how to assess tools for traceability, filters, and lawyer validation.
What fields belong in a case chronology template?
Keep the event statement short and factual. Put argument in a separate analysis field. One row should normally represent one event, even if a document describes several events.
Use fields such as:
| Field | Purpose |
|---|---|
| Event ID | Stable reference for discussion and updating |
| Date and time | Normalised value without discarding source wording |
| Date status | Exact, approximate, range, inferred, disputed, or unknown |
| Event | Neutral description of what allegedly or demonstrably occurred |
| Actor and recipient | People or entities involved |
| Issue tags | Controlled links to pleaded or investigatory issues |
| Source | Document ID, page, paragraph, timestamp, or exhibit |
| Source type | Contemporaneous record, pleading, testimony, order, or other |
| Position | Agreed, alleged, admitted, denied, disputed, or untested |
| Reviewer note | Significance, contradiction, gap, or next step |
| Review status | Extracted, checked, approved, or requires decision |
Preserve the date as written alongside any normalised date. “Early March,” “within seven days,” and a timestamp in another time zone should not be converted into false precision.
How do you extract events without distorting the source?
Work from an authorised document set with stable identifiers. Read enough surrounding text to understand the event. Capture the actor, action, object, date, and conditions, then cite the precise passage. If the document reports what another person said, preserve that distinction.
Follow a repeatable workflow:
- Inventory documents and identify versions, duplicates, amendments, and gaps.
- Prioritise sources tied to the chronology's stated question.
- Extract candidate events with page-level or passage-level citations.
- Split compound entries into separate events.
- Normalise dates while retaining source expressions and assumptions.
- Tag issue, witness, and procedural relationships.
- Compare sources for corroboration or conflict.
- Have a lawyer review material entries and analytical conclusions.
The eCourts Services portal can provide official case information and access services. Record when and how an external entry was obtained, and verify it against the relevant court record where the task requires it. Gotham's practice workspace can keep chronology entries near their sources, and workflow automation can support staged extraction and review.
How should disputed, inferred, and missing dates be shown?
Uncertainty belongs in the data, not in a footnote that disappears during sorting. Use an explicit date-status field. If a date is inferred, state the inference and cite the inputs. If sources conflict, preserve both accounts and link them rather than choosing the more convenient one.
Examples of honest date treatment include:
- “Email sent 14:32 IST” as exact when the source and time zone are clear;
- “Meeting during the week commencing 6 April” as a range;
- “Delivery occurred before inspection on 12 May” as an event with an upper boundary;
- “Date alleged in paragraph 18 of the plaint” as an allegation; and
- “No source located for the stated call” as an evidence gap.
This discipline matters under the Bharatiya Sakshya Adhiniyam, 2023, which is an official legislative source concerning evidence. The application of any provision to a document or electronic record is a legal question. A chronology should preserve the material needed for counsel to analyse that question, not announce admissibility.
How can a chronology support limitation analysis?
Create a dedicated view for events that may affect time. Include the asserted cause-of-action event, knowledge-related facts where relevant, acknowledgements, part payments, disability or exclusion arguments if raised, notices, holidays or court closure material where relevant, and the filing or presentation record. Cite every input.
Consult the official text of the Limitation Act, 1963 and current applicable law. Do not encode one generic “limitation date” rule across claims. The applicable article, accrual analysis, exclusions, forum, relief, and later facts can materially alter the answer.
Use a calculation record rather than a bare deadline:
| Calculation element | What to record |
|---|---|
| Legal basis under review | Provision or proposition counsel is assessing |
| Trigger fact | Event and source asserted to start time |
| Candidate start date | Date plus status and rationale |
| Adjustments | Each proposed exclusion, extension, or other effect |
| Candidate deadline | Calculated output, not an unqualified legal conclusion |
| Reviewer | Qualified person who checked assumptions and law |
| Review date | When sources and legal basis were last checked |
Set reminders earlier than any candidate deadline, but do not let workflow alerts replace legal analysis and diary controls.
How do you verify a chronology before relying on it?
Review in layers. First verify citations and transcription. Then review dates, actors, and issue tags. Finally assess narrative completeness, contradictions, and legal significance. Use a second reviewer for high-impact events and deadline calculations.
Apply this quality checklist:
- Every material event has a source or is labelled as unsupported.
- Citations open the correct document and passage.
- Source wording and normalised dates are both retained.
- Allegations, admissions, findings, and reviewer inferences are distinct.
- Duplicate accounts are linked rather than counted as separate proof.
- Conflicting dates and descriptions remain visible.
- Amendments and corrected orders are represented historically.
- Time zones and calendar assumptions are documented.
- Limitation calculations show inputs and review status.
- Privileged analysis has suitable access controls.
The Supreme Court of India and relevant court websites should be used for current official material in matters before those courts. Internal summaries should link back to the controlling source.
How should a chronology be used in hearing and witness preparation?
Create filtered views rather than separate uncontrolled copies. A hearing view can show only events tied to the issues being argued, with source links and the parties' positions. A witness view can isolate events the witness participated in while keeping impeachment or privileged analysis appropriately restricted.
For each important event, prepare a compact card: neutral event statement, date status, source passage, competing account, issue relevance, and open question. This makes the chronology useful during preparation without turning it into a script.
How do you keep the chronology current as the case develops?
Assign ownership and preserve revision history. New pleadings, disclosure, witness material, orders, and hearing records should enter an intake queue. Record who added or changed an event and why. Freeze a reviewed snapshot before a major hearing so the team can reconstruct the version used.
Review gaps, not just rows. Missing periods, references to absent attachments, unexplained changes in account, and orders without recorded compliance may be more valuable than another routine event.
A strong case chronology remains modest about what the record proves. It separates evidence from argument, makes uncertainty sortable, and lets a lawyer reach the source quickly. To explore a source-linked litigation workflow, contact Gotham, see the security overview, or review pricing.
