From the Public Safety edition of November 3, 2026
A Crown Prosecution Service lawyer cited a nonexistent case, traced to an AI search summary, while arguing in the High Court to prosecute a child
Crown Prosecution Service (England and Wales) · Courts / prosecution / legal research with AI · England and Wales, United Kingdom
- Publisher
- The Guardian
- Original publication
- The Guardian, Nov. 3, 2026
- Source retrieved
- 2026-11-04
- Event date
- 2026-10-31
What happened
The Guardian reported that a senior crown prosecutor in the CPS rape and serious sexual offences unit cited a nonexistent precedent, "R v J [2024] EWCA Crim 3529", in a High Court challenge to the decision to prosecute a boy who was 11 at the time of an alleged offence. The prosecutor admitted the error in October; two High Court judges called her explanation unsatisfactory. The Guardian understands the citation came from an AI summary in an internet search. The court said the error did not change the outcome. It is the second known CPS case after a February extradition matter. The CPS says its policy bars AI from legal decisions and requires human accuracy checks; after an internal review it told staff case law must come from trusted legal sources. A barrister’s UK tracker now lists 101 AI-related court errors.
Why it matters
Shows a government prosecutor, not a self-represented litigant, introducing an AI-fabricated authority despite an existing AI policy; the control gap was in everyday research tools, not approved AI systems.
Evidence and measured results
Opened and read the full Guardian article. Court documents are described but not linked; the CPS internal review was not published.
Limitations and uncertainty
UK prosecution and court practice differ from U.S. state systems; facts come from one news report and court documents it describes; the AI source is the newspaper’s understanding, while the CPS said internet research.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Government lawyers can file AI-fabricated authorities even under an AI policy, damaging cases and public trust.
- Stakeholders
- Chief prosecutor or district attorney
- Public defender leadership
- Legal research librarian
- Court liaison
- Discovery questions
- Which research tools do staff use day to day?
- Is each citation checked against an authoritative database before filing?
- How are errors reported and reviewed?
- Value hypothesis
- A verified-citation workflow reduces sanctions risk and protects case outcomes.
- Potential engagement
- Citation-verification workflow and staff training for a prosecution or defense office.
- Unsupported claims
- That AI definitely produced the citation
- That the error affected the case outcome
- That a policy alone prevents recurrence
Pre-sales engineering
Role takeaway
- Fit
- Relevant to any prosecution, defense or court office drafting legal filings.
- Architecture and integration
- Citation checking integrated with document drafting and case management, flagging authorities not found in a trusted database.
- Prerequisites
- Access to an authoritative case-law database
- Inventory of research tools in use
- Filing workflow with review step
- Constraints
- Confidential case material
- Time pressure
- Staff use of personal search tools
- Security
- Keep confidential case material out of public AI tools and log use of approved ones.
- Proof of value
- Run a validator on past filings
- Measure unmatched citations
- Time added per filing
Delivery
Role takeaway
- Work
- Add a citation-verification step and training to the drafting process.
- Dependencies
- Legal research subscription
- Case-management integration
- Supervisor sign-off
- Ownership
- Office lead with legal research staff and IT.
- Skills and adoption
- Staff need to recognise AI summaries in search results and verify every authority.
- Governance checkpoints
- Verification rule adopted
- Pilot on one unit
- Review of errors after 90 days
- Acceptance criteria
- All filings carry verified citations
- Checks recorded
- No fabricated authority filed during pilot
- Risks
- Policy without enforcement
- Workload pressure
- Errors found only by opponents
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
The failure came from an AI summary inside a general web search, outside any approved tool, so tool allow-lists alone do not cover it.
Governance
Who approves, reviews and stays accountable for outcomes?
An AI policy existed and still failed; citation verification against authoritative databases needs to be a checked step, not a policy statement.
Security and privacy
What data, permissions and controls need testing?
A barrister warned of confidentiality risks when prosecutors handle sensitive case material near AI tools.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Opposing counsel and barristers now spend time verifying every authority, shifting workload across the system.
Procurement
What should contracts, pricing and exit terms secure?
Legal research subscriptions with citation checking may be a cheaper control than banning AI; agencies should budget for verification tooling.
Operating model
Which teams own the service once it runs?
Prosecution offices need a review step where a second person or a tool confirms each cited authority before filing.
Publication history
- 2026-11-03Public Safety · Issue 585 resources
Stable resource ID: uk-cps-prosecutor-cites-nonexistent-ai-generated-case-in-high-court-child-prosecution-20261103