June 16 and 30, 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 June:

• June 16, 2026
• June 30, 2026

These notes include all items in the June 16 and 30 releases. See the previous notes for items included in the June 2 release.

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 release items for Records in June.

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 June 16, 2026.

• This update only applies to organization’s that use site attributes.
  • If a user is assigned to one primary site attribute in Command Hierarchy, that primary site attribute will be selected by default when the user creates a new report.
  • If a user is assigned to multiple primary site attributes, the attributes will be sorted in alphabetical order, and the first one site will be selected when the user creates a new report.

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

• 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.

Task Inboxes

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

• You can now work with Axon Support or your Axon representative to disable routing notes for reports that move through specific workflows.

Search

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

• Incident and standalone report search results now display linked persons and vehicles.
  • On incident search result cards, the names of involved vehicles and people as well as the roles they played in the incident are displayed; on standalone documents, associated people and vehicle names are displayed (but not role information).

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

• 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.
• You can now use a new Evidence ID filter to search for reports using the Evidence ID or name of attached evidence.
  • Note that you cannot currently export the Evidence ID or name of the attached evidence when exporting reports from search. The export improvement will be included in a future release.
• You can now can search for reports by a user’s name in the top search box and more reliably find reports authored by that user. This improvement will be rolled out gradually over several weeks and will be fully available by the beginning of July.

Case Management

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

• You can now select multiple units from the Unit filter in case management inboxes. This enhancement helps you more easily view and manage cases for multiple units at the same time without having to manually switch between units.
• You can use a new privilege, Edit due dates for auto-created tasks, to control which users can update the due dates of templated case tasks. (Templated case tasks are tasks that are automatically created when an incident is created.)
  • This new privilege helps you maintain the integrity of investigative workflows by preventing unauthorized or untracked schedule changes. By limiting who can adjust case task due dates, you can improve accountability, support internal policies and compliance requirements, and gain greater confidence that case timelines accurately reflect approved operational decisions.

Analytics

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

• Administrators who can access the Analytics tool in the Administrator Console can now copy the privileges configured for one dashboard to another dashboard.
  • For example, an administrator can copy the privilege configuration for Dashboard A to Dashboard B. As a result, all users who have access to Dashboard A can also access Dashboard B. This update makes it easier to upload new versions of dashboards without having to manually recreate privilege configurations.

Property Management

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

• You can now see Recovery details on property profiles and printed property labels.
• The Dropoff Location selector in incident reports has been improved to support infinite scrolling. You can now continuously scroll through all available dropoff locations without needing to load results manually or navigate through limited result sets.
  • When using this field, you can search for a dropoff location using any part of the location name. For example, typing “storage”, “bin”, or “1” will find Storage Bin 1.

Administrator Console

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

• This update only applies to organizations that use the site attribute feature. You can now work with your Axon representative or Axon Support to have a site attribute be added to an Add restriction rule automation. When this rule is configured, a report is restricted only if it belongs to the selected site.

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

• Now, audit log timestamps include hundredths of a second. Previously, they only included hours and minutes. This update was made to comply with CJIS Security Policy AU-8.B in CJISSECPOL v6.
• 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.

Search

The following issue will be resolved on June 16, 2026.

• Previously, Location search would occasionally fail to return results based on how the search query was entered in the search box. This issue has been resolved, and Location search functions as expected.

Axon mobile app

The following issue will be resolved on June 16, 2026.

• An issue has been resolved in the Axon mobile app where property-related forms appeared in the selection list when creating a new report. These property reports now no longer appear, consistent with the desktop Axon Records experience.

Printing

The following issues will be resolved on June 30, 2026.

• Previously in some instances, the form name would print as the title of the report instead of the print template title. This issue has been resolved, and the printout now correctly displays the title configured by the print template. The form name is printed only if a print template name has not been configured.
• Previously, when printing a supplement for an incident report (-2, -3, and later versions), the printout could include the entire report instead of only the items that were new or edited since the previous version. This issue has been resolved, and supplements now print only new and changed items, making it easy to identify what was updated in each version.

Property Management

The following issues will be resolved on June 30, 2026.

• Previously, scanning a single item in Chain of Custody (CoC) could create multiple log entries. This issue has been resolved and scanning an item now correctly generates only one log entry.
• Previously, scanning multiple property barcodes during property intake could incorrectly display an "already scanned" error when checking in or submitting items. This issue has been resolved, and items can now be scanned and checked in without receiving this erroneous message.

NIBRS

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

All organizations

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

• An issue has been resolved where the Recovery Details section on Property and Vehicle cards was incorrectly hidden in certain scenarios, preventing users from entering required NIBRS recovery information. The issue occurred when a property item had both a Status of "Recovered" and an Involvement of "Found" — the form rule incorrectly hid Recovery Details when both conditions were true simultaneously.
  • The Recovery Details section now correctly appears whenever any property or vehicle status is Recovered or any involvement is Found (or Recovered Outside Agency Stolen for vehicles), so users can always record the required recovery information.
  • No action is required. The corrected form behavior will apply automatically.
• An issue has been resolved where NIBRS submission eligibility was not respecting the organization's configured time zone when determining which incidents to include in the submission.Previously, incidents near date boundaries (especially those occurring in the evening) could be incorrectly included in or excluded from NIBRS submission files because dates were being compared in UTC rather than in the organization’s local time. For example, an incident on 02/22 at 8:17 PM Eastern would convert to 02/23 in UTC and be incorrectly picked up as eligible even though the organization’s submission begin date was 02/23.
  • The system now uses the organization’s time zone when comparing incident dates against the NIBRS submission begin date, ensuring accurate monthly reporting and flat file generation.
  • Contact Axon Support or your NIBRS Customer Support Specialist if you have any questions or concerns.

Arizona organizations

The following update will be applied to the production environments of all Arizona organizations on June 30, 2026.

• A validation rule has been added for Arizona NIBRS submissions to prevent error 390 (Illogical combinations involving burglary and motor vehicle theft). Users will now see a validation error during report writing when a property description is not logically compatible with the reported offense — for example, reporting a Property Type of "Structures - Storage" on a 220 (Burglary) offense — so the issue can be corrected before submission.
  • No action is required. The validation rule will be applied automatically.

Arkansas organizations

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

• An issue was resolved where Arkansas NIBRS submission files were missing the Property segment for incidents with a 290 (Destruction/Damage/Vandalism of Property) offense and a Property Loss Type of 4 (Damaged). As a result, property type and value information was not reported to the state.
  •  The Property segment is now correctly included in the submission file for these incidents.
  • If your organization has affected reports, contact Axon Support or your NIBRS Customer Support Specialist to have the impacted incidents requeued for submission.

California organizations

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

• The California NIBRS (CIBRS) edit 560 restriction that previously blocked same-sex victim and offender combinations on 11A (Rape) offenses has been removed.
  • The CIBRS 2023 Technical Specifications align with the FBI standard and no longer restrict same-sex combinations for 11A offenses.
  • No action is required. The updated validation will apply automatically. If your organization has previously been unable to submit 11A incidents due to edit 560 for same-sex combinations, those reports can now be submitted.
• An issue has been resolved where the Property Value field was incorrectly required on California NIBRS incidents when the Property Loss Type was set to 1 (None). Property Value is not reported when no property is involved and should not be required in that case.
  • Users can now save an incident with Property Loss Type 1 (None) without entering a Property Value.
  • No action is required. The validation will be updated automatically.

Florida organizations

The following updates will be applied to the production environments of all Florida organizations on June 30, 2026.

• An issue has been resolved where Florida NIBRS submissions were rejected by FDLE when the Bias Motivation was set to "Unknown." The system was sending an empty value for the Bias Motivation Primary Indicator field, which FDLE rejected as an invalid boolean.
  • The translator now defaults this field to "false" when the bias motivation is Unknown, allowing these submissions to process successfully.
  • If your organization was previously experiencing these rejections, contact Axon Support or your NIBRS Customer Support Specialist to resubmit affected incidents.
• An issue has been resolved where Florida NIBRS submissions failed XML schema validation with error cvc-datatype-valid.1.2.1 when Bias Motivation was set to "Unknown." The system was generating an empty value where a boolean was expected.
  • The submission file now correctly defaults or omits this field, allowing FDLE to accept the submission.
  • If your organization was previously experiencing these rejections, contact Axon Support or your NIBRS Customer Support Specialist to resubmit affected incidents.
• 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 June 16, 2026.

• An issue has been resolved where Louisiana NIBRS submission files contained duplicate offense sequence numbers, causing errors at the state repository.
  •   The system now correctly increments offense sequence numbers when the same offense is tied to multiple victims, and maintains the integrity of the property-to-offense association to prevent additional submission errors.
  • If your organization was previously experiencing these errors, contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.
• A validation rule has been added for Louisiana NIBRS submissions to prevent state rejections on incidents with a 13B (Simple Assault) offense. The Louisiana Incident-Based Reporting System (LIBRS) requires a weapon or force to be reported for 13B offenses, with an acceptable Type Weapon/Force Involved value of 40 (Personal Weapons), 90 (Other), or 95 (Unknown). Previously, users could submit a 13B offense with "Was Weapon/Force Involved" set to No, which resulted in the state rejecting the submission.
  • Users will now see a validation error if a 13B offense does not include a weapon/force value of 40, 90, or 95, preventing the rejection before submission.
  • No action is required. The validation rule will be applied automatically. If your organization has received state rejections related to missing weapon/force on 13B offenses, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents updated and requeued for submission.

Maryland organizations

The following updates will be applied to the production environments of all Maryland organizations on June 30, 2026.

• An issue has been resolved where Maryland organizations saw Error 173 rejections ("Incident Date occurred before the agency converted over to NIBRS") on incidents where the Report Date was after the organization’s NIBRS start date but the Incident Date was before it.
  •   Organizations that use the Report Date to trigger NIBRS reporting will no longer have incidents rejected based solely on the Incident Date when the report was finalized after the organization’s NIBRS submission begin date.
  • If your organization was previously experiencing these rejections, contact Axon Support or your NIBRS Customer Support Specialist to review the affected incidents.
• An issue has been resolved where Maryland NIBRS submissions were rejected with Error 206 (duplicate data values). The submission file was including duplicate Force Category Code values for the same offense, which is not permitted.
  • The translator now ensures each Force Category Code appears only once per offense in the submission file.
  • If your organization was previously experiencing this error, contact Axon Support or your NIBRS Customer Support Specialist to resubmit affected incidents.

Michigan organizations

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

• An issue has been resolved where Michigan NIBRS submissions were rejected by the MICR portal with error 943 when reporting offense 24002 (Possession of Stolen Vehicle). The Number of Stolen/Recovered Vehicles was incorrectly included in the submission file for 24002 offenses when it should only be present for offense 24001 (Motor Vehicle Theft).
  • The system now only includes the Number of Stolen/Recovered Vehicles count when the offense is 24001 (Motor Vehicle Theft) and the property meets the required class and loss type criteria. Recovery details such as recovery date are still included for all applicable recovered property regardless of offense type.
  • If your organization received MICR error 943 on prior submissions, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents regenerated and requeued.
• The arrest charge code configuration has been updated for Michigan NIBRS organizations. Several arrest charge codes were linked to incorrect offense file classes or were missing from the system, causing errors during state reporting.
  • The arrest charge codes now align with the MICR Arrest Charge Codes documentation, ensuring correct offense file class associations and complete code coverage.
  • No action is required. The updated configuration will apply automatically.
• An issue has been resolved where the Juvenile Arrest Disposition value was not included in Michigan NIBRS submission files even when the field was filled in on the report. The state was rejecting these submissions with a "Juvenile Arrest Dispo is Required" error.
  • The Juvenile Arrest Disposition now appears correctly in the XML submission file when populated on a juvenile arrestee.
  • If your organization received this rejection on prior submissions, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents regenerated and requeued.
• An issue has been resolved where the Type of Victim field did not appear on the organization victim card when the associated offense was a Group B offense, even though the organization's role was set to Victim. This was a follow-up to the earlier change that limited Type of Victim to organizations with a Victim role, which inadvertently kept the field hidden for Group B offenses that allow organization victims.
  • Type of Victim now surfaces on the organization card for Group B offenses that allow organization victims when the organization's role is Victim, so users can complete the field and submit the incident without workarounds.
  • No action is required. The updated visibility will apply automatically.
• An issue has been resolved where Michigan NIBRS submissions were rejected by the MICR portal with errors 1028 (Activity Type must be entered) and 1029 (Assignment Type must be entered).
  • The system now includes the required Activity Type and Assignment Type values in the Enforcement Official segment of the Michigan NIBRS XML submission file.
  • No action is required. The updated submission format will apply automatically to new and resubmitted incidents.
• A validation rule has been added for Michigan NIBRS submissions to prevent MICR edit 301. When the incident's Type of Clearance is set to Exceptional Clearance, at least one offender on the incident must have a non-Unknown value for Age, Sex, and Race.
  • Users will now see a validation error during report writing if every offender on a cleared incident has Unknown for one or more of those fields, so the submission can be corrected before it is sent to MICR.
  • No action is required. The validation rule will be applied automatically. If your organization has received MICR edit 301 on prior submissions, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents updated and requeued for submission.
• Validation rules have been added for Michigan NIBRS submissions to prevent multiple MICR property-related errors before submission.
  • The system now catches the following issues during report writing so they can be corrected before the file is sent to MICR:
    • Duplicate property loss types on the same property item for the same offense (edit 904)
    • Property detail fields included when the loss type is None or Unknown (edit 906)
    • Property description types not allowed for the associated offense (edit 911)
    • Recovered property descriptions restricted to allowed types for Motor Vehicle Theft offenses (edit 916)
    • More than one property item with a None or Unknown loss type on the same report (edit 918)
    • Pending Inventory listed alongside other property items (edit 927)
    • Recovered property present without a corresponding Stolen entry on the same offense (edit 969)
  • No action is required. The validation rules will be applied automatically.
• A validation rule has been added for Michigan NIBRS submissions to enforce the mutual exclusion between arrests and Exceptional Clearance. When an arrest record exists on an incident, the Exceptional Clearance disposition must be set to Not Applicable.
  • Users will now see a validation error if they attempt to set an Exceptional Clearance value on an incident that contains an arrest, preventing MICR errors 115 and 150 at state submission.
  • No action is required. The validation rule will be applied automatically.
• An issue has been resolved where the Elder Abuse Indicator validation (MICR edit 532) could incorrectly fire on non-individual victims (such as Society or Law Enforcement Officer) whose age resolved to 60 or greater.
  • The Elder Abuse Indicator is now only required when the victim is an Individual with an age of 60 or older, matching the MICR specification.
  • No action is required. The corrected validation behavior will apply automatically.

New Mexico organizations

The following update will be applied to the production environments of all New Mexico organizations on June 30, 2026.

• An issue has been resolved where New Mexico NIBRS submissions did not include the arrest segment (Segment 6) when an incident contained both Group A and Group B offenses and the arrest was linked to the Group B offense. Previously, if an officer arrested a subject for a Group B offense on a Group A incident, the arrest was dropped from the submission file.
  • The system now correctly retains Group B arrests in the submission file when a Group A offense is also present on the same incident, so the full arrest record is submitted to the state.
  • If your organization had incidents affected by this issue, contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.

New York organizations

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

• An issue has been resolved where the validation warning "Each Arrestee must have at least one Arrest Charge" displayed under the Arrest Charges heading instead of in the standard warning area on the right side of the screen.
  • The warning now appears in the correct location, consistent with how other validation flags are displayed.
  • No action is required. The corrected warning placement will apply automatically.

Ohio organizations

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

• Ohio-specific implied edit rules for statute codes 2919.22 and related subsections (2919.22A through 2919.22C1) have been added. These edits ensure the correct NIBRS offense code, victim type, and relationship requirements are enforced when Ohio organizations use these statute codes, preventing downstream submission rejections.
  • No action is required. The validation rules will be applied automatically.

Pennsylvania organizations

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

• An issue has been resolved where Pennsylvania NIBRS submissions were rejected with Error 178 (Segment Length) and Error 056 (Duplicate Incident Number). Once an agency begins participating in Cargo Theft reporting, the Administrative Segment must be formatted as 88 characters rather than 87.
  • The submission file now correctly uses the 88-character format for organizations that have started reporting Cargo Theft, preventing these rejections.
  • If your organization was previously experiencing these errors, contact Axon Support or your NIBRS Customer Support Specialist to resubmit affected incidents.

Texas organizations

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

• An issue has been resolved where Texas NIBRS flat-file submissions were rejected with Texas NIBRS Error 70 when a victim was associated to an offender using the Victim-Offender Relationship of "Otherwise Known Family." Affected submissions contained the internal relationship name in the flat file instead of the required 2-character relationship code, causing the state to reject the file.
  • The Texas NIBRS flat file now writes the correct 2-character code "OF" for the "Otherwise Known Family" relationship, so these submissions pass state validation.
  • No action is required for new incidents. If your organization has received Texas NIBRS Error 70 rejections related to this relationship, contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.

Virginia organizations

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

• An issue has been resolved where Virginia NIBRS flat-file submissions were rejected with Error 221 (Type of Weapon/Force Involved value must be entered) for offense 720 (Animal Cruelty). When no weapon was involved, the required default value of 99 (None) was not being included in the submission file.
  • The flat file now correctly outputs 99 in the first weapon slot when no weapon is reported for a 720 offense.
  • If your organization was previously experiencing this error, contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.
• An issue has been resolved where Virginia organizations received Error 219 (Invalid Type Criminal Activity/Gang Information) when submitting incidents that included offense code 520 (Weapon Law Violations). Although the Gang/Criminal Activity Involvement field was correctly hidden for this offense, the submission file was still sending a "No" value, causing the state to reject the report.
  • Affected incidents now submit without the invalid value.
  • If your organization was previously experiencing this error, 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.

There are no preview release items for Standards in June.

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 June 16, 2026.

• This update only applies to organization’s that use site attributes.
  • If a user is assigned to one primary site attribute in Command Hierarchy, that primary site attribute will be selected by default when the user creates a new report.
  • If a user is assigned to multiple primary site attributes, the attributes will be sorted in alphabetical order, and the first one site will be selected when the user creates a new report.

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

• 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.

Task Inboxes

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

• You can now work with Axon Support or your Axon representative to disable routing notes for reports that move through specific workflows.

Search

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

• Now, in Events search, search results display any people or vehicles associated with the event, along with the roles they played in the event.

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

• 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.
• You can now can search for reports by a user’s name in the top search box and more reliably find reports authored by that user. This improvement will be rolled out gradually over several weeks and will be fully available by the beginning of July.
• You can use a new Evidence ID filter to search for Standards events using the Evidence ID or the name of attached evidence.
  • Note that you cannot currently export the Evidence ID or name of the attached evidence when exporting events from search. The export improvement will be included in a future release.

Case Management

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

• You can now select multiple units from the Unit filter in case management inboxes. This enhancement helps you more easily view and manage cases for multiple units at the same time without having to manually switch between units.
• You can use a new privilege, Edit due dates for auto-created tasks, to control which users can update the due dates of templated case tasks. (Templated case tasks are tasks that are automatically created when an incident is created.)
  • This new privilege helps you maintain the integrity of investigative workflows by preventing unauthorized or untracked schedule changes. By limiting who can adjust case task due dates, you can improve accountability, support internal policies and compliance requirements, and gain greater confidence that case timelines accurately reflect approved operational decisions.

Analytics

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

• Administrators who can access the Analytics tool in the Administrator Console can now copy the privileges configured for one dashboard to another dashboard.
  • For example, an administrator can copy the privilege configuration for Dashboard A to Dashboard B. As a result, all users who have access to Dashboard A can also access Dashboard B. This update makes it easier to upload new versions of dashboards without having to manually recreate privilege configurations.

Administrator Console

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

• This update only applies to organizations that use the site attribute feature. You can now work with your Axon representative or Axon Support to have a site attribute be added to an Add restriction rule automation. When this rule is configured, a report is restricted only if it belongs to the selected site.

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

• Now, audit log timestamps include hundredths of a second. Previously, they only included hours and minutes. This update was made to comply with CJIS Security Policy AU-8.B in CJISSECPOL v6.
• 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.

Printing

The following issue will be resolved on June 30, 2026.

• Previously in some instances, the form name would print as the title of the report instead of the print template title. This issue has been resolved, and the printout now correctly displays the title configured by the print template. The form name is printed only if a print template name has not been configured.

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.

There are no preview release items for the Axon Notes Module in June.

Axon Notes Module general release

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

Shift details

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

• Users can now search for shift details directly from the Notes search. Users can look up shifts by Note ID or keyword, filter by shift start date, and select any result to view or edit the shift record. Access to shift details search is governed by the existing privileges.