Skip to content
Build a chronologyCorrespondence

Communications Timeline Builder

Turn an email and letter production into a dated who-knew-what-when timeline with thread lineage and Bates cites — knowledge milestones flagged.

Report a correction

Worked example · Synthetic fictional details

Sample prompt

Synthetic example: The names, dates, case details, and issues below are fictional CasePrompts sample values, not client data or evidence from a real matter. They demonstrate the prompt format, not the accuracy of any AI model's output.

Preview the complete sample prompt
Customize in builder
CONTEXT:
You are a litigation support analyst assisting defense counsel in a commercial contract dispute matter. The attached production is correspondence — emails, letters, and attachments. The issues that matter are: notice of the defect; cure-period communications; decision to terminate.

INSTRUCTIONS:
Build a complete dated timeline of every communication in the production. For each item capture: date and time as precisely as the document states; author; recipients and copied parties; the thread it belongs to (link replies and forwards to their parents); the substance in one or two sentences; and which key issue it bears on, if any. Separately and explicitly:
1. Flag every "knowledge milestone" — the first communication showing that a person or organization knew of a fact bearing on a key issue.
2. Flag forwards and blind copies that put a communication in front of someone outside the original thread.
3. Flag referenced attachments, enclosures, or prior communications that are not in the production.

TEMPLATE — format your output exactly as follows:
## Timeline
| Date / time | From → To (cc) | Thread | Substance | Bears on | Cite |
|---|---|---|---|---|---|
## Knowledge milestones
| Date | Who knew | What they knew (verbatim where possible) | Cite |
|---|---|---|---|
## Referenced but not produced
| Referenced item | Where referenced (cite) |
|---|---|

EVIDENCE REQUIREMENTS:
For every finding, cite the exhibit or Bates number and page; if neither exists, cite the PDF page number. Attribute every entry to its author exactly as the document states; never infer authorship from context. Quote verbatim wherever knowledge or notice is the point. If a date is ambiguous or absent, say so in the entry rather than estimating one.

If the provided record does not support a requested finding, write "not found in the record." Do not infer or fill gaps from outside knowledge.
The scope is limited to the requested task, stated issues, and provided record. Do not introduce outside subjects or sources.
A human reviewer must verify every material statement and citation against the source record before relying on or sharing the output.

AI output is a starting point, not work product. Verify every citation against the record before you rely on it, file it, or send it.

What you'll fill in

  • 01Your role
  • 02Case typee.g., "trucking liability," "first-party property," "medical malpractice"
  • 03Key issue(s) — 1 to 3e.g., "vehicle speed at impact; brake maintenance; visibility"

Pro tip The 'Referenced but not produced' table is a ready-made follow-up production request.

Record-first path

Related verification workflow