Build a Motion or Opposition Brief From the Record
Go from pleadings, declarations, transcripts and exhibits to a pin-cited record map, an argument outline that anticipates the other side, and draft brief sections with authority placeholders that are filled only after verification.
When to use this
Use this when you are moving for or opposing a motion that turns on the record: summary judgment, a motion to compel, a motion in limine, a suppression motion, or an opposition to any of them. Claude does the record work (finding every relevant fact and pinning it to a source) and the structural work (point headings, counterarguments, a first-draft statement of facts), while legal authority comes only from research you verify yourself.
Most of the time on a record-heavy motion goes into the record, not the law. You need every fact that supports each element, a pin cite for each one, and an honest list of what the record does not show. Then the brief has to be organized so the judge can follow the argument and check every factual assertion against the exhibits.
Claude is well suited to the record work if you hold it to one rule: no fact without a pin cite to a document you pasted. This workflow builds the record map first, then an argument outline with record cites under each point, then draft sections. Legal argument is drafted with [AUTHORITY NEEDED] placeholders instead of case names, because Claude must not supply citations from memory. Courts have sanctioned lawyers for filing briefs with citations that did not exist, and some courts now require disclosure or certification of AI use.
Authority enters the brief only through a separate gate: the Legal Research and Cite-Check workflow, where every case and statute is pulled from a research database, read and verified before a placeholder is filled. The final brief, including every record cite and every authority, is the responsible attorney's work.
The Workflow
Frame the motion and load the record
Tell Claude which side you are on, the motion, the relief sought, the standard (as you have researched it), and the dates. Paste the record excerpts in labeled document tags using the same exhibit labels you will use in the brief.
PromptI represent [PARTY], the [MOVING / OPPOSING] party, on a [MOTION TYPE] in [CASE, COURT]. The relief sought is [RELIEF]. The standard, as I have researched it, is: [STATE THE STANDARD IN YOUR OWN WORDS, citing APPLICABLE RULE]. The filing deadline is [DATE] and the hearing is [DATE]. The elements or issues the motion turns on are: 1. [ELEMENT OR ISSUE] 2. [ELEMENT OR ISSUE] 3. [ADD AS NEEDED] Record excerpts follow. Use these labels in every cite. <document title="Ex. A: [DESCRIPTION]"> [PASTE] </document> <document title="[WITNESS] Dep. (page:line numbering intact)"> [PASTE] </document> <document title="[DECLARANT] Decl. (paragraph numbers intact)"> [PASTE] </document> <document title="Complaint / Answer"> [PASTE RELEVANT PARAGRAPHS] </document> List each document with its label, a one-line description and its cite format (e.g., Ex. A at 4; Smith Dep. 12:3–15; Jones Decl. ¶ 7). Flag anything that looks incomplete. Do not analyze yet.
What you get: An inventory and a cite convention for each source. Fix any labels now so the record map and brief use the same ones.
Build the record map
For each element or issue, have Claude pull every relevant fact from the record with a pin cite, including facts that hurt you. The gaps list is the most important part: it shows what the argument needs that the record does not supply.
PromptFor each element or issue I listed, build a record map with these columns: Fact (one sentence) | Pin cite (using the labels above) | Quote (the exact supporting language) | Helps / hurts [OUR SIDE] | Disputed? (is there contrary evidence in what I pasted; cite it) Rules: - Every fact must have a pin cite and a quote from the pasted record. No fact without a source. - Include facts that hurt our position. List them under the element they affect. - Do not characterize testimony beyond what it says. If a witness hedged, keep the hedge. Then, under a heading "Record gaps", list for each element the facts our argument would need that the record does not establish, and what kind of evidence might supply them (a declaration, a document, further testimony).
What you get: A pin-cited fact table organized by element, with adverse facts and a gaps list. Gaps either change the argument or become a to-do list (a supplemental declaration, an exhibit you forgot to paste).
Outline the argument and stress-test it
Build point headings and sub-arguments with record cites under each, then have Claude argue the other side. This is the argument-strengthener approach applied to the record you mapped.
PromptUsing the record map, draft an argument outline for our [MOTION / OPPOSITION]. Format: I. [Point heading as a complete sentence stating the conclusion] A. [Sub-argument] - Supporting fact, with pin cite - [AUTHORITY NEEDED: describe the legal proposition this point requires] Then add a section "Opposing arguments" listing the strongest arguments the other side will make on each point, the record facts they will cite (with pin cites), and a suggested response grounded in the record. Rank the opposing arguments by how much damage they could do. Rules: do not name any case, statute or rule from memory. Describe each needed legal proposition in an [AUTHORITY NEEDED] placeholder so I can research it. Flag any point where the record support is thin.What you get: An outline you can rearrange, with a research list built in: every [AUTHORITY NEEDED] placeholder is a proposition to research. The opposing-arguments section often shows a point is better dropped than defended.
Draft the statement of facts and argument sections
Have Claude draft the statement of facts using only record-cited facts, and argument sections that keep the authority placeholders in place. Give it a page or word budget so the draft is close to the court's limit.
PromptDraft (1) the statement of facts and (2) argument sections I.A through [LAST SECTION] from the outline. Statement of facts: use only facts from the record map, each sentence followed by its pin cite in the form I gave you. Present facts accurately, including material adverse facts that the other side will raise, framed fairly. Do not argue in the facts section. Argument: follow the outline. Keep every [AUTHORITY NEEDED: ...] placeholder in the text exactly where the authority will go. Do not insert any case name, citation, quotation from a case, or statutory language unless it appears in a document I pasted. Target length: about [N] words total, consistent with a [PAGE / WORD] limit of [LIMIT] under [APPLICABLE RULE]. Write in [OUR HOUSE STYLE: e.g., short paragraphs, conclusion-first headings]. After the draft, list every factual sentence you were unsure how to cite.
What you get: A full draft with record cites throughout and visible authority placeholders. Read the statement of facts against the record map; it should contain nothing the map does not.
Run the verified-authority gate
Research each [AUTHORITY NEEDED] proposition in a legal research database, read the authority, confirm it is still good law, and only then replace the placeholder. Use the Legal Research and Cite-Check workflow for this step. Claude can help you organize the research and check that a quoted passage actually appears in an opinion you paste, but it is not the source of the citation.
What you get: Every placeholder replaced with an authority you have read and verified, or the point revised or dropped. No citation enters the brief from Claude's memory.
Run the local-rules and filing checklist
Have Claude build a checklist of format and filing requirements as placeholders, then confirm each against the court's current local rules, the judge's standing orders and any AI-disclosure or certification requirement that applies.
PromptBuild a pre-filing checklist for this [MOTION / OPPOSITION] in [COURT], before Judge [NAME]. List each item as a question with a blank for the answer and the source I should check, using [APPLICABLE RULE] or [STANDING ORDER] as placeholders. Do not state what any rule requires; I will confirm each item. Cover: page or word limits and whether the tables count; caption and formatting (font, spacing, margins); table of contents and table of authorities; separate statement of facts or statement of undisputed facts requirements; meet-and-confer certification; proposed order; exhibit and declaration formatting; courtesy copies; hearing and notice requirements; any certification or disclosure of AI use; and the filing and service deadline. Then check the current draft against the items you can assess from the text (length, headings, presence of a table of contents) and report what is missing.
What you get: A checklist with sources to confirm. Judges' standing orders change; check the current version on the court's website before filing.
Example Output
Illustrative example — names, facts, and figures are fictional.
RECORD MAP EXCERPT (ILLUSTRATIVE / FICTIONAL)
Matter: Reyes v. Calloway Freight Lines. We represent the defendant, opposing plaintiff's motion for partial summary judgment on liability.
ELEMENT 2: Defendant knew of the brake defect before the trip.
Fact | Pin cite | Quote | Helps / hurts | Disputed?
1. The pre-trip inspection form was marked "OK" for brakes. | Ex. C at 1 | "Brakes: OK (initialed T.M.)" | Helps | Yes: Pratt Dep. 33:4–9 ("the form gets initialed before anyone looks")
2. A mechanic emailed about "soft brakes" on the unit two days earlier. | Ex. F at 2 | "Unit 418 brakes feel soft, need to look at it" | Hurts | No
3. The dispatcher testified she did not see that email before dispatch. | Lowe Dep. 21:12–18 | "I didn't open it until after the accident." | Helps | Partly: Ex. F at 1 (header shows it was sent to the dispatch group inbox)
RECORD GAPS (Element 2)
- No evidence of when the dispatch inbox was checked on the trip date. Possible source: a declaration from the IT administrator on read receipts or access logs.
ARGUMENT OUTLINE EXCERPT
I. A genuine dispute of material fact exists on whether Calloway knew of the defect before dispatch.
A. The only witness with dispatch authority testified she had not read the mechanic's email. (Lowe Dep. 21:12–18)
[AUTHORITY NEEDED: standard for imputing an employee's knowledge to the employer in [JURISDICTION]]
Opposing argument (ranked 1): the email went to a shared inbox, so knowledge is imputed regardless (Ex. F at 1). Suggested response: [depends on the imputation standard; research before responding].
DRAFT for attorney review. No authority has been supplied; every placeholder must be filled through verified research.Tips
- •State the standard in your own words in step 1. Claude should apply the standard you researched, not one it recalls, and writing it out forces you to confirm it early.
- •Include the adverse facts in the record map. The other side will cite them, and a statement of facts that ignores them costs credibility with the court.
- •Use the exact exhibit and transcript labels you will file with. Renaming exhibits after the draft is written is where cite errors creep in.
- •Treat every [AUTHORITY NEEDED] placeholder as a research assignment. If research does not support the proposition, revise or drop the point rather than softening the language.
- •Before filing, ask Claude to list every record cite in the final brief and check each one against the record map; then check the map items against the exhibits yourself.
A note on confidentiality
The record for a motion often includes documents designated under a protective order, sealed material, medical or financial records, and in criminal matters, discovery subject to restrictions on dissemination. Confirm the protective order or any discovery restrictions permit the use you intend, use a Claude plan whose terms exclude your inputs from model training (such as Team or Enterprise), and keep sealed material out of any draft that will be filed publicly. The brief Claude helps draft is a draft for attorney review: every record cite must be checked against the exhibits, and every authority must be researched and verified independently before filing.
Frequently Asked Questions
Why does this workflow keep case names out of Claude's draft?
Because a language model can produce citations that look real and are not, or attach a real case to a proposition it does not support. Keeping authority as [AUTHORITY NEEDED] placeholders separates the record work Claude does well from legal authority, which must come from a research database and be read and verified by the attorney before it enters the brief.
Can I use this for an opposition as well as a motion?
Yes. For an opposition, paste the moving papers as their own document and ask Claude to map each factual assertion in them to the record, flagging assertions that are unsupported or contradicted. That map becomes the backbone of the opposition and of any response to a statement of undisputed facts.
Do I need to disclose that I used Claude?
It depends on the court. Some judges and courts require disclosure or certification of generative AI use in filings, and the requirements vary. Check the local rules and the assigned judge's standing orders, which is why the filing checklist includes that item.
How long a record can Claude handle in one conversation?
A focused motion record (key pleadings, a few transcripts, a set of exhibits) usually fits. For a large record, build the record map one element at a time in separate passes, or use Projects to keep the record available across conversations, and combine the maps before outlining.
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.