The design principle
AI in legal work should find and organise, never conclude. Every output must link to the source document so a professional can verify it in seconds. Systems that produce confident summaries without traceable citations are professionally unusable regardless of how good they seem.
Legal document work has genuine AI opportunity and a hard boundary. The boundary is where output stops being verifiable.
Where AI helps and where it does not
| Task | Suitability | Why |
|---|---|---|
| Locate clauses across many documents | Strong | Verifiable, high volume |
| Flag deviations from a standard template | Strong | Comparison against known text |
| Extract key dates, parties, values | Strong | Structured, checkable |
| Summarise a long document | Good, with citations | Reviewer verifies against source |
| Categorise documents for disclosure | Good, with review | Triage, not final decision |
| Draft standard clauses | Moderate | Requires professional review |
| Advise on legal position | Unsuitable | Professional judgement |
| Cite case law from memory | Unsuitable | Documented fabrication risk |
The last row deserves emphasis. Models generating plausible-looking citations that do not exist is a well-documented failure with real professional consequences. Any system touching legal authority must retrieve from a verified source and link each citation — never allow the model to produce them from its own knowledge.
What "verifiable" requires architecturally
- Retrieval from your document set only — the model answers from what was found, not from training.
- Every claim linked to a source, at paragraph or clause level rather than document level.
- Show the source text alongside the finding, so verification takes seconds not minutes.
- Explicit refusal when the documents do not support an answer.
- Confidence indication distinguishing strong matches from weak ones.
A legal AI tool is judged by how fast a professional can verify its output. If checking takes as long as doing the work, the tool has no value.
The highest-value applications
Contract review triage
Comparing incoming contracts against your standard positions, flagging deviations by clause type and severity. The lawyer reviews the flagged items rather than reading everything.
Due diligence document sorting
Categorising large document sets, extracting key terms, surfacing anomalies. Reduces the volume a human must read without deciding anything.
Clause library search
Finding how a particular provision has been drafted across past matters — semantic search over your own precedent bank, which keyword search handles poorly.
Obligation extraction
Pulling dates, deliverables, notice periods and renewal terms from executed contracts into a structured register. Verifiable, high volume, and currently manual.
Confidentiality and privilege
- Confirm vendor data terms contractually — retention, training use, processing location — before any client material is processed.
- Matter-level access control, so information barriers are respected by the retrieval layer.
- Audit logging of who accessed which documents through the system.
- Minimise what leaves your environment — send relevant passages, not whole matters.
- Deletion capability covering the index, not just source storage.
Information barriers must be enforced in retrieval, not by the model. Filter documents by the requesting user's matter access before ranking. Placing restricted material into the model's context and instructing it not to mention that content is not a control — it is a hope.
Measuring whether it works
| Metric | What it tells you |
|---|---|
| Recall on known clauses | Does it find what is there? |
| False positive rate | How much noise reviewers wade through |
| Verification time per finding | Whether the tool actually saves time |
| Citation accuracy | Do links point at the right passage? |
| Reviewer override rate | How often the flag was wrong |
Recall matters more than precision here. A missed clause is a professional risk; a false positive is a few seconds of a reviewer's time.
Deployment approach
- Start with your own precedent bank — internal, no client confidentiality exposure, immediately useful.
- Move to obligation extraction from executed contracts, which is verifiable and structured.
- Add contract review triage against your standard positions.
- Measure verification time honestly against the manual process.
- Never remove professional review from anything that leaves the firm.
Building legal technology with AI components? Tell us the review workflow. See our AI agent service, document processing, and retrieval architecture.