Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Public Safety edition of September 8, 2026

Government auditCautionaryNewly relevant · May 2026

Corrections AI audit separates a completed system from an unfinished effectiveness evaluation

U.S. Department of Justice Office of the Inspector General · Public safety · Indiana, United States; federally funded county community-supervision research

Publisher
DOJ OIG Report 26-051
Original publication
May 7, 2026; project period January 2020–December 2023
Source retrieved
2026-09-09
Read original source

What happened

OIG found a developed AI intervention system but incomplete deployment and efficacy analysis following human-subject compliance failures and weak oversight.

Why it matters

Historical evidence newly added to fill the corrections implementation gap: a research partnership with Tippecanoe County demonstrates dependencies beyond software development.

Evidence and measured results

The audit reports $1,908,515 spent from a $1,999,778 award. Recruitment reached 61 of 250 planned participants; collected human-subject data were abandoned. OIG used interviews, records and judgmental expenditure sampling, not a causal effectiveness evaluation.

Limitations and uncertainty

Nonstatistical audit sampling cannot support population-wide projections. OIG explicitly did not assess application effectiveness. Purdue disputed several recommendations and emphasized technical delivery; OJP agreed with the recommendations. No claim that the tool caused absconding or changed recidivism is justified.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-09; this does not change the original publication date. Labels below come from the analysis itself.

Sales

Role takeaway

Corrections leaders, research sponsors, grant administrators and community partners need assurance that a functional prototype can become an evaluable service. Ask who approves protocol changes, what participant access exists, and which milestones demonstrate outcomes rather than demonstrations. A bounded engagement could assess research readiness and partner responsibilities before additional development. The value hypothesis is avoiding an unevaluable rollout and unsupported spending. The audit does not show that AI reduces recidivism or that all spending lacked value. Avoid transferring this award's failures to every corrections product; customer discovery must establish the actual funding and oversight model.

Pre-sales engineering

Role takeaway

Fit is supervised support and research instrumentation around a specifically authorized intervention. Map participant devices, behavioral data, dashboards, notifications and researcher access, keeping research data separate from enforcement decisions unless explicitly authorized. Prerequisites include approved protocols, feasible recruitment, device management and clear incident ownership. Test offline operation, withdrawal, lost equipment, access revocation and message delivery. A proof of value needs a valid outcome design and usable follow-up data, not merely a working dashboard. Hosting and model details remain insufficiently established here; obtain those from the proposed system before asserting security or scalability.

Delivery

Role takeaway

The principal investigator and corrections liaison should jointly establish enrollment, consent, support, adverse-event handling and escalation, with grant administration tracking subrecipients. Train staff on scope changes and stop-work boundaries before recruiting. Dependencies include approved participant criteria, realistic intake and budget for device support. Proposed acceptance requires documented approvals for every pilot activity, reconciliation of participant and device inventories, and a complete dataset that the approved evaluation can use. Decide continuation at explicit governance checkpoints. Risks include recruitment shortfalls, unclear agency-research boundaries, spending during a stop order and incentives that undermine voluntary participation.

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?

A device-to-dashboard intervention needs data permissions, device lifecycle controls, escalation and tested withdrawal procedures. Validate connectivity and support burden before selecting hosting. An autonomous agent's authority to trigger sanctions is unsupported.

Governance

Who approves, reviews and stays accountable for outcomes?

Treat research approval, scope changes and partner responsibilities as enforceable release gates.

Security and privacy

What data, permissions and controls need testing?

Minimize location and behavioral data, test lost-device handling and align research-only access with supervision boundaries.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Test device usability and support needs with the intended participants without making access to services depend on technical proficiency.

Procurement

What should contracts, pricing and exit terms secure?

Tie payments and device purchases to approved recruitment and evidence milestones, with clear unused-inventory disposition.

Operating model

Which teams own the service once it runs?

Name both a research owner and supervision liaison; define incident reporting and subrecipient oversight before enrollment.

Publication history

  1. 2026-09-08Public Safety · Issue 033 resources
Read preserved resource versions (JSON)

Stable resource ID: doj-oig-purdue-community-supervision-ai-2026