The Vanishing Draft: How a Product Built to Forget, a Six-Hundred-Thousand-Report Milestone, and Two State Statutes Collided Over Police Accountability
AI now drafts police reports in roughly 600 departments nationwide — while the leading tool was engineered to leave no record of what it wrote. Two enacted state laws, a wall of prosecutor refusals, and a November wave of study bills are forcing the question the design deferred: who wrote this report?
The Scale of the Shift
Axon Enterprise, the company best known for the Taser, says its AI report-writing tools are now in use by 600 police departments across the country and have helped write 600,000 police reports, saving an estimated 300,000 hours according to its customer surveys [1]. Its AI Era product bundle — which includes Draft One, the tool that writes incident narratives from body-camera audio — costs $199 per officer per month, and the company booked approximately $750 million in AI Era contracts in the year after Draft One launched, with first-quarter 2026 revenue from AI products growing more than 700 percent year-over-year [1]. These are no longer pilot programs; they are infrastructure.
The stakes follow from what a police report is. Officers spend as much as 15 hours a week on reports, and those documents are either stored for reference or handed to prosecutors who decide whether to file charges — making them, as one criminologist put it, a crucial part of the criminal justice system rather than clerical residue [1]. When the drafting of that document moves from an officer’s memory to a language model’s output, the policy question is not whether paperwork gets faster. It is whether the justice system retains the ability to ask, after the fact, what the machine said and what the human changed.
Two Enacted Laws, Two Philosophies
Only two states have enacted statutes governing AI-assisted police reports, and they anchor opposite ends of a spectrum: disclosure with full audit infrastructure, versus disclosure with agency self-governance.
- California SB 524 (Penal Code §13663). Signed October 10, 2025 and effective January 1, 2026, the law requires every law enforcement agency to maintain a policy under which an official report generated fully or partially with AI must, on each page or in the body of the text, identify every specific AI program used and prominently state: “This report was written either fully or in part using artificial intelligence” [2]. The officer must sign the report, verifying they reviewed its contents and that “the facts contained in the official report are true and correct” [2]. The core logic is evidentiary: only the final signed report counts as the officer’s statement, and the first AI-generated draft must be retained for as long as the final report — so that a court, a defense attorney, or a records requester can always compare what the machine proposed against what the officer swore to.
- Utah SB 180 (Law Enforcement Usage of Artificial Intelligence). Effective May 2025, the statute directs each agency to adopt a written policy governing AI use, requires officers to disclose when AI was involved in generating a report, and requires the officer’s certification that the report was reviewed for accuracy [3][4]. Utah’s approach puts the compliance burden on the agency’s own policy process rather than a statutory retention mandate — the state sets the floor of disclosure, and the department writes the procedure.
California’s statute reaches one step further than Utah’s, and the step is vendor-facing. A contracted vendor “shall not share, sell, or otherwise use information provided by a law enforcement agency to be processed by artificial intelligence” except for the agency’s own purposes or pursuant to a court order, though vendors may access processed data for troubleshooting, bias mitigation, accuracy improvement, or system refinement [2]. An audit trail must identify, at minimum, the person who used the AI and the video and audio footage used to create the report [2]. The law effectively nationalizes, for California agencies, a data-governance standard that no vendor contract had established on its own.
A Product Built to Forget
The reason California’s retention mandate matters is that the dominant product was designed without it. An Electronic Frontier Foundation investigation — built on police reports, emails, procurement documents, department policies, and Axon’s own manuals and marketing materials — concluded that Draft One is engineered so that no one, including a police chief or an independent researcher, can meaningfully audit its use [5]. Draft One processes only the audio from body cameras, not the video; the officer edits the generated text and then copies it into the department’s records system, at which point the draft disappears when the browser tab closes [5]. There is no log distinguishing which portions of a final report were written by the machine and which by the officer, except the officer’s own recollection [5].
EFF, which obtained a recording of an Axon roundtable discussion, quotes the company’s senior principal product manager for generative AI explaining the retention decision in terms that will likely be quoted in courtrooms for years:
“So we don’t store the original draft and that’s by design and that’s really because the last thing we want to do is create more disclosure headaches for our customers and our attorney’s offices.” [5]
The consequences surface in public-records responses. The Lafayette, Indiana Police Department — one of Axon’s most promoted Draft One clients — told EFF: “Regarding the attached request, we do not have the ability to create a list of reports created through Draft One. They are not searchable. This request is now closed.” [5] The Palm Beach County Sheriff’s Office, by contrast, requires a disclosure footer in every AI-assisted report and was able to isolate more than 3,000 Draft One reports generated between December 2024 and March 2025 with a simple keyword search [5]. The difference between the two agencies is not the software — it is whether local policy forced a marker into the text. Axon itself tracks which reports used Draft One internally, and provided a Colorado agency custom code to extract the data after a media request revealed the agency could not [5].
Axon’s stated position is that officers remain in control: the company describes its approach as “officer-in-the-loop,” saying narratives “cannot be submitted without officer review and approval,” and a spokesperson noted that “AI capabilities and Draft One have evolved significantly in the last two years” [1]. EFF’s finding is narrower but harder to answer: even if officers review every draft, the system keeps no record proving they did, and Axon disclosed a bug that let officers bypass the review guardrails on at least three occasions [5]. A safeguard that leaves no trace is a safeguard that cannot be audited — which is precisely the gap SB 524’s first-draft retention requirement was written to close.
The Accuracy Record
The retention question would be academic if the drafts were reliably right. Public records obtained by Forbes suggest they are not, and that the editing burden can consume the promised savings. In Lafayette, officers testing Axon’s Form One tool — which fills in names, license plates, and vehicle details from camera audio — reported in emails that the tool struggled to record the right names or car plates even when they were clearly stated in the footage, with one officer writing: “I know it doesn’t save me time and I know it has inaccuracies that I will have to edit,” and another concluding that “Form One dramatically increases the time it takes to finish reports” — a form that took 30 seconds by hand now taking three minutes [1].
The only data-driven study of the flagship tool points the same direction. Criminologist Ian Adams, a former police officer, studied the Manchester, New Hampshire Police Department’s use of Draft One for a 2024 Journal of Experimental Criminology paper and found no improvement in report completion time: officers without access filed at the same pace because Draft One users spent their time removing irrelevant information, fixing inaccuracies, and adding facts the system missed [1]. Manchester dropped the tool in 2024, the same year Anchorage police stopped using it citing zero time savings — yet about half of Manchester’s officers still believed it had helped, a gap Adams called “a definite gap between the perception and objective reality” [1]. That perception gap is itself a policy problem: if officers systematically overestimate the tool’s reliability, the human review that the whole framework depends on weakens precisely where it is hardest to observe.
The Prosecutor Wall
The fastest-moving constraint has come not from legislatures but from the officials who decide what evidence they will take to court. The Prosecuting Attorney’s Office in King County, Washington — which includes Seattle — informed law enforcement agencies in 2024 that it would not accept reports written with AI assistance because of hallucinations, and its policy remains in force [1]. Its 2024 memo was explicit:
“We do not fear advances in technology — but we do have legitimate concerns about some of the products on the market now… For now, our office has made the decision not to accept any police narratives that were produced with the assistance of AI.” [1]
King County Prosecutor Daniel Clark described the concrete failure modes: AI getting the names of witnesses and officers wrong, or placing officers at a scene when they were only on the radio. “It’s a type of error that can really challenge an officer’s credibility when they’re on the stand, and then that puts the officer at risk of being either called lazy, sloppy or dishonest,” Clark said. “None of those are good options.” [1] The logic cuts across the usual ideological lines: a prosecutor refusing AI-drafted reports is not protecting defendants from police so much as protecting the evidentiary value of police work itself.
The refusals are stacking up beyond Seattle. Connecticut’s Chief State’s Attorney imposed a statewide, non-statutory moratorium on AI-drafted official reports in April 2026, and county-level prosecutor restrictions are in place in King County, Wayne County, Michigan, and Hays County, Texas [4]. No state has banned the practice by statute — a Nevada ban was stripped from its bill before it died in 2025, and Minnesota’s government-wide prohibition on generative AI in official records lapsed at the May 2026 adjournment [4]. The pattern is a governance inversion: the branch of the system with the least formal rulemaking power is setting the de facto national standard, one charging decision at a time.
The Vendor Incentive Problem
Disclosure laws address who wrote the report, but the ACLU has raised a second-order concern: the company that writes the draft may have reasons of its own to shape it. Axon and its rival Motorola Solutions do not merely sell report-writing AI — both sell license plate readers, surveillance cameras, body cameras, drones (in Axon’s case), Tasers, and real-time crime center software, meaning the same vendor’s products may be what the report is about [6]. A report-drafting model, in other words, could be trained or prompted to mention some technologies favorably, or not at all.
The concern is not hypothetical. EFF found that Vigilant Solutions — the license-plate-reader company later acquired by Motorola — recommended in a training slideshow that officers omit its technology from reports when possible: “If the use of the LPR equipment can be left out of the report, that is what is recommended” [6]. The precedent shows a police-technology vendor actively coaching officers on report content that affected the vendor. California’s vendor-data restrictions and audit trail are the first statutory answer to that conflict of interest; they still do not reach the model itself — what it was fine-tuned to include, omit, or emphasize — which remains invisible to agencies, courts, and the public [6].
The Next Wave: Study Bills and Deadlines
The statehouses are now processing what the first two laws started. New Jersey is the most recent test case: two bills — A-759 on facial recognition and A-3076 on AI — would direct the attorney general to study how police use the technologies and recommend statewide policies, with A-3076 calling for a policy requiring officers to review AI-generated reports for accuracy and completeness [7]. Both cleared the Assembly Public Safety and Preparedness Committee on October 19 [7]. Assemblyman Balvir Singh, whose district already has departments using AI report writers without statewide guidance, named the core risk:
“The concern is that police reports are often central to court proceedings, where specific words, phrasing, and details matter,” Singh said. “Generative AI doesn’t just clean up grammar. It can add supporting details, substitute words, and change phrasing for clarity and flow. These unintended changes, especially when they go unnoticed, can alter the meaning of an officer’s account and potentially affect legal proceedings.” [7]
State Senator Benjie Wimberly, who is expected to introduce identical bills in the upper chamber, framed the choice in fewer words: “We shouldn’t have to wait for something to go wrong before establishing appropriate safeguards. Public safety and civil liberties are not mutually exclusive. We have an obligation to protect both.” [7] Skeptics argue studies are the slower of two paths — Montclair State justice studies professor Jason Williams would prefer accountability measures, use restrictions, and independent audits now, warning that “Officer review is necessary… but it may not be sufficient because sometimes people have this tendency to just rely on the AI output” [7].
Elsewhere the calendar is doing the work:
- New York. S10425/A9253-A would have required 90 days’ public notice before deploying a covered AI product and disclosure to the defense within 20 days of any post-arrest AI use; it stalled in committee and dies with the 2025–26 term in January 2027 unless reintroduced [4]. Its defense-disclosure clock is the most defendant-facing provision any legislature has drafted.
- Virginia. HB 1294, requiring disclosure, first-draft retention, and an audit trail, was carried over to the 2027 session [4] — the closest pending analogue to California’s regime.
- Connecticut, Michigan, Washington. Prosecutor-level restrictions remain the operative rule where legislatures have not acted, a reminder that the current national baseline is a patchwork of charging policies rather than law [4].
What to Watch
- The first enforcement test of SB 524. California’s first-draft retention requirement took effect January 1, 2026, and EFF’s finding is that Draft One “cannot comply” with it as designed [5]. Whether Axon ships a retention feature for California agencies — and whether any department without it continues using the tool — is the first real compliance question.
- Disclosure in the courtroom. California requires the disclosure statement to be “readily apparent to the reader” on every page [2]. The first appellate fight over whether an AI-assisted report was properly disclosed to a jury will define how far the statute reaches in practice.
- Whether prosecutors codify their refusals. The King County and Connecticut policies are internal decisions, reversible at will [4]. If a legislature converts any of them into statute, the de facto standard becomes binding.
- The vendor audit trail. Axon tracks Draft One report usage internally that its customer agencies cannot extract [5]. Whether California’s audit-trail requirement forces that data into agency hands is an open implementation question — and a test of whether disclosure law can outrun product design.
- New Jersey’s study reports. If A-3076-style provisions advance, the attorney general’s recommended statewide policy — particularly its officer-review requirement — would give the study-bill approach its first output [7].
The collision at the center of this story is simple to state. A product that writes the foundational document of criminal prosecution was designed, in its vendor’s own words, to avoid “disclosure headaches” — and two state legislatures have now answered that design with a disclosure mandate. The question the next year will settle is whether the record of what the machine wrote becomes something the justice system can see, or whether six hundred thousand reports join the system with no one able to say which words were the officer’s.
References
[1] Forbes — [SECONDARY] Brewster, Thomas. “Axon Says AI Police Reports Save Time. Public Records Show They Get Facts Wrong.” July 22, 2026.
[2] California Legislative Information — [PRIMARY] SB 524 (Arreguín), Chapter 587, Penal Code §13663. Approved October 10, 2025; effective January 1, 2026.
[3] Utah State Legislature — [PRIMARY] SB 180, “Law Enforcement Usage of Artificial Intelligence.” 2025 General Session; effective May 2025.
[4] Barricade AI — [SECONDARY] “AI Police Report Laws by State: 2026 Tracker.” Updated November 2026. (vendor-maintained research tracker)
[5] Electronic Frontier Foundation — [ADVOCACY] Guariglia, Matthew, and Dave Maass. “Axon’s Draft One Is Designed to Defy Transparency.” July 10, 2025. (digital rights organization)
[6] American Civil Liberties Union — [ADVOCACY] Stanley, Jay. “Another Problem With AI-Assisted Police Reports: Companies Can Have Incentives to Distort Their Content.” August 28, 2026. (civil liberties organization)
[7] The Jersey Vindicator — [SECONDARY] Janoski, Steve. “NJ lawmakers want safeguards for police use of AI, facial recognition software.” November 2, 2026.
AI automated and generated content. Human reviewed.
Listen to the Podcast: AI Policy for the Bears
Two bears break down this story on AI Policy for the Bears, Episode 45.
