How to Build Litigation Chronologies from Evidence

A chronology often fails before anyone disputes the facts. An email is placed on the date it was printed rather than sent. A voice note is summarized without the second where the key statement appears. A document is treated as contemporaneous even though its date refers to an earlier event. To build litigation chronologies that remain useful through investigation, pleading, discovery, and preparation, each entry must retain its connection to the underlying source.

A litigation chronology is not merely a list of dates. It is a controlled fact record that distinguishes what happened from when someone described it, preserves uncertainty, and lets the reviewing lawyer return to the relevant message, passage, recording point, or document page.

Start with the question the chronology must answer

Do not begin by sorting every file by date. Begin with the factual question. In a contract dispute, the critical sequence may concern notice, performance, cure, and termination. In an employment matter, it may concern reports, management knowledge, scheduling changes, and alleged retaliation. In a family or succession case, it may concern possession, transfers, communications, and the preparation of key documents.

That question determines what counts as an event. A February 12 email may be an event because it gives notice. The attached agreement may be relevant because its clause defines the notice requirement. A later call recording may matter because it describes what occurred after receipt. Treating all three as identical dated items loses the relationship between them.

Set a working scope at the outset: the relevant period, people and entities, locations, transaction or matter identifiers, and event categories. Scope can expand as the record develops, but a stated starting frame keeps the chronology from becoming a running inventory of every document in the case.

Separate event dates from document dates

The most common chronology error is assigning a single date to a source that contains several dates. A message sent on June 4 may state that a meeting occurred on May 30 and that payment is due June 15. Those are three different temporal facts with different levels of certainty.

For each entry, record the event date or date range first, then identify the date type supporting it. That might be a message sent time, an email received time, a date stated in a contract, a recording timestamp, or a date inferred from surrounding communications. If the source only establishes that an event occurred sometime before a message, say so. Precision should come from the evidence, not from formatting pressure.

Time zones require the same discipline. Messaging exports, mailbox data, cloud files, and witness-created records may display different time zones or no reliable zone at all. Preserve the time as supplied, document the convention used for the chronology, and avoid silently converting times when the source does not justify it. A one hour difference can matter in a notice dispute, an alibi investigation, or a sequence of instructions.

Date only documents present another judgment call. A signed letter dated March 3 can support that the document bears that date. It does not necessarily prove delivery, receipt, or the time of signing. The chronology should identify the proposition actually supported.

Build every entry around a traceable source

A useful entry contains a concise factual proposition, its date or range, the actor or actors, and a precise source reference. The reference must allow a reviewer to locate the supporting material without recreating the original search.

For example, instead of writing, “Vendor acknowledged delayed delivery,” write: “June 18, 2:14 p.m.: Vendor representative states that shipment will not leave until the following week, in a WhatsApp message.” The entry can then point to the relevant message within the exported conversation. If the fact comes from a recording, identify the recording and the relevant second. If it comes from a scanned PDF, identify the page. If it comes from a Word file or spreadsheet, identify the relevant section.

The wording should also distinguish direct evidence from a reported account. “Employee stated that the supervisor made the comment on April 8” is not the same proposition as “Supervisor made the comment on April 8.” The first describes what the employee reported and when. Whether it establishes the underlying event is a legal and factual judgment for counsel.

Avoid replacing a source with an unsupported summary. A short description can make a chronology readable, but it should not flatten qualifications, conditions, or disputed language. If an email says, “We may be able to extend the deadline if financing is approved,” the conditional language is part of the fact.

Use a repeatable review sequence

Chronologies become less reliable when team members extract facts in different ways. A repeatable sequence helps keep the record consistent.

First, inventory the available sources and identify their original form. A WhatsApp export, email mailbox, and connected OneDrive folder may each reveal a different part of the sequence. Preserve the original source materials alongside the working chronology rather than treating a copy and paste document as the case record.

Next, identify candidate events. Search for people, project names, property addresses, invoice numbers, key phrases, and date references. Review the surrounding context before creating an entry. A message that reads as an admission in isolation may be a reply to a question that changes its meaning.

Then normalize each candidate event into a consistent entry format. Use the same approach to names, date expressions, uncertainty labels, and source references across the team. Consistency makes gaps and conflicts easier to see.

Finally, conduct a source check. Compare the entry against the original message, document, or recording. Confirm that the stated date, actor, and proposition match the cited material. This check is particularly necessary after an entry has been condensed for a case memo or witness outline.

Treat conflicts and gaps as facts to investigate

A chronology should not conceal inconsistencies in the record. If a June 10 invoice states that work was completed June 7, but messages indicate work continued June 9, enter both facts with their sources. Do not choose between them merely to create a cleaner sequence.

The same principle applies to missing intervals. If communications discuss a call that is not in the production, record that a call was referenced, identify who referenced it, and note the absent source. That gap may later inform a request for additional records, an examination topic, or a witness interview.

Separate confirmed events, reported events, and open questions. A practical approach is to use clear language in the narrative field: “Source states,” “Email reports,” “Date appears in document,” or “Timing not established.” These labels preserve analytical honesty without requiring the chronology to resolve every dispute.

Build the chronology from the case record, not isolated excerpts

Digital evidence frequently arrives in fragmented forms: a long email chain, a ZIP export of chats, scanned PDFs, a spreadsheet tracking payments, and recordings with relevant statements buried in extended conversation. In general practice, the central task is not only extraction. In any disciplined review, it also means preserving the connection between a useful fact and its full context.

TranscriptMe imports WhatsApp chat exports in ZIP files, email mailboxes in .mbox or .eml format, OneDrive folders connected with read only permission, and loose files. Within those sources, it reads PDFs, including scanned PDFs through OCR, as well as Word, Excel, PowerPoint, and text files. On paid plans, it transcribes English and Portuguese audio and video, and provides descriptions of photos and videos.

A legal team can ask focused factual questions across the case record, then review answers with citations to the underlying message, audio or video second, PDF page, or relevant document section. In general practice, locating candidate chronology entries takes patience, especially where a fact appears across a message thread, a hearing recording, and a later email. The source still controls. TranscriptMe organizes facts and does not provide legal advice: the lawyer makes the judgment about relevance, reliability, and case theory.

For file provenance, retain the original source materials and record how they entered the matter. TranscriptMe records a SHA-256 hash for each file on arrival, isolates each case in the database with row level security, and keeps data encrypted in transit. In general practice, questions about authentication and evidentiary use remain legal judgments for the reviewing lawyer. Keeping a disciplined record of the materials reviewed remains the team's own practice.

Let the chronology change as the evidence changes

A chronology is a working instrument, not a finished story created at the first review. New productions may clarify a date, contradict an account, or expose a missing attachment. Update the entry while preserving the basis for the revision. If a previously estimated time becomes exact after a mailbox export is received, replace the estimate and cite the newly available source.

The most valuable chronology does not pretend that the record is complete. It makes the evidence easier to test: one proposition, one date assessment, and one traceable source at a time. That discipline gives counsel a clearer place to begin the next question.