Most attorneys who try AI and give up after a week share a common failure mode: they asked the AI to "write a contract" or "research this case" and got output so generic it was unusable, then concluded that AI is overhyped. The output they got was a result of the input they provided — vague instructions produce vague output. This is the problem prompt engineering solves.

Prompt engineering is not a technical skill. It is a communication skill: the discipline of giving an AI assistant enough context, specificity, and structure that it can produce output worth using. For most legal work, the techniques that matter are simple, and learning them takes an hour, not a course.

This guide covers the practical techniques and includes a starter prompt library organized by the tasks that come up most often in a solo or small-firm practice.

The core techniques

Give context before the request

AI tools have no knowledge of your practice, your client, your matter, or your typical working style unless you provide it in the prompt. A prompt that provides context produces dramatically better output than the same request without it.

Without context: "Draft a declination letter."

With context: "I am a solo family law attorney. I need to decline a potential client who came in for a consultation about a custody dispute. They are in a different jurisdiction than I practice in. Draft a short, professional declination letter that: (1) thanks them for the consultation, (2) explains I'm unable to help due to jurisdiction, (3) encourages them to seek counsel in their jurisdiction promptly, (4) does not offer an opinion on their case, and (5) does not create an attorney-client relationship. Keep it under 150 words."

The second prompt takes thirty seconds to write and produces something you can actually use.

Assign a role

Tell the AI what role to take. This is not ceremony — it shapes the vocabulary, tone, and frame of the output.

"You are drafting professional correspondence for a solo litigation attorney..."
"You are an experienced legal editor reviewing this contract clause for ambiguity..."
"You are helping a transactional attorney prepare for a closing..."

Specify the format

If you want a list, ask for a list. If you want three short paragraphs, say so. If you want headers and sub-bullets, describe that structure. An AI asked to "explain this doctrine" will produce a flowing essay; an AI asked for "a bullet-point summary under five headers, each with one clarifying example" produces something you can paste into a memo.

Set the boundaries

Tell the AI what NOT to do. This is especially important for legal work:

"Do not cite specific statutes or case law — I will fill in the authority."
"Do not give a legal opinion or characterize the strength of the claim."
"Do not use the client's name — use 'the client' throughout."
"Do not quote specific dollar figures — leave those in brackets."

Explicit prohibitions prevent the most common types of AI output that require rework.

Iterate, do not start over

A bad first draft is not a failure; it is a starting point. Rather than reprompting from scratch, work with the AI iteratively:

"The tone is too formal — rewrite it for a client who prefers plain English."
"The third paragraph repeats the second — cut the repetition and tighten it."
"Add a section about the next steps the client needs to take before our next call."

Iteration gets to a usable draft faster than successive attempts from scratch.

Prompt library by task

These are starter templates. Adapt the specifics to your practice — the role, the output requirements, and the prohibitions should match how you actually work.

Correspondence

Status update to a client:

"Draft a professional status update email from an attorney to a client. The matter is [brief description, no names]. Developments this week: [what happened]. Next steps: [what comes next]. What the client needs to do (if anything): [none / specific action]. Timeline for next update: [when]. Tone: direct and professional, no jargon. Length: 3-4 short paragraphs. Leave dates in brackets."

Declination letter:

"Draft a professional declination letter from a [practice area] attorney declining representation of a prospective client. Reason for declining: [brief reason — jurisdiction, conflict, outside practice area, capacity]. The letter must: thank them for the inquiry, decline clearly without equivocation, encourage them to seek other counsel promptly, not offer any legal opinion on their matter, and not create an attorney-client relationship. Under 150 words."

Settlement summary for a client:

"Draft a plain-English summary of a settlement offer for a client who is not a lawyer. Key terms: [list the material terms]. What the client must decide: whether to accept or reject. Next step if they accept: [procedure]. Next step if they reject: [procedure]. Tone: neutral — do not advocate for or against acceptance. Do not include a recommendation. Under 250 words. Leave all specific amounts in brackets."

Research and analysis drafting

Issue spotting on a set of facts:

"I am going to describe a factual situation. Identify the legal issues it raises, organized by category. Do not cite specific cases or statutes — just identify the issues and the key questions under each. Do not characterize the strength of any claim. Factual situation: [facts, anonymized]."

Explaining a legal concept to a client:

"Explain [legal concept] in plain English to a client who has no legal background. Cover: what it means, why it matters for their situation, and the two or three things they most need to understand about it. Do not give an opinion on how it applies to their specific case. Under 200 words."

Drafting a memo structure:

"Create an outline for a legal memo analyzing [legal issue] under [jurisdiction] law. The memo is for [internal use / client delivery]. Include the standard sections: Introduction, Issue Presented, Short Answer, Facts, Analysis (with sub-headings for each legal element), Conclusion. Under each section heading, write 2-3 bullet points describing what that section should cover for this specific issue. Leave the substance for me to write."

Document drafting

Contract clause from scratch:

"Draft a [clause type — confidentiality, limitation of liability, assignment, etc.] for a [type of agreement] between a [party A description] and a [party B description]. Governing law is [jurisdiction]. The clause should favor [party A / party B / be balanced]. Include a [carve-out for / exception for] [specific situation if applicable]. Keep it under [X] words. Do not add recitals or other sections — just the clause."

Reviewing a clause for issues:

"Review the following contract clause and identify: (1) any ambiguous terms, (2) any one-sided provisions, (3) any missing protections a [buyer / seller / service provider / client] would typically want, and (4) any drafting improvements for clarity. Do not rewrite the clause — just identify the issues as a list. Clause: [paste clause]."

Drafting an engagement letter section:

"Draft the [scope of representation / fee arrangement / termination / client obligations] section of an attorney-client engagement letter for a [practice area] attorney. Keep it clear and plain-English — this document is client-facing. Do not include professional-responsibility boilerplate — I will add that separately."

Administrative and practice management

Agenda for a client call:

"Draft a structured agenda for a [X]-minute client call in a [practice area] matter. The call covers: [topics]. Format: headers with time allocations and 2-3 bullet points under each. Leave specific item details in brackets."

Follow-up task list from a meeting summary:

"Based on the following meeting notes, create a clear action item list with who is responsible for each item (attorney, client, or third party) and a blank for due date. Meeting notes: [paste notes, anonymized]."

The confidentiality guardrail applied to prompting

Every prompt that includes case-specific information triggers the confidentiality analysis. For prompts that use client names, matter details, or identifying information:

Consumer-tier tools (free ChatGPT, Claude.ai free) typically train on inputs — do not use these for client-specific prompts
Business or enterprise tiers (ChatGPT Team, Claude Pro, Gemini Workspace) generally offer no-training terms and DPAs — verify the current terms before relying on them
When in doubt, anonymize: replace names with roles ("the client," "the other party"), replace specific amounts with placeholders, remove identifying case details. The quality of the output does not depend on the AI knowing who the client is

This is covered fully in client confidentiality and AI tools and is the first chapter of ABA Formal Opinion 512.

Building your own prompt library

The prompts above are starting points. The ones that work best for you will be specific to your practice area, your clients, and your writing style. As you iterate:

Save prompts that produced a good result — in a doc, a note, wherever you keep things you use regularly
Note what context made them work ("this works best when I describe the matter type upfront")
Update them as you learn what produces better output from your preferred tools

A dozen well-refined prompts for the tasks you do every week is more useful than a library of fifty generic ones. Start small and build.

For the tool decisions that underlie which assistant to use these prompts with, see the best AI tools for lawyers. For the practical workflow on email drafting specifically, see using AI for client communication drafting.

Prompt Engineering for Lawyers: How to Get Better Results from Legal AI