From the Public Safety edition of September 16, 2026
CCJ defender case study allows general-purpose AI only when confidentiality preconditions enable Standard Deploy
Council on Criminal Justice Task Force on Artificial Intelligence · Indigent defense / courts-adjacent practice · United States (hypothetical large urban public defender office)
- Publisher
- CCJ
- Original publication
- September 2026
- Source retrieved
- 2026-09-17
What happened
September 2026 CCJ case study examines general-purpose AI for public defender research, drafting, discovery analysis, and case prep in a large urban office. Classification is low risk and substantial opportunity—triggering Standard Deploy—only if privacy/confidentiality preconditions are met: enterprise-tier or air-gapped tools, no-training-on-customer-data terms, MDM and network blocks against consumer AI for client work, and lawyer-in-the-loop verification. Without those preconditions, recommendation flips to Generally Avoid because consumer accounts create a privilege-loss pathway (citing Heppner). Notes ~300 judicial AI standing orders (as of March 2026) and large hallucination-case counts as operational context. Not an RCT of defender outcomes.
Why it matters
Useful for public defender offices, court IT, and county counsel setting acceptable-use policy: distinguishes efficiency opportunity from privilege risk. Cross-relevant to prosecutor offices with similar confidentiality duties. Interpretation; jurisdiction-specific disclosure matrices still required.
Evidence and measured results
Opened original HTTPS HTML. Executive summary and risk section state the binary privacy precondition; implementation details specify MDM, domain blocking, and Acceptable-Use Policy (Appendix J).
Limitations and uncertainty
Hypothetical office; opportunity claims reference secondary efficiency reports; criminal-defense-specific accuracy benchmarks remain limited; Heppner and standing-order counts are evolving.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-17; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Under-resourced defender offices need efficiency without destroying privilege or inviting sanctions from unverified AI output.
- Stakeholders
- Chief public defender
- IT/security lead
- Training/CLE coordinator
- County counsel
- Line attorneys and investigators
- Discovery questions
- Are consumer AI domains blocked on office networks and managed devices?
- Does the contract forbid training on customer data and bind model subprocessors?
- How will verification time be measured against claimed savings?
- Which judges' standing orders require AI disclosure in this venue?
- Value hypothesis
- Enterprise-controlled AI plus verification workflows can reallocate attorney time to counseling and investigation if—and only if—confidentiality preconditions hold.
- Potential engagement
- Acceptable-use policy + enterprise tool selection + 60–90 day pilot with verification-time and citation-error metrics.
- Unsupported claims
- Guaranteed case-outcome improvement
- That consumer ChatGPT is safe for client facts
- That RAG legal tools eliminate hallucination
- One disclosure rule covering all assigned courts
Pre-sales engineering
Role takeaway
- Fit
- Fit for offices that can field MDM, SSO, and enterprise AI; unfit if staff must use personal consumer accounts for client work.
- Architecture and integration
- Enterprise AI behind SSO into DMS; network DNS/proxy blocks for consumer AI; optional air-gapped research appliance for sealed matters.
- Prerequisites
- Contractual confidentiality and no-train terms
- MDM on office devices
- Acceptable-use policy with consequences
- Filing checklist hooks for court disclosure
- Constraints
- Budget limits on legal-AI enterprise pricing
- Weak state/local-law model performance
- Frequent foundation-model migrations
- Detection gaps for personal-device bypass
- Security
- Treat prompts containing client facts as privileged ESI; DLP; eDiscovery-ready logging; prohibit sealed-record entry into non-approved systems.
- Proof of value
- Net time savings after verification
- Citation-error catch rate in attorney review
- Zero confirmed privilege incidents
- Compliance rate with court disclosure rules
Delivery
Role takeaway
- Work
- Write Acceptable-Use Policy, deploy MDM/network controls, train on hallucination and ethics, maintain court-rule matrix, run pilot.
- Dependencies
- IT security capacity
- CLE budget
- Vendor public-sector pricing
- Supervising attorney bandwidth
- Ownership
- Named managing attorney accountable for AI practice policy, with IT owning technical controls.
- Skills and adoption
- Role-specific training for research, drafting, discovery review; emphasize lawyer-in-the-loop and jurisdiction disclosure.
- Governance checkpoints
- Precondition checklist before Standard Deploy
- Pilot go/no-go on confidentiality/sanctions
- Reassessment before contract renewal
- Triggered review on vendor privacy-term changes
- Acceptance criteria
- No approved client work on consumer accounts
- Disclosure checklist used on AI-assisted filings
- Pilot shows net time benefit or tool scope narrowed
- Risks
- Personal-device shadow AI
- Hallucinated citations reaching court
- Privilege waiver under Heppner-line facts
- Verification effort erasing savings
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?
Prefer enterprise SSO, document-management integration, air-gap where needed; block consumer AI domains on office networks; log approved-tool use; keep verification and court-disclosure checklists in filing workflow.
Governance
Who approves, reviews and stays accountable for outcomes?
Adopt Acceptable-Use Policy defining permitted/prohibited uses and data-entry bans; maintain court-rule matrix; measure citation-flag catch rates and prohibited-tool use; reassess before renewal or on model/policy changes.
Security and privacy
What data, permissions and controls need testing?
Confidentiality is the controlling risk: contractual confidentiality, no training on customer data, bind subprocessors, data residency where required; personal consumer accounts for client work are a primary failure mode.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Training and CLE are core controls; understaffed offices may lack verification capacity, which itself weakens the opportunity case.
Procurement
What should contracts, pricing and exit terms secure?
Level 1 terms only if Standard Deploy applies: enterprise/air-gap requirement, hallucination methodology disclosure, migration notice, confidentiality and no-train clauses, termination for rights concerns.
Operating model
Which teams own the service once it runs?
Shift from informal individual AI use to office-controlled tooling with continuous monitoring of prohibited-tool use and disclosure volume.
Publication history
- 2026-09-16Public Safety · Issue 104 resources
Stable resource ID: ccj-public-defender-genai-case-202609