Build a Case Chronology From a Document Set

Turn a mixed set of documents into a dated, source-cited case chronology that surfaces conflicts, gaps, and the events most material to your legal issues.

The Workflow

1. 1

   Load the documents and have Claude inventory them

   Upload or paste the full document set — emails, records, filings, intake notes, anything dated. Before any analysis, have Claude tell you exactly what it received and flag anything it cannot read, so you know the chronology is built on the complete set and not a silently truncated one.

   PromptCopy

   You are helping me build a case chronology for a litigation matter. I am going to give you a set of documents: [DESCRIBE THE DOCUMENTS, e.g., "42 pages of emails, two medical records, and a complaint, Bates ABC-0001 to ABC-0044"].
   
   Before analyzing anything, inventory what I have given you. List each distinct document you can identify, with: a short label, the date or date range it covers, its apparent type (email, record, filing, note), and the page or Bates range it occupies. Then separately flag anything you cannot read clearly — illegible scans, cut-off pages, missing attachments, or documents with no identifiable date. Do not build the chronology yet.

   What you get: A numbered inventory of the documents with labels, dates, types, and page/Bates ranges, plus a separate list of anything unreadable or undated. Use this to confirm Claude received everything and to spot gaps in your own production before you go further.

2. 2

   Build the date-ordered chronology table

   Have Claude produce the core deliverable: a chronology table with one row per event, ordered by the date the event actually occurred, with a source citation on every single row. The source column is what makes the whole thing verifiable.

   PromptCopy

   Now build a case chronology from these documents as a table with exactly these columns: Date | Event | Actor(s) | Source (page/Bates) | Significance.
   
   Rules:
   - One row per discrete event.
   - Order rows by the date the event OCCURRED, not the date of the document describing it. If an email dated March 10 describes a meeting that happened March 3, the row date is March 3.
   - Put a specific source citation (page or Bates number) in the Source column on EVERY row. If an event has more than one source, list them all.
   - Use the actual date from the document. If a document gives only a partial or approximate date ("early April," "that summer"), record it exactly as written and mark it [approximate].
   - In Significance, note in a few words why the event may matter to the case — but keep it factual; do not argue the case.
   - Do not infer events that are not supported by a document. If something is implied but not stated, leave it out.

   What you get: A clean, date-ordered table with a source cite on every row. Dates should reflect when events happened, not when documents were written. Approximate dates should be flagged. Spot-check a handful of rows against the cited pages before relying on it.

3. 3

   Flag conflicts, gaps, and material events

   Now turn the chronology into investigative leads. Have Claude surface where documents contradict each other, where the timeline has unexplained gaps, and which events are most material to your legal issues — all as questions for you to run down, not conclusions.

   PromptCopy

   Using the chronology you just built, give me three separate lists.
   
   1. CONFLICTS: Every place where two or more documents disagree about a date, a sequence, or what happened. For each, cite both sources and state the contradiction plainly. Do not resolve it — just surface it.
   
   2. GAPS: Notable stretches of time with no documented activity, missing records you would expect to exist given the surrounding events, or events referenced in one document but never documented directly. Frame each as a question I should investigate.
   
   3. MATERIAL EVENTS: The events most likely to matter given that the legal issues in this case are [STATE YOUR CLAIMS/DEFENSES/ELEMENTS, e.g., "breach of contract and the date of the alleged breach" or "notice and causation in a slip-and-fall"]. Explain in one line why each is material.
   
   Treat all of this as leads for me to investigate, not findings.

   What you get: Three lists — conflicts (with both sources cited), gaps framed as investigative questions, and material events tied to your stated issues. Each item is a lead to run down against the source documents, not a settled conclusion.

4. 4

   Draft a narrative statement of facts (optional)

   If you need prose for a brief, demand letter, or memo, have Claude turn the verified chronology into a plain narrative. Keep it neutral and tied to the record so it stays easy to check against your sources.

   PromptCopy

   Draft a chronological statement of facts in plain prose based on the chronology above. Requirements:
   - Neutral and factual — narrate what happened, do not argue.
   - Follow the chronological order of events.
   - After each factual sentence, include the source citation (page/Bates) in parentheses so I can verify it.
   - Do not include any fact that is not in the chronology.
   - Where the chronology flagged a conflict, present both versions rather than picking one.
   
   Keep it to a clean first draft I will edit and verify.

   What you get: A neutral, chronological narrative with a parenthetical source cite after each sentence. It is a first draft to edit, not final copy — confirm every citation and adjust tone for your audience.

5. 5

   Verify every date and event against the source

   Before this chronology informs any filing, discovery decision, or settlement position, verify it. Because each row carries a citation, this is a targeted spot-check rather than a full re-read — but the responsibility is yours.

   What you get: A chronology you have personally checked. Pull the cited page for each material row and confirm the date, the event, and the actors match the source. Pay special attention to the date-occurred rule (events placed on the date they happened, not the document date), any [approximate] dates, and every flagged conflict. Correct anything Claude got wrong, fill the gaps you can, and only then rely on it. The output is a lead and a first draft; you are responsible for what goes in the record.

Example Output

Illustrative example — names, facts, and figures are fictional.

CASE CHRONOLOGY — Estate of Doe v. Riverside Property Mgmt (ILLUSTRATIVE / FICTIONAL)
Legal issues: notice of the hazard and causation in a premises-liability claim.

Date | Event | Actor(s) | Source (page/Bates) | Significance
2023-01-14 | Tenant emails property manager that stairwell light on Floor 3 is out | J. Tenant; M. Manager | RPM-0007 | First documented notice of the alleged hazard
2023-01-16 | Manager replies "will send maintenance this week" | M. Manager | RPM-0008 | Acknowledgment of notice; no completion date
2023-02-02 | Maintenance work order opened for "3rd flr lighting" | Maintenance | RPM-0021 | Gap: 17 days after notice; status left blank
2023-02-09 | Plaintiff falls on Floor 3 stairwell ~9:15 PM | A. Plaintiff | RPM-0031 (incident report); MED-0003 (ER intake) | Core event; ER intake time conflicts with report (see Conflicts)
2023-02-09 | ER intake lists arrival 10:05 PM, "fall on stairs" | A. Plaintiff | MED-0003 | Establishes injury and same-day treatment
2023-02-21 | Light bulb replaced per closed work order | Maintenance | RPM-0022 | Repair completed 12 days after the fall

CONFLICTS
- Time of fall: incident report says ~9:15 PM (RPM-0031); ER intake says arrival 10:05 PM (MED-0003). Not necessarily contradictory, but the 50-minute gap is unexplained — investigate.

GAPS
- No record of any maintenance activity between the Jan 16 reply (RPM-0008) and the Feb 2 work order (RPM-0021). Was the hazard inspected in that window?
- Work order RPM-0021 status field is blank — was any work done before Feb 9?

MATERIAL EVENTS
- Jan 14 notice (RPM-0007): goes directly to whether defendant had notice of the hazard.
- Feb 9 fall (RPM-0031): the injury-causing event and the heart of causation.

Tips

• •Give Claude your legal issues up front. "The elements are notice and causation" produces a far more useful Significance column and material-events list than a generic "summarize the timeline."
• •The date-occurred rule is the one that trips up timelines most. When you verify, specifically check that an email describing a past meeting is dated to the meeting, not to the email.
• •Treat conflicts and gaps as your to-do list, not Claude's conclusions. A flagged contradiction means "go read both documents"; a gap means "ask whether a record is missing or was never produced."
• •Keep everything in one conversation. Building the chronology, then the conflicts list, then the narrative all in the same thread lets Claude reuse the citations it already established, which keeps sources consistent across outputs.

Prompts used in this workflow

Related Reading

• Claude AI for Litigation: Depositions, Motions & Trial Prep
• How to Use Claude for Legal Work
• Litigation Practice