Search "Code Four vs Axon" and you are weighing two AI report drafting tools: Code Four REPORT and Axon Draft One. Both turn bodycam recordings into a first draft the officer reviews, edits, and owns. The scope before the verdict:

• The two products buyers cross-shop: Code Four REPORT and Axon Draft One.
• Not this page: "code four" the radio phrase, Axon the programming language, and Axon body-camera hardware.
• The lens that decides it: the software stack your agency already runs.

Disclosure: CLIPr publishes this comparison and offers a separate report-drafting option shown for reference. Its claims are held to the same evidence bar as Code Four and Axon.

The right workflow also depends on the material officers begin with. During evaluation, test representative body-camera audio, officer dictation, typed notes, and uploaded audio clips instead of assuming every report starts from the same input.

Code Four REPORT vs Axon Draft One at a Glance

The comparison below is a dependency-first decision tool, not a scorecard: the installed stack is the first branch, then input and traceability requirements decide the path.

Each section below carries its own three-way table. The Code Four and Axon columns hold the conditional fit guidance; a third CLIPr (for reference) column shows where a camera-agnostic overlay would sit, since CLIPr publishes this guide.

The decision at a glance

Decision criterion			CLIPr (for reference)
Inputs and review	Multimodal inputs; first draft with statement-to-source links; officer verifies, edits, approves	Audio-powered inputs; side-by-side review, required acknowledgment, supervisor path	Audio-first from existing cameras; officer remains author of record
Integration and deployment	Named RMS, CAD, API paths; subscription pilot on the wider family	Native Evidence, Records, Standards; add-on inside the Axon stack	Camera-agnostic overlay; drag-and-drop pilot live within a shift
Public price reference	$50 per officer per month (vendor-published)	Quote-based; one published agency quote (Laramie, 2024)	Usage-based: audio $0.105/min, video $0.21/min
Where each fits best	Greenfield or mixed-stack agency not locked into Axon, wanting multimodal inputs and source-linked review	Agency already standardized on Axon Evidence, with the required Draft One licenses, wanting native controls	The third option to shortlist: starts light on the camera fleet you already run, draft-first, priced on utilization

Compiled from current public vendor documentation and procurement records. The CLIPr column reflects CLIPr's own published materials. Re-verify every line in procurement.

Product Scope and Source Inputs

Code Four's product page says REPORT builds a first draft from a wide set of inputs (vendor-reported), and describes a video language model that analyzes frames, audio, and visual content together. INSIGHTS and Flash stay outside this comparison unless contractually part of the REPORT deal.

Axon documents an audio-powered workflow for Draft One (April 2026 records release notes), and its product guide (updated May 28, 2026) states Draft One can use any playable file Axon Evidence supports, so Axon cameras are not strictly required.

One distinction keeps this fair both ways: accepting a playable video file is not the same as analyzing visual events, so Axon's file support is not visual analysis, and Code Four's is not a tested result.

Either way, audio quality is the shared foundation, which is why how bodycam transcription software handles accuracy matters. Scoping wider? These police report writing software evaluation criteria apply beyond this pair.

Scope and inputs, side by side

Scope and inputs			CLIPr (for reference)
Inputs the draft draws on	Multimodal: video, transcripts, metadata, dispatch/CAD, notes, photos (vendor-reported)	Audio-powered: recordings, narration or notes, selected evidence, report fields (published)	Field and bodycam audio, transcribed and speaker-identified
Visual analysis and footage source	Video language model (vendor-reported, not tested); named camera and evidence paths	Audio-powered; visual analysis not documented; Axon Evidence plus playable files	Audio-first; any fleet including Axon, Motorola, Getac, Reveal, i-PRO

Officer Review and Source Verification

Both vendors keep the officer as the author, the load-bearing part of this category. Code Four describes its output as a first draft: officers verify facts, edit, and approve, and its enterprise terms (updated December 23, 2025) keep the officer responsible for signing.

Its pages also describe statement-to-source links and timestamps (vendor-reported).

Review workflow, side by side

Officer review			CLIPr (for reference)
Ownership and sign-off	Officer verifies, edits, and signs (enterprise terms hold the officer responsible)	Officer edits; required acknowledgment; side-by-side review, supervisor path in Records or Standards	Officer reviews, edits, and remains author of record; nothing files itself
Tracing back to the evidence	Statement-to-source links and timestamps (vendor-reported)	Side-by-side review; statement-level links not documented	Speaker-identified, timestamped transcripts to search and cross-check

Axon documents a required acknowledgment before a draft becomes a report and a supervisor path in Records or Standards; its FAQ says drafts can contain mistakes and require sign-off. Neither workflow files anything itself: under both, the officer reviews, edits, approves, and owns the report.

Retention, Version History, Audit, and Reporting

Retention, version history, audit events, and usage reporting answer different questions, so evaluate them separately, not as one "audit" feature.

Retention and audit, side by side

Retention and audit			CLIPr (for reference)
Retention and versions	Versioned drafts claimed (deployment-specific); agency decides retention, subject to contract	Original-draft retention optional, off by default, original only; agency decides within those defaults	Customer retains ownership per CLIPr's published terms; agency sets retention in procurement
Audit events	Immutable logs: login, access, generation, edits, approvals (published)	Request and sign-off events, usage reports, downloads, deletions (published)	SOC 2 compliant architecture; audit posture verified in the agency review

Per Axon's auditing and reporting guide (updated June 10, 2026), the precision that matters is this: Axon's original-draft retention is optional, off by default, and saves only the original unedited AI draft; edited versions are not saved.

This control has a public history: in July 2025 the Electronic Frontier Foundation argued that Draft One's handling of original drafts frustrated public-records transparency, and Axon's current guide documents the setting and its defaults.

Whether the configured behavior satisfies your records obligations is an agency decision, not a vendor default.

Camera, Evidence, CAD, and RMS Fit

Compare the actual data path, not vendor adjectives.

Integrations, side by side

Integrations			CLIPr (for reference)
Camera fleet	Named camera and evidence paths for mixed fleets	Native to Axon Evidence; playable third-party files accepted	Camera-agnostic; CLIPr names Axon, Motorola, Getac, Reveal, and i-PRO among supported vendor families. Verify the exact model, export, metadata, and handoff in the pilot.
RMS and CAD path	Named RMS, CAD, API paths (deployment-specific); validate the exact path in your environment	Native Records or Standards, or narrative copied into a third-party RMS	Overlay beside the existing RMS; not an RMS, CAD, or DEMS

Code Four's integrations page names Axon Evidence, Motorola, Getac, JailCore, Securus, Tyler Technologies, Mark43, Motorola PremierOne, middleware, and custom APIs (vendor-published). A named vendor is a starting point, not a validated connection.

For either product, verify the boring specifics before contract: camera model, file type, and metadata; export permissions and API entitlement; data-flow direction and field mapping; retries, duplicates, and latency; and support ownership and added cost.

Pricing and Total Cost

Every public number below carries a date and a context, and none is your quote.

• Axon does not publish a rate card for Draft One. Cooperative contracts (for example, the OMNIA Partners Axon contract, 3544-21-4615) publish pricebooks with contract-maximum rates; request the current pricebook, since a ceiling is not a quote. Its documented prerequisites (Draft One add-on, Unlimited Auto-Transcribe, and Evidence Pro, with Respond+ for LTE upload) change the math.
• A dated agency example shows the line items. A July 19, 2024 City of Laramie quote for 56 licenses lists Draft One at $68.47, Respond+ at $20.86, and Unlimited Auto-Transcribe at $21.91 per license-month, a historical negotiated quote, not current standard pricing.

Normalize before comparing anything:

annual evaluated cost = licenses + prerequisites + processed usage + storage + implementation + integrations + support + training + internal review labor + export and termination costs

Pricing, side by side

Pricing			CLIPr (for reference)
Reference and model	$50 per officer per month (vendor-published); per-officer subscription	Quote-based, one published agency quote (Laramie, 2024); per-license plus add-ons	Usage-based (audio $0.105/min, video $0.21/min); unused capacity carries forward
Prerequisites	Subscription; confirm specifics in a quote	Add-on, Unlimited Auto-Transcribe, Evidence Pro; Respond+ for LTE upload	None to start; 30-day agency pilot, subject to approval, with no dock required for the initial upload workflow

Security, Privacy, and Contract Evidence

Treat this section as a gate, not a scoring category: a product either produces the evidence your agency requires or it does not advance, and publication volume is not a quality score. Code Four's published set includes a data processing agreement (DPA) summary; Axon adds a broader trust portal.

Security posture, side by side

Security posture			CLIPr (for reference)
Published materials	Encryption and authentication, roles, audit, DPA summary, subprocessors, incidents	Data-location, audit, retention detail, plus a broader trust portal	SOC 2 compliant architecture; documentation supplied during procurement
Compliance and ownership	Agency-level CJIS review; ownership per contract and DPA terms	Agency-level CJIS review; ownership per contract and trust-portal terms	CJIS Security Policy-aligned, reviewed at agency level; customer retains ownership per CLIPr's published terms

Frameworks like the FBI's Criminal Justice Information Services (CJIS) Security Policy apply to the whole deployment, so evaluate them as agency-level reviews rather than vendor badges.

This guide to law-enforcement data compliance covers how to run that evidence request evenly; do not draw a certification conclusion for either vendor from public marketing.

What Independent Evidence Shows, and How to Validate Locally

No independent Code Four versus Axon head-to-head was found in this review, and results vary by agency, case mix, and rollout, so the number that matters is the one you measure on your own reports.

Independent local reporting from The Maine Monitor, February 24, 2026, confirms one Wilton, Maine Code Four deployment with human editing and sign-off; that corroborates the workflow, not a controlled result, so keep vendor time-savings claims labeled vendor-reported.

If you want a low-commitment way to generate that local number, CLIPr offers a 30-day agency pilot for up to 50 officers, subject to approval, and the same fair-pilot design below applies to whichever tool you test.

Which Product Should Your Agency Evaluate First?

Start with Code Four REPORT when

• Your agency is not locked into a required Axon software path.
• Visual-plus-audio analysis and source-linked timestamps are central requirements.
• Mixed camera, CAD, or RMS paths can be validated in technical discovery.
• A fixed $50 per-officer public reference is useful for initial budgeting.
• You will test the model and integration behavior on representative evidence, not demo clips.

Start with Axon Draft One when

• You already use Axon Evidence and the required companion products.
• Native Records or Standards workflow, permissions, sign-off, audit, and usage reporting reduce implementation change.
• The original-draft retention controls fit your records policy after configuration.
• You accept the documented prerequisites and receive a complete quote.

Pause both when

• Approved report types and exclusions are not yet defined.
• Source preservation, version history, review ownership, and retention are unresolved.
• Security or contract evidence is incomplete.
• You are comparing list references without full total cost.
• There is no baseline, error rubric, stop condition, or data-exit plan.

The default recommendation, stated plainly: if the pause conditions do not apply and your agency is not committed to an Axon software path, pilot Code Four REPORT first. If you already run the qualified Axon stack, evaluate Axon Draft One first.

Run the Same Fair Pilot for Both Products

Whichever product you evaluate first, the pilot design should be identical so the results are comparable. It follows the phased, review-first approach in DOJ COPS Office guidance (January 2025), and pairs with a phased police-report automation plan if you are writing rollout policy too.

1. Define approved lower-risk report types, exclusions, and policy owners.
2. Use the same case mix and source-quality bands for both products, where permissions allow.
3. Record baseline drafting, review, supervisor return, and RMS-entry time first.
4. Measure factual errors, unsupported additions, omissions, source-trace coverage, required edits, and reviewer agreement.
5. Record ingest failures, latency, manual steps, support effort, and integration exceptions.
6. Verify retention, draft versions, audit events, permissions, export, deletion, and incident handling in the pilot configuration.
7. Normalize total cost, define stop and remediation conditions, and test data exit before any rollout.

Consult prosecutors, legal counsel, records staff, labor representatives, security, and community stakeholders as appropriate. Turn the comparison above into your procurement worksheet, then request comparable current quotes and deployment evidence from both vendors before anyone signs.

A Third Path When Neither Deployment Model Fits

Some agencies do not fit either mold: not ready to commit to Code Four's wider family, and not standardized on the Axon ecosystem Draft One expects. That gap is where a camera-agnostic, start-light option earns a look.

CLIPr publishes this comparison and appears in the reference column and the verdict throughout; hold it to the same evidence bar as the two products above.

Building a wider shortlist? Two roundups apply the same evaluation lens to each product's field: Axon Draft One alternatives and Code Four alternatives.

Frequently Asked Questions

Bottom Line

For the Code Four vs Axon decision, the dependency-first read still holds between the two. A greenfield or mixed-stack agency should advance Code Four REPORT to a controlled pilot, matching multimodal inputs, source-linked review, named cross-system paths, and a simpler published rate.

An agency already standardized on Axon Evidence and the required products should evaluate Axon Draft One first, as the lower-change path with more detailed product-level audit, reporting, and retention controls.

CLIPr is a third option to shortlist when the agency wants to retain its camera fleet and keep the officer reviewing, editing, and owning each draft-first report. The appropriate choice should come from the same local evidence set, procurement gates, and reviewer rubric used for Code Four and Axon.

CLIPr prices on utilization you can validate through the 30-day agency pilot for up to 50 officers, subject to approval.

Security, records, legal, and total-cost gates can stop any of these paths, and no public page replaces a fair local test on your agency's own evidence.