From the Public Safety edition of September 19, 2026
U.S. Courts: Judicial Conference update on AI task force and interim non-delegation guidance
Administrative Office of the U.S. Courts · Courts / judiciary · United States (federal judiciary)
- Publisher
- uscourts.gov
- Original publication
- September 17, 2026
- Source retrieved
- 2026-09-20
- Event date
- 2026-09-17
What happened
On 2026-09-17 the AO reported to the Judicial Conference that the AI advisory task force (appointed 2025) identified more than 60 issues, prioritized them, and formed seven subject-matter subgroups. Director Conrad stated he issued Task Force-developed interim guidance: courts cautioned not to delegate core judicial functions to AI, including decision-making or case adjudication, and all Judiciary users reminded they are accountable for work performed with AI assistance. Additional guidance will roll out as issues are resolved. Ninth Circuit Judge Sidney R. Thomas (task force chair) updated the Conference. Release also covers CM/ECF modernization and real-property authority—not used as AI evidence here.
Why it matters
Primary-source federal courts AI control statement useful for state/local court peers; complements prior Reuters secondary coverage already archived by supplying the official interim non-delegation and accountability language.
Evidence and measured results
Opened uscourts.gov HTTPS page via WebFetch and curl; confirmed >60 issues, seven subgroups, interim guidance quotes on non-delegation of core functions and user accountability, and Thomas update.
Limitations and uncertainty
Interim guidance text itself is not published in full on this page; no empirical outcome evaluation of AI tools; federal context may differ from state courts; adjacent CMM/RPA content is out of scope for AI findings.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-20; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Courts need AI productivity aids without surrendering adjudication authority or accountability.
- Stakeholders
- Chief judge
- Clerk of court
- Court IT/security
- Probation/pretrial
- Public defenders (as system users)
- Discovery questions
- Is there a written ban on AI for core judicial functions?
- How is user accountability attested and audited?
- Which administrative uses are approved now?
- How will further task-force guidance be adopted locally?
- Value hypothesis
- Bounded value is safer administrative AI under non-delegation rules—not AI-decided cases.
- Potential engagement
- 2–4 week interim-policy alignment workshop for a state/local court mirroring federal non-delegation language.
- Unsupported claims
- That interim guidance is a complete public rulebook
- Measured case-quality improvements from court AI
- Resolution of litigant-filed AI hallucinations
Pre-sales engineering
Role takeaway
- Fit
- Administrative and drafting assists with human ownership—explicitly not case adjudication engines.
- Architecture and integration
- Optional assist tools in clerk/chambers productivity suite; force human approve/sign; deny automated dispositive decision APIs.
- Prerequisites
- Written interim policy
- Role-based access
- Audit logging of AI assists
- Training curriculum
- Constraints
- Full guidance text not on page
- 60+ issues still open
- Federal vs state procedural differences
- Security
- Keep sensitive case text off unapproved models; align with continuous diagnostics/mitigation expectations cited for Judiciary IT.
- Proof of value
- Compliance sampling of AI-assisted work
- No AI-only adjudicative outputs
- User accountability attestations on file
Delivery
Role takeaway
- Work
- Roll out interim policy memo, training, approved-tool list, and periodic compliance checks.
- Dependencies
- AO/task-force updates
- Local IT
- Judicial leadership endorsement
- Ownership
- Chief judge owns policy; clerk owns administrative implementation.
- Skills and adoption
- Train staff that AI assistance does not transfer responsibility for filed work product.
- Governance checkpoints
- Policy issuance
- 90-day compliance review
- Update when next guidance tranche arrives
- Acceptance criteria
- Non-delegation language adopted
- Accountability acknowledgment completed by AI users
- Risks
- Uneven local adoption
- Hidden AI use in chambers
- Public trust hits from AI errors in opinions
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?
Keep generative AI out of adjudication decision paths; confine tools to administrative assists with human sign-off and audit logs.
Governance
Who approves, reviews and stays accountable for outcomes?
Adopt written non-delegation rules and user accountability attestations before expanding chambers or clerk-office AI.
Security and privacy
What data, permissions and controls need testing?
Pair AI use with IT security program updates (release also stresses CDM coverage for Judiciary systems).
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Training every Judiciary AI user on accountability is required; capacity varies across courts.
Procurement
What should contracts, pricing and exit terms secure?
Court AI purchases should contractually forbid use for core adjudicative functions and require auditability.
Operating model
Which teams own the service once it runs?
Separate administrative AI assists from judicial decision-making workflows as a standing operating rule.
Publication history
- 2026-09-19Public Safety · Issue 134 resources
Stable resource ID: uscourts-ai-interim-guidance-20260917