AI Writes the Police Report: Nobody Can Say Who Testifies

Somewhere in the United States tonight, a patrol officer will finish a shift, sit down at a terminal, and read an account of something they did a few hours earlier. The account will be fluent, chronological, written in the first person, and organised in the familiar grammar of a police report. It will describe what the officer saw, what the officer said, what the suspect did in reply. And the officer will not have written a word of it. A large language model will have assembled the narrative from the audio picked up by the body-worn camera clipped to the officer's chest, transcribed it, and returned a finished draft within minutes of the incident ending. The officer's job is now not to compose but to correct: to read the machine's version, fill in a few bracketed blanks, delete what is wrong, and then sign it as a sworn and truthful account of events. Once signed, that document becomes evidence. It may establish the probable cause for an arrest. It may be read to a jury. It may decide whether a defendant's version of events is believed or dismissed as a lie.
The tool most responsible for this shift is called Draft One, built by Axon Enterprise, the company that already dominates the American market for Tasers and body cameras. Since its launch in April 2024, it has spread across police departments from Oklahoma City to Fort Collins to Lafayette, promising to hand officers back the hours they lose to paperwork, and it has done so at a speed that has outrun almost every attempt to scrutinise it. Axon insists that a human remains in control at every step. But a growing chorus of researchers, defence lawyers, civil-liberties organisations and even prosecutors argues that something more fundamental is being quietly rearranged: the relationship between what an officer remembers, what a machine reconstructs, and what a court is ultimately asked to trust.
The Machine That Learned to Testify
The scale of the deployment is no longer experimental. Axon says that Draft One is now in use at roughly six hundred police departments, that it has produced something in the order of six hundred thousand reports, and that, on the evidence of the company's own customer surveys, it has saved an estimated three hundred thousand hours of officer time. The commercial trajectory matches the operational one: Axon reported that revenue from its artificial-intelligence products grew by more than seven hundred per cent year over year in the first quarter of 2026, against total quarterly revenue of $807 million. It is worth pausing on the provenance of that headline figure, because those three hundred thousand hours are not a measurement. They are an aggregation of what officers and their supervisors told the company they believed had happened, which is to say a survey of perception rather than a stopwatch, and the distinction will turn out to matter a great deal.
The mechanics of Draft One are, on their surface, unremarkable. Axon has long argued that officers spend a punishing share of their working lives writing reports; the company cites figures suggesting report-writing can consume up to forty per cent of an officer's time. Draft One is pitched as the remedy. Audio from an officer's body-worn camera is uploaded, transcribed automatically, and passed to a large language model built on a version of OpenAI's GPT-4 technology. Within seconds, the system produces a first-person narrative in the house style of a police report. Axon says the underlying model has been calibrated to suppress speculation and embellishment, and that it will not invent facts the audio does not contain.
The company has also engineered a set of deliberate friction points, apparently designed to keep the officer engaged rather than passive. Each generated draft is salted with bracketed placeholders, fill-in-the-blank prompts that an officer must either complete or delete before the report can be submitted. The intention is to force a human eye across every paragraph, to make it impossible to submit the machine's work without at least appearing to have read it. At the end sits the crucial ritual: the officer must review the narrative, attest to its accuracy, and sign it. Axon describes this as an “officer-in-the-loop” philosophy, a design in which the algorithm proposes and the human disposes. On paper, nothing has changed about accountability. The officer's signature still means what it has always meant, that the account below it is true to the best of their knowledge.
Axon has also mounted a defence of the product's quality, publishing its own research arguing that Draft One narratives are comparable to officer-written ones and that the company rigorously tests its models to reduce inherent bias before release. The firm's market position lends these assurances unusual weight. Because Axon already supplies the cameras that capture the footage, the evidence-management platform that stores it, and now the model that narrates it, a single vendor increasingly sits astride the entire evidentiary pipeline of an encounter, from the moment a camera is switched on to the moment a sworn report enters the case file. That vertical integration is precisely what makes independent scrutiny difficult, and it is why the question that will not go away matters so much: whether an officer's signature can still carry the same weight when the words above it were composed by something other than the person signing.
The Path of Least Resistance
To understand why researchers are uneasy, it helps to leave policing for a moment and consider a body of work in human-factors psychology that long predates generative artificial intelligence. For decades, researchers studying pilots, radiologists, air-traffic controllers and clinicians have documented a stubborn tendency they call automation bias: the inclination of human operators to over-trust an automated system, to defer to its output even when their own judgement, properly consulted, would contradict it. A closely related phenomenon, sometimes called automation complacency or cognitive offloading, describes what happens when people under time pressure allow a machine to do their thinking for them, quietly outsourcing not just the labour of a task but the vigilance it demands.
The literature is consistent about the conditions that make automation bias worse, and they read like a description of the average patrol shift. Heavy workloads intensify it. Tight deadlines intensify it. So does the sheer cognitive difficulty of verification: the harder it is to check a machine's work against an independent standard, the more likely a tired human is to simply accept it. Humans, as the research bluntly puts it, are cognitive misers. We prefer the simpler path. When a plausible, well-structured, grammatically clean narrative is already sitting on the screen, the effort required to reconstruct events independently, to close one's eyes and recall the smell of the room, the sequence of movements, the exact words exchanged, and to measure that memory against the text, becomes an act of discipline that a busy officer at the end of a long shift has every incentive to skip.
This is the specific risk that critics of AI-generated reports keep returning to. It is not, primarily, the danger that the model will hallucinate a fact, though that danger is real. It is that the mere existence of a fluent draft changes the psychology of the person meant to check it. Reviewing a document you did not write is a fundamentally different cognitive act from composing one. Editing tends to correct surface errors, awkward phrasing, an obvious factual slip, while leaving the underlying structure and framing intact. The officer becomes a proofreader of their own memory, and the machine's version becomes the anchor against which everything else is judged. The report is no longer a reconstruction of what happened; it is a lightly amended transcript of what a language model inferred from a microphone.
The bracketed placeholders that Axon inserts are, in this light, a fascinating admission. They exist precisely because the company understands that officers might otherwise submit a draft without reading it, and they are engineered as a kind of cognitive forcing function, a deliberate obstacle intended to compel attention. But the human-factors research offers a sobering caution about such measures. Forcing functions can raise the floor of engagement without raising its ceiling; an officer who dutifully fills in a blank about the make of a vehicle or the time of an arrest has demonstrated that they scanned the surrounding text, not that they measured its substance against an independent memory of the encounter. Compliance with a prompt is easily mistaken for scrutiny of a claim. The blanks confirm that the officer read the sentence; they cannot confirm that the sentence is true. And because the placeholders draw the eye toward discrete, checkable facts, they may paradoxically steer attention away from the softer and more consequential elements of a narrative, the framing of a suspect's demeanour, the ordering of events, the inference of intent, which is exactly where a language model's interpretive choices do their quiet work and where an error is hardest to catch.
Two Witnesses Collapse Into One
The most articulate version of this concern belongs to the American Civil Liberties Union, and in particular to Jay Stanley, a senior policy analyst with the organisation's Speech, Privacy, and Technology Project, who authored a November 2024 white paper urging departments not to adopt the technology. Stanley's central argument is deceptively simple, and it turns on the idea of evidence as something that must be independent to be valuable.
In the ordinary course of policing, Stanley points out, an encounter that ends up in court generates two distinct records. There is the body-worn camera footage, an imperfect and partial mechanical record that captures some things and misses others. And there is the officer's own account, reconstructed from memory and written into a report. These two records are valuable precisely because they are separate. When they corroborate each other, that agreement means something. When they diverge, the divergence is itself informative, an invitation to ask why the camera saw one thing and the officer remembered another. The friction between the two is a feature of the system, not a flaw.
Draft One, in Stanley's analysis, threatens to collapse that structure. If the police report is essentially an AI rehash of the body-camera audio, then the two records are no longer independent. You do not have a mechanical record and a human recollection that can be checked against each other; you have the mechanical record and a derivative summary of it, dressed in the first person and signed as though it were an independent memory. The corroboration becomes circular. Worse, the ACLU warns, human memory is not a fixed recording but a malleable, reconstructive process, and psychologists have shown for decades that exposure to an external account can reshape a person's recollection of an event. An officer who reads a machine's confident narrative before committing their own memory to paper may find that the narrative quietly overwrites what they would otherwise have recalled. The report does not just record the memory; it contaminates it. Stanley has argued that some of these problems are not merely difficult but, as he puts it, not even theoretically solvable, because you cannot un-ring the bell of having read the machine's version first.
There is a darker corollary that the ACLU has been careful to name. The same mechanism that can overwrite an honest memory can also launder a dishonest account. If an officer does something during an encounter that the camera's audio did not capture, an unjustified use of force framed as compliance, a search conducted without the basis later claimed, the machine cannot narrate what it never heard, and the officer is handed a clean, authoritative-sounding scaffold onto which a convenient version of events can be grafted. The report's machine provenance may even lend it a veneer of objectivity it has not earned. Written justifications for stops and searches exist in part so that supervisors can read them and detect when an officer has strayed beyond the limits of the law; a narrative optimised for fluency rather than candour makes that internal check harder, not easier.
The Draft That Vanishes
If the memory problem is philosophical, the transparency problem is brutally practical, and it is here that the Electronic Frontier Foundation has done its most damaging investigative work. In July 2025, EFF researchers Matthew Guariglia and Dave Maass published the results of a review of public records, user manuals and marketing materials from departments using Draft One, and their conclusion was blunt: the product appears designed to make itself impossible to audit.
The heart of the problem, as the investigators found it in the summer of 2025, was that Draft One did not preserve the draft it generated. In the standard workflow, an officer copied the AI-produced text and pasted it into the department's records system, and the original draft simply disappeared when the window closed. No version was retained showing what the machine had written before the human touched it. No record captured which sentences were the algorithm's and which were the officer's own. As the EFF documented, an Axon senior product manager acknowledged that the company does not store the original draft “by design,” explaining that “the last thing we want to do is create more disclosure headaches for our customers and our attorney's offices.” The deletion of the evidentiary trail, in other words, was not an oversight. It was a selling point.
The consequences ripple outward. When a finished report contains a biased phrasing, a factual error, a misinterpretation or an outright falsehood, there is no way to determine whether the officer or the algorithm introduced it. The audit trail that might allow a judge, a defence attorney, a supervisor or a member of the public to assess how the technology behaves simply does not exist. The EFF found that many departments could not even generate a list of which reports had been produced with Draft One; officers at one Indiana department reported that such reports were not searchable at all. One internal email unearthed by the investigation captured the institutional mood with unusual candour, an administrator writing that “we love having new toys until the public gets wind of them.” Without the ability to separate machine-authored text from human-authored text, the very research that might tell us whether these systems make policing more accurate or less, more biased or less, becomes impossible to conduct. Civil-liberties groups have made the deeper point that opacity of this kind does not merely frustrate researchers; it deprives communities and their elected representatives of the information they would need to decide whether they want the officers who serve them to use such tools at all.
That position has since shifted, and the shift deserves to be recorded as carefully as the original finding. In the release cycle spanning November and December of 2025, Axon added an original-draft retention capability to Draft One, allowing agencies in the United States to retain and later access the original, unedited narrative the model produced. The company's own documentation describes the feature as supporting “legislation that requires organizations to maintain the original AI-generated drafts associated with official police reports,” which is an unusually candid statement of cause and effect. The capability the company had said it deliberately omitted was built because lawmakers came to require it, not because the argument for an audit trail was finally won on its merits. Axon has added other instrumentation alongside it, a Draft One AI-Generated Drafts Report allowing preserved drafts to be exported, and audit-trail entries that record when a draft was requested, when the settings governing retention were altered, and when a draft was downloaded or deleted.
The improvement is real and should be acknowledged as such. But its shape matters as much as its existence. Retention is off by default, a choice Axon explains as being intended to avoid automatically storing drafts before an organisation has updated its policies or retention schedules, and it is switched on, if it is switched on at all, agency by agency. Only the unedited machine version is saved; the intermediate states through which an officer's editing passed are not. Each department decides for itself how long the drafts persist and whether they are purged alongside the associated evidence. What this produces is a patchwork rather than a guarantee. Whether the report in any given case has a preserved original now depends on which state the department sits in and which box an administrator happened to tick, and a defence lawyer cannot know the answer before asking. The absence of an audit trail has become a local policy choice rather than a product-wide certainty, which is unquestionably better than what came before. It is not the same thing as a uniform evidentiary record that a court can rely on being there.
What a Report Is Actually For
It is tempting to treat a police report as mere administrative residue, a bureaucratic formality generated after the real work of policing is done. It is nothing of the kind. In the machinery of American criminal justice, the incident report is one of the most consequential documents a state actor ever produces, and its influence begins early and never really ends.
A report frequently supplies the probable cause that justifies an arrest, the written articulation of facts that a magistrate relies upon to conclude that a crime likely occurred and that this person likely committed it. It shapes the charging decision a prosecutor makes. It becomes part of the discovery that the defence receives, and its contents can be read into evidence at trial. Under the constitutional obligations established by the Supreme Court in Brady v. Maryland and Giglio v. United States, prosecutors must disclose to the defence any evidence that is favourable to the accused or that bears on the credibility of a witness, including the police officers who testify. An officer's report is a primary artefact against which their courtroom testimony is measured; inconsistencies between the two are among the most powerful tools a defence lawyer possesses on cross-examination.
Introduce a machine into the authorship of that document, and a cascade of unfamiliar questions follows. If a report's phrasing originated with a language model, whose statement is it, exactly, for the purposes of the hearsay rules that govern what may be admitted at trial? If a defence attorney wishes to probe how a particular characterisation of the defendant found its way into the sworn narrative, what is there to examine when the draft has been deleted and the prompt engineering behind it is a trade secret? The chain of custody that the law demands for physical evidence, the documented provenance that lets a court trust that a thing is what it purports to be, has no clear equivalent for a narrative that passed through a proprietary model before an officer adopted it as their own. When an officer on the witness stand swears that their report is accurate, is later shown to be wrong, and explains that the artificial intelligence must have made the error, there is, as one prosecutor has warned, no draft to consult that could confirm or refute the claim. The officer cannot fully account for words they did not write, and the defendant cannot fully interrogate an accusation whose origin has been erased.
The ACLU has argued that the disclosure questions run deeper still, reaching past the vanished draft to the entire apparatus behind the report: the way Axon has customised and instructed its language model, the queries it runs, the error rates of the generated output. All of these might, in a given case, constitute material that a defendant is entitled to examine. Yet almost none of it is available for inspection, and much of it is shielded as proprietary. A defendant's Sixth Amendment right to confront the evidence against them was written for a world in which accusations came from people who could be questioned. It is not obvious how that right survives contact with an accusatory narrative whose most influential author is a model that cannot be cross-examined, cannot be placed under oath, and cannot be asked why it chose one word rather than another.
The federal courts have begun, slowly, to respond. The Advisory Committee on Evidence Rules has proposed a new Federal Rule of Evidence 707, which would take machine-generated evidence offered without a supporting human expert and subject it to substantially the standard that already governs expert testimony: that the output rests on sufficient facts or data, that it is the product of reliable principles and methods, and that those methods have been reliably applied to the facts of the case. It is a sensible instrument, and the pace of it is the point. The public comment period closed on 16 February 2026, and even on the most favourable procedural timetable the rule could not take effect before 1 December 2027. Deployment is measured in months and rule-making in years, and in the interval between the two the reports are being written, filed, charged upon and relied upon regardless. The law will arrive, in the way that law does, some time after the thing it governs has become ordinary.
A Taxonomy of Ways This Goes Wrong
The academic literature has begun to catch up with the deployment, and in March 2026 a group of British researchers published one of the most systematic attempts yet to map the hazards. The paper, titled “Responsible AI in criminal justice: LLMs in policing and risks to case progression” and posted to the arXiv preprint server, was written by Muffy Calder, Michele Sevegnani and Evdoxia Taka of the School of Computing Science at the University of Glasgow, together with Marion Oswald of Northumbria Law School and Elizabeth McClory-Tiarks of Newcastle University. Grounded in the law and policing structures of England and Wales rather than the United States, it nonetheless offers a framework that travels well across jurisdictions.
The researchers catalogue fifteen distinct policing tasks that large language models could be used to perform, and seventeen categories of risk that arise from doing so, illustrating them with more than forty worked examples of how a given failure might damage a case as it moves through the system. The risks they identify range across the whole pipeline. Some concern the outputs themselves: erroneous omissions or additions that quietly alter the strength of a case, factual inaccuracies, inappropriate linguistic style that undermines the integrity of a statement, cultural and dialectal misinterpretations, and the social and cultural biases, including racial and victim-blaming biases, that models are known to reproduce. Others concern the inputs, such as the design of prompts and the vulnerability of systems to injection, jailbreaking and the leakage of sensitive information to third parties. Still others concern the near-impossibility of proper evaluation, because there is often no objective ground truth against which a generated narrative can be measured, and the systems-engineering reality that models are updated and reconfigured in undocumented ways that make yesterday's output impossible to reproduce.
Two of their categories bear directly on the evidentiary anxieties raised on the American side of the Atlantic. One concerns what they call intermediate unused material: the draft versions and discarded outputs that, under disclosure rules, may create precisely the burdens Axon has designed its product to avoid. Another concerns the acute shortage of qualified expert witnesses able to explain to a court how such a tool actually works, a problem that compounds as the tools grow more numerous and are chained together, each feeding its output into the next until no single human understands the whole pipeline. The paper stops short of declaring the technology unusable; its authors suggest that many of these risks could be reduced as good practice is agreed and systematically applied. But the sheer length of the list is itself an argument, a reminder that a fluent paragraph produced in seconds carries a long tail of ways in which it can quietly corrupt the record it was meant to serve.
It is worth setting that taxonomy against the failures that have actually surfaced in the field, because the most widely reported of them is instructive for entirely the wrong reasons. In December 2025 the Heber City Police Department in Utah began testing Draft One alongside a second tool called Code Four. In early January 2026, one of the generated reports recorded that an officer had been turned into a frog. The system had picked up the audio of the Disney film “The Princess and the Frog”, playing in the background of a body-camera recording, and folded it into the narrative as though it were an account of events. A department sergeant caught the error and corrected it, observing that the department does not employ amphibious officers. The department intended to carry on with the software regardless, citing an estimated six to eight hours saved each week.
The story travelled because it is funny, and its comedy is precisely what makes it unrepresentative of the danger. An officer transformed into an amphibian is caught instantly, because nothing in a police report could be further from the plausible; the error announces itself. The failures that should worry a court are the ones that do not. A sentence attributed to the wrong speaker, a characterisation of a suspect's demeanour hardened by a degree or two, a sequence of events reordered so that a movement appears to precede rather than follow a command: all of these read exactly like the truth, and they survive a tired officer's review at the end of a shift for the same reason, which is that nothing about them signals that they should not. This is where automation bias does its damage. A reviewer's attention is a finite resource, spent most readily on what looks wrong, and a fluent, confident, well-formed falsehood looks like nothing at all.
The Ledger of Independent Evidence
Set against this catalogue of risks is the promise that supposedly justifies accepting them: time. Axon's core pitch is efficiency, the claim that Draft One can roughly halve the hours officers spend writing reports and return that time to the street. It is a seductive proposition for chronically short-staffed departments. It is also, according to the independent evidence gathered so far, largely unsubstantiated.
The most rigorous critic of the efficiency claim is Ian T. Adams, a criminology professor at the University of South Carolina and himself a former police officer, who has become something close to the field's designated empiricist. In a study circulated on the CrimRxiv preprint platform, Adams and colleagues recruited ninety-two senior law-enforcement officers, sergeants and above, with an average of twenty-two years of experience approving reports, and asked them to evaluate eighty police reports, twenty of which had been drafted using Draft One. The results were not kind to the technology. Reviewers rated the AI-assisted reports significantly worse on accuracy, a finding that was statistically significant and substantively meaningful; the estimated effect moved a report from roughly the fiftieth to the thirty-sixth percentile on perceived accuracy. On broader composite measures of quality, the machine-drafted reports showed no reliable improvement, and expert reviewers proved unable to distinguish AI-written from human-written reports at a rate better than chance.
On the central question of time saved, Adams has been withering, summarising the state of the evidence with the observation that there is not a single independent evaluation supporting the vendor claims being made to police departments. His own earlier work found that Draft One produced no measurable time savings, and a separate evaluation of a different AI report-writing tool reportedly found not a saving but an increase of some eighteen and a half minutes per incident. The field experience appears to bear him out. The Anchorage Police Department, after a three-month trial, abandoned Draft One, its deputy chief explaining that the department had hoped the tool would deliver significant time savings for officers but had simply not found that to be the case. The reason offered was instructive: because the system works from audio alone, it routinely missed the visual details officers had observed but never spoken aloud, forcing them to add material by hand and eroding whatever efficiency the automation had promised. Body-camera audio, it turns out, is a thin and partial record of a physical encounter, and building a legal narrative on it requires precisely the independent human reconstruction that the tool was supposed to make unnecessary.
Anchorage is no longer alone. Manchester, New Hampshire, the first agency in the country to test Draft One and the department that supplied the officers for Adams's randomised trial, has abandoned it as well. Lieutenant Matthew Barter, who took part in the research, put the reason with a plainness that no vendor presentation can easily absorb: it was simply easier for officers to type the report themselves.
A more recent picture of how these systems behave in daily use arrived in July 2026, when the reporter Thomas Brewster published a Forbes investigation built on emails obtained under public-records law, covering seven months of testing at the Lafayette Police Department in Indiana. The product at issue there was not Draft One but Form One, a separate and newer Axon tool that listens to body-camera audio and populates the structured fields of a form rather than composing a narrative, and the distinction is worth holding onto, because the complaints were nonetheless familiar. Officers reported that the system repeatedly failed to capture names and vehicle registration plates that were clearly audible in the footage, and that a form which had taken thirty seconds to complete by hand now took three minutes, because of the volume of corrections the machine's version required. Axon characterised the deployment as early access to a product that was not yet finished, which may well be true. It is also true that the same pattern has now recurred across two products of quite different design, which suggests that the constraint does not lie in the software but underneath it. Audio is a thin record of a physical event, and no amount of model improvement can recover from a microphone the details that were never spoken aloud.
The research Adams began has meanwhile moved out of preprint and into the peer-reviewed literature, which matters because it removes the last easy objection to it. The randomised controlled trial, published in the Journal of Experimental Criminology under the title “No man's hand: artificial intelligence does not improve police report writing speed”, followed eighty-five officers and seven hundred and fifty-five reports, and buttressed the experimental result with a difference-in-differences robustness check across 6,084 reports written over a full year. It found no significant effect on the time taken to write a report. The single quantity on which the entire commercial case for the technology rests did not move.
The companion paper is the more unsettling of the two. Under the title “Writing at the speed of hype: officers' post-experimental perceptions of AI report writing”, also in the Journal of Experimental Criminology, a team led by Hunter M. Boehme and including Adams, Barter, Irick A. Geary and Kyle McLean asked the officers who had taken part what they made of the tool, and found that their perceptions and the measurements had come apart. Roughly forty-eight per cent of the officers who used it reported that it had saved them time. Supervisors perceived improvements in the quality and completeness of the reports they were approving. The trial data showed no such effect on any of these dimensions.
This is the empirical heart of the matter, and it deserves stating without hedging. The tool reliably produces the feeling of time saved without the fact of it. Nearly half the officers who used it came away convinced that a burden had been lifted, while the clock recorded that nothing had been lifted at all, and their supervisors believed the reports had improved when, by the study's measures, they had not. A technology that generates a sense of effortlessness while measurably changing nothing about the duration of the task is not simply a productivity tool that has failed to deliver. It is something more specific and considerably more troubling, because that is precisely the profile of a system that lowers vigilance rather than workload. The subjective experience of ease has to come from somewhere, and if it is not coming from the clock, the most parsimonious explanation is that it is coming from effort, from the attention an officer no longer spends reconstructing an event because a plausible reconstruction is already sitting on the screen. That is automation bias observed not as a laboratory prediction but as a field measurement, and it is also the mechanism by which three hundred thousand hours can be sincerely reported on a customer survey and still not exist.
The Prosecutors Who Said No
Perhaps the most telling resistance has come not from privacy advocates or academics but from within the criminal justice system itself, from the prosecutors whose cases depend on the reliability of the reports they receive. In 2024, the King County Prosecuting Attorney's Office in Washington State, which covers Seattle, circulated guidance instructing local law-enforcement agencies not to use AI to draft narrative reports, and warning that reports written with the assistance of such tools would be rejected. The memo, issued by Chief Deputy Prosecutor Daniel J. Clark, was careful to strike a measured tone. “We do not fear advances in technology,” Clark wrote, “but we do have legitimate concerns about some of the products on the market now.”
Those concerns were concrete rather than reflexive. Clark noted that errors could easily slip past a reviewing officer confronting a volume of material under deadline, the very automation-bias dynamic the human-factors literature predicts. He warned of the scenario in which an officer testifies that their report is accurate, is shown to be wrong, and attributes the mistake to the artificial intelligence, at which point there would be no preserved draft to establish whether the machine or the human was truly responsible, with consequences that could be devastating for the case, the community and the officer alike. He raised questions about whether the products complied with the security requirements governing criminal-justice information. It was not a Luddite's rejection; Clark acknowledged that a day would likely come when such tools could assist prosecutors in valuable, time-saving ways. It was a judgement that the day had not yet arrived.
Legislatures have begun to move as well, and the shape of their response is revealing. Rather than banning the technology, the first statutes have targeted precisely the transparency deficits the EFF identified. Utah moved first, enacting Senate Bill 180, which took effect on 7 May 2025 and made it the first state in the country to legislate on the question. The statute requires that AI-authored reports carry a disclaimer, that officers certify their accuracy, and that agencies maintain a written policy governing their use of generative artificial intelligence. California went further. In October 2025, Governor Gavin Newsom signed Senate Bill 524, which took effect on the first day of 2026. The law requires that any report generated wholly or partly by artificial intelligence identify every AI programme used and carry a prominent disclosure stating that “This report was written either fully or in part using artificial intelligence,” alongside the signature of the officer verifying that they reviewed it and that its facts are true. Crucially, it also requires departments to retain the first draft, so that judges, defence attorneys and auditors can see which portions of the final report were written by the machine and which by the officer, and it forbids vendors from selling or sharing the data that agencies feed into their systems. In a single provision, California legislated into existence the audit trail that Axon had assured its customers was deleted by design, and within weeks the company had built it. The mandate came first and the capability followed, which is to say that the law extracted from the vendor precisely what its customers had been told was deliberately unavailable. Observers of the field expect other states to follow California and Utah, and the coming years are likely to see a patchwork of disclosure requirements harden into something closer to a national norm.
Whose Words Are They, Anyway
Return, at the end, to the officer at the terminal, reading a report they did not write and preparing to make it their own. The deepest difficulty with Draft One is not that a language model is imperfect, nor even that its drafts vanish, though both matters gravely. It is that the technology quietly relocates the point at which a human mind independently reconstructs the truth of an event, and it relocates it to a place where that reconstruction may never actually happen.
The traditional police report, for all its well-documented flaws, its biases, its self-serving omissions, its occasional dishonesty, rested on a particular premise: that a human being had sat down and tried, from their own memory, to render an account they were willing to swear to. The account might be wrong, but it was theirs, and its wrongness could be probed, cross-examined, contradicted by the footage, tested against the physical evidence. What automation threatens is not the accuracy of that account so much as its independence, the quality that made it worth having as a separate thing in the first place. When the first draft is machine-made, the officer's signature attests less to an act of recollection than to an act of ratification. The human remains in the loop, but the loop has been redrawn so that the human's role is to approve rather than to author.
And this is where the question of responsibility becomes genuinely hard to answer. If an AI-drafted narrative shapes a prosecution, subtly framing an ambiguous encounter, importing a characterisation the officer would not independently have chosen, embedding a bias the model absorbed from its training data, who is answerable? The officer signed it and is formally accountable, yet cannot fully explain the provenance of words they did not compose. The vendor built the model but disclaims responsibility for how any given department deploys it, and has arranged matters so that the evidence needed to trace an error back to its source no longer exists. The prosecutor introduces the report but may not know it was machine-drafted at all. The defendant, who has the most at stake, is left interrogating a sworn account whose true author is a proprietary system they will never be permitted to examine. Everyone is partly responsible, which is another way of saying that no one quite is.
That diffusion of accountability, more than any single hallucinated fact, is what should give a society pause before it lets the most basic evidentiary unit of its justice system be drafted, first, by a machine that remembers nothing and can be asked nothing, and then quietly forgotten. The efficiency gains, on the current evidence, are illusory. The risks to the reliability of the record are not. And a criminal justice system that cannot say, with confidence, who wrote the accusation, has surrendered something that no amount of saved time can buy back. The remedy is not necessarily to forbid the machines outright, but to insist that they leave a trace, that the draft survive, that the human account precede rather than follow the algorithm's, and that the person on the stand be able to say, truthfully, that the words are their own. Until then, every signature at the bottom of an AI-drafted report is a small act of faith in a witness who cannot testify.
References
- Axon Enterprise, “Draft One” product page. https://www.axon.com/products/draft-one
- Axon Enterprise, “Axon reimagines report writing with Draft One, a first-of-its-kind AI-powered force multiplier for public safety,” 23 April 2024. https://investor.axon.com/2024-04-23-Axon-reimagines-report-writing-with-Draft-One,-a-first-of-its-kind-AI-powered-force-multiplier-for-public-safety
- Axon Enterprise, “Auditing and reporting,” Draft One product guide. https://www.axon.com/help/draft-one/software/draft-one/auditing-reporting.htm
- Matthew Guariglia and Dave Maass, “Axon's Draft One Is Designed to Defy Transparency,” Electronic Frontier Foundation, July 2025. https://www.eff.org/deeplinks/2025/07/axons-draft-one-designed-defy-transparency
- Electronic Frontier Foundation, “AI Police Reports: Year In Review,” December 2025. https://www.eff.org/deeplinks/2025/12/ai-police-reports-year-review
- Electronic Frontier Foundation, “Anchorage Police Department: AI-Generated Police Reports Don't Save Time,” March 2025. https://www.eff.org/deeplinks/2025/03/anchorage-police-department-ai-generated-police-reports-dont-save-time
- Jay Stanley, “AI-Generated Police Reports Raise Concerns Around Transparency, Bias,” American Civil Liberties Union. https://www.aclu.org/news/privacy-technology/ai-generated-police-reports-raise-concerns-around-transparency-bias
- American Civil Liberties Union, “Police Departments Shouldn't Allow Officers to Use AI to Draft Police Reports” (white paper), November 2024. https://assets.aclu.org/live/uploads/2024/12/Automated-Police-Reports-1291.pdf
- American Civil Liberties Union, “Studies Question Value of AI-Assisted Police Reports.” https://www.aclu.org/news/privacy-technology/studies-question-value-of-ai-assisted-police-reports
- Muffy Calder, Marion Oswald, Elizabeth McClory-Tiarks, Michele Sevegnani and Evdoxia Taka, “Responsible AI in criminal justice: LLMs in policing and risks to case progression,” arXiv:2603.18116, March 2026. https://arxiv.org/abs/2603.18116
- Ian T. Adams, Matt Barter, Kyle McLean, Hunter M. Boehme and Irick A. Geary, “No man's hand: artificial intelligence does not improve police report writing speed,” Journal of Experimental Criminology. https://doi.org/10.1007/s11292-024-09644-7
- Hunter M. Boehme, Ian T. Adams, Matt Barter, Irick A. Geary and Kyle McLean, “Writing at the speed of hype: officers' post-experimental perceptions of AI report writing,” Journal of Experimental Criminology, 2025. https://doi.org/10.1007/s11292-025-09679-4
- Ian T. Adams et al., “A Good College Essay but a Bad Police Report: A Triple-Blind Expert Evaluation of AI-Assisted Police Reporting,” CrimRxiv. https://www.crimrxiv.com/pub/u7azgqzd/release/1
- Thomas Brewster, “Axon Says AI Police Reports Save Time. Public Records Show They Get Facts Wrong,” Forbes, 22 July 2026. https://www.forbes.com/sites/thomasbrewster/2026/07/22/axon-says-ai-police-reports-save-time-public-records-show-they-get-facts-wrong/
- Axios Salt Lake City, “How AI turned a Utah police officer into a frog,” 7 January 2026. https://www.axios.com/local/salt-lake-city/2026/01/07/ai-police-utah-heber-city-princess-frog
- “Prosecutors in Washington State Warn Police: Don't Use Gen AI to Write Reports,” Electronic Frontier Foundation, October 2024. https://www.eff.org/deeplinks/2024/10/prosecutors-washington-state-warn-police-dont-use-gen-ai-write-reports
- KOMO News, “AI-assisted police reports not welcome in King County due to error concerns.” https://komonews.com/news/local/king-county-prosecutor-tells-police-not-to-use-ai-artificial-intelligence-for-official-reports-for-now-errors-concerns-law-enforcement-perjury-criminal-justice
- Utah Senate Bill 180 (2025), law enforcement use of generative artificial intelligence.
- California Legislature, Senate Bill 524, “Law enforcement agencies: artificial intelligence.” https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB524
- Electronic Frontier Foundation, “Victory! California Requires Transparency for AI Police Reports,” October 2025. https://www.eff.org/deeplinks/2025/10/victory-california-requires-transparency-ai-police-reports
- United States Courts, Advisory Committee on Evidence Rules, proposed Federal Rule of Evidence 707 (machine-generated evidence).
- GovTech, “ACLU Slams AI Police Reports, and Axon in Particular.” https://www.govtech.com/biz/aclu-slams-ai-police-reports-and-axon-in-particular

Tim Green UK-based Systems Theorist & Independent Technology Writer
Tim explores the intersections of artificial intelligence, decentralised cognition, and posthuman ethics. His work, published at smarterarticles.co.uk, challenges dominant narratives of technological progress while proposing interdisciplinary frameworks for collective intelligence and digital stewardship.
His writing has been featured on Ground News and shared by independent researchers across both academic and technological communities.
ORCID: 0009-0002-0156-9795 Email: tim@smarterarticles.co.uk
Listen to the free weekly SmarterArticles Podcast








