What has to be preserved when an officer uses AI to draft a report?

By Verillian. Published . Updated .

Keep what the tool was given, the AI’s first draft, and who used it. California requires keeping the draft and an audit trail; Utah requires a disclaimer.

A long aisle of labelled wooden file drawers in a records room.

When an officer uses AI to draft a report, what the tool was given, the AI’s own first draft before anyone touched it, and a record of who used the tool all need to survive past the moment of filing. Then anyone checking the report later can see what changed before an officer signed the final version.

California already requires agencies to keep the first draft and an audit trail naming the person who used the AI and any footage it drew on.

Utah requires a disclaimer on the report and the author’s certification that it was reviewed for accuracy, but not that the draft be kept. As far as we can tell, no other state has a statute written for AI-drafted reports as of November 2026, and the CJIS Security Policy has no provision written for them.

Whether that surviving record is later discoverable to the defense is a question for state discovery and Brady rules, but a record that was never kept cannot be produced either way.

What changed between the AI draft and the filed report, and how do you show it?

Keep both documents, the AI’s first draft and the filed report. That is what makes the difference between them visible later, to a supervisor, an auditor, or defense counsel.

California’s SB 524, chaptered as Penal Code section 13663, sets the clearer floor here. It defines a report’s first draft as “the initial document or narrative produced solely by artificial intelligence” and requires the agency to retain that first draft for as long as the official report itself is retained.

Except for the signed official report, no draft created with AI may be treated as the officer’s statement. The first draft and the filed report are two different documents by design.

Utah’s SB 180 does not go that far. It requires a disclaimer on any report created wholly or partly with generative AI, and a certification from the author that they reviewed it for accuracy, but it does not require the first draft itself to be kept.

Under Utah’s statute alone, an agency can meet the letter of the law and still have nothing left to compare the filed report against once the AI’s original output is gone.

Whether either document, the AI’s first draft or the audit record around it, is discoverable to the defense is decided by the jurisdiction’s own discovery rules and, in a criminal case, by Brady v. Maryland’s disclosure obligations for material favorable to the defense.

That is a state-by-state and often a case-by-case question. The retention requirement settles a narrower question that comes first, whether the record exists at all for a court to ever rule on.

Who is accountable for what the AI was given?

The officer who signs is accountable for the content, and the agency’s audit trail records who used the tool. California’s statute requires the signature of the officer or agency member who prepared the report, “verifying that they reviewed the contents of that report and that the facts contained in the official report are true and correct.”

That signature is what makes the report the officer’s statement at all. Separately, California requires the agency’s audit trail to identify the person who used artificial intelligence to create the report and, if any, the video or audio footage used to create it.

That audit trail is its own record, and losing it creates a different problem.

Utah folds both into one certification, in which the author of the report certifies they read and reviewed it for accuracy.

Utah also places a second layer of accountability on the agency itself, which must maintain a policy naming which generative AI technologies staff may use, for which tasks, with an acknowledgment that violating the policy can bring administrative discipline. Neither state makes the vendor accountable for what a report says.

California does reach the vendor on a different point. A contracted vendor may not share, sell, or otherwise use the information an agency gives its tool except for the agency’s own purposes or under a court order, though it may still access the processed data for troubleshooting, bias mitigation, accuracy improvement, or system refinement.

Preservation and discoverability are two different questions. A department controls the first one. It can keep the input, the first draft, and a record of who touched it. Whether a court later orders that record produced is a separate question that state discovery rules and Brady decide, case by case.

What does state law require?

As far as we can tell, as of November 2026, California and Utah are the only two states with a statute specifically addressing AI-drafted police reports, and what each one asks for is different enough that treating them as interchangeable would be a mistake.

RequirementCalifornia (Penal Code sec. 13663, SB 524)Utah (Code sec. 53-25-901, -902, SB 180)
EffectiveJanuary 1, 2026May 7, 2025
Disclosure on the reportRequired, on each page or in the body, with a stated sentenceRequired, a disclaimer that the record contains AI-generated content
Officer sign-offSignature verifying review and accuracyCertification that the author reviewed for accuracy
First-draft retentionRequired, as long as the official report is retainedNot required
Audit trail of who used AIRequired, plus footage used, if anyNot required
Agency AI use policyOnly a policy requiring the disclosure and signature aboveRequired, naming permitted tools and tasks
Vendor data restrictionsNo sharing, sale, or other use beyond agency purposes or a court order; access for troubleshooting, bias mitigation, accuracy, and refinement allowedNot addressed

Neither statute reaches an agency outside its own state, and as far as we can tell, no other state has enacted an equivalent law as of November 2026. Bills have been introduced elsewhere, and prosecutors have moved without a statute.

At least one prosecutor’s office has told agencies it will not accept reports drafted with AI. Connecticut’s Chief State’s Attorney told a state board in 2026 that, with the support of the state’s police chiefs, he and the state’s attorneys “imposed a moratorium on the use of AI programs to draft, author and/or narrate criminal reports.”

Broader AI laws could touch a department too, depending on each law’s own text and scope, so confirm the current rule in your own state.

How long must the first draft be kept?

In California, for as long as the official report is retained, and the department’s own retention schedule decides how long that is. Utah sets no retention duty on the draft.

Where CJIS also applies, its one-year floor for audit records runs alongside, so keep the audit trail for the longer of the two. How the two clocks fit together.

What does a defensible audit trail contain?

Put the two layers together and the list is short:

  • Who used the tool. A specific person, per California’s audit trail and CJIS’s requirements that users be uniquely identified (IA-2) and that audit records establish the identity of the individuals associated with each event (AU-3).
  • What happened, and when. The type of event, when and where it occurred, its source and its outcome (AU-3), with time stamps from the system clock (AU-8).
  • Which footage the tool drew on, if any. California’s addition, not required by CJIS.
  • How the record is protected. CJIS control AU-9 requires audit information to be protected from unauthorized access, modification and deletion.
  • How long it’s kept. The longest retention period that applies to your agency.

What should a department’s AI policy require for record keeping?

Even where no statute requires it yet, the two enacted laws describe a floor worth meeting voluntarily. A department writing or updating its own AI use policy should require, at minimum:

  • Name the tool and the task. Utah’s statute requires an agency’s policy to say which generative AI technologies staff may use and for which tasks. A policy that only says “AI use must be reviewed” does not meet even that floor.
  • Keep the input and the first draft, not only the signed report. Whatever the tool was given, footage, dictation, or notes, and whatever it produced before anyone edited it, retained for as long as the filed report itself is retained. California requires that for the first draft, along with an audit trail naming any footage used, and it is a reasonable standard to adopt regardless of where the department sits.
  • Log identity and timing separately from content. Who ran the tool, on which report, and when, is a fact about the process, not about the narrative, and it needs its own record so it survives even if the report is later amended.
  • Require a named person to certify the final version. In substance, both enacted statutes require a signature or certification that a specific person reviewed the content and stands behind its accuracy.
  • Use the report’s own retention schedule, not a separate one made for AI. A generation record that expires before the case file it supports is not there when discovery finally asks for it.
  • Treat the vendor agreement and the audit record as two different documents. A services contract can restrict what a vendor does with agency data, and California’s statute already restricts the vendor directly, but a contract is not itself a log of who used the tool on which report. One does not substitute for the other.

What does the CJIS Security Policy say about AI-drafted reports?

The CJIS Security Policy, at version 6.1 (June 25, 2026), has no provision written for AI-drafted reports or for generative AI. Its one mention of artificial intelligence is in the discussion of malicious code protection (SI-3), as a technique malware detection can use. That is not really a gap.

The policy applies to every entity with access to criminal justice information or that operates systems used to process, store, or transmit it, so an AI report-writing tool that receives CJI is such a system, and the policy’s audit and accountability controls apply to it as to any other, with no AI-specific exception and no AI-specific extra requirement.

What that means for an agency’s own CJIS audit is covered in CJIS audit requirements for AI use. CJIS sets the floor for controlling and auditing access to criminal justice information, and California’s and Utah’s report-specific statutes sit on top of it.

Sources

  • California Penal Code section 13663, added by SB 524 (2025 to 2026 Regular Session), chapter 587, Statutes of 2025, approved by the Governor and filed with the Secretary of State October 10, 2025. Chaptered bill text, read September 25, 2026.
  • Utah Code sections 53-25-901 and 53-25-902, enacted by SB 180 (2025 General Session, chapter 330) as sections 53-25-601 and 53-25-602 and numbered 901 and 902 in the Utah Code, effective May 7, 2025. Enrolled bill text and current code section, read September 25, 2026.
  • CJIS Security Policy, version 6.1, June 25, 2026, FBI Criminal Justice Information Services Division. Full policy text, read September 25, 2026.
  • Connecticut Division of Criminal Justice, news story of April 30, 2026, read November 3, 2026.

What record does Verillian keep?

Every AI request Verillian captures on an enrolled device is a signed record on your department’s own servers, each entry naming the person assigned to the enrolled device, the device and the time.

What Verillian does for public safety agencies

See Verillian govern AI on a real device.