LearnGrok
← Prompts
PromptIntermediateEveryday workflows

Evidence chronology for case strategy

Build a dated evidence chronology for litigation teams preparing an early case assessment or strategy meeting.

4 min read

Nothing here is legal advice. A draft is a starting point for a qualified person, not a substitute for one.

Use these prompts to turn a document bundle into a chronology the team can discuss at an early case assessment or strategy meeting. They are for correspondence, records, witness accounts and key documents where dates, sequence and source quality matter.

The output is a draft work product. It is not legal advice, and it does not decide what happened. A qualified person must assess the evidence, the issues and the next steps.

Key point

Build from sources, not a narrative

Record what each document says and where it says it. Keep competing accounts separate until the team reviews them.

Choose the right prompt

Use the prompts in the order below when you have a new matter. You do not need to use every prompt for every bundle.

  1. Start with Build the master chronology. Paste the source material in manageable batches if needed. Its table gives you a dated baseline, source pinpoints and an initial list of missing material.
  2. Use Reconcile competing event accounts when two or more documents describe one meeting, call, incident or instruction differently. Limit the material to that event. This keeps the comparison usable.
  3. Run Find chronology gaps after the first pass. It turns references to attachments, records, calls and meetings into a collection or review list without pretending those documents have been seen.
  4. Use Prioritise documents for review if the available bundle is too large for full review before the meeting. Give it a document index, metadata and any extracts. Treat its ranking as a review order, not a finding.
  5. Finish with Prepare the strategy meeting chronology. Use a checked master chronology, rather than raw documents, so the meeting version stays short and traceable.

Note

Keep the source material identifiable

Include the file name, document ID, email header or page number with each extract. A chronology entry without a route back to its source is difficult to test.

Prepare the material before you paste it

Do a small amount of document handling first. It prevents avoidable errors in dates and attribution.

  • Give every document a stable reference, such as its existing disclosure identifier or file name. Do not rename documents between chronology versions without recording the change.
  • Keep email headers with the email body. The sent date, sender, recipients, subject line and attachments may matter as much as the text.
  • Mark whether a record is contemporaneous, a later summary, a draft or an account given after the event. The prompts use that distinction when describing certainty.
  • Preserve pages around a key passage. A single quoted sentence can lose its meaning when the preceding qualification or attached document is omitted.
  • Separate your own issue list from the evidence bundle. Label it as a team instruction, not as evidence, if you include it.

If the bundle is long, split it by period or document family. Ask for a chronology for each batch, then use the master chronology prompt again with the batch outputs and their source references. Do not merge entries merely because they have similar dates or descriptions.

Watch out

Do not convert uncertainty into a date

A reference to “the following week” or “our last call” may help place an event, but it is not an exact date unless the source establishes one.

Check the returned chronology

A polished table can still be wrong. Review a sample of entries against the underlying records before relying on it in a meeting. Start with the events that affect sequence, notice, identity, action taken or the date range in dispute.

Check each selected entry as follows:

  1. Open the cited source and confirm that the pinpoint leads to the stated passage.
  2. Check whether the entry reports the source, rather than silently adopting its account as fact.
  3. Compare the event date with the document date. An email sent later may report an earlier event. Both dates may belong in the chronology.
  4. Check names, roles and organisations. Similar names, forwarded emails and shared inboxes can produce false attribution.
  5. Read the attachment or linked record where the source refers to one. A message saying “see attached” is not evidence of the attachment's contents.
  6. Search for duplicates, drafts and later summaries before treating multiple documents as independent confirmation.

Check

A useful entry is traceable and qualified

You should be able to find the source quickly, see how the date was derived, and tell whether the event is recorded, alleged, inferred or disputed.

Use the Coverage limits and Chronology boundaries sections as part of the meeting material. They show what the chronology does not establish. That is often more useful than a longer list of asserted events.

Handle sensitive and incomplete material carefully

Only paste material into the service where your team's information handling requirements permit it. Redact personal data or confidential content where a redacted copy is sufficient for chronology work. Do not assume that an incomplete extract carries the same meaning as the full document.

Service features and applicable limits can vary. Check the current documentation before setting a repeatable workflow: xAI documentation overview.

When the output does not work

If entries are missing, provide the omitted source documents and ask for the relevant date range again. If dates are wrongly ordered, ask for a revised table that separates event date from document date and preserves approximate dates. If the answer makes unsupported conclusions, repeat the task with the source-pinpoint requirement and instruct it to label unknowns as not established from supplied materials.

If the bundle remains inconsistent, do not force one combined account. Use the competing-accounts prompt, retain both versions in the chronology, and take the source documents to the qualified team member for review.

Copy-ready prompts

5 prompts. Open one to read it, or take the whole pack.

1Build the master chronologyUse this first, once you have a mixed bundle of correspondence, records and key documents.
You are assisting a litigation team preparing an early case assessment. Create a master evidence chronology from the materials below for [case name / matter reference]. This is a draft work product for review by a qualified legal professional, not legal advice.

Materials:
[paste correspondence, records and key documents]

Extract each event that is stated, recorded or clearly evidenced in the materials. Return a Markdown table with these columns, in this exact order:
1. Date and time
2. Date status (exact / approximate / range / undated)
3. Event
4. People or organisations involved
5. Source document
6. Source location (page, paragraph, email date and time, attachment name, or other available pinpoint)
7. Evidence type (contemporaneous record / later account / correspondence / draft / other)
8. Certainty (expressly recorded / inferred from record / disputed)
9. Related documents or missing attachments
10. Review note

Sort by date and time. Preserve the source's wording for dates, names and key actions where that matters. Where a document gives only a month, year or relative period, do not invent a precise date. Put it in chronological position as far as possible, mark the date status, and explain the basis in Review note.

Treat statements by different people as separate accounts unless the materials independently confirm them. Do not resolve disputes or state legal conclusions. If a source is illegible, incomplete, contradictory, or refers to an unavailable document, record that fact in Review note. After the table, provide:
- a section titled `Date conflicts and ambiguities`, listing each conflict or uncertainty with source pinpoints;
- a section titled `Documents to obtain or review`, listing the document, why it matters, and the source that refers to it;
- a section titled `Coverage limits`, stating which materials were supplied and what the chronology cannot establish from them.
2Reconcile competing event accountsUse this when witness accounts, emails, meeting notes or records describe the same event differently.
You are assisting a litigation team preparing an early case assessment for [case name / matter reference]. Compare the accounts of the events identified below. This is a draft work product for review by a qualified legal professional, not legal advice.

Event or date range to compare:
[identify the event, meeting, call, incident, or period]

Source materials:
[paste the relevant witness accounts, correspondence, notes, records and documents]

Do not decide which account is true. Separate what each source says from what the documents independently record. Return:

1. A Markdown comparison table with these columns:
- Issue or event detail
- Account or record A, with source pinpoint
- Account or record B or other account, with source pinpoint
- Agreement / difference / cannot compare
- Contemporaneous supporting record, with pinpoint
- Missing evidence or follow-up question

2. A dated mini-chronology containing only events relevant to the identified event or date range. Use the fields: date, event, source, pinpoint, and date status.

3. A section titled `Points requiring team review`. For each point, state whether the issue is a date conflict, identity conflict, sequence conflict, missing record, ambiguous wording, or incomplete document.

If a source is unsigned, undated, internally inconsistent, or appears to be a draft, say so. If dates conflict, report both dates and explain the source basis. Do not infer an event merely because it would make the accounts consistent. Quote short decisive wording only where needed, and give a pinpoint for every quotation.
3Find chronology gapsUse this after producing a first chronology, when you need a focused request list before further review or collection.
You are assisting a litigation team preparing an early case assessment for [case name / matter reference]. Review the chronology and source materials below to identify gaps in the evidential record. This is a draft work product for review by a qualified legal professional, not legal advice.

Current chronology:
[paste the chronology]

Source materials or document list:
[paste documents, correspondence, records, indexes and metadata]

Return a Markdown table with these columns, in this exact order:
1. Gap ID
2. Date or date range affected
3. Missing event, document or record
4. Why the gap appears to exist
5. Source that identifies the gap, with pinpoint
6. Likely holder or system, only if named in the materials
7. Suggested search terms, custodians, date range or attachment name
8. Priority (high / medium / low)
9. Effect on chronology (sequence / identity / notice / action / other)
10. Assumption or limitation

Only identify a likely holder or system where the materials name it or provide a clear basis. Otherwise write `unknown`. Do not claim that a document exists merely because it would be useful. Distinguish an expressly referenced missing document from a possible category of record.

After the table, provide a section titled `Collection sequence` containing a numbered list of the first five collection or review actions, ordered by the gap's effect on the chronology. For each action, name the exact document or record sought, the relevant date range, and the source pinpoint. Then provide `Items not suitable for inference`, listing facts that cannot be established from the supplied material.
4Prioritise documents for reviewUse this where the document set is larger than the time available before the strategy meeting.
You are assisting a litigation team preparing an early case assessment for [case name / matter reference]. Triage the documents below for chronology review. This is a draft work product for review by a qualified legal professional, not legal advice.

Case issues or event period already identified:
[paste the known issues, parties and date range]

Document list, index, metadata or document extracts:
[paste the document list and any available extracts]

Create a Markdown table with these columns:
1. Review rank
2. Document ID or file name
3. Document date
4. Author, sender or record owner
5. Document type
6. Chronology value
7. Event or period it may clarify
8. Reason for priority
9. Related documents, attachments or duplicates
10. Review status (review now / review next / hold)

Rank documents by their likely ability to establish date, sequence, participants, notice, action taken, or a conflict between accounts. Use only the document list and extracts supplied. Do not treat a file name, document date or metadata as proof of the event described in it.

After the table, provide:
- `First-pass review route`: a numbered list of the first documents to open and what exact chronology question each may answer;
- `Duplicate and version risks`: documents that may be duplicates, drafts, forwarded copies, or later summaries;
- `Unavailable information`: metadata, attachments, linked records or source documents needed to assess priority reliably.

Where the document contents are not supplied, label the chronology value as provisional. Do not provide legal conclusions or recommendations on the merits.
5Prepare the strategy meeting chronologyUse this last, when the team needs a short, source-led chronology for discussion rather than a full review table.
You are assisting a litigation team preparing a strategy meeting for [case name / matter reference]. Convert the material below into a concise chronology for discussion. This is a draft work product for review by a qualified legal professional, not legal advice.

Master chronology and supporting materials:
[paste the reviewed chronology, key source extracts and document references]

Meeting focus:
[paste the issues, event period, parties and questions for the meeting]

Return the answer in these four sections only.

## 1. Key dated events
Provide a Markdown table with: date, event, source and pinpoint, participants, status (recorded / account / disputed / approximate), and why it matters to the meeting question. Include only events relevant to the stated meeting focus. Sort oldest first.

## 2. Disputed or uncertain events
For each item, state the competing accounts or uncertainty, the supporting source pinpoints, and the specific document or information needed to clarify it. Do not choose between accounts.

## 3. Evidence gaps and review priorities
Provide a numbered list. Each item must name the missing or unreviewed document, the relevant date range, the reason it matters, and the next review question.

## 4. Chronology boundaries
State the earliest and latest reliable dates, the supplied sources relied on, and facts that remain unverified. If a date is inferred from context, mark it as approximate and state the basis.

Use neutral language. Do not state legal conclusions, assess credibility, or advise on the merits. Every factual statement must have a source pinpoint. If a source cannot be pinpointed from the material supplied, say `pinpoint unavailable`.

Last checked against xAI’s own pages on 2026-08-21. Grok changes quickly; anything version-specific should be confirmed upstream before you rely on it.

More in Everyday workflows

WorkflowIntermediate

Contract review checklist for procurement approval

Produce a procurement contract review checklist with accept, query and escalate decisions for in-house legal and operations teams.

Everyday workflows6 min read

WorkflowIntermediate

Liability clause comparison for negotiation

Compare liability, indemnity and insurance clauses and prepare a negotiation position note for commercial lawyers.

Everyday workflows6 min read

WorkflowIntermediate

Discovery triage register for review priority

Sort an initial document set into review groups and hand over a checked triage register for litigation lawyers and e-discovery teams.

Everyday workflows7 min read

Found something out of date?

Grok changes quickly and this page is a snapshot. If something here is wrong, or you know a better resource, send it over.

Suggest a link →

Advertise on LearnGrok

$420.69one-time, for a 30-day run

Square works best. PNG, JPEG or WebP, up to 2 MB.

Stripe on the next step. Live once approved.