December 2025

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 are two releases scheduled for December:

  • December 2, 2025
  • December 16, 2025

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.

There are no preview items for Records in December.

Records general release

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

Axon Evidence

The following update will be applied to the production environments of all organizations on December 2, 2025.

  • We will be updating the font used throughout the site. This change affects the font style only and will not impact page layouts or workflows.

Case Management

The following feature will be available for all organizations to use in their production environments on December 2, 2025. Contact your Axon representative to have it activated for your organization.

  • Agencies can now generate PDF files and upload them to Axon Evidence without an automatic case creation occurring. This improvement reduces duplicate cases, streamlines document preparation, and allows Records staff and digital evidence units to manage sharing workflows more effectively.

Property Management

The following update will be applied to the production environments of all organizations on December 2, 2025.

  • When releasing property items, users will be able to import person details into the Authorized Disposition from either a report or the incident overview page. See MyAxon for more information.

Bookings

The following update will be applied to the production environments of all organizations on December 16, 2025.

  • Users with the correct permission can now fully or partially expunge bookings, including associated people, charges, and arrests. Booking expungements will work the same way incident expungements does. When a booking is expunged, all related records, including intake and release forms, are removed.
    • Expunged bookings will behave like expunged incidents and appear in the Expungements section of the Administrator Console.
    • See MyAxon for more information.

Administrator Console

The following update will be applied to the production environments of all organizations on December 2, 2025.

  • Administrators can now give users the ability to create or update supplements without allowing them to create new incident reports. To enable this, go to Administrator Console > Command Hierarchy & Teams and locate the team of users this will apply to, then change the following privileges:
    1. Go to Reports - Records and Standards > Create and set Create Reports to Prohibit.
    2. Go to Reports - Records > Create and set Create incident reports and supplements in Records to Prohibit.
    3. Go to Reports - Records > Workflow-Collaborative Incident Report Contribution > Draft State and set Create tasks to Allow.

Records resolved issues

This section includes information about upcoming bug fixes and resolved issues that will be released to all production environments.

There are no resolved issues for Records in December.

NIBRS

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

Florida agencies

The following update will be applied to the production environments of all agencies on December 2, 2025:

  • We’ve resolved an issue in Florida NIBRS submissions where arrest segments were being omitted from the XML file when an arrestee’s Primary Offense for Arrest was set to an offense marked Exclude from NIBRS. This resulted in a mismatch between the report header and the expected arrest segment, causing the state to return FLPRT00220 – Report type in the header must be consistent with the Parent element XML Id. The system now prevents users from selecting an excluded offense as the primary arrest offense and ensures that valid arrest segments are included in the submission whenever applicable, preventing FLPRT00220 errors and ensuring compliant Florida NIBRS reporting.
    • Any reports affected by this issue may need to be resubmitted. Please contact Axon Customer Support or your NIBRS Specialist for assistance.

Louisiana agencies

The following update will be applied to the production environments of all agencies on November 18, 2025:

  • We’ve resolved an issue that prevented some agencies from generating their Louisiana NIBRS submission files. An invalid value in a state-specific code table caused the system to produce an error during file creation, resulting in failed submissions. The code table has been corrected to ensure only valid values are used when building submission files, allowing reports to generate and submit successfully. No software update was required for this fix.

North Carolina agencies

The following update will be applied to the production environments of all agencies on December 2, 2025:

  • We’ve updated Axon Records to align with the NC-DEx NIBRS IEPD 2023.0 specification. This update incorporates statewide changes to victim–offender relationship rules for property crimes (Edits 401.4 and 460.1), applies the FBI’s revision to Bias Motivation Code 28 (“Anti-Church of Jesus Christ”), removes Edit 560, updates schema paths for bias motivation, and expands Edit 301.1 to cover all applicable federal offenses. The system now also enforces the new Edit 4109 requirement that Property Description cannot be 20 – Money when reporting 26F – Identity Theft or 26G – Hacking/Computer Invasion. These updates ensure Axon Records remains fully compliant with the NC-DEx NIBRS 2023.0 reporting standard.

Pennsylvania agencies

The following update will be applied to the production environments of all agencies on December 2, 2025:

  • We’ve corrected an issue in Pennsylvania NIBRS submissions where the Longitude field in Segment 10 was being sent one character short, causing the segment length to fall below the required 80 characters. This resulted in state errors (A03, A20, A21) and caused subsequent fields, such as Municipality Code, UCR Arrest Offense Code, and PA Statute Code, to shift and be rejected. The system now ensures the Longitude field is always submitted at the required nine-character length, preventing downstream field misalignment and ensuring compliant PA NIBRS submissions.

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.

There are no preview items for Standards in December.

Standards general release

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

Axon Evidence

The following update will be applied to the production environments of all organizations on December 2, 2025.

  • We will be updating the font used throughout the site. This change affects the font style only and will not impact page layouts or workflows.

Administrator Console

The following feature will be available for all organizations to use in their production environments on December 2, 2025. Contact your Axon representative or Axon Support to have it activated for your organization.

  • Agencies can now manage Finalize access for each workflow individually. Previously, Finalize was a single permission applied across all workflows, which created challenges for agencies with different reporting requirements.

Standards resolved issues

This section includes information about upcoming bug fixes and resolved issues that will be released to all production environments.

There are no resolved issues for Standards in December.

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.
  • Old DataStore accounts will be removed after January 31, 2026. DataStore users must get their new account and secret through DataStore Access Control module before then.

Updates

The following features will be available on December 2, 2025. Contact Axon Support to have it activated for your organization.

  • Starting December 2, the DataStore Access Control module will have a new feature that allows DataStore administrators to create DataStore access for external users—such as third-party vendors, Axon representatives, and users who do not have an evidence.com account. The DataStore administrator is responsible for generating, transferring, and managing the access credentials for these external accounts, ensuring that proper security and data governance practices are followed.
    • See MyAxon for more information.
  • DataStore is introducing a new feature that allows administrators to set detailed access permissions for users. Before this update, any user with access to DataStore could view all available views and schemas without restriction. With the new Fine-Grained Access Control feature, administrators can now manage and limit access to specific views or schemas for individual users. This provides agencies with greater flexibility and security, ensuring that users only have access to the data relevant to their roles.
    • See MyAxon for more information.