From the Public Safety edition of October 27, 2026
At IACP 2026, a police legal adviser tells chiefs that AI report writing is a command decision: the officer, not the software, testifies, and prosecutors may refuse AI-assisted reports
Massachusetts Chiefs of Police Association (general counsel); IACP 2026 conference · Policing / AI-assisted report writing · United States (Orlando, Florida conference)
- Publisher
- Police1
- Original publication
- Police1, Oct. 27, 2026
- Source retrieved
- 2026-10-28
What happened
Police1 reports a presentation at the 2026 IACP conference in Orlando by Eric Atstupenas, general counsel to the Massachusetts Chiefs of Police Association, who said he neither advocates for nor against AI report writing but that adopting it is a command decision. Key points: the officer, not the software, testifies and must be able to explain every statement; reviewers may grow complacent after many accurate drafts; King County prosecutors (September 2024) refused AI-assisted narratives and Connecticut prosecutors imposed a moratorium in 2026, so agencies should meet prosecutors before buying; California Penal Code 13663 (effective Jan. 1, 2026) requires disclosure, signed verification and retention of the first AI draft with an audit trail, and Utah requires disclosure and accuracy certification; a 2024 randomized trial (85 officers, 755 reports) found no statistically significant time reduction. He urged agencies to test the full workflow, including discovery of drafts, prompts and logs, negotiate exit and data-retrieval terms, check that vendor default settings match policy, and set approved uses, retention, supervisory review and training before piloting on live cases.
Why it matters
A practitioner checklist from inside policing that shifts AI report-writing decisions from IT procurement to legal, prosecutorial and records review.
Evidence and measured results
Opened the Police1 article and read it in full.
Limitations and uncertainty
Conference presentation reported by a trade publication; legal points are summaries, not legal advice; the RCT cited is from 2024 and the state laws are as described in the article.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-28; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Police leaders may buy AI report writing before confirming that prosecutors will accept the reports and that records can be produced in discovery.
- Stakeholders
- Police chief and command staff
- Agency legal counsel
- District attorney or prosecutor’s office
- Records management staff
- Patrol officers and supervisors
- Discovery questions
- Has your prosecutor said it will accept AI-assisted reports?
- Can the system retain first drafts and audit logs for the report’s retention period?
- Can the vendor change settings or add features without your approval?
- What are the exit and data-retrieval terms?
- Value hypothesis
- Interpretation: a readiness review could avoid buying a tool prosecutors will not accept; savings remain unproven.
- Potential engagement
- A pre-procurement readiness review of legal, prosecutorial and records requirements for AI report writing.
- Unsupported claims
- Guaranteed reductions in report-writing time
- That officer review reliably catches errors
- That disclosure laws are uniform across states
Pre-sales engineering
Role takeaway
- Fit
- Relevant to any agency evaluating Draft One or similar tools, especially in California and Utah.
- Architecture and integration
- Requires draft, prompt and audit-log retention integrated with records and discovery processes.
- Prerequisites
- Prosecutor consultation
- Retention schedule mapping
- Contract exit terms
- Constraints
- State disclosure and certification laws vary
- Prosecutor refusals in some jurisdictions
- Conference summary, not legal advice
- Security
- Control vendor defaults, subcontractor access and automatic updates; ensure data ownership and deletion on exit.
- Proof of value
- Retrieve full draft history for a sample case
- Verify vendor settings match policy
- Time the complete workflow including review and records
Delivery
Role takeaway
- Work
- Establish policy, retention, review and training before piloting on live cases; test the complete workflow.
- Dependencies
- Prosecutor acceptance
- Vendor contract terms
- Records system integration
- Ownership
- Police chief, with legal counsel and records management
- Skills and adoption
- Officers trained to review against recordings and to explain every statement they sign.
- Governance checkpoints
- Prosecutor sign-off
- Policy adoption before pilot
- Pilot scope and duration defined
- Post-pilot review
- Acceptance criteria
- Written prosecutor acceptance before live use (proposed)
- Full draft and audit-log retrieval in 100% of test cases (proposed)
- Risks
- Review complacency
- Pilots bypassing policy
- Discovery disputes over draft differences
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?
Systems must preserve original drafts, prompts and audit logs, support litigation holds and export records years later.
Governance
Who approves, reviews and stays accountable for outcomes?
Agencies should consult prosecutors before deployment and treat pilots on live cases as carrying full evidentiary consequences.
Security and privacy
What data, permissions and controls need testing?
Raises data ownership, subcontractor access, retention settings and automatic updates that could override agency policy, citing an ALPR sharing-settings example.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Officer credibility and careers are at risk if officers sign narratives they cannot defend; training must address automation bias.
Procurement
What should contracts, pricing and exit terms secure?
Negotiate data retrieval, deletion, preservation and exit provisions before signing; question vendors on system prompts and update controls.
Operating model
Which teams own the service once it runs?
Report creation becomes a records, discovery and prosecutorial workflow, which may offset drafting time saved.
Publication history
- 2026-10-27Public Safety · Issue 496 resources
Stable resource ID: iacp-2026-ai-police-reports-officer-testifies-prosecutor-acceptance-records-20261027