This page covers ai prompts for lawyers and legal teams who need consistent, repeatable output from tools like ChatGPT, Claude, Copilot, and Gemini. It is built for legal team leads and in-house counsel who want their staff working from the same tested prompts, not rewriting from scratch every time. The pack covers contract review, client communication, legal research, internal drafting, and compliance tasks.
What is in this pack
Twenty-five prompts organized into five categories: contract and document review, client-facing communication, legal research, internal drafting, and compliance and risk. Each prompt is written to work across the major AI assistants without modification, though the section on adapting for your team covers the adjustments worth making for your jurisdiction or practice area.
The prompts assume you are working with a general-purpose AI, not a specialized legal research platform. That matters because the ceiling is lower for citation accuracy and case law. Where that limitation is relevant, the prompts flag it directly.
If you manage a team, the final section explains how to save this pack as a shared folder so every member pulls from the same source.
The prompts, by category
These prompts are grouped by the kind of work they support. They are written for general use across ChatGPT, Claude, Copilot, and Gemini. Paste them as written, fill in the bracketed variables, and adjust the tone or jurisdiction to match your practice.
One honest caveat before you start: AI models are unreliable for jurisdiction-specific legal citations. They will hallucinate case names and statutory references with complete confidence. Use these prompts for drafting, summarizing, and structuring work. Have a qualified lawyer verify any output that will leave your office.
Contract Review and Analysis
Draft a plain-English summary of a contract
When to use it: Before a client call when the client is not legally trained. What to change first: The party names and the key obligations you want highlighted.
Variables: [CONTRACT TEXT], [PARTY NAME], [CONTRACT TYPE]
You are a senior lawyer reviewing a [CONTRACT TYPE] for [PARTY NAME].
Summarize the following contract in plain English. Structure your summary as:
1. What each party must do
2. Key dates and deadlines
3. Payment terms
4. Termination rights
5. The three clauses most likely to cause a dispute
Flag any clause that is unusual or potentially unfavorable to [PARTY NAME]. Keep the summary under 400 words.
CONTRACT TEXT:
[CONTRACT TEXT][NEEDS REAL OUTPUT] What to notice: Whether the model correctly identifies the termination clause and flags one-sided indemnity language.
Identify missing standard clauses
When to use it: When reviewing a contract drafted by the other side. What to change first: The contract type, since missing clauses differ significantly between an NDA and a service agreement.
Variables: [CONTRACT TEXT], [CONTRACT TYPE], [GOVERNING LAW JURISDICTION]
Review the following [CONTRACT TYPE] governed by [GOVERNING LAW JURISDICTION] law.
List any standard clauses that are absent or materially incomplete. For each gap, explain in one sentence why it matters and suggest a brief placeholder clause.
CONTRACT TEXT:
[CONTRACT TEXT]Extract all obligations and deadlines into a table
When to use it: At the start of a transaction to build a compliance checklist. What to change first: Ask it to sort by deadline date if the contract is long.
Variables: [CONTRACT TEXT], [PARTY NAME]
Read the following contract. Extract every obligation, deadline, and condition precedent that applies to [PARTY NAME].
Present the results as a table with four columns:
| Clause | Obligation or Deadline | Due Date or Trigger | Consequence of Breach |
If a due date is not specified, write "not stated".
CONTRACT TEXT:
[CONTRACT TEXT][NEEDS REAL OUTPUT] What to notice: Whether the model catches implied obligations, not just those with explicit deadline language.
Legal Research and Memos
Draft a research memo structure
When to use it: When a partner needs a memo quickly and the associate needs a reliable scaffold. What to change first: The legal question and jurisdiction.
Variables: [LEGAL QUESTION], [JURISDICTION], [CLIENT CONTEXT]
Draft the structure and section headings for a legal research memo on the following question:
Legal question: [LEGAL QUESTION]
Jurisdiction: [JURISDICTION]
Context: [CLIENT CONTEXT]
For each section, write two to three sentences explaining what it should cover and what sources to consult. Do not invent case citations. Flag any area where the law is genuinely unsettled.Summarize a judgment in plain English
When to use it: Before briefing a client or preparing for a hearing. What to change first: Ask for a different length if this is for a client letter versus an internal note.
Variables: [JUDGMENT TEXT], [AUDIENCE]
Summarize the following judgment for [AUDIENCE].
Cover: the facts, the legal question, the court's reasoning, and the outcome. Then add one paragraph on practical implications for someone in a similar position.
Keep the summary under 300 words. Do not invent citations or add case law not present in the text.
JUDGMENT TEXT:
[JUDGMENT TEXT]Compare two legal positions on a question
When to use it: When preparing for a negotiation or advising on litigation risk. What to change first: The strength weighting if one position is clearly stronger.
Variables: [LEGAL QUESTION], [POSITION A], [POSITION B], [JURISDICTION]
Compare the following two legal positions on [LEGAL QUESTION] under [JURISDICTION] law.
Position A: [POSITION A]
Position B: [POSITION B]
For each position: state the strongest argument, the weakest point, and likely counterarguments. Conclude with a short paragraph on which position you assess as stronger, and why. Flag where you are uncertain.Client Communications
Write a client update email
When to use it: After a hearing, filing, or significant development. What to change first: The tone (adjust for a sophisticated commercial client versus an individual).
Variables: [MATTER NAME], [DEVELOPMENT], [NEXT STEPS], [CLIENT NAME]
Write a brief client update email for [CLIENT NAME] about [MATTER NAME].
Development: [DEVELOPMENT]
Next steps: [NEXT STEPS]
The email should be professional but plain. Avoid legal jargon. Keep it under 200 words. End with a clear call to action.Draft a client-facing FAQ for a standard process
When to use it: For conveyancing, employment matters, or any process clients ask about repeatedly. What to change first: The process name and the five questions your clients actually ask.
Variables: [PROCESS NAME], [JURISDICTION], [TYPICAL CLIENT PROFILE]
Draft a FAQ document explaining [PROCESS NAME] to [TYPICAL CLIENT PROFILE] in [JURISDICTION].
Include eight questions. Write each answer in plain English, no longer than 100 words. Avoid Latin phrases. Flag any question where the answer varies significantly by individual circumstance.[NEEDS REAL OUTPUT] What to notice: Whether the model stays genuinely plain or drifts back into legal register by question four or five.
Turn a client intake form into a matter summary
When to use it: At the start of a new matter, before the first substantive call. What to change first: Add any firm-specific fields from your own intake form.
Variables: [INTAKE FORM RESPONSES]
Read the following client intake responses. Produce a one-page matter summary covering:
- Client and matter overview
- Key facts
- Apparent legal issues
- Immediate next steps
- Questions to clarify on the first call
Be concise. Do not invent facts not present in the intake form.
INTAKE FORM RESPONSES:
[INTAKE FORM RESPONSES]Document Drafting
Draft a non-disclosure agreement
When to use it: For a first-draft NDA in a commercial context. Always have a qualified lawyer review before signing. What to change first: The governing law and whether it is mutual or one-way.
Variables: [DISCLOSING PARTY], [RECEIVING PARTY], [PURPOSE], [GOVERNING LAW], [DURATION]
Draft a standard non-disclosure agreement between [DISCLOSING PARTY] and [RECEIVING PARTY].
Purpose of disclosure: [PURPOSE]
Governing law: [GOVERNING LAW]
Duration of confidentiality obligation: [DURATION]
Include: definition of confidential information, exclusions, permitted disclosures, return or destruction of information, and dispute resolution. Flag any clause where standard practice varies significantly by jurisdiction.Draft a cease and desist letter
When to use it: As a first draft only. Tone and legal basis need attorney review. What to change first: The specific conduct and the remedy being requested.
Variables: [SENDER], [RECIPIENT], [CONDUCT COMPLAINED OF], [LEGAL BASIS], [REMEDY REQUESTED], [DEADLINE]
Draft a cease and desist letter from [SENDER] to [RECIPIENT].
Conduct: [CONDUCT COMPLAINED OF]
Legal basis: [LEGAL BASIS]
Remedy: [REMEDY REQUESTED]
Response deadline: [DEADLINE]
The tone should be firm and professional. State the consequences of non-compliance clearly. Keep it under 400 words.Draft standard terms and conditions for a service
When to use it: For a first draft when a client is launching a new service or product. What to change first: The service description and the governing law jurisdiction.
Variables: [SERVICE DESCRIPTION], [BUSINESS NAME], [GOVERNING LAW], [KEY RISKS]
Draft standard terms and conditions for [BUSINESS NAME] offering [SERVICE DESCRIPTION] under [GOVERNING LAW] law.
Pay particular attention to: limitation of liability, intellectual property ownership, payment terms, termination, and [KEY RISKS].
Flag any section where legal requirements differ materially between jurisdictions or where a specialist solicitor should review before publication.[NEEDS REAL OUTPUT] What to notice: Whether the model includes a reasonable limitation of liability clause or omits it, which is a common gap in AI-drafted T&Cs.
Regulatory and Compliance
Summarize a regulatory update for a non-lawyer audience
When to use it: When a compliance or operations team needs to act on a regulatory change. What to change first: The audience description, which changes how much technical detail to include.
Variables: [REGULATORY UPDATE TEXT], [AUDIENCE ROLE], [AFFECTED BUSINESS AREA]
Summarize the following regulatory update for [AUDIENCE ROLE] in [AFFECTED BUSINESS AREA].
Cover: what has changed, when it takes effect, what the business must do, and what happens if it does not comply. Use plain English. Flag any area of genuine ambiguity in the regulation.
REGULATORY UPDATE TEXT:
[REGULATORY UPDATE TEXT]Draft a compliance checklist from a regulation
When to use it: When implementing a new regulatory requirement across a team. What to change first: The regulation name and the specific business context.
Variables: [REGULATION NAME], [REGULATION TEXT], [BUSINESS TYPE]
Read the following regulatory text. Produce a compliance checklist for a [BUSINESS TYPE] subject to [REGULATION NAME].
Format: a table with columns for Requirement, Action Required, Responsible Party (leave blank), and Deadline.
Do not invent requirements not present in the text. Flag obligations that are likely to need legal interpretation.
REGULATION TEXT:
[REGULATION TEXT]Identify data protection obligations in a contract
When to use it: Before signing a vendor or supplier agreement. What to change first: The data types involved, since obligations differ for health data versus contact information.
Variables: [CONTRACT TEXT], [DATA TYPES INVOLVED], [JURISDICTION]
Review the following contract and identify all data protection obligations relevant to [JURISDICTION] law, given that the data types involved are [DATA TYPES INVOLVED].
List: existing clauses that address data protection, any gaps relative to standard requirements, and specific clause language you would recommend adding.
CONTRACT TEXT:
[CONTRACT TEXT]Litigation Support
Summarize a witness statement
When to use it: When preparing for cross-examination or building a case chronology. What to change first: Ask for a different output format if you need a timeline rather than a narrative summary.
Variables: [WITNESS STATEMENT TEXT], [CASE CONTEXT]
Summarize the following witness statement in the context of [CASE CONTEXT].
Cover: key factual claims, any internal inconsistencies, claims that are likely to be disputed, and questions this statement leaves unanswered. Keep it under 300 words.
WITNESS STATEMENT TEXT:
[WITNESS STATEMENT TEXT][NEEDS REAL OUTPUT] What to notice: Whether the model flags genuine inconsistencies or only surface-level ones. Internal contradictions across paragraphs are the real test.
Draft deposition preparation questions
When to use it: Before a deposition, once you have reviewed the key documents. What to change first: The theory of the case and what you most need to establish or undermine.
Variables: [WITNESS ROLE], [CASE SUMMARY], [KEY DOCUMENTS], [THEORY OF CASE]
Draft deposition preparation questions for a [WITNESS ROLE] in the following case.
Case summary: [CASE SUMMARY]
Theory of case: [THEORY OF CASE]
Key documents to probe: [KEY DOCUMENTS]
Organize questions into: background and credibility, key factual disputes, and document authentication. Flag any area where the question is likely to draw an objection.Draft a demand letter
When to use it: As a starting point for a pre-litigation demand. Attorney review is required before sending. What to change first: The damages figure and the legal theory.
Variables: [CLAIMANT], [RESPONDENT], [FACTS], [LEGAL THEORY], [AMOUNT DEMANDED], [RESPONSE DEADLINE]
Draft a demand letter from [CLAIMANT] to [RESPONDENT].
Facts: [FACTS]
Legal theory: [LEGAL THEORY]
Amount demanded: [AMOUNT DEMANDED]
Deadline for response: [RESPONSE DEADLINE]
Tone: professional, factual, and firm. State the consequences of non-response. Avoid inflammatory language. Keep it under 500 words.Prepare a case chronology from documents
When to use it: At the start of a matter to build a shared factual record. What to change first: The date format and whether you need page references for each entry.
Variables: [DOCUMENT COLLECTION TEXT], [MATTER NAME]
Read the following documents from [MATTER NAME]. Construct a chronology of key events in table format.
Columns: Date | Event | Source Document | Significance
Where a date is unclear, note it as "approx." with your reasoning. Flag any gaps in the timeline that may indicate missing documents.
DOCUMENT COLLECTION TEXT:
[DOCUMENT COLLECTION TEXT]Real example outputs
Five prompts in this pack are marked [NEEDS REAL OUTPUT]. Once those outputs are captured from an actual model run, each entry will show the full text returned and a "what to notice" line explaining what a good response looks like and where you might push back or refine.
Until then, here is what to expect from a well-formed response to the contract summary prompt:
- The model identifies the parties, the governing law clause, and the key obligations in the first paragraph.
- It flags missing or unusual terms (for example, an unusually short cure period) in a separate section.
- It does not give legal advice. It summarizes. That distinction matters.
When outputs are added, they will come from real runs on Claude, ChatGPT, and Gemini so you can compare tone and structure across the models your team already uses.
How to adapt these for your team
The prompts above are starting points. A contract review prompt written for a generic commercial lease will need adjustment before it works reliably on your NDAs or employment agreements.
Three things are worth changing before you distribute any prompt to your team.
- Jurisdiction. Add your governing law by default. "Apply [JURISDICTION] law" prevents the model from defaulting to a generic common-law frame that may not match your practice.
- Defined terms. If your firm uses specific internal language, like "Matter" instead of "Case", substitute it in the prompt so outputs slot into your existing documents without editing.
- Tone calibration. Client-facing letters need a different register than internal memos. Keep two versions of any prompt that crosses that line.
Once you have adjusted a prompt, save it to a shared folder your whole team can access so everyone runs the same version, not twelve slightly different variants.
Save this folder to your workspace
These prompts work best when your whole team draws from the same source. If one person refines a contract-review prompt and the improvement lives only in their chat history, everyone else keeps starting from scratch.
Convergence shared folders let you store the prompts above in one place, push updates to the whole team instantly, and run the same prompt across ChatGPT, Claude, Copilot, or Gemini without reformatting anything.
A few practical tips before you start:
- Pin the highest-frequency prompts (NDA review, clause extraction) so they appear at the top of the folder.
- Add a short note to each prompt explaining what it does not check, so no one over-relies on the output.
- Review the folder every quarter. Prompts that worked well six months ago may need updating as your standard clause library or jurisdiction changes.
Frequently asked questions
Are ai prompts for lawyers safe to use with confidential client information?
No prompt tool makes confidential information safe by default. Before pasting any client details, check whether your AI platform processes inputs for model training and review your firm's data-handling policy. Many teams use placeholder names or anonymized facts during drafting, then substitute real details in a separate step.
Can these prompts replace a lawyer's review?
They cannot. Every output needs attorney review before it goes to a client or counterparty. These prompts handle first drafts and research summaries, not final legal judgment.
Do these prompts work across ChatGPT, Claude, Copilot and Gemini?
Yes. The prompts use plain language instructions that run on any major model without modification. Output quality will vary slightly by model, so test on the platform your team uses daily.
How long does it take to adapt these for a specific practice area?
Most teams need one focused session of under an hour to swap in their jurisdiction, clause preferences and common matter types.
What if a prompt produces inaccurate legal citations?
Verify every citation independently. AI models can hallucinate case names and docket numbers with high apparent confidence.