Summarize a Brief, Transcript, or Long Document for Yourself
Turn a long brief, transcript, regulation, or contract into a structured, source-cited working summary you can verify and use.
When to use this
You have a 40-page opposing brief, a 200-page deposition transcript, a dense new regulation, or a long expert report to get through, and limited time. This workflow digests it into a summary tuned to the document type so you can grasp the shape of it fast, then drill into the parts your matter turns on. The output is a working aid for you, the lawyer — not a client-facing explainer and not a substitute for reading the passages that matter.
Long documents are the tax of litigation and regulatory practice. Opposing counsel files a brief, a deposition runs hundreds of pages, an agency drops a rule that reshapes your client's obligations — and you need the gist today, not next week. Reading every word cover-to-cover is often the right call eventually, but you frequently need a fast, accurate map first so you know where to spend your close-reading time.
This workflow uses plain Claude to produce that map. You paste the document, tell Claude exactly what it is and what you need from it, and get back a summary structured for the document type: arguments-and-authorities for a brief, admissions-and-cites for a transcript, obligations-and-deadlines for a regulation. Then you drill in — surfacing the strongest and weakest points, asking follow-ups, and flagging anything surprising.
This is an internal tool for you, in lawyer's terms — distinct from a client-facing plain-English explainer, which strips out the analysis you actually want here. Treat every summary as a working aid: demand a source locator for each point so verification is a quick spot-check, confirm the key quotes and cites against the document, and read the passages your case turns on yourself. The summary points you to them faster; it does not read them for you, and you remain responsible for the work.
The Workflow
Paste the document and say what it is and what you need
Open one Claude conversation and give it the full document plus context: what kind of document it is, the matter it relates to, your role, and what you're trying to get out of it. The more specific you are about your goal, the more useful the summary — 'help me oppose this' produces a different summary than 'tell me what deadlines my client now faces.' Paste the whole document; do not truncate or summarize it yourself first.
PromptI'm a lawyer and this is for my own internal use, in lawyer's terms — not a client-facing explanation. I'm pasting a [DOCUMENT TYPE, e.g., opposing motion for summary judgment / deposition transcript of the plaintiff / newly finalized regulation / expert report]. It relates to [BRIEF MATTER DESCRIPTION], and I represent [YOUR PARTY/ROLE]. What I need from it: [YOUR GOAL, e.g., understand and prepare to oppose their arguments / find admissions I can use / understand what my client must now do and by when]. Before you summarize, ask me up to 3 clarifying questions if anything about the document or my goal is ambiguous. Otherwise, confirm what you're looking at and wait for my next message. Here is the document: [PASTE FULL DOCUMENT]
What you get: Claude confirms the document type and your goal, and either asks a couple of targeted clarifying questions or signals it's ready to produce the structured summary in the next step.
Get a structured summary tuned to the document type
Ask for a summary whose structure matches what this kind of document is for. Pick the framing that fits: for an opposing brief, you want each argument paired with the authority it leans on and a first cut at your response; for a transcript, key admissions and topics with page:line cites; for a regulation, obligations, deadlines, and who is affected. Insist on a source locator for every point so you can verify quickly.
PromptNow summarize it for my working use. Match the structure to the document type: - If it's a BRIEF or MOTION: list each argument they make. For each, give (a) a one-line statement of the argument, (b) the key authority or evidence they cite for it, and (c) a brief note on how I might respond or where it looks weak. - If it's a TRANSCRIPT: list the key admissions and concessions, the main topics covered, and any answers that help or hurt my side — each with a page:line cite. - If it's a REGULATION or STATUTE: list the obligations it imposes, the deadlines, who is affected, and what changed from prior law if discernible. - If it's a CONTRACT or REPORT: list the key terms/findings, the obligations or conclusions, and anything unusual or one-sided. For EVERY point, include a source locator (page, section, or page:line) pointing to where in the document it comes from, so I can verify it fast. If something isn't actually stated in the document, say so rather than inferring. Keep it tight and in lawyer's terms.
What you get: A structured, scannable summary organized for the document type, with a page / section / page:line locator attached to each point — and explicit flags where the document is silent rather than invented detail.
Drill into what matters
The structured summary is your map; now dig into the terrain that matters for your matter. Ask follow-ups in the same conversation: pull the strongest and weakest points, expand a thin section, list anything that surprised Claude or cuts against the obvious read. This is where the real value is — you're using the summary to direct your attention, not to replace your judgment.
PromptGood. Now help me dig in, still citing a source locator for each point: 1. What are the 3 strongest points in this document from [the other side's / the author's] perspective, and why? 2. What are the 3 weakest or most vulnerable points — places I can push, distinguish, or attack? 3. Is there anything in here that's surprising, internally inconsistent, or that cuts against the document's apparent thrust? 4. [ADD YOUR OWN: e.g., "Pull every statement the deponent made about the August meeting, with page:line" / "Which of their cited cases are most distinguishable on our facts?"] If the document doesn't support an answer, tell me that instead of guessing.
What you get: A focused analysis naming the strongest and weakest points with reasons, surfacing surprises or inconsistencies, and answering your targeted follow-ups — each tied to a locator you can check.
Verify the key points, quotes, and cites against the source
Treat the summary as a draft to confirm, not a finding to rely on. Use the locators to spot-check: open the document to the cited page / section / page:line for each point you'll actually use, confirm any quoted language is accurate, and confirm that authorities are characterized correctly. For anything your matter turns on, read the full passage yourself — the summary gets you there faster but you own the analysis. This step has no prompt; it's you and the source document.
What you get: A short list of points, quotes, and cites you have personally confirmed against the document — and a clear sense of which passages you still need to read in full before you rely on them.
Example Output
Illustrative example — names, facts, and figures are fictional.
STRUCTURED SUMMARY — Opposing MSJ (illustrative, fictional) Document: Defendant's Motion for Summary Judgment, 28 pp. Matter: Nguyen v. Brightline Logistics (wrongful termination). We represent Plaintiff. ARGUMENT 1 — No protected activity (pp. 8–12) - Their claim: Plaintiff's internal email was a personal grievance, not a protected complaint about illegal conduct. - Authority: Cites Harlow v. Cantor Freight, 211 Cal.App.4th 55 (p. 9); relies on the email text at Ex. C. - Possible response: Harlow is distinguishable — the Harlow plaintiff never referenced a statute; ours cites wage law expressly (verify email language, Ex. C). ARGUMENT 2 — No causal link (pp. 13–19) - Their claim: 7-month gap between complaint and termination defeats causation. - Authority: Temporal-proximity line of cases (pp. 14–15); termination memo at Ex. F. - Possible response: Intervening discipline pattern may bridge the gap; check the three write-ups dated after the complaint (pp. 16–17). ARGUMENT 3 — Legitimate business reason (pp. 20–26) - Their claim: Reduction-in-force eliminated the role for budget reasons. - Authority: CFO declaration (¶¶ 4–9, p. 22). - Possible response: Role was re-posted 6 weeks later per their own Ex. H (p. 25) — strongest weakness in their motion. WEAKEST POINT: The re-posting at Ex. H (p. 25) undercuts the RIF rationale. SURPRISE: CFO declaration (p. 22) concedes Plaintiff "met expectations" in the last review — cuts against the performance framing. [Verify all page/exhibit cites and the Harlow holding against the filing before use.]
Tips
- •Tell Claude your goal, not just the document. 'Summarize this' yields a generic digest; 'find admissions on causation' or 'tell me what my client must do by when' produces a summary you can actually act on.
- •Always demand a source locator (page / section / page:line) for every point. It turns verification from a re-read into a 30-second spot-check and makes hallucinated detail obvious.
- •Keep it to one conversation. Pasting the document once and asking follow-ups in the same thread keeps Claude anchored to the source and lets you drill progressively without re-establishing context.
- •This is your internal map, not a client deliverable and not a brief. Read the passages your matter turns on yourself — the summary tells you where they are; it doesn't relieve you of reading them.
A note on confidentiality
Use Claude Team or Enterprise, where your inputs are not used to train models, and keep client documents and confidential filings off consumer tiers. Confirm this use is consistent with your duty of confidentiality under ABA Model Rule 1.6 and the guidance in ABA Formal Opinion 512 on generative AI.
Prompts used in this workflow
Get New Workflows Like This Every Week
Join the free Claude for Lawyers newsletter — practical workflows, prompts, and guides for everyday practice.