Legal professionals face the highest stakes of any corporate function when using AI. A misplaced word in a contract summary, an overlooked clause in an NDA review, or a jurisdiction-blind compliance summary can expose an organisation to significant legal and financial risk. Generic AI prompts in a Legal context are not just inefficient — they are potentially dangerous.
The three risks that make Legal prompting fundamentally different from every other corporate function are language precision, liability awareness, and jurisdictional specificity. A well-engineered Legal prompt addresses all three before Claude produces a single output.
Language precision
Legal language is deliberate. A single word — "shall" vs "may," "including" vs "including but not limited to" — can change the meaning of a clause entirely. Generic prompts produce legally imprecise output.
Liability awareness
Claude is not a qualified lawyer and cannot provide legal advice. Every Legal prompt must include explicit instructions to flag items requiring human review rather than producing output that appears definitive.
Jurisdictional specificity
Employment law, data protection, and contract law differ significantly between the UK, USA, and EU. Without jurisdiction context, Claude defaults to generic output that may not apply to your legal environment.
The fix: every Legal template in this course includes jurisdiction flags, liability disclaimers, escalation instructions, and precision constraints — the four elements that make Legal AI output genuinely useful without creating false confidence.
These five templates cover the most common Legal drafting and review tasks. Copy them directly, replace the bracketed placeholders with your specifics, and paste into Claude. Each one is built on the 4-Pillar Framework — Role, Context, Task, Format.
Act as a Legal Analyst at [Company Name] operating under [UK / US / EU] law. Summarise the following contract for a non-legal business stakeholder:
[Paste contract text or key clauses here]
Produce a structured summary with the following sections:
1. Parties and purpose (one sentence each)
2. Key obligations of each party (bullet points)
3. Payment terms and amounts
4. Term and termination rights
5. Key risk areas (flag anything unusual or potentially unfavourable to [Company Name])
Tone: plain English — no legal jargon. Maximum 400 words. Flag any clause you cannot interpret with confidence as [REQUIRES LEGAL REVIEW].
Act as a Legal Analyst reviewing an NDA on behalf of [Company Name] under [UK / US] law. Review the following NDA and produce a checklist of key findings:
[Paste NDA text here]
Check for and report on:
1. Definition of Confidential Information — is it appropriately broad or too narrow?
2. Obligations of receiving party — are they reasonable and enforceable?
3. Exceptions to confidentiality — are standard exceptions included (public domain, prior knowledge, compelled disclosure)?
4. Term of the NDA — is the duration appropriate?
5. Remedies clause — does it include injunctive relief?
6. Jurisdiction and governing law — does it match our operating jurisdiction?
Format: numbered checklist. For each item: status (OK / CONCERN / MISSING) and a one-sentence explanation. Flag items requiring a qualified lawyer's review with [ESCALATE TO LEGAL COUNSEL].
Act as a Legal Communications Specialist at [Company Name]. Rewrite the following internal policy in plain English for a non-legal employee audience:
[Paste policy text here]
Requirements:
- Replace all legal and technical terms with plain language equivalents
- Use short sentences (maximum 20 words each)
- Use active voice throughout
- Where a policy requirement is mandatory, use "you must" — not "employees are required to"
- Where something is prohibited, use "you must not" — not "it is prohibited to"
Format: keep the original section structure but rewrite all content. Add a one-sentence summary at the top of each section. Maximum 500 words total. Do not change the meaning of any clause — if you are unsure, flag with [CHECK MEANING].
Act as a Legal Risk Analyst at [Company Name] operating under [jurisdiction]. Review the following document or situation description and identify potential legal risks:
[Paste document text or describe the situation here]
Identify risks in the following categories:
1. Contractual risk (obligations, liabilities, indemnities)
2. Regulatory and compliance risk (data protection, employment law, sector-specific regulation)
3. Reputational risk (public statements, commitments, disclosures)
4. Operational risk (practical enforceability of obligations)
Format: numbered list of risks. For each risk: category, description (2 sentences maximum), likelihood (Low / Medium / High — your assessment only), and recommended action. End with a summary paragraph. Flag anything requiring immediate escalation with [URGENT: ESCALATE TO LEGAL COUNSEL].
Act as a Legal PA at [Company Name]. Draft formal meeting minutes from the following notes or transcript:
[Paste meeting notes or transcript here]
Meeting details:
- Date: [Date]
- Attendees: [Names and roles]
- Purpose: [e.g. contract negotiation / compliance review / board legal update]
Format the minutes as follows:
1. Meeting details (date, attendees, purpose)
2. Items discussed (one paragraph per agenda item — factual, no opinions)
3. Decisions made (numbered list — clear and unambiguous)
4. Action items (table: Action | Owner | Deadline)
5. Next steps
Tone: formal and precise. Do not include any content that was not in the source notes. Flag any unclear or ambiguous items with [CLARIFICATION NEEDED].
Save these templates: copy all five into a Google Doc titled "Legal Claude Prompts" and share with your Legal and Compliance team. Consistent prompting ensures consistent risk flagging standards across the entire function.
These templates are starting points. Every Legal team operates in a different jurisdiction, with different risk appetite, company size, and regulatory exposure. Here is how to adapt any template to your specific Legal environment in under two minutes.
1
Always specify your jurisdiction
Add to every Legal prompt: "Jurisdiction: [England & Wales / Scotland / New York / California / Federal US / EU — GDPR applies]." This single addition prevents Claude from producing jurisdiction-blind output. For cross-border matters, list all relevant jurisdictions: "This agreement is governed by English law but the counterparty is a US entity — flag any clauses that may be interpreted differently under US law."
2
Set your escalation threshold explicitly
Tell Claude exactly when to stop and escalate: "If any clause creates potential liability exceeding [£X / $X], flag it as [HIGH VALUE — ESCALATE]. If any clause relates to data protection, employment, or intellectual property, flag it as [SPECIALIST REVIEW NEEDED]." This prevents Claude from producing output on high-risk matters without triggering the right review process.
3
Add your company's standard positions
For contract review tasks, add: "Our standard position is: payment terms Net 30, liability cap at 12 months' fees, governing law English law, jurisdiction English courts. Flag any deviation from these positions." This turns Claude into a first-pass contract review tool that checks against your actual negotiating baseline — not a generic standard.
4
Never remove the human review step
Add to every output-facing Legal prompt: "This output is a first-pass analysis only and does not constitute legal advice. All findings must be reviewed by a qualified lawyer before any action is taken." This instruction does two things: it reminds Claude to flag uncertainty rather than guess, and it ensures the output itself carries the appropriate caveat when shared with business stakeholders.
Claude is not a lawyer. These templates are designed to help Legal professionals work faster on drafting, summarising, and reviewing — not to replace qualified legal advice. Every output produced using these templates must be reviewed by a qualified lawyer before it is relied upon, shared externally, or used to make decisions.