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 long opposing brief, a lengthy deposition transcript, a dense new regulation, or an expert report to get through, and limited time. This workflow digests it into a summary tuned to the document type so you can grasp its shape quickly, 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 a constant in litigation, transactional, and regulatory practice. Opposing counsel files a brief, a deposition runs hundreds of pages, an agency issues a rule that reshapes your client's obligations, and you need the gist today. Reading every word is often the right call eventually, but you frequently need an 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 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, written in lawyer's terms, and distinct from a client-facing plain-English explainer, which strips out the analysis you want here. Treat every summary as a working aid: require 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 in <document> tags, followed by the 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 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.
Prompt<document type="[DOCUMENT TYPE, e.g., opposing motion for summary judgment / deposition transcript of [WITNESS] / newly finalized regulation / expert report]" date="[DATE]"> [PASTE FULL DOCUMENT] </document> I'm a lawyer and this is for my own internal use, in lawyer's terms, not a client-facing explanation. The document above 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 (type, length, and any pages or exhibits that appear to be missing) and wait for my next message.
What you get: Claude confirms the document type and your goal, notes anything that looks missing, and either asks a couple of targeted clarifying questions or signals it's ready to produce the structured summary.
Get a structured summary tuned to the document type
Ask for a summary whose structure matches what this kind of document is for. 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. Require 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, named exactly as it appears in the document, 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 the document says so. - If it's a CONTRACT or REPORT: list the key terms or findings, the obligations or conclusions, and anything unusual or one-sided. For EVERY point, include a source locator (page, section, or page:line). Quote the exact language for any point I'm likely to rely on. Do not add authorities or facts that aren't in the document, and do not characterize what a cited case holds beyond what the document itself says about it. If something isn't 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, or page:line locator on each point, quotes where it matters, 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 what 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. You're using the summary to direct your attention, not to replace your judgment.
PromptNow help me dig in, still citing a source locator and quoting the relevant language 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 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 do they rely on most heavily, and for what proposition?"] If the document doesn't support an answer, tell me that instead of guessing. If answering would require knowing what a cited case actually holds, say I need to read the case.
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, or page:line for each point you'll use, confirm any quoted language is accurate, and pull and read any authority the other side cites before you characterize it. For anything your matter turns on, read the full passage yourself. 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 and cited authorities 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: [Plaintiff A] v. [Logistics Co. B] (fictional wrongful-termination case). 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 [Case A] (fictional), [CITATION AS IN BRIEF] (p. 9); relies on the email text at Ex. C. - Possible response: The brief describes the [Case A] plaintiff as never referencing a statute (p. 9); ours cites wage law expressly (verify email language, Ex. C, and read [Case A] before relying on this distinction). ARGUMENT 2: No causal link (pp. 13–19) - Their claim: 7-month gap between complaint and termination defeats causation. - Authority: Temporal-proximity cases cited at 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), the clearest 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, which cuts against the performance framing. [Verify all page and exhibit cites against the filing, and pull and read every cited case, 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 act on.
- •Always require a source locator (page, section, or page:line) for every point. It turns verification into a spot-check instead of a re-read and makes invented detail obvious.
- •Never rely on Claude's characterization of a case the other side cites. The summary tells you what the brief says about the case; only reading the case tells you what it holds.
- •Keep it to one conversation. Pasting the document once and asking follow-ups in the same thread keeps Claude anchored to the source.
- •This is your internal map, not a client deliverable and not a brief. Read the passages your matter turns on yourself.
A note on confidentiality
What you summarize here varies: opposing briefs may be public filings, but deposition transcripts, expert reports, and discovery are often designated confidential under a protective order, and your own notes on the summary are work product. Check any protective order or confidentiality designation before uploading a transcript or report, and redact third-party personal information (medical details, Social Security numbers, minors' names) the summary doesn't need. Run client work on a commercial plan (Team or Enterprise) whose terms exclude your content from model training. On Pro or Max, disable model training in Privacy settings; a commercial plan's contract terms are the stronger answer for client work. Confirm this use is consistent with ABA Model Rule 1.6 and ABA Formal Opinion 512. Every output is a draft for attorney review: verify every quote, locator, and citation against the source.
Frequently Asked Questions
Is this the same as having Claude write a plain-English summary for my client?
No, it's deliberately the opposite. A client-facing explainer strips out the legal analysis, citations, and tactical notes that make this output useful to you. This workflow keeps all of that and writes in lawyer's terms for your own internal use. If you also need a client version, do that as a separate task with separate instructions.
Can I trust the page:line and page citations Claude gives me?
Treat them as pointers to verify, not facts to rely on. Claude can occasionally misattribute a locator or paraphrase a quote imprecisely. That's why this workflow requires a locator for every point: it makes spot-checking fast. Confirm any cite, quote, or characterization against the source before you put it in a filing or rely on it in argument.
How long a document can I paste into one conversation?
Claude handles long documents; full briefs, lengthy transcripts, and dense regulations typically fit. If a document is too long to paste at once, work in logical sections (for example, by deposition topic or by part of a brief) rather than asking Claude to summarize a truncated version, and never silently cut the document down. If you split it, tell Claude how so it keeps the context straight.
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.