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

  • October 6, 2026
  • October 20, 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 several 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.

Profiles

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

  • You can now add a flag to people, locations, organizations, and vehicles directly from Report Writer. Previously, you had to open the profile to add the flag.
    • You can also see any flags that have already been added to that profile directly within Report Writer. The flag description for flags added this way display the Report ID they were added from.

Sealing

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

  • Now, when sealing an incident, you can chose to seal an individual offense or charge within a report. Sealing one offense or charge does not seal the rest of the report.

Records general release

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

Axon Evidence URL change

To support growing evidence volumes, storage needs, and AI-powered workflows, Axon is expanding Axon Cloud to more locations. As part of this expansion, the evidence.com URL will transition to a new web address under axon.com, such as evidence.usa.axon.com. Agencies will be migrated to this new URL over the next few months. This URL change does not impact Axon Evidence functionality or how your agency uses Axon Evidence. Existing evidence.com bookmarks and links will continue to work through automatic redirects.

For most agencies, no action is required. However, if your agency restricts outbound internet access using domain or IP allowlists, proxies, SSL inspection, or DNS filtering, your IT team may need to take a few steps to allow the updated domain. Your IT team can use the connectivity self-test page and follow the detailed technical guidance in Axon IP addresses and network requirements.

For more information, see

Contact Axon Support or your Axon representative if you have questions about these changes.

Report Writer

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

  • Now, when searching to add a person to a report, you can turn on an Include old profile versions setting. This setting broadens the list of search results and surface profiles where a name has changed or other details in the profile have been updated.
    • This is the same as the setting that appears in Search where you can set your search to include old versions of profiles.
  • Previously, reports created with the Copy Info to New Report feature did not fill in the default values configured in Form Builder for the new report's form. The most noticeable instance of this issue was the linked Incident ID, which users had to look up and re-enter into the new form.
    • Now, default values are filled in automatically for copied reports, the same as all other new reports that are created outside the Copy Info feature. The new report opens with those values already in place, so there is no need to refresh the page.
    • If a field containing a default value is changed in the original report, and a new report is created with the Copy Info feature, the value from the original report is carried over into the new report. The default value does not replace the value provided by the user who created the original report.
    • This update applies in all instances when a new report is created using the Copy Info feature: a standalone form, a citation, a crash, a Standards event, or a new incident.
  • This update only applies to organizations using the Move Charges to Past Incidents feature. Previously, when moving charges to a past incident, the incident selection list could include incidents where the person already had a finalized arrest. With this update, incidents where the person already has a finalized arrest no longer appear in the Incident ID field on the Move Charges to Past Incidents tab or in the Search Incidents pane.
    • In the list of incidents associated with the person, those entries now show a disabled action with a tooltip explaining why the incident cannot be selected. Eligible incidents continue to appear and behave as before.

Task Inboxes

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

  • Now, when a report is marked as urgent during submission to the Records Review state, an Urgent stamp appears on the report in the Records Tasks inbox. Additionally, these urgent reports are listed at the top of the inbox.
    • This update only applies to newly created reports; it does not impact reports created before this feature release.

The following update has been applied to the production environments of all organizations.

  • You can now save search configurations (search terms, filters, sorting, etc.) to quickly re-run common search queries.
    • To create a saved search, first configure your search using filters, the search box, and other search options like sort order, and then save and name your search. When you return to search, you can choose a saved search from the dropdown near the search box to immediately re-run that search.
    • For more information, see Saved searches.

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

  • In Location search, you can now search for verified cross streets/intersections using the top search box.
  • A new toggle appears inside the User search filters in the Search module and User search fields in reports (such as Officer). When this toggle is turned on, any users whose Axon Evidence accounts have been deactivated are included in search results. If the toggle is disabled, those users are excluded from your search.
    • Additionally, when the toggle is turned on and inactive users appear in the search, [INACTIVE] is displayed beside the name of any users whose Axon Evidence accounts have been deactivated. Inactive users appear at the bottom of the list of users.
    • This toggle only appears in Search and in User search fields in reports. It does not appear other user search areas (Case inbox filters, task assignment fields, etc.).
    • The toggle to include inactive users in the search results is turned on by default. If you would prefer to have the toggle turned off by default, contact your Axon representative or Axon Support (users can still turn the toggle to include inactive users in their search).

Notifications

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

  • You can now view notifications from a new Notification Center that can be accessed by selecting the bell icon in the main navigation menu. Filter notifications by all or unread, and select a notification to open the report. By default, the Notification Center only includes shared report notifications.
    • Contact your Axon representative or Axon Support for assistance configuring the Notification Center to also include all email notifications configured for your organization.
    • For more information, see Notification Center.
  • You can now share a report directly from Report Writer by sending it to specific people, Command Hierarchy groups, or teams, either while working on the report or when you submit it. Recipients receive an email and a Notification Center alert, and you can check who a report's been shared with from the Share history tab in a report.

Case Management

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

  • You can now manually reorder case tasks within a case.
    • Open a case and go to the Tasks tab. Select Edit Task Order in the top right corner of the tab. While in this Edit mode, you can drag and drop tasks to any position in the list, or type a number in the Order column to move a task to a specific location in the list.
    • The updated order is immediately reflected for all users who have access to the case and persists across sessions — including after logging out and back in, or navigating away from the case and returning.
    • Tasks cannot be reordered while a case is in a Closed or In Review disposition.

Property Management

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

  • You can now update the retention date of property items from a new action pane. Previously, retention dates could only be updated from the Update status/disposition pane. This new experience lets you update property retention dates without also needing to update the property disposition/status.
    • This new Set Retention Date pane can be accessed from the Actions menu in the following locations:
      • Property search
      • Property profiles
      • Property scan dashboard
    • Retention updates are logged in the Chain of Custody.
    • This update does NOT apply to organizations who use the Authorized Disposition feature. These organizations can continue to update retention dates when updating the Authorized Disposition.
    • Similarly, this new Set Retention Date pane is NOT an option for property containers. Retention dates must be set for each individual item.

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

  • Previously, you could enter a new property location and select Move directly on the property profile page to move a property’s location. This interaction could be confusing and unclear if the property actually was updated. Now, the property location field no longer appears on the property profile. Instead, you can click the Move button, and a Move To pane opens where you can enter a new location and capture your signature (if required by your organization’s policies). This is the same Move to pane that appears when you move items from Property search.
    • This update removes confusion around property movement actions and creates a more consistent workflow between the property profile and Property search actions.

Form Builder

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

  • Axon Records now automatically clears out leftover report data that can get stranded when a report's Purpose change hides a section — for example, when an offense section disappears after switching a report to Field Interview.
    • This update resolves the reported issue where some reports showed an "Unable to Save" error, or were submitted to the state NIBRS system missing information that should have been included.
    • If your organization is unable to save a report due to a Purpose change, or a NIBRS rejection that traces back to leftover offense/vehicle/property data, contact your Axon representative or Axon Support to see if this feature can be enabled for you.

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 issue will be resolved on October 6, 2026.

  • An issue has been resolved where when searching for evidence to add to a report, partial text searches were not working. Instead, search results would only appear for an exact match.
    • This has been resolved, and evidence search now respects partial text searches.

NIBRS

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

California organizations

The following updates will be applied to the production environments of all California organizations on October 20, 2026.

  • An issue has been resolved where California NIBRS submissions were rejected with Error 352 ("Data Elements 15–22 must be blank when Property Loss Code = 1 or 8") when a vehicle on the report had Vehicle Status set to None or Unknown. The submission file was including Vehicle Type even though those data elements must be omitted for that property loss code.
    •   Vehicle Type and related vehicle data elements are now omitted from the submission file when Vehicle Status is None or Unknown. Officers can still enter vehicle information on the report in Axon Records; that information is simply not sent to the state when it is not required.
    • If your agency received Error 352 on submissions with vehicles set to None or Unknown, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents regenerated and requeued.
  • An issue was resolved where Victim Details on the Organization card appeared only when Victim was the organization's first role. If another role was entered first, such as Legal Owner or Registered Owner, and Victim was added afterward, Victim Type did not display and California NIBRS submissions could fail because Victim Type was missing.
    • Victim Details now displays whenever the organization has a Victim role, regardless of the order the roles are entered. If the organization is not a Victim, Victim Details stays hidden.
    • If an incident could not be submitted because Victim Type could not be entered for an organization victim, reopen the report, enter Victim Type, and resubmit.

Colorado organizations

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

  • An issue has been resolved where Colorado NIBRS required a drug property to be linked to a DUI-D offense even when no arrest was present.
    • A linked drug property is now required only when the DUI-D offense has an arrest. Property Status on that drug item now includes N/A as well as 1 - None, so non-reportable property can be linked without an invalid property type error.
    • No action is required. The updated validation applies automatically on new and reopened reports.
  • An issue was resolved where Colorado NIBRS submissions were rejected with C69 Invalid arrestee POB when an arrestee's Place of Birth was XX - Unknown. The submission file was sending UN instead of XX. Place of Birth XX - Unknown is now sent as XX, which Colorado accepts.
    • If your agency received C69 rejections for arrestees with Place of Birth XX - Unknown, contact Axon Support or your NIBRS Customer Support Specialist to have those submissions regenerated and requeued.

Louisiana organizations

The following update will be applied to the production environments of all Louisiana organizations on October 6, 2026.

  • The Louisiana NIBRS validation for Value of Property (Data Element 16) has been updated to match LIBRS requirements across property descriptions and loss types. Previously, Value of Property could be left blank or set to a value the state does not allow for some property types, which could cause the state repository to reject the submission.
    •   Users will now see validation in Axon Records when Value of Property is required, must be $0, or is not permitted for the selected property type and loss type. This builds on the mandatory-zero property types addressed in a prior update (Credit/Debit Cards, Nonnegotiable Instruments, and related document and identity property types).
    • No action is required. The updated rules apply automatically when entering property on an incident. If your agency submitted property with an invalid or missing value, please contact Axon Support or your NIBRS Customer Support Specialist to have affected incidents corrected and requeued.

The following update will be applied to the production environments of all Louisiana organizations on October 20, 2026.

  • An issue has been resolved where Louisiana NIBRS submission files included incorrect property-to-offense links when the same property was associated to more than one offense with different Property Status values. The file was creating extra links that did not exist on the incident report, including Property Status combinations that are not valid for that offense, which caused rejections at the Louisiana state repository.
    • The submission file now creates property-to-offense associations only for the offenses and Property Status values entered on the report for each property item.
    • If your agency received repository rejections for invalid or unexpected property-to-offense associations on multi-offense incidents, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents regenerated and requeued for submission.

Michigan organizations

The following update will be applied to the production environments of all Michigan organizations on October 20, 2026.

  • MICR Error 918 was resolved where the same Property Item Number was used more than once when property rows shared a MICR property class but had different loss types.
    • Michigan NIBRS export now assigns a unique item number to each distinct loss type, except a valid Stolen (7) and Recovered (5) pair on the same item, so reports are not rejected for duplicate item numbers.
    • No action is required. The corrected export behavior applies automatically.

Ohio organizations

The following update will be applied to the production environments of all Ohio organizations on October 6, 2026.

  • The Ohio NIBRS validation rule for ORC 2903.12 offenses has been corrected so that the Weapon/Force Type field only accepts values consistent with the reported Type of Injury. Previously, some invalid weapon selections could be entered without an error, including when Type of Injury was None, Apparent Minor Injury, or Unknown.

Oklahoma organizations

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

  • An issue was resolved where Oklahoma NIBRS submissions with Vehicle Status set to 4-Damaged did not include the required property loss code or a Vehicle Code Type flag of true. Oklahoma rejected those submissions with "At least one Vehicle Code Type must be 'true'."
    • The submission file now includes the correct loss code and Vehicle Code Type when Vehicle Status is 4-Damaged.
    • If your agency has already received this rejection, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.

Pennsylvania organizations

The following update will be applied to the production environments of all Pennsylvania organizations on October 20, 2026.

  • An issue was resolved for Pennsylvania NIBRS where required arrestee information was not enforced when an Arrestee was added to an incident. Arrest Location—including latitude and longitude required for Pennsylvania submissions—and Ethnicity could be left blank even though they are required for arrest reporting.
    • When you add an Arrestee, Arrest Location (including latitude and longitude) and Ethnicity must now be completed before the report can be submitted, consistent with FBI NIBRS requirements for arrestees. Ethnicity remains conditionally required for Victims and Offenders as before.

Virginia organizations

The following update will be applied to the production environments of all Virginia organizations on October 20, 2026.

  • An issue was resolved where Virginia NIBRS submissions were rejected with Error 40E_VA ("VA Victim LEOKA must contain a valid Arrestee or Offender Seq. Number associated with incident"). The Victim segment's LEOKA Victim Offender/Arrestee Relationship field was not writing the correct offender or arrestee sequence number into the submission file.
    • The submission file now includes the correct sequence number so LEOKA victim relationships export correctly.
    • If your agency was previously experiencing this error, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.

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.

Profiles

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

  • You can now add a flag to people and vehicles directly from Report Writer. Previously, you had to open the profile to add the flag.
    • You can also see any flags that have already been added to that profile directly within Report Writer. The flag description for flags added this way display the Report ID they were added from.

Standards general release

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

Axon Evidence URL change

To support growing evidence volumes, storage needs, and AI-powered workflows, Axon is expanding Axon Cloud to more locations. As part of this expansion, the evidence.com URL will transition to a new web address under axon.com, such as evidence.usa.axon.com. Agencies will be migrated to this new URL over the next few months. This URL change does not impact Axon Evidence functionality or how your agency uses Axon Evidence. Existing evidence.com bookmarks and links will continue to work through automatic redirects.

For most agencies, no action is required. However, if your agency restricts outbound internet access using domain or IP allowlists, proxies, SSL inspection, or DNS filtering, your IT team may need to take a few steps to allow the updated domain. Your IT team can use the connectivity self-test page and follow the detailed technical guidance in Axon IP addresses and network requirements.

For more information, see

Contact Axon Support or your Axon representative if you have questions about these changes.

Report Writer

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

  • Now, when searching to add a person to a report, you can turn on an Include old profile versions setting. This setting broadens the list of search results and surface profiles where a name has changed or other details in the profile have been updated.
    • This is the same as the setting that appears in Search where you can set your search to include old versions of profiles.
  • Previously, reports created with the Copy Info to New Report feature did not fill in the default values configured in Form Builder for the new report's form. The most noticeable instance of this issue was the linked Incident ID, which users had to look up and re-enter into the new form.
    • Now, default values are filled in automatically for copied reports, the same as all other new reports that are created outside the Copy Info feature. The new report opens with those values already in place, so there is no need to refresh the page.
    • If a field containing a default value is changed in the original report, and a new report is created with the Copy Info feature, the value from the original report is carried over into the new report. The default value does not replace the value provided by the user who created the original report.
    • This update applies in all instances when a new report is created using the Copy Info feature: a standalone form, a citation, a crash, a Standards event, or a new incident.

Search

The following update has been applied to the production environments of all organizations.

  • You can now save search configurations (search terms, filters, sorting, etc.) to quickly re-run common search queries.
    • To create a saved search, first configure your search using filters, the search box, and other search options like sort order, and then save and name your search. When you return to search, you can choose a saved search from the dropdown near the search box to immediately re-run that search.
    • For more information, see Saved searches.

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

  • A new toggle appears inside the User search filters in the Search module and User search fields in reports (such as Officer). When this toggle is turned on, any users whose Axon Evidence accounts have been deactivated are included in search results. If the toggle is disabled, those users are excluded from your search.
    • Additionally, when the toggle is turned on and inactive users appear in the search, [INACTIVE] is displayed beside the name of any users whose Axon Evidence accounts have been deactivated. Inactive users appear at the bottom of the list of users.
    • This toggle only appears in Search and in User search fields in reports. It does not appear other user search areas (Case inbox filters, task assignment fields, etc.).
    • The toggle to include inactive users in the search results is turned on by default. If you would prefer to have the toggle turned off by default, contact your Axon representative or Axon Support (users can still turn the toggle to include inactive users in their search).

Notifications

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

  • You can now view notifications from a new Notification Center that can be accessed by selecting the bell icon in the main navigation menu. Filter notifications by all or unread, and select a notification to open the report. By default, the Notification Center only includes shared report notifications.
    • Contact your Axon representative or Axon Support for assistance configuring the Notification Center to also include all email notifications configured for your organization.
    • For more information, see Notification Center.
  • You can now share a report directly from Report Writer by sending it to specific people, Command Hierarchy groups, or teams, either while working on the report or when you submit it. Recipients receive an email and a Notification Center alert, and you can check who a report's been shared with from the Share history tab in a report.

Case Management

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

  • You can now manually reorder case tasks within a case.
    • Open a case and go to the Tasks tab. Select Edit Task Order in the top right corner of the tab. While in this Edit mode, you can drag and drop tasks to any position in the list, or type a number in the Order column to move a task to a specific location in the list.
    • The updated order is immediately reflected for all users who have access to the case and persists across sessions — including after logging out and back in, or navigating away from the case and returning.
    • Tasks cannot be reordered while a case is in a Closed or In Review disposition.

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 issue will be resolved on October 6, 2026.

  • An issue has been resolved where when searching for evidence to add to a report, partial text searches were not working. Instead, search results would only appear for an exact match. This has been resolved, and evidence search now respects partial text searches.

Axon Notes Module

Note

The Axon Notes Module contains a set of features that enable digital in-field note writing. Contact your Axon representative or Axon Support to discuss if this product is a good fit for your organization's use case.

General release

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

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

  • An issue has been resolved where the Notes preview now shows the Call Type Description. Previously it showed the Call Type Code.

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

  • You can now add a supplement to a finalized note directly from the Notes task list, without opening the note.
    • If the note already has a supplement in progress, a message notifies you of the existing supplement and lets you open that supplement instead of creating a new one.
  • Previously, if a note had offline edits stored locally on a user’s mobile device but was finalized from the desktop application, users couldn’t discard the local edits on their mobile device.
    • With this change, A Discard Edits button now lets users discard offline notes from the Axon app.

Axon DataStore

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

Upcoming deprecations

  • DataStore administrators with access to the DataStore Access Control tools can now generate and manage their own access credentials from within the Administrator Console. To continue to streamline access management, Axon will deprecate legacy DataStore user accounts on September 30, 2026.
    • These legacy accounts are those that were created by the Axon Support team before the DataStore Access Control tools were released. Legacy accounts cannot be migrated and must instead be recreated from within the Administrator Console.
    • See DataStore Access Control for full instructions on creating and managing DataStore user accounts. If you have any questions or need assistance, please contact your Axon representative or the Axon Support team.
  • To ensure a reliable connection, you must connect to the DataStore using your agency-specific server address: pus1ge1-[AgencyName].database.usgovcloudapi.net
    • You can find your exact server address in the DataStore Secret Generation tool in the Administrator Console. For more information about this tool, see DataStore Access Control - Secret Generation.
    • Connections to the following generic addresses (without an agency name) may fail and should not be used:
      • pus1ge1-axon-datastore-tx.database.usgovcloudapi.net
      • pus1ge1-axon-datastore-va.database.usgovcloudapi.net
    • If your connection is working today, no action is needed. If you're using one of the generic addresses listed above, update it to your agency-specific address to ensure continued connection to the DataStore. Please contact your Axon Support if you need assistance.