Cases › made things up › LR-2026-0535
Pinsent Masons reprimanded over AI hallucinations in UK court filings
Preliminary Why: Publisher not yet named · subject to change
Status: no action reported
No source states: loss or records, developer and model, agent tool, could do, deployer.
Severity moderate: test: data or systems of others touched with a bounded scope (one insolvency application); the firm met its former client's costs, including costs of finding new lawyers.
A junior solicitor at Pinsent Masons used an AI tool for legal research on a block transfer insolvency application in a High Court proceeding. The firm's letter to the court cited an insolvency rule that did not exist, and a follow-up letter, also prepared with AI, repeated the problem. The judge described the first letter as likely an AI hallucination that had not been checked, after querying it with the firm. The judge found the material had not been checked properly, and that supervisors had not adequately reviewed the work, although they were unaware AI had been used. The firm apologised, self-referred to the Solicitors Regulation Authority, and met its former client's costs. The judge said contempt proceedings would be disproportionate.
What happened
What was done
No source states an action or fix.
Risks
Read from the sources; not yet reviewed by a person.
Controls
ApplicationNot effective Human approval for high-impact actions
Did not exist User policy and training
Control failure chain
L1 · ModelProvider not namedModel provider
No source mentions a control at this layer.
Model version not linked to a model card.
L2 · HarnessHarness not namedAgent framework vendor
No source mentions a control at this layer.
L3 · ApplicationDeployer not namedDeployer
Other controls for this risk at this layer, not mentioned in the sources: Grounding and fact checks, Output filtering and redaction, People told they are dealing with AI.
L4 · Infrastructure / targetOrganisation hit
No source mentions a control at this layer.
EffectiveNot effectiveNot effective (bypassed)Did not existNot stated in sourcesNot yet checkedAttacker's ownOrder: model · harness · application · target
Controls for this risk: result in this incident
| Control | Part of the system | Result |
|---|---|---|
| Human approval for high-impact actions | L3 Application | Not effective |
| User policy and training | L3 Application | Did not exist |
| People told they are dealing with AI | L3 Application | Not stated in sources |
| Output filtering and redaction | L3 Application | Not stated in sources |
| Grounding and fact checks | L3 Application | Not stated in sources |
Evidence
- Cause a human check that existed was skipped or failed
No source states: what it reached or did, how it was caught, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, what set it off, what was done.
Show the full account: 2 items from the primary sources
What happened, in order
Not dated in the sources:
- Pinsent Masons was instructed to prepare a block transfer application for an insolvency matter.
- The firm has since self-referred to the SRA.
Show every field, with its source and grade
The AI system
What happened
Impact
Context
Notes on gaps
No dollar figures, record counts or third-party counts are stated. Resultsense claims about partner pay and other cases are excluded as unsupported by the other sources.
LR-2026-0535 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON