From the Public Safety edition of October 7, 2026
Phoenix police start a 90-day Axon Draft One pilot with signed attestations, a planted error officers must find, and overtime and report-time metrics
Phoenix Police Department / Phoenix City Council (reported by ABC15 Arizona) · Municipal policing · Phoenix, Arizona, United States
- Publisher
- ABC15 Arizona
- Original publication
- Oct. 7, 2026, 6:03 PM MST (ABC15)
- Source retrieved
- 2026-10-08
- Event date
- 2026-10-01
What happened
ABC15 reported that the Phoenix Police Department launched a 90-day pilot of Axon Draft One, which generates first-draft police report narratives from body-worn camera audio, running Oct. 1 through Dec. 31, 2026 in the Mountain View Precinct Patrol Bureau, the Family Investigations Bureau and the Mountain View Assaults Unit. Councilwoman Ann O'Brien, who pushed for the pilot, framed it as a response to officer vacancies. Each draft must be reviewed and corrected and carries a signed officer attestation before entering the records system, and O'Brien said an intentional error is placed in every draft that the officer must find before signing. The department will track overtime, response times, calls answered, arrests, body-camera activation and report-writing time for patrol, and case-management and call-out overtime, case disposition and report time for investigations, then decide whether to extend or expand.
Why it matters
Directly relevant to policing AI: a large-city department is defining measurable success criteria and an anti-rubber-stamp control before deciding on department-wide AI report drafting.
Evidence and measured results
Local TV reporting based on interviews with the council sponsor and a description of the pilot design. No results exist yet; the metrics list and the planted-error control are as described by O'Brien, not from a published Phoenix PD policy or Axon configuration document.
Limitations and uncertainty
No outcome data yet. The planted-error safeguard is described by the councilwoman, not documented by the department. A 2024 randomized trial (not opened tonight) and prior Hays County experience in the archive suggest time savings may not materialize; Phoenix's results should be compared against a baseline.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-08; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Officer vacancies and hours of report writing push leaders toward AI drafting, but they need evidence before committing department-wide.
- Stakeholders
- Police chief and patrol bureau commanders
- Family Investigations and Assaults Unit supervisors
- Councilmember sponsoring the pilot and the public safety subcommittee
- County prosecutors who receive reports
- Records management system administrators
- Discovery questions
- What baseline report-writing time and overtime exist for the pilot units?
- Is the planted-error check enforced in the software or by supervisors?
- Are original AI drafts retained and disclosed to prosecutors and defense?
- What threshold on the tracked metrics would justify expansion?
- Value hypothesis
- A well-instrumented 90-day pilot can show whether drafting reduces report time and overtime in specific units, giving a defensible buy or stop decision.
- Potential engagement
- Design the pilot evaluation: baseline extraction, comparison units, metric dashboards and an end-of-pilot decision memo.
- Unsupported claims
- Guaranteed reductions in report time or overtime
- Improved response times or more officers on patrol
- Report accuracy improvements
- Suitability for all incident types
Pre-sales engineering
Role takeaway
- Fit
- Fits departments already on Axon body cameras and evidence storage with an RMS that accepts drafted narratives.
- Architecture and integration
- Body-camera audio is uploaded and transcribed in Axon, a draft is generated, edited and attested, then entered into the department's RMS; metrics come from RMS and payroll data.
- Prerequisites
- Axon body cameras and evidence platform
- RMS integration or manual paste workflow
- Payroll and CAD data for overtime and response-time metrics
- Defined comparison units
- Constraints
- Drafts limited to recorded, transcribed audio
- Sensitive family-violence cases
- Pilot ends Dec. 31, 2026
- Arizona public-records and disclosure rules for drafts
- Security
- Confirm access controls on transcripts and drafts, retention of AI drafts, audit trail of draft generation and edits, and disclosure labeling.
- Proof of value
- Compare report-writing time against pre-pilot baseline for the same units
- Measure the share of drafts where the planted error was caught
- Sample attested reports for factual errors against video
- Track overtime changes against non-pilot precincts
Delivery
Role takeaway
- Work
- Run the pilot: train officers, configure attestation and the planted-error check, collect metrics, and deliver an end-of-pilot evaluation.
- Dependencies
- Axon configuration access
- RMS and payroll data extracts
- Supervisor review capacity
- Council subcommittee schedule
- Ownership
- Phoenix PD patrol and investigations leadership, reporting to the City Council's Public Safety and Justice Subcommittee.
- Skills and adoption
- Officers need training to verify and correct drafts rather than accept them; supervisors need sampling routines.
- Governance checkpoints
- Written pilot policy before go-live
- Mid-pilot metric review
- End-of-pilot report before any expansion vote
- Prosecutor consultation on draft disclosure
- Acceptance criteria
- Proposed: baseline and pilot report-time measured for every pilot unit
- Proposed: at least 95% of sampled drafts show the planted error was caught
- Proposed: no attested report found to contain uncorrected AI-introduced factual errors in audit sample
- Proposed: evaluation memo delivered within 30 days of Dec. 31
- Risks
- Rubber-stamping despite attestation
- Missing baseline makes results unprovable
- Errors in sensitive investigations
- Pilot extended without evaluation
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?
Drafts are generated only after body-camera footage is uploaded and transcribed in Axon's environment, then edited and attested before entry into the department's records management system, so the integration point is the RMS hand-off.
Governance
Who approves, reviews and stays accountable for outcomes?
Human accountability is enforced by attestation and a deliberately inserted error; the pilot has a fixed end date and a decision point, which gives the council a natural review gate.
Security and privacy
What data, permissions and controls need testing?
Drafts derive from recorded audio of public encounters; the report does not describe retention of AI drafts, disclosure labels or prosecutor access to drafts, which should be confirmed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Framed as relief for an officer shortage; officers must learn to edit and verify drafts, and investigators in family and assault units will use it on sensitive cases.
Procurement
What should contracts, pricing and exit terms secure?
A time-boxed pilot with named metrics positions Phoenix to make a buy decision on measured overtime and report-time data rather than vendor claims.
Operating model
Which teams own the service once it runs?
Results will be assessed after Dec. 31; the department may extend the evaluation or move toward department-wide use.
Publication history
- 2026-10-07Public Safety · Issue 316 resources
Stable resource ID: phoenix-pd-draft-one-90-day-pilot-metrics-20261007