May 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 May:

• May 19, 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 Writer

The following feature will be available for all organizations to use in their training environments on May 19, 2026. Contact your Axon representative or Axon Support to activate it for your organization.

• Previously, users could not embed photos directly within narrative text. Photos had to be referenced separately or attached outside of the narrative, making it difficult to create visual reports such as BOLOs or detailed incident summaries that require images alongside written descriptions.
  • With this update, users can now insert photos inline within narrative text across both Records and Standards.
  • A new option on the narrative toolbar lets users select photos attached to the report and insert them directly into the narrative. Inserted photos appear as thumbnails within the text and include a link to the Evidence details page in Axon Evidence. Photos can be removed from the narrative without affecting the original file in Axon Evidence. Printed narratives include the embedded photos.

Property Management

The following feature will be available for all organizations to use in their training environments on May 19, 2026. Contact your Axon representative or Axon Support to activate it for your organization.

• Administrators can now configure and manage property label templates directly in the Property Management tool within the Administrator Console.
  • With this release, administrators can:
    • Customize a default Axon property label template or upload a custom PDF label.
    • Configure and map property report fields to the fields on the property label template.
    • Rename, reorder, resize, and customize label fields.
    • Add conditional icons, images, barcodes, and item identifiers.
    • Preview and test print labels before publishing.
    • Save label changes as drafts and publish when ready.
    • Replace or update label templates without Axon engineering support.
  • This feature can also be used by organizations who have third-party property integrations in addition to Axon Property.
  • For more information about this feature, see Property Management - Label configuration.

Form Builder

The following features will be available for all organizations to use in their training environments on May 19, 2026. Contact your Axon representative or Axon Support to activate them for your organization.

• Form Builder now supports drag-and-drop reordering of fields within the UI.
  • To reorder, select More actions […] > Reorder fields on a card. Form Builder enters a dedicated reorder mode where you can:
    • Drag and drop sections to reorder them within the card.
    • Drag and drop fields within a section to re-order them within the section. (Fields from one section can’t be dragged into another section.)
    • Select the Show Reorder Groups option to highlight sections hidden by form logic (in blue) and reorder them.
• You can now add a new default value to fields: Insert from fields. This new type of default value allows a field to automatically pull its value from another field on the same form. In other words, you can set the default value for Field B to be whatever value is entered in Field A.
  • For example, an organization can configure a phraseology template so that when an officer selects a specific ordinance, the corresponding legal language is inserted into a separate field — complete with any variable details the officer provided. This new feature eliminates manual copy-paste and reduces the risk of errors in legally required documents.

Records general release

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

Report Writer

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

• You can now create sub-bullets in the Narrative rich text editor.
  • To create sub-bullets, use the indent-increase and indent-decrease toolbar buttons, or press Tab and Shift+Tab, to nest and un-nest bullet items.

Search

The following updates will be applied to the production environments of all organizations on May 19, 2026.

• The new search experience is now the only search experience available in Axon Records and Standards.
  • The old search experience has been deprecated and can no longer be used.
• Search results in the All search category can now be sorted by Recency (previously, results were sorted by Relevance).
  • The date used for sorting varies depending on the type of search result (report, vehicle, etc.).

Property Management

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

• Now, if your organization does not require the Drop-off location field to be completed before a property item is submitted, users will no longer see a validation error that indicates the Drop-off location is required.

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

• Previously, Chain of Custody entries for property items submitted as part of a container did not show the drop-off location. This behavior has been updated and now the chain of custody entries for both containers and the property items they contain show the drop-off location captured at check-in.
  • This update provides clearer location traceability for containerized evidence, improving auditability and compliance for property and evidence handling.

Administrator Console

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

• This update will reverse the sort order of Records/Standards Audit Logs. Currently, entries in audit logs are sorted from oldest at the top to newest. After this update, they will be sorted from newest at the top to oldest.

Records resolved issues

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

Report Writer

The following issues will be resolved on May 19, 2026.

• Previously, when a Person type was switched from Unknown to Known, the age was not calculated automatically if the Person had the Date of Birth field set.
  • This issue has been resolved, and the Age field is now auto-filled as expected.
• Previously, the validation error count displayed in the Report Writer footer ("X errors need to be fixed before submitting") could show a lower number than the actual number of validation errors.
  • This issue has been resolved, and the footer count now accurately reflects the number of validation errors.

Search

The following issues will be resolved on May 19, 2026.

• Previously, sometimes searches would return no results, even if search results were available.
  • This issue has been resolved, and search results appear as expected.
• An issue has been resolved where highlighting in search results sometimes displayed an unfriendly UUID number.
  • Now, the search result highlighting displays the form name, clearly indicating why the search result appears.

NIBRS

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

Arkansas organizations

The following update will be applied to the production environments of all Arkansas organizations on May 19, 2026.

• An issue has been resolved where the Arkansas NIBRS submission file was being saved with a .txt extension when downloaded. The state expects the submission file to be saved without a file extension.
  • The downloaded file no longer includes the .txt extension, matching the format expected by the state and removing the need to rename the file before upload.

Florida organizations

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

• An issue was resolved where Florida NIBRS submissions were rejected by the state with error FLNBR 0093 ("Victim's associated Offenses cannot contain multiple data values representing Mutually Exclusive and Lesser Included offenses") for incidents that contained both a primary offense and a lesser-included offense (for example, 220 Burglary paired with 23H Theft from Coin-Operated Machine).
  • Previously, the lesser-included indicator was set to False on both offenses, causing the state to treat them as conflicting. The system now correctly identifies and flags the lesser-included offense, allowing incidents with primary and lesser-included offenses to be submitted successfully.
  • If your organization has received FLNBR 0093 rejections, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.

Louisiana organizations

The following updates will be applied to the production environments of all Louisiana organizations on May 19, 2026.

• An issue was resolved where Method of Entry (Data Element 11) was not populated in NIBRS submission files even when a value was entered on the incident. For example, an incident with a 220 (Burglary/Breaking & Entering) offense and Method of Entry set to Force was being sent with the field blank, which can cause state validation errors for offenses that require this data element.
  • Method of Entry is now correctly included in the submission file when the offense requires it under NIBRS reporting rules.
  • If your organization has received rejections related to Method of Entry, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.
• Previously, Louisiana NIBRS submissions sent the Victim Injury Type (Data Element 33) as a single value in the submission file. The state has since corrected its technical specification to require this field as a list, supporting up to 5 injury types per victim. This mismatch caused state submission errors for affected reports.
  • This issue has been resolved, and the submission file now sends Victim Injury Type in the correct list format required by the updated Louisiana specification.
  • No action is required. Impacted reports will be resubmitted by your NIBRS Customer Support Specialist.

Michigan organizations

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

• A validation rule has been updated for Michigan NIBRS submissions to align with MICR requirements on Group B offenses. Type of Victim (Data Element 25) is now required on Group A and Group B offenses whenever MICR requires it (base NIBRS only requires this field on Group A).
  • Previously, Michigan incidents containing Group B offenses could be submitted without Type of Victim, putting organizations at risk of MICR rejections for missing data. Users will now see a validation error if Type of Victim is not completed on an offense where MICR requires it. Offenses that MICR specifically exempts will continue to allow this field to be left blank.
  • No action is required. The validation rule will be applied automatically. If your organization has received MICR rejections related to missing Type of Victim on Group B offenses, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents updated and requeued for submission.
• Validation rules have been updated for Michigan NIBRS submissions to align with MICR requirements on Group B offenses.
  • The following fields are now required on Group A and Group B offenses (base NIBRS only requires them on Group A):
    • Offender Suspected of Using
    • Offense Attempted/Completed
    • Was Bias Motivation Involved
  • Previously, Michigan incidents containing Group B offenses could be submitted without these values, resulting in MICR rejections for missing data. Users will now see a validation error if any of these fields are not completed on a Group A or Group B offense.
  • No action is required. The validation rules will be applied automatically. If your organization has received MICR rejections related to these fields on Group B offenses, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents updated and requeued for submission.
• An issue was resolved where Michigan NIBRS submissions were rejected by MICR with "Victim Information is Required" for incidents containing offenses that require a Society victim (for example, 48000 Obstructing Police, 50000 Obstructing Justice, and 38001 Family Abuse/Neglect). The submission file did not include a Society victim segment for these offenses when other victims on the incident were associated only to different offenses, leaving the society-victim offense without a victim connection.
  • The submission file now automatically includes a Society victim segment for offenses that require one, so these incidents pass MICR validation. No officer action is required to add Society victims in the incident report.
  • If your organization has received MICR rejections related to "Victim Information is Required" on these offenses, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.
• An issue was resolved where Michigan NIBRS submissions were rejected by MICR with a missing Arrest Charge Code (error 741, with cascading error 231) for incidents that included an arrest. Although the arrest charge was captured on the incident report, the value was not being included in the submission file.
  • The Arrest Charge Code is now correctly populated in the submission file from the value entered on the incident, clearing the related MICR rejections.
  • If your organization has received MICR rejections related to missing Arrest Charge Code, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.
• A validation rule has been added for Michigan NIBRS submissions to prevent MICR error 582. When the Victim-Offender Relationship is 31 (Victim is Offender) and two or more victims are associated with the same offense, the Type of Victim must be I (Individual) for those victims.
  • Users will now see a validation error if the Type of Victim is not set to Individual for victims that meet these conditions, preventing the submission from being rejected by the state.
  • No action is required. The validation rule will be applied automatically. If your organization has received MICR error 582 on prior submissions, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents updated and requeued for submission.

Minnesota organizations

The following updates will be applied to the production environments of all Minnesota organizations on May 19, 2026.

• An issue has been resolved where Minnesota NIBRS submissions returned a Bureau of Criminal Apprehension (BCA) warning that the Apartment/Suite Number field was not stored. The submission file was including values that exceeded the BCA limit of 10 alphanumeric characters. The Apartment/Suite Number is now truncated to the 10-character limit before being sent, preventing the warning and ensuring the value is stored by the state.
  • If your organization has received this warning for prior submissions, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.
• An issue was resolved where Minnesota NIBRS submissions were rejected by the Bureau of Criminal Apprehension (BCA) due to invalid Vehicle Make and Model values. Two corrections were made to align with BCA requirements:
  • The Vehicle Model field was sending a combined make and model value. The submission file now sends only the NCIC Vehicle Model code, separate from the Vehicle Make.
  • The Vehicle Make and Vehicle Model codes are now limited to 10 alphanumeric characters each, matching the BCA limit and preventing rejections.
  • If your organization received rejections related to Vehicle Make or Model values, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.

New York organizations

The following update will be applied to the production environments of all New York organizations on May 19, 2026.

• An issue was resolved where New York organizations could not select certain valid Location Category values on the offense card. Some NYIBRS-specific options (for example, Residential Facility) were hidden from the dropdown because the underlying validation was using an older base NIBRS list rather than the full NYIBRS list.
  • The Location Category dropdown now displays all valid NYIBRS values, and the filter is correctly limited to reports that submit to NIBRS.
  • No action is required. The dropdown will reflect the corrected list automatically.

Virginia organizations

The following updates will be applied to the production environments of all Virginia organizations on May 19, 2026.

• Validation rules have been added for Virginia NIBRS submissions to align with the Virginia Incident-Based Reporting System Technical Specification 2025.2. For incidents containing a 280 (Stolen Property Offenses) or 520 (Weapon Law Violations) offense:
  • The Criminal Activity section (Data Element 12) now requires at least one — and no more than two — of the following codes: B, C, D, E, O, P, T, or U.
  • The Gang Information section (Data Element 12) prohibits any code entry (J, G, or N) for these offenses.
  • No action is required. The validation rules will be automatically applied, and users will see a validation error if these requirements are not met.
• A validation rule has been added for Virginia NIBRS submissions to require at least one Type Weapon/Force Used value (Data Element 13) when the incident contains a 720 (Animal Cruelty) offense. If no weapon or force was used, 99 (None) should be selected. This update aligns with the VA Technical Specification Manual 2025.1.1.
  • No action is required. The validation rule will be automatically applied.

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.

Report Writer

The following feature will be available for all organizations to use in their training environments on May 19, 2026. Contact your Axon representative or Axon Support to activate it for your organization.

• Previously, users could not embed photos directly within narrative text. Photos had to be referenced separately or attached outside of the narrative, making it difficult to create visual reports such as BOLOs or detailed incident summaries that require images alongside written descriptions.
  • With this update, users can now insert photos inline within narrative text across both Records and Standards.
  • A new option on the narrative toolbar lets users select photos attached to the report and insert them directly into the narrative. Inserted photos appear as thumbnails within the text and include a link to the Evidence details page in Axon Evidence. Photos can be removed from the narrative without affecting the original file in Axon Evidence. Printed narratives include the embedded photos.

Form Builder

The following features will be available for all organizations to use in their training environments on May 19, 2026. Contact your Axon representative or Axon Support to activate them for your organization.

• Form Builder now supports drag-and-drop reordering of fields within the UI.
  • To reorder, select More actions […] > Reorder fields on a card. Form Builder enters a dedicated reorder mode where you can:
    • Drag and drop sections to reorder them within the card.
    • Drag and drop fields within a section to re-order them within the section. (Fields from one section can’t be dragged into another section.)
    • Select the Show Reorder Groups option to highlight sections hidden by form logic (in blue) and reorder them.
• You can now add a new default value to fields: Insert from fields. This new type of default value allows a field to automatically pull its value from another field on the same form. In other words, you can set the default value for Field B to be whatever value is entered in Field A.
  • For example, an organization can configure a phraseology template so that when an officer selects a specific ordinance, the corresponding legal language is inserted into a separate field — complete with any variable details the officer provided. This new feature eliminates manual copy-paste and reduces the risk of errors in legally required documents.

Standards general release

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

Report Writer

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

• You can now create sub-bullets in the Narrative rich text editor.
  • To create sub-bullets, use the indent-increase and indent-decrease toolbar buttons, or press Tab and Shift+Tab, to nest and un-nest bullet items.

Search

The following updates will be applied to the production environments of all organizations on May 19, 2026.

• The new search experience is now the only search experience available in Axon Records and Standards.
  • The old search experience has been deprecated and can no longer be used.
• Search results in the All search category can now be sorted by Recency (previously, results were sorted by Relevance).
  • The date used for sorting varies depending on the type of search result (report, vehicle, etc.).

Administrator Console

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

• This update will reverse the sort order of Records/Standards Audit Logs. Currently, entries in audit logs are sorted from oldest at the top to newest. After this update, they will be sorted from newest at the top to oldest.

Standards resolved issues

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

Report Writer

The following issues will be resolved on May 19, 2026.

• Previously, when a Person type was switched from Unknown to Known, the age was not calculated automatically if the Person had the Date of Birth field set.
  • This issue has been resolved, and the Age field is now auto-filled as expected.
• Previously, the validation error count displayed in the Report Writer footer ("X errors need to be fixed before submitting") could show a lower number than the actual number of validation errors.
  • This issue has been resolved, and the footer count now accurately reflects the number of validation errors.

Search

The following issues will be resolved on May 19, 2026.

• Previously, sometimes searches would return no results, even if search results were available.
  • This issue has been resolved, and search results appear as expected.
• An issue has been resolved where highlighting in search results sometimes displayed an unfriendly UUID number.
  • Now, the search result highlighting displays the form name, clearly indicating why the search result appears.

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.

Axon Notes Module

The following feature will be available for all organizations to use in their training environments on May 19, 2026. Contact your Axon representative or Axon Support to activate it for your organization.

• You can now organize notes by shift.
  • Additionally, you can now view and edit shift details while offline and sync shift detail edits once you regain connectivity. Notes created while offline can be linked to an existing shift automatically when applicable.

Axon Notes Module general release

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

Axon Notes Module

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

• You can now search for shift details in the Axon app.
  • From Notes search, tap the filter icon to switch between searching for notes and searching for shifts. When searching for shifts, you can use Shift IDs, keywords, and shift start date filters.
  • This search functionality is currently only available in the mobile app and will be released to Notes on desktop in a future release.

Axon DataStore

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

Updates

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

• Until now, organizations that needed to share DataStore access broadly while protecting sensitive cases — Internal Affairs, juvenile records, ongoing investigations, and other restricted content — relied on custom views built by Axon. That process was slow to deliver, inconsistent across organizations, and brittle as schemas evolved. DataStore v2 now replaces this process with native row-level access that leverages the restrictions applied to reports in Axon Records and Standards.
  • This new feature includes:
    • Restriction-aware queries: DataStore v2 excludes rows a user is not authorized to see — no custom views required.
    • Per-user access: DataStore administrators can grant each DataStore user either full access or access scoped to specific restrictions. If a row carries multiple restrictions, the user must be authorized for all of them. Rows without restrictions remain visible to any user with access to that table or schema.
    • Organization-controlled enablement: Restriction enforcement is off by default. Administrators can turn it on using a new setting in the DataStore Settings tool (Access Policy > Restricted Data Settings). Once this setting is enabled, restriction access can be applied to individual users individually or to the default access profile template.
  • For more information about this new feature, see Access control - Restricted data.
  • Row-level security adds additional processing to every query, which carries performance implications:
    • Users with full access see no change in query performance.
    • Users with restriction-based access should expect query times to increase by roughly 40%, with similar growth in resource usage.
  • This feature is now available in preview on DataStore v2, with general availability planned for August 2026. It is not supported on DataStore v1. If your organization still uses DataStore v1 and you want to leverage row-level access control, contact Axon Support to discuss upgrading to v2. To enable the preview for your v2 environment, contact Axon Support.