January 2026

These release notes describe all user-facing changes that will be included in the next Axon Records and Standards releases, along with advance notice of major upcoming features, updates, and applications.

There is one release scheduled for January:

• January 27, 2026

Releases begin rolling out at 11 AM Pacific time and may continue through the following day. We do not expect any downtime during these updates. Please note that availability is subject to change. Depending on the complexity and amount of items included in a release, some items in these notes may not be available until two days after the release.

Additional help documentation for Axon Records and Standards is located at axon.com/help. Do you have feedback about Axon's release notes? Submit it here.

Download this month's release notes

Records preview release

This section includes information about upcoming features and updates that are available for testing in training environments. These are beta features, and all functionality may not be fully present or completely reliable.

Report management

The following features will be available on January 27, 2026. Contact your Axon representative to activate them in your organization's training environment.

• You can now use a new report redaction tool to securely manage sensitive report content.
  • This tool lets you:
    • Search, redact, annotate, and preview redactions before applying them to reports.
    • Print reports with redactions in place.
    • Track redaction actions in the audit log, including who performed the redaction, when it was done, and the reason for redaction (if provided).
  • This new redaction tool can be accessed from the following locations:
    • Incident profiles (incident report redaction)
      • Select More Actions > Prepare for Sharing while viewing the incident profile. During the prepare documents workflow, can redact the report before exporting the PDF.
        • Users must have the Cases - Records > More Actions > Prepare Documents for Sharing privilege to view this option on incident profiles.
      • The redacted version of the report is automatically saved as an file belonging to the incident (and appears on the Files tab of the incident profile).
    • Report Writer (report redaction)
      • While viewing a report in Report Writer, select More Actions […] > Print Report.
      • During the print workflow, you can redact the report before exporting it to PDF for printing.
    • Person profiles
      • While viewing a profile, select Actions > Print.
      • During the print workflow, you can redact the profile before exporting it to PDF for printing.
• You can now delete draft incident reports and draft non-incident reports by opening the report in Report Writer and selecting More Actions […] > Delete report.
  • Users must have the Reports - Records > Delete privileges to delete reports.
  • Reports cannot be deleted if they have been finalized, contain property items, or have supplements (incident reports only).
• You can now print large reports from the incident profile or from within Report Writer with faster speeds.
  • With this new print platform, large reports that previously took a long time to print now print in seconds. Contact out to your Axon representative to enable this feature in your environments.

Case Management

The following features will be available on January 27, 2026. Contact your Axon representative to activate them in your organization's training environment.

• You can now assign a case to multiple investigative units to allow detectives from different units to work together on the same case without creating duplicate cases or relying on manual workarounds. With this release, detectives and supervisors can:
  • Assign a case to 1 primary unit and up to 4 secondary units, each with its own assigned detective.
  • Track progress, dispositions, case tasks and case documents independently for each unit while maintaining a shared case.
  • View all case artifacts, evidence, and activity logs from all participating units in a single, unified case overview.
  • Filter and organize cases by lead or secondary detective to easily monitor case ownership and workload.
• You can now initiate and manage investigations without requiring an associated incident.
  • This feature provides flexibility for detectives to create investigations based on field intelligence, tips, or proactive leads; enabling investigative work to start earlier and detectives to stay organized even when no formal report or call for service exists. Key capabilities include:
  • Independent investigation creation: Create investigations without a linked incident or event.
  • Investigation profile: Access a centralized view of all investigative details including case summary, linked documents, assigned tasks, and activity history in a single streamlined workspace.
  • Documentation tools: Manage investigation summaries, tasks, and documents within the investigation. Record findings, upload supporting materials, and document progress as the investigation evolves.
  • Supervisor review workflow: Supervisors can review investigations and provide feedback, ensuring accountability and oversight before investigations are closed.
  • Inbox filtering: Quickly locate investigations in inboxes using filters.
  • Access control: Organizations can configure privileges to control who can create, edit, or close investigations.
• Now, when a case with templated case tasks (i.e., case tasks that are automatically created when the case is created) is reassigned, the new lead detective only receives a single case reassignment notification instead of multiple case task notifications.
  • If individual case tasks are reassigned, individual case task reassignment notifications are still sent.
  • This improvement reduces email clutter and allows detectives to focus on important updates rather than unnecessary noise.
• You can now view the media and transcripts for files that have been added to an incident or report from an enhanced evidence review experience.
  • Selecting a file name, either from a report or from the Files tab of an incident profile opens a window containing two tabs:
    • Overview: Includes an overview of the file, including a media player and evidence metadata
    • Transcript: Displays the transcript for the file (if one has been generated)

• You can now view Brief One’s AI-powered evidence insights directly in Axon Records in the form of transcript summaries, key moments, and in-app video playback. These new features include:
  • Transcript summaries: AI-generated transcript summaries now appear in the Files sections of reports and incident profiles, as well as the file selection window.
  • Enhanced evidence review experience: In addition to the Overview and Transcript tabs described above, the Brief One feature set includes a Moments tab. This tab contains AI-detected key events ("moments") that allow users to jump directly to important places in the recording.
  • Moments filtering: The Moments Filter on the Files tab of the incident profile helps investigators rapidly find evidence files containing key events.

Records general release

This section includes information about upcoming features and updates that are available in all production environments.

Report management

The following update will be applied to the production environments of all organizations on January 27, 2026.

• Previously, when adding an offense to an incident report, the list of offenses could take 10-15 seconds to load.
  • This issue has been resolved, and the offense options will now load more quickly.

Search

The following feature will be available for all organizations to use in their production environments on January 27, 2026. Contact your Axon representative to activate it for your organization.

• You can now use the new search experience, which shows search results from all categories - reports, people, vehicles, and more - on one page.
  • Instead of choosing which category to search before you start (e.g., People, Vehicles, etc.), you can simply enter what you’re looking for in the top search box and view search results organized by category. To focus in on a single category, you can select that category's filter below the search box.
  • You can still switch back to the old search experience (where search categories appeared on separate pages) by select the Old Experience button in the banner at the top of the page.

Case Management

The following update will be applied to the production environments of all organizations on January 27, 2026.

• Previously, when trying to navigate between multiple narratives from the Case Summary window, you were returned to the case profile instead of the next narrative.
  • This issue has been resolved, and now when viewing the Case Summary window, you can page through multiple case summary narratives.
  • Additionally, you can view snippets of all case summary narratives from the case profile.

Bookings

The following update will be applied to the production environments of all organizations on January 27, 2026.

• Now, when expunging an entire booking or an person, the images from that booking will also be expunged.
  • At this time, booking images cannot be expunged separately from an entire booking or entire person expungement (for example, you cannot expunge images if you are only expunging a person’s PII).

Administrator Console

The following update will be applied to the production environments of all organizations on January 27, 2026.

• Previously, organizations have faced issues where certain incident reports became corrupted and prevented users from joining as contributors to add information to the report. To unblock this issue, a new Document Repair tool will be released to the Administrator Console.
  • If users experience issues while editing incident reports, they can ask their Axon representative or one of the organization's administrators to use this tool to fix the report.
  • Administrators can the incident number of the corrupted report into this tool and select Repair. The tool automatically fixes the report so users can continue working.

NIBRS

This section includes information about upcoming updates and bug fixes for NIBRS validation rules, errors, and submissions.

Colorado organizations

The following updates will be applied to the production environments of all Colorado organizations on January 27, 2026.

• Previously, after the transition to TS-NIBRS, some Colorado arrest submissions did not include required drug item information, and certain validation rules behaved incorrectly. In some cases, users were prompted to complete fields that were not required, while other required drug-related fields were not enforced, leading to validation issues and incomplete state submissions.
  • This issue has been resolved, and arrest records now correctly include drug item details in the submission file when applicable.
  • Group B arrests with NCIC Offense Code 5403 (Driving Under the Influence – Drugs) now require at least one suspected drug type, property status filtering behaves as expected, and an incorrect requirement to enter a completed/attempted offense value has been removed.
• Previously, some Colorado incidents that were not NIBRS-reportable (such as incidents marked Unfounded or with an invalid NIBRS date) could still require the Victim Was Injured field to be completed. This created a situation where users were prompted to enter injury information even though the incident was not eligible for NIBRS submission, and the requirement could not be satisfied.
  • This issue has been resolved, and the system now applies the Victim Injury requirement only when an incident is NIBRS-reportable. When an incident is not reportable, the injury fields will no longer be required or block submission.
  • This update prevents unnecessary validation errors and allows non-reportable incidents to be completed without additional data entry.

Florida organizations

The following update will be applied to the production environments of all Florida organizations on January 27, 2026.

• Previously, some Florida NIBRS arrest records incorrectly required and included a Juvenile Disposition when the arrestee was 18 years old or older at the time of arrest, even if the arrestee was a juvenile at the time of the offense. This caused valid reports to be rejected by FDLE with error ERR_FLNBR_0081.
  • This issue has been resolved, and the Juvenile Disposition field is now displayed, required, and included in the submission file only when the arrestee is under 18 at the time of arrest. When the arrestee is an adult at arrest, the field will no longer be required or sent to the state.

Indiana organizations

The following update will be applied to the production environments of all Indiana organizations on January 27, 2026.

• A rule validation was introduced to latitude and longitude field manual entries not containing the correct format.

Michigan organizations

The following updates will be applied to the production environments of all Michigan organizations on January 27, 2026.

• Previously, Michigan agencies were unable to indicate that the time of an incident was unknown, even though MICR allows this to be reported.
  • In addition, the system did not consistently enforce when an unknown time was permitted based on the offense and victim type.
  • This behavior has been updated to ensure Michigan incidents are completed accurately and in compliance with state reporting rules.
  • Now, the Is Time of Incident Unknown? field is required and correctly controls this behavior. When set to "Yes", the system automatically reports the Hour Occurred* as "99" in the MICR submission file.
  • When the Victim Type field is set to "Law Enforcement Officer" and the offense is "Murder (09001)" or "Assault (13001–13004)," an unknown time is not permitted and the system will require a known time to be entered.
• Previously, some Michigan NIBRS (MICR) incident submissions could fail with a Victim Information is Required error when an incident included certain offenses, even when a victim was not required under Michigan rules.
  • This most often occurred when a Group B offense was included in the report.
  • This issue has been resolved, and the system now applies Michigan-specific MICR rules when determining whether a victim is required for an offense, instead of relying on general NIBRS rules. As a result, valid MICR submissions with Group B offenses should now submit successfully without unnecessary errors.
  • If an incident previously failed due to this issue, it can now be resubmitted successfully.
• Previously, when an incident included a fatal offense (such as Murder), the system would hide the Victim Injury fields for all victims on the report — even victims who were not associated with the fatal offense.
  • This behavior prevented users from entering injury information for victims tied to other offenses, such as Aggravated Assault.
  • This issue has been resolved, and the system now evaluates victim injury requirements based only on the offenses linked to each individual victim, rather than all offenses on the incident.
  • Victims associated with a fatal offense will continue to have their injury automatically set to "Fatal," while victims linked to non-fatal offenses will now correctly see and be required to complete the Victim Was Injured field when applicable.
  • Reports affected by this issue can now be reviewed and resubmitted if needed.

Oklahoma organizations

The following update will be applied to the production environments of all Oklahoma organizations on January 27, 2026.

• Previously, the Value of Property field was not being included in Oklahoma NIBRS submission files for certain offenses, which caused state validation errors (including NIBRS error 301) when reporting 35A – Drug/Narcotic Violations or 35B – Drug Equipment Violations with applicable property.
  • This issue has been resolved, and the system now correctly includes the Value of Property whenever required by state rules, ensuring that reports with valid property information are successfully accepted by the state.

Texas organizations

The following update will be applied to the production environments of all Texas organizations on January 27, 2026.

• The issues that could cause Texas NIBRS (TIBRS) submissions to be rejected when the Family Violence Indicator did not align with the Victim-to-Offender Relationship have been resolved.
  • The system now correctly evaluates victim–offender relationships and automatically sets the Family Violence Indicator field to "Y" when any qualifying family or dating relationship is present.
  • If only non-family relationships are present, the indicator will be submitted as "N."
  • Submissions will no longer be rejected for inconsistencies between family violence indicators and valid relationship codes.
  • This update addresses scenarios where:
    • Family relationships (such as parent/child, spouse, ex-spouse, or dating relationships) were present but the Family Violence Indicator was incorrectly submitted as "N."
    • Non-family relationships (such as Stranger or Relationship Unknown) were incorrectly submitted with the Family Violence Indicator set to "Y."

Virginia organizations

The following update will be applied to the production environments of all organizations on January 27, 2026.

• Previously, some Virginia incidents were incorrectly evaluated as reportable when an arrest was linked to a non-reportable offense, even if another Group B offense existed on the report.
  • This caused the system to attempt to generate a NIBRS submission for incidents that should not have been reported, resulting in failed or broken submission files.
  • This issue has been resolved, and the system now correctly prevents NIBRS submissions when arrests are associated only with non-reportable offenses, even if other non-qualifying data (such as property) exists on the report. Reports that should not be submitted will no longer be processed for NIBRS.

Standards preview release

This section includes information about upcoming features and updates that are available for testing in training environments. These are beta features, and all functionality may not be fully present or completely reliable.

Printing and redaction

The following features will be available on January 27, 2026. Contact your Axon representative to activate them in your organization's training environment.

• You can now use a new report redaction tool to securely manage sensitive report content.
  • This tool lets you:
    • Search, redact, annotate, and preview redactions before applying them to reports.
    • Print reports with redactions in place.
    • Track redaction actions in the audit log, including who performed the redaction, when it was done, and the reason for redaction (if provided).
  • This new redaction tool can be accessed from the following locations:
    • Event profiles
      • Select More Actions > Prepare for Sharing while viewing the incident profile. During the prepare documents workflow, can redact the report before exporting the PDF.
        • Users must have the Cases - Standards > More Actions > Prepare Documents for Sharing privilege to view this option on incident profiles.
      • The redacted version of the report is automatically saved as an file belonging to the incident (and appears on the Files tab of the event profile).
    • Report Writer (report redaction)
      • While viewing a report in Report Writer, select More Actions […] > Print Report.
      • During the print workflow, you can redact the report before exporting it to PDF for printing.
    • Citizen profiles
      • While viewing a profile, select Actions > Print.
      • During the print workflow, you can redact the profile before exporting it to PDF for printing.
• You can now print large reports from the incident profile or from within Report Writer with faster speeds.
• With this new print platform, large reports that previously took a long time to print now print in seconds. Contact out to your Axon representative to enable this feature in your environments.

Case Management

The following features will be available on January 27, 2026. Contact your Axon representative or Axon Support to activate them for your organization.

• You can now assign a case to multiple investigative units to allow detectives from different units to work together on the same case without creating duplicate cases or relying on manual workarounds. With this release, detectives and supervisors can:
  • Assign a case to 1 primary unit and up to 4 secondary units, each with its own assigned detective.
  • Track progress, dispositions, case tasks and case documents independently for each unit while maintaining a shared case.
  • View all case artifacts, evidence, and activity logs from all participating units in a single, unified case overview.
  • Filter and organize cases by lead or secondary detective to easily monitor case ownership and workload.
• You can now initiate and manage investigations without requiring an associated incident.
  • This feature provides flexibility for detectives to create investigations based on field intelligence, tips, or proactive leads; enabling investigative work to start earlier and detectives to stay organized even when no formal report or call for service exists. Key capabilities include:
  • Independent investigation creation: Create investigations without a linked incident or event.
  • Investigation profile: Access a centralized view of all investigative details including case summary, linked documents, assigned tasks, and activity history in a single streamlined workspace.
  • Documentation tools: Manage investigation summaries, tasks, and documents within the investigation. Record findings, upload supporting materials, and document progress as the investigation evolves.
  • Supervisor review workflow: Supervisors can review investigations and provide feedback, ensuring accountability and oversight before investigations are closed.
  • Inbox filtering: Quickly locate investigations in inboxes using filters.
  • Access control: Organizations can configure privileges to control who can create, edit, or close investigations.
• Now, when a case with templated case tasks (i.e., case tasks that are automatically created when the case is created) is reassigned, the new lead detective only receives a single case reassignment notification instead of multiple case task notifications.
  • If individual case tasks are reassigned, individual case task reassignment notifications are still sent.
  • This improvement reduces email clutter and allows detectives to focus on important updates rather than unnecessary noise.

Standards general release

This section includes information about upcoming features and updates that are available in all production environments.

Search

The following update will be applied to the production environments of all organizations on January 27, 2026.

• You can now use the new search experience, which shows search results from all categories—reports, people, vehicles, and more—on one page.
  • Instead of choosing which category to search before you start (e.g., People, Vehicles, etc.), you can simply enter what you’re looking for in the top search box and view search results organized by category.To focus in on a single category, you can select that category's filter below the search box.
  • You can still switch back to the old search experience (where search categories appeared on separate pages) by select the Old Experience button in the banner at the top of the page.

Case Management

The following update will be applied to the production environments of all organizations on January 27, 2026.

• Previously, when trying to navigate between multiple narratives from the Case Summary window, you were returned to the case profile instead of the next narrative.
  • This issue has been resolved, and now when viewing the Case Summary window, you can page through multiple case summary narratives.
  • Additionally, you can view snippets of all case summary narratives from the case profile.

Axon Notes Module preview release

This section includes information about upcoming features and updates that are available for testing in training environments. These are beta features, and all functionality may not be fully present or completely reliable.

The following feature will be available on January 27, 2026. Contact your Axon representative to activate it in your organization's training environment.

• To support officers working on their notes in areas with limited or no connectivity, the Axon Notes Module in the Axon App now supports offline editing and creation of notes on both iOS and Android platforms.
  • Officers can now:
    • Access and edit notes they opened within the last 7 days while offline.
      • The app automatically downloads the last 7 days of accessed notes for offline use. Notes not opened in the last 7 days will NOT be available offline.
    • Create new notes even without a network connection.
    • Store all edits and new notes locally until the device is reconnected to the internet.
  • To create a new note while offline:
    • Tap the "+" icon and select Create New Note to begin a new entry.
    • Content can be added as usual, but finalization requires an online connection.
  • To sync an offline note once internet connection is restored:
    • All offline notes appear in a dedicated Local tab for quick access.
    • Officers can either bulk sync using or sync individual notes using the More Actions […] menu.
    • Error messages will appear if syncing fails, with the ability to retry.
      • If a note has been edited both offline and online, a merge conflict prompt will appear. Officers can choose to overwrite the cloud version with the local version.
    • Synced notes are removed from the local device.
  • Offline limitations include:
    • Notes cannot be finalized while the officer is offline to ensure audit integrity and avoid version conflicts.
    • Features such as dictation and Person search from within a note are unavailable.

Axon Notes Module general release

This section includes information about upcoming features and updates that are available in all production environments.

There are no general release items for the Axon Notes Module in January.

Axon DataStore

This section includes information about upcoming changes to the Axon Records and Standards DataStore.

Upcoming deprecations

• Azure Data Studio will be deprecated in February 2026 and will no longer support connections to the Axon DataStore. To maintain uninterrupted access, please begin using Visual Studio Code or SQL Server Management Studio to connect to the DataStore.
  • See MyAxon for more information on connecting with Visual Studio Code or SQL Server Management Studio.