From the Public Safety edition of September 13, 2026
Post-trial survey separates officer enthusiasm from verified reporting benefits
Hunter Boehme and colleagues · Policing · New Hampshire, United States; single agency
- Publisher
- CrimRxiv
- Original publication
- March 19, 2025 preprint release
- Source retrieved
- 2026-09-14
What happened
Favorable attitudes did not differ significantly between treated and control officers; reported workflow problems complicate adoption.
Why it matters
Historical workforce evidence complements the archived Manchester timing trial; this is a separate survey, not independent replication.
Evidence and measured results
Final analytical sample: 96 respondents. Table 2 records 19 of 40 time-question respondents perceiving savings and 19 perceiving no difference. These are self-reports, not measured labor reductions. Methods use group comparisons and descriptive analysis.
Limitations and uncertainty
Single agency, immediate post-intervention perceptions, uneven item denominators, limited demographic diversity. No objective quality or downstream court outcome assessment. Preprint version inspected.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-14; this does not change the original publication date. Labels below come from the analysis itself.
Sales
Role takeaway
Command staff, records supervisors, training leads and finance teams need to understand whether a reporting assistant addresses their bottleneck. Ask which incident types staff actually choose it for, where corrections accumulate, and whether enthusiasm survives complex cases. A bounded engagement could map one reporting category and develop a balanced adoption and workload scorecard. The value hypothesis is a better-informed purchase decision and identification of avoidable friction. Do not translate satisfaction into guaranteed savings or improved evidence. Applicability is to departments able to observe actual use and protect evaluation time; a single historical survey cannot establish a current product's business case.
Pre-sales engineering
Role takeaway
Fit is a draft-only assistant around an existing records workflow. Prerequisites include reliable incident identifiers, permissioned recordings, meaningful timestamps and reviewer participation. Preserve the original narrative inputs and every accepted edit. Test omitted observations, conflicting chronology and incomplete audio against an officer-adjudicated reference. A proof of value should compare active handling effort and factual completeness with conventional reports while recording non-use. Hosting must follow local data-handling requirements; this survey does not validate cloud, on-premises or hybrid options. Keep automated agents from submitting reports, and include upload failures and interrupted reviews in the test rather than benchmarking text generation alone.
Delivery
Role takeaway
A records lead should coordinate patrol representatives, trainers, legal reviewers and IT. Baseline conventional reporting, prepare a limited cohort and schedule feedback sessions tied to observed corrections. Dependencies include usable logs and protected staff time.
- Proposed acceptance
- every pilot report has an accountable approver, all deliberately seeded material errors are caught in the test set, and total handling effort meets a locally agreed target without quality deterioration. Train supervisors to distinguish readability from evidentiary adequacy and offer a conventional reporting route. Risks include selective participation, self-estimation bias and extra supervisory work hidden outside the officer's measured task.
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?
Instrument camera ingestion, narrative drafting, structured records entry and approval as separate stages.
Governance
Who approves, reviews and stays accountable for outcomes?
Define success independently of satisfaction scores.
Security and privacy
What data, permissions and controls need testing?
Keep protected recordings within authorized case permissions throughout evaluation.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Test training comprehension and correction effort across officer experience and language needs.
Procurement
What should contracts, pricing and exit terms secure?
Require local evidence of total workload before converting a trial into recurring licenses.
Operating model
Which teams own the service once it runs?
Records supervisors should own acceptance and distinguish adoption support from efficacy evaluation.
What changed
New-to-archive historical source adds practitioner adoption evidence to the already archived objective timing study. No new trial or recent update claimed.
Publication history
- 2026-09-13Public Safety · Issue 083 resources
Stable resource ID: police-posttrial-adoption-perceptions-2025