How to Build a Case Chronology Where Every Entry Traces to a Source

A case chronology is where a matter’s facts become usable. When it is built well, an attorney can answer “what happened in March, and how do we prove it?” in under a minute. When it is built badly, it becomes a narrative nobody trusts, because no one can tell which entries came from documents and which came from someone’s recollection of a phone call.

This guide sets out a practical method: what a chronology is and isn’t, the columns to use, sourcing rules, how to handle difficult dates, a step-by-step build, quality checks, and how the finished chronology turns into hearing and trial work. It is written for the paralegals and associates who do the building, and it applies whether the matter is a custody dispute, a contract case or a personal injury claim.

What is a case chronology, and what isn’t it?

A case chronology is internal work product: a sortable table of dated facts with a source cited for each one. It is not a narrative, a statement of facts, or a courtroom demonstrative, though it feeds all three.

Because it is prepared in anticipation of litigation, a chronology is generally protected work product under Federal Rule of Civil Procedure 26(b)(3) and state equivalents. Label it that way and keep it out of anything that gets produced. A visual built from it for court is a different document; see timeline demonstratives that persuade.

What columns should a case chronology have?

Enough to sort, filter and cite, and no more than people will actually fill in. These eight cover most matters.

How do you source every entry?

Every row cites at least one specific source, or is explicitly marked as resting on someone’s account. The source column is what separates a chronology from a story.

• Cite the smallest unit. A Bates page rather than a range, a deposition page and line rather than a whole transcript, a message timestamp rather than a thread.
• Quote sparingly and exactly. When wording matters, quote it in quotation marks, copied from the source rather than retyped from memory.
• Label account-only facts. If a fact comes only from a client interview, cite the interview note and mark it so no one mistakes it for documented fact.
• Don’t resolve conflicts silently. When sources disagree on a date or detail, enter both versions or note the conflict. The attorney decides what to make of it.
• Combine, don’t duplicate. When several sources prove the same event, keep one row and list every source.

How do you handle uncertain dates and time zones?

Record exactly what the source supports and flag the rest. Guessed dates are a common source of errors that later surface in depositions and briefs.

Approximate dates

Use “circa,” “on or before,” or a date range, and keep a separate sort date so approximate entries still fall in the right place. Never convert “sometime in spring” into a specific day.

Time zones

Message exports and server logs sometimes record times in UTC, while screenshots show the device’s local time. Travel and daylight saving changes add further offsets. Pick a basis for the chronology, usually local time where the events happened, record it in the column header, and convert consistently. When an event near midnight could fall on either side of a date line, note both.

Recurring events

For patterns such as weekly exchanges or monthly payments, one row can describe the pattern with its source, followed by individual rows only for exceptions.

How do you build a case chronology step by step?

Work source by source rather than date by date, so you always know what has been covered.

1. Get the issue list. Ask the attorney for the claims, defenses or factors in play. These become your issue tags.
2. Build a skeleton. Pull key dates from the pleadings, orders and core documents: filing dates, contract dates, incidents, hearings.
3. Process one source set at a time. Work through each production, folder or transcript in full, add rows, and record the set as complete in a source log.
4. Add the client’s account. Enter interview facts as client-account rows, then look for corroboration.
5. Merge and deduplicate. Combine rows describing the same event and keep every source.
6. Tag issues and people. Make sure every row has at least one issue tag or is marked as background.
7. Run quality checks. See the checklist below.
8. Version and date it. Save the master with a date, and keep earlier versions.

A chronology is never finished while discovery is open. Assign one owner for the master version, and have everyone else submit new entries through a simple queue the owner reviews, so sourcing and wording stay consistent. Each time a new production, transcript or set of client documents arrives, log it in the source log as pending and work it in before the next deadline that depends on the facts. A short change note at the top of each dated version (“added defendant’s third production; corrected two dates from deposition errata”) lets the attorney see what moved since the last time they looked.

Working from tagged, searchable evidence makes each pass faster. An intake process that keeps each item described, dated, tagged and mapped to issues gives you most of a chronology row before you start. Some teams go further and link each entry to its source document; in CourtBriefly, for example, facts and working notes can be linked to their sources and carried into hearing binders.

How do you check a chronology for accuracy?

Check sources, wording and sort order, and have a second person review the rows that matter most.

• Every row has a source or an account-only label.
• A sample of rows has been checked against the cited source, page by page.
• Rows tagged to key issues have been checked in full.
• The event column contains no characterizations or conclusions.
• Dates sort correctly and the time zone basis is stated.
• Disputed facts are marked as disputed.
• The source log shows every production and transcript as processed or pending.

How does the chronology get used?

As the starting point for almost every fact-heavy task in the matter. Filtered views, by issue, by witness or by date range, turn one master into many working documents.

• Deposition outlines. Filter by witness to see every event they were part of. Testimony then flows back in; see how to write a deposition summary.
• Motions and briefs. Filter by issue to draft a statement of facts with citations already attached.
• Hearing and trial outlines. Key rows become examination topics and exhibit lists.
• Summaries and demonstratives. A Federal Rule of Evidence 1006 summary or a Rule 107 illustrative aid may be built from it, with the attorney deciding what is offered and how.

Chronology practice varies by firm and by practice area, and the supervising attorney decides how it is used and what is disclosed. Built with a source on every row, it is the document the whole team will reach for first. For the next step in organizing evidence, see the evidence review workflow for paralegals.