Skip to content
Summarize the recordMixed / full case record

Plain-English Client Summary

A client-friendly status summary of the record at an eighth-grade reading level — jargon translated, honest about what's unresolved, nothing overpromised.

Report a correction

What is an AI plain-English client summary prompt?

It is a CITE prompt that asks an AI tool to summarize case records. A client-friendly status summary of the record at an eighth-grade reading level — jargon translated, honest about what's unresolved, nothing overpromised. You fill in four fields; the Evidence block requires a page:line, Bates, page, or timestamp cite for every finding so a person can check each one against the record.

Sample prompt

Synthetic data

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 counsel's paralegal in a motor vehicle negligence matter. The attached materials are the case record. You are preparing a status summary for the client. The issues that matter are: fault for the collision; medical treatment; time off work.

INSTRUCTIONS:
Summarize where the case stands in plain English at an eighth-grade reading level:
1. Explain what has happened so far and what the documents show, in ordinary words.
2. Translate every legal or procedural term you must use ("deposition" → "a formal interview under oath").
3. State plainly what is still unresolved or unknown — do not paper over uncertainty.
4. Describe what happens next procedurally, without predicting outcomes.
Keep a respectful, calm tone. No legal advice, no opinions on the merits, no settlement talk — those belong to the attorney.

TEMPLATE — format your output exactly as follows:
## Where things stand
[short paragraphs, plain language]
## What the documents show
[bullet points, one fact each, plain language]
## What we don't know yet
[bullet points]
## What happens next
[short paragraphs — process only, no predictions]
## Words you'll hear
| Term | What it means here |
|---|---|

EVIDENCE REQUIREMENTS:
For every finding, identify the source document by name and cite page:line for transcripts, timestamps for audio/video, and Bates/page for documents. Keep the citations in the working draft so the attorney can verify every statement; they can be stripped from the client copy. Never speculate, predict outcomes, or soften a fact the record states plainly. If something a client would ask about is not in the record, say "the file doesn't answer that yet."

Unless a section above specifies its own marker, write "not found in the record" wherever the provided record does not support a requested finding. 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"
  • 04Recipient / audience(optional)e.g., "claims adjuster," "client," "mediator"

Verification checklist

  1. Mixed / full case record: open each cited page:line, Bates, page, or timestamp location and confirm it supports the finding. The prompt asks: “For every finding, identify the source document by name and cite page:line for transcripts, timestamps for audio/video, and Bates/page for documents.”
  2. Re-check every item labelled “the file doesn't answer that yet” or “not found in the record” against the full source; these labels flag gaps or judgment calls for a person to resolve, not proof of absence.
  3. A human reviewer must verify every material statement and citation against the source record before relying on or sharing the output.

Pro tip Read it aloud once — if a sentence doesn't survive being spoken, it isn't plain English yet.

Related verification workflow