---
title: "Prompt engineering for lawyers: techniques that improve legal drafts"
url: https://notionforlawyers.com/library/guide-prompt-engineering
updated: 2026-10-17
author: Raghav Handa
---

# Prompt engineering for lawyers: techniques that improve legal drafts

Prompt engineering for lawyers means designing instructions that make an AI assistant's output more consistent and easier to check. Useful techniques include giving examples, asking for stepwise structure, requesting a critique, constraining the output format and testing prompts on dummy cases. None of them replaces verification.

## Key takeaways

- Show an example of the output you want; it often beats a long description.
- Ask for structure that makes checking easy: tables, quoted sources, flagged assumptions.
- Test prompts on invented cases and keep a log of versions.
- Technique reduces errors but cannot remove them.

## Seven techniques

General information, not legal advice. Check your own bar or regulator's guidance and your client engagement terms before putting any client information into an AI tool.

1. Give an example: Paste one invented example of a good output and say 'follow this format'.
2. Ask for stages: 'First list the issues, then list facts needed, then suggest next steps.' Stages make errors visible.
3. Constrain the output: 'Return a table with these exact columns.' Predictable shapes are easier to paste into Notion.
4. Require sources from your text: 'Quote the sentence you relied on.' You can then check against your own material.
5. Add a critique pass: 'Now review your answer as a sceptical senior lawyer and list weaknesses.'
6. Set refusal rules: 'If the text does not say, answer "not stated" rather than guessing.'
7. Test and version: Run the prompt on three invented cases and record changes.


## A worked example

Goal: extract key dates from a non-confidential agreement. Prompt: 'You are a careful paralegal. From the text below, extract every date, deadline or time period. Return a table with Item, Date or period, Exact quote, Section. If an item is ambiguous, write "unclear". Do not calculate dates. Text: [text].'

Why it works: it gives a role, a precise task, a fixed table, a quote column for checking, a rule for uncertainty and a ban on calculation, where assistants often err.


## Testing prompts

| Test | What you learn |
| --- | --- |
| Run on an easy invented case | Whether the basic structure works |
| Run on a tricky case with an exception | Whether it misses edge cases |
| Run twice | How consistent the output is |
| Run in another assistant | Whether the prompt depends on one model |

Store tested prompts with a version and test date in a Notion database so your team reuses what works.


## Limits of technique

A beautifully engineered prompt can still produce a wrong answer. The assistant has no responsibility; you do. Keep human review, keep data anonymised, and avoid using AI for steps where one error is costly, such as limitation periods.

- How to write prompts: https://notionforlawyers.com/library/guide-ai-prompts
- Prompt library: https://notionforlawyers.com/ai/prompts
- AI workflows: https://notionforlawyers.com/ai/workflows


## FAQ

### Is prompt engineering a real skill for lawyers?

It is mostly clear writing and good instructions, which lawyers already practise. The new part is testing.

### Do I need special tools?

No. A chat assistant and a place to store prompts are enough.

### Do these techniques work for every model?

Generally, but results vary. Test in the assistant you use.

### Can prompting prevent fabricated citations?

It can reduce them by asking for no citations, but the safest approach is to verify everything independently.
