{"resourceId":"hmcts-case-readiness-assistant-20261002","versions":[{"version":"external-4242d602cb0c264ad8bc980d5ad9ce3b9af66a9c186d3111c172e496b36da046","resource":{"id":"hmcts-case-readiness-assistant-20261002","title":"HMCTS: AI Case Readiness Assistant pilot begins at Inner London Crown Court","organization":"HM Courts & Tribunals Service / Ministry of Justice","sector":"Courts / case administration","geography":"United Kingdom — England & Wales (Inner London Crown Court)","publishedAt":"2 October 2026","publicationDate":"2026-10-02","eventDate":"2026-10-02","sourceName":"Inside HMCTS","sourceLabel":"Official HMCTS government blog by Deputy Director Digital Delivery and AI","sourceUrl":"https://insidehmcts.blog.gov.uk/2026/10/02/testing-how-ai-could-help-improve-case-readiness-in-the-crown-court/","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["knowledge-work","governance-procurement","operating-model","developers-agents"],"finding":"On 2 October 2026, HMCTS announced it will begin an October 2026 pilot of an AI Case Readiness Assistant at Inner London Crown Court. The tool reviews case information to flag outstanding pre-trial actions so staff can intervene earlier and reduce delayed hearings. Court staff remain responsible for deciding any action; the assistant will not make or recommend judicial decisions and will not determine case outcomes or how the law is applied. Listing remains a judicial function, with judiciary engagement through the Criminal Courts Improvement Group AI working group. HMCTS states wider use will be considered only if the pilot shows clear value and safe, responsible operation—no accuracy or adjournment metrics are published yet.","sledRelevance":"Same-day government courts signal for SLED court administrators designing generative/admin copilots: explicit non-judicial boundary and evidence-gated rollout before scale.","evidence":"Opened Inside HMCTS HTTPS blog via WebFetch (full post); confirmed pilot site, staff-retention language, non-judicial-decision ban, CCIG oversight mention, and learn-before-scale framing.","architectureImplications":"Keep case-readiness copilots outside judicial decision paths; integrate as staff queue flags with human accept/reject, not auto-listing or outcome scoring.","governanceImplications":"Require written non-judicial-use policy, pilot evaluation plan, and judiciary working-group sign-off before any multi-court expansion.","securityPrivacyImplications":"Case-file AI review expands CMS data exposure; need access controls, logging, and retention limits for model inputs/outputs.","caveats":"UK Crown Court pilot announcement without measured outcomes; transfer to U.S. state/local courts needs local rules and CMS architecture mapping.","streamIds":["public-safety"],"roles":{"sales":"Sales should open on backlog and incomplete-case prep—not AI judging. HMCTS is piloting an AI Case Readiness Assistant at Inner London Crown Court that flags missing pre-trial actions while explicitly forbidding judicial recommendations or outcome determination, with staff retaining action decisions and rollout gated on demonstrated value. Position any SLED court engagement as a bounded discovery on admin copilots inside CMS workflows—human queue ownership, evaluation metrics, and non-judicial boundaries—before pitching generative courtroom or sentencing tools. Do not claim this UK pilot proves U.S. trial-delay reductions.","engineering":"Engineering fit is a staff-facing case-readiness flagger that reads structured CMS fields and returns actionable incompleteness lists for human review—not a model that ranks guilt, sentence, or listing priority. Architecture should quarantine assistant outputs from judicial decision objects, log every accept/reject, and keep listing as a separate judicial system of record. Prerequisites: clean case-status schemas, staff RACI, and evaluation metrics (earlier issue detection, vacated hearings). Constraints: England & Wales procedure; no published accuracy yet. Proof of value: pilot dashboard showing earlier flag rates without judicial-decision spillover.","delivery":"Delivery work is a controlled court-admin pilot: map incomplete-case failure modes, wire read-only CMS access, train listing/case progression staff, and run a time-boxed evaluation before scale. Ownership sits with court operations/digital delivery for the tool and with judiciary governance for any boundary questions. Acceptance criteria should include a signed non-judicial-use policy, staff override rate logging, zero assistant-written judicial recommendations in audited samples, and a go/no-go memo tied to measured prep improvements."},"roleDetails":{"sales":{"customerProblem":"Courts face delayed hearings when missing pre-trial actions are found too late, and want AI help without ceding judicial decisions.","stakeholders":["Court administrator","Presiding/criminal judge","CMS/IT lead","Prosecution case progression","Defense liaison","Judicial AI working group"],"discoveryQuestions":["Which incomplete-case failures drive most adjournments?","Is there a written ban on AI judicial recommendations?","What CMS fields are authoritative for readiness?","What metrics would justify multi-site expansion?"],"valueHypothesis":"Bounded value is a staff-facing readiness flagger with human action ownership—not AI listing or sentencing.","potentialEngagement":"4–8 week readiness-copilot discovery and pilot design with court ops and judiciary governance.","unsupportedClaims":["Guaranteed backlog reduction from this UK pilot","That the tool is ready for U.S. judicial decision support","Vendor accuracy claims without local evaluation"]},"engineering":{"fit":"Read-only CMS incompleteness detection with human accept/reject; excluded from judicial decision objects.","architectureIntegration":"CMS case record → readiness assistant → staff work queue → human action → listing remains judicial SOR.","prerequisites":["Authoritative readiness schema","Staff RACI","Audit logging","Evaluation plan"],"constraints":["UK procedural context","No published accuracy metrics yet","Listing is judicial"],"security":"Minimize case-file tokens to the model; encrypt logs; restrict vendor retention of court records.","proofOfValue":["Earlier flag-to-fix lead time measured","Zero audited judicial recommendations from the tool","Staff override reasons captured"]},"delivery":{"work":"Stand up single-site pilot, train staff, instrument metrics, and produce go/no-go evidence pack.","dependencies":["CMS access","Judiciary working-group review","Change management calendar"],"ownership":"Court digital delivery owns the tool; judiciary owns decision-boundary policy; ops owns queue handling.","skillsAdoption":"Train staff that flags are suggestions requiring human judgment, not automated readiness certificates.","governanceCheckpoints":["Pre-pilot legal review","Mid-pilot metric check","Expansion gate review"],"acceptanceCriteria":["Signed non-judicial policy","Logged human decisions on 100% flagged cases","Published pilot learning note"],"risks":["Scope creep into judicial advice","Staff over-trust of flags","Privacy incidents on case data"]}},"retrievedAt":"2026-10-05T02:59:19Z","enrichedAt":"2026-10-05T02:59:41Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Court staff need plain-language training that AI flags do not replace professional judgment or create new accessibility barriers for unrepresented parties.","procurementImplications":"Procure as a bounded pilot with evaluation exit criteria; avoid enterprise CMS AI SKUs that blur admin vs judicial functions.","operatingModelImplications":"Add a readiness-flag review step in case progression SOPs without changing judicial listing authority.","sourceVerification":{"openedUrl":"https://insidehmcts.blog.gov.uk/2026/10/02/testing-how-ai-could-help-improve-case-readiness-in-the-crown-court/","referenceExcerpt":"The Case Readiness Assistant will not make or recommend judicial decisions","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}