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

  • July 15, 2026
  • July 28, 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 July 28, 2026. Contact your Axon representative or Axon Support to activate it for your organization.

  • You can now copy information from an Axon Records incident report directly into a new Axon Standards event report (Use of Force/R2R, Vehicle Pursuit, Vehicle Collision, Internal Complaint, or Citizen Complaint), eliminating duplicate data entry across the two products.
    • Incident date/time, location, people, and vehicles are pre-filled in the new Standards event, with demographic and sensitive fields intentionally excluded to support unbiased review.

Case Management

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

  • You can now share cases directly from Axon Records and Axon Standards without switching to Axon Evidence. The new Share case experience lets you create, view, update, and stop case shares with external partners such as your DA office.
    • When sharing, you can choose to share the entire case, a specific folder, or a selected subset of evidence. Additional sharing methods — including a secure download link and direct individual access — are also available.

Audit Log

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

  • A new version of the Audit Log Tool is now available where, administrators can filter using multiple combined criteria at the same time, including date range, actors, targets, event types, and audit types. This update makes it easier for administrators to find the exact audit data they need in a single export, without manually filtering exported audit files or combining data from multiple files.
    • Previously in the Audit Log Tool in the Administrator Console, administrators could only filter audit logs by date range and one additional criterion, such as one actor, one target, or one specific event type, including Print and DataStore Access.
    • Additionally, unlike in the old version of the tool, the filtered results are displayed directly within the Audit Log Tool, so administrators can preview them before exporting them to CSV or PDF.
    • For example in the new tool, an administrator can export audit logs for actions a user took on a specific report within a week, export audit logs for multiple reports within an incident, or export all privilege update events for a specific date.
  • The Event Type filter in the new Audit Log Tool lets administrators view several new events:
    •   Create/Update restriction classification: These events are recorded if a restriction classification is created or updated from the Restrictions tool in the Administrator Console.
    • Add privilege to team/Remove privileges from team: These events have always been tracked in the audit log but were only viewable when administrators exported an audit log for specific actors. With the new Audit Log Tool, these events now can be viewed from the Event type filter, even if the administrator does not know the specific actor who made the privilege change.

Records general release

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

Task Inboxes

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

  • 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 will be applied to the production environments of all organizations on July 15, 2026.

  • Incident and standalone report search result cards can now be configured to 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 can be displayed; on standalone documents, associated people and vehicle names can be displayed (but not role information).

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

  • Previously, when exporting Incident, Booking, Property or Vehicle search results to a CSV file, a date range was automatically applied to the result set. Now, a date range is no longer automatically applied. You can instead use date range search filters to refine which search results are included in your CSV export.
  • 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 also displayed; on standalone documents, associated people and vehicle names are displayed (but not role information).

Case Management

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

  • You can now receive an email notification when a case task on your case is marked as complete. This update is available in both Axon Records and Axon Standards for organizations with the Case Task workflow enabled.

Analytics

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

  • Analytics users can now get daily, weekly, or monthly email snapshots of their Analytics dashboards delivered right to their inboxes.
    • Simply configure the dashboard filters you want to see, then use the new Actions > Manage subscriptions option to schedule when and how frequently you’d like the email to be sent to you.
    • You can set the email to include a link to the dashboard or a downloadable export (PDF, PNG, PPT).

Property Management

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

  • You can now use an Add note button on property profiles to add internal notes to property items. These notes do NOT appear in the property item’s chain of custody.
    • You can now also add separate status update notes to property items when updating the property status. The notes provided during status changes are saved to the property item’s chain of custody.

Warrants

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

  • In the Agency Court Papers inbox, you can now filter warrants using Identity Documents.

Expungement

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

  • Administrators can now export expungement data (which users performed expungements and when) from the Expungements tool in the Admin Console as a CSV file. This functionality enables administrators to review and manipulate expungement data for state compliance.

Audit Log

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

  • Events related to multiple targets during a report update are now tracked as multi-target events in the audit log. This allows the same event to appear when exporting audit logs by report or by related entities, such as person or location.
    •  As a result, admins can see all actions related to a specific entity, such as a person or location, in a single export.
    • Previously in audit logs, events related to multiple targets during a report update, such as adding a person or location to a report, were only tracked at the report level. Administrators could only see these events when exporting audit logs for a specific report. They would not see these events when exporting audit logs for a person or location. This behavior made it difficult for administrators to track all activity related to a specific person or location, especially when they did not know which reports the person or location had been added to.
  • Three new Open events have been added to audit logs to help administrators see when a report, incident, or Standards event was opened and its full content accessed.
    • Previously, audit logs only showed “View Document,” “View Incident,” and “View Event” events. These events do not clearly indicate whether the user viewed partial information (in search results or breadcrumbs) or accessed the full content of the report, incident, or event.
    • The new Open events include:
      • Open Document
      • Open Incident
      • Open Event
    • Additionally, search keywords now appear in audit logs so administrators can see exactly what users were searching for when they viewed the document, incident, or event.
  • Previously, the View events were frequently duplicated in audit logs. With this update, duplicate View events have been removed to ensure audit logs are easier to review.
  • Two new columns now appear in audit logs in compliance with CJIS Security Policy AU-8.B in CJISSECPOL v6:
    • Device Name
      • Because Axon Records and Standards are SaaS-based and run in browsers, machine-level device information can’t be captured. However, browser-level information associated with where the action was taken is captured.
    • IP Address
  • 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.

Form Builder

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

  • You can request that Axon Support or your Axon representative customize the metadata displayed at the top of printed reports and sub-documents.
    • You can define exactly which fields appear in the header, their display order, and whether each field displays dynamic report data (author, date, etc.) or static text.

Axon App

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

  • Officers and report authors can now access the full set of routing options when submitting custom Axon Records standalone reports from the Axon mobile app.
    • The mobile routing screen now includes assignee selection, District/Attribute Group selection, and the ability to mark a report as urgent. These are the same options that appear on desktop for all users with the same roles and permissions.

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 July 15, 2026.

  • Previously, unassigned warrants would display as Assigned in the Agency Court Papers inbox. This issue has been resolved, and warrants will now display the correct assignment.

NIBRS

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

All organizations

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

  • Manual submission is now available in the Compliance module in Axon Records (Early Access). Organizations that report compliance data in batches as flat files (currently NIBRS and Citations, with more report types coming) can now review, package, and download their submission files directly in Records. This new experience replaces the existing IBR Submission flow in the Tasks inbox and will support additional compliance report types over time.
    • This experience includes:
      • Filtering and sorting: Choose which reports go into a submission — include or exclude specific reports before generating the file.
      • Custom file names and notes: Name submission files and add or edit submission file notes for easier tracking.
      • Reliable file generation: With improved file generation success rates, see which reports caused a failure and should be corrected.
    • Each compliance reporting integration appears as its own inbox (for example, IBR Submissions Manual).
      • In the compliance inbox, the Ready tab lists every finalized report not yet submitted, with filters for Report ID, Occurrence Date, Created Date, and Finalized date. Filter to exactly the reports you want, select Generate File, and name it — Axon Records builds the submission file in the background. The Submitted tab tracks every file you've generated, showing its status (Generating, Available, Generation Failed), report count, and note. You can download these files, view their contents, then regenerate or delete as necessary. Once you’ve downloaded the file from Axon Records, you can deliver it to your state or reporting system.

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

  • An issue has been resolved where an incident could submit two Aggravated Assault/Homicide Circumstances (Data Element 31) values from mutually exclusive categories on the same victim, returning NIBRS Error 456 (values are mutually exclusive). Reports now submit only the applicable circumstance value so this rejection no longer occurs.
    • No action is required. The updated behavior will be applied automatically.

Arizona organizations

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

  • An issue has been resolved where an Arizona NIBRS victim-to-offender relationship requirement could be satisfied by a non-reportable role (such as Reporting Party) instead of the victim, allowing incidents to be submitted with a missing or incorrect relationship and rejected by the state. Validation now requires the relationship to be entered on the victim, and the submission no longer reports a relationship when none has been entered on the victim.

California organizations

The following updates will be applied to the production environments of all California organizations on July 15, 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 victims, property, and vehicles linked only to an offense marked Exclude from NIBRS were omitted from California NIBRS (CIBRS) submissions. When multiple offenses on the same incident share the same NIBRS code but different CJIS codes, CIBRS requires the organization to exclude duplicate offenses while still reporting victims, property, and vehicles from those excluded offenses on the surviving same-UCR offense. The submission file now includes these rolled-up victims, property, and vehicles.
    • If your organization has incidents where victims, property, or vehicles may have been underreported due to this issue, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents regenerated and requeued for submission.

The following update will be applied to the production environments of all California organizations on July 28, 2026.

  • An issue has been resolved where California NIBRS incidents received error CA922 for the Senior Citizen Indicator when a victim's age was entered as a range (for example, 50-70). The indicator was being evaluated using the maximum age in the range instead of the minimum age, so it could incorrectly report the victim as a senior citizen when the minimum age was under 60. The Senior Citizen Indicator now evaluates the minimum age, matching California's rule, so age-range entries validate correctly.

Florida organizations

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

  • An issue has been resolved where Florida NIBRS submissions were rejected by FDLE when an incident contained two or more offenses with the same NIBRS code. The submission file now merges duplicate offenses into a single offense per NIBRS code, combining weapons, bias motivation, and other offense data as required for FDLE reporting.
    • No action is required for new incidents. If your organization has received FDLE rejections for duplicate NIBRS offense codes, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents regenerated and requeued for submission.

Louisiana organizations

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

  • An issue has been resolved where Louisiana NIBRS submissions were missing property-to-offense associations when a single piece of property was linked to more than one offense. The submission file now includes a property-to-offense segment for every offense a property is linked to, and correctly reflects the property status for each linked offense, preventing Louisiana state repository rejections caused by missing property segments.
    • If your organization has received repository errors for missing property segments on multi-offense incidents, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents regenerated and requeued for submission.
  • An issue affecting Louisiana NIBRS submissions has been resolved. Group B incidents were being sent to the state with an action type of "A" instead of "I" (new insert), which could block them from being accepted for state certification. Group B incidents now submit with the same action type as Group A incidents for both the initial submission and any later updates.
    • No action is required. The updated behavior will be applied automatically.
  • An issue affecting Louisiana NIBRS submissions has been resolved where the submission file included data segments that the offense's NIBRS code does not permit — for example, weapon/force details on a Criminal Damage to Property (290) offense — causing errors at the state repository. The submission file now includes segment data only when it is permitted for the associated NIBRS code, so organizations can keep collecting that information in the report without it being transmitted when it does not apply.
    • No action is required. The updated behavior will be applied automatically.
  • A new Louisiana NIBRS validation rule now requires at least one Individual victim on Robbery (120) offenses. Organizations were receiving state repository errors when robbery incidents included business victims but no individual victim. Business victims may still be entered on robbery offenses, but the report will now show a validation error during report writing unless at least one victim has Type of Victim set to Individual.
    • No action is required. The validation rule will be applied automatically.

Maryland organizations

The following update will be applied to the production environments of all Maryland organizations on July 28, 2026.

  • An issue has been resolved where Maryland NIBRS submissions were rejected with the error "The string '' is not a valid Boolean value - OffenseAttemptedIndicator," even though the offense's Attempted/Completed selection was filled out in the report. The submission file now correctly includes the Attempted/Completed value (Offense Attempted Indicator) so these incidents are no longer rejected.
    • If your organization has received this error, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents regenerated and requeued for submission.

Michigan organizations

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

  • A new Michigan NIBRS validation rule now requires vehicle status Destroyed/Damaged/Vandalized when a vehicle is linked to a completed Damage to Property offense. Property status on completed Damage to Property offenses were already validated; vehicle-linked records now follow the same requirement. Users will see a validation error during report writing if the vehicle status does not include Destroyed/Damaged/Vandalized on a completed Damage to Property offense. Validation for attempted Damage to Property offenses and other offense types is unchanged.
    • No action is required. The validation rule will be applied automatically.
  • An issue has been resolved where Property Value was not consistently required on Michigan NIBRS incidents when Property Type was set to Other. Users will now see a validation error during report writing if Property Value is missing for this property type, aligning with MICR requirements. Existing recovered-value rules and validation for other property types are unchanged.
  • A new Michigan NIBRS validation rule now requires the victim's age to be less than the offender's age when the Victim-Offender Relationship is Parent, Grandparent, or Foster Parent. Previously, reports could pass validation even when the victim was the same age or older than the offender. Users will now see a validation error during report writing when ages do not meet MICR requirements for these relationship values.
    • No action is required. The validation rule will be applied automatically.
  • An issue has been resolved where Michigan NIBRS reports could be submitted with Offender Suspected of Using set to No for offenses 26005 and 26008, causing MICR error 182 (Offender Suspected of Using must equal C when Offense File Classes 26005 and/or 26008 exist). For these two offenses, Offender Suspected of Using is now required to be Computer Equipment, and a validation error will appear during report writing if it is not.
    • No action is required. The validation rule will be applied automatically.
  • An issue has been resolved where Michigan NIBRS validation incorrectly enforced two property requirements on certain property offenses (such as 23H and 26A). Users saw both "This Offense requires an associated Vehicle or Property" and "This Offense requires an associated Property," which caused unnecessary validation failures and forced extra data entry. Only the single rule requiring an associated vehicle or property is now enforced, matching Michigan TS NIBRS requirements.
    • No action is required. The corrected validation behavior will apply automatically.

Minnesota organizations

The following update will be applied to the production environments of all Minnesota organizations on July 15, 2026.

  • An issue was resolved where Minnesota NIBRS XML submissions were missing the NIBRS Property Category code (ItemCategoryNIBRSPropertyCategoryCode) for property items on an incident, causing the submission to fail validation. Production submissions for the same incident included the required element, but affected reports did not. The NIBRS Property Category code is now included correctly in the submission file when property is reported on an incident.
    • If your organization received a submission validation error for a missing NIBRS Property Category code, contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.

The following update will be applied to the production environments of all Minnesota organizations on July 28, 2026.

  • A new Minnesota NIBRS validation rule now requires Email Type when an email address is entered for a person on an incident report. This prevents CRS schema validation failures caused by missing EmailAddressTypeCode in the submission file.
    • No action is required. The validation rule will be applied automatically.

New York organizations

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

  • An issue has been resolved where NYIBRS submissions could report blank values for Incident Occurrence Date and Time when Date/Time of Occurrence was marked Unknown. Submissions now report the required placeholder values (99999999 for date, 9999 for time) in this scenario, preventing related validation errors.

Ohio organizations

The following updates will be applied to the production environments of all Ohio organizations on July 15, 2026.

  • An issue has been resolved where completed ORC 2909.07 (Criminal Mischief) offenses coded as 90Z incorrectly required associated property or vehicle information even when nothing was stolen or damaged. Users previously received the validation error "NIBRS UCR Code: This Offense requires an associated Vehicle or Property" and could not submit the report without entering inaccurate property data. Reports for this scenario can now be validated and submitted without property, matching Ohio reporting guidance.
    • No action is required. The validation rule will be applied automatically. If your organization has incidents stuck on this validation error, contact Axon Support or your NIBRS Customer Support Specialist to update the affected incidents and requeue them for submission.
  • An issue has been resolved where Ohio NIBRS submissions were rejected with error 5042-99 when an incident had multiple suspects and at least one victim was also an arrestee or offender on another offense. The submission file was missing victim-to-suspect relationship entries for some suspect-and-victim combinations, even when the relationships were entered correctly on the report. The submission file now includes the required victim-to-suspect links for all suspects on each Individual and Police Officer victim.
    • If your organization has received Ohio error 5042-99 on affected incidents, contact Axon Support or your NIBRS Customer Support Specialist to have the impacted incidents regenerated and requeued for submission.
  • 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.

The following updates will be applied to the production environments of all Ohio organizations on July 28, 2026.

  • An issue has been resolved where Ohio NIBRS submissions for ORC 2921.33 and 2921.33A incorrectly included Type of Criminal Activity (Data Element 17), causing the state to reject the report with Error 2046. This occurred when the victim type was not Law Enforcement Officer (P) but the submission still sent a criminal activity value — including when "Was Criminal or Gang Activity Involved?" was set to “No”. Type of Criminal Activity is now omitted from the submission unless all Ohio-required conditions are met: victim type P, a weapon/force code other than 17 or 99, and Officer Injury Type other than 0.
    • If your organization previously received Error 2046 on incidents with these statute codes, contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.
  • A new Ohio NIBRS validation rule for ORC 2907.12 has been added so that an error is shown when this offense code is used with an incident date after September 3, 1996. This code is not valid for later incident dates, and the rule prevents state rejections for this implied edit.
  • The Ohio NIBRS validation rules for ORC 2907.05 and 2907.06 have been corrected so that the Victim-to-Offender relationship can no longer be Spouse (SE). This matches the existing rule for ORC 2907.04 and prevents state rejections for these codes.
  • The Ohio NIBRS validation rules for ORC 2907.03 subsections A5, A7, A8, A9, A11, A12, and A13 have been corrected. When the victim is 12 years old or younger and the same gender as all offenders, and the injury type is anything other than Apparent Minor Injury, Aggravated Assault/Homicide Circumstances are now required and can no longer be set to 07 - Mercy Killing, matching Ohio's implied edit.
  • The Ohio NIBRS validation rules for ORC 2907.03 (and subsections A1, A2, A3, A4, A6, and A10) have been corrected. When the victim is the same gender as all offenders and the injury type is anything other than Apparent Minor Injury, Aggravated Assault/Homicide Circumstances are now required and can no longer be set to 07 - Mercy Killing. In addition, the Victim-to-Offender relationship can no longer be Spouse (SE) for these codes, matching Ohio's requirements.
  • A new Ohio NIBRS validation rule for ORC 2907.02AS has been added so that an error is shown when this offense code is used with an incident date after July 1, 2002. This code is not valid for later incident dates, and the rule prevents state rejections for this implied edit.
  • The Ohio NIBRS validation rule for ORC 2907.02 has been corrected. When the victim is the same gender as all offenders and the injury type is anything other than Apparent Minor Injury, Aggravated Assault/Homicide Circumstances are now required and can no longer be set to 07 - Mercy Killing, matching Ohio's implied edit and preventing state rejections.
  • Ohio implied validation for ORC 2903.12 offenses has been added to align Type of Weapon/Force Used with Type of Injury per the Ohio technical specification. Previously, users could select invalid weapon values - including when Type of Injury was None (0), Apparent Minor Injury (7), or Unknown (U) - without receiving a validation error. Users will now see a validation error during report writing when the selected weapon and injury combination does not meet Ohio requirements.
    • No action is required. The validation rules will be applied automatically.
  • The Ohio NIBRS validation rule for ORC 2903.11 (Felonious Assault) has been corrected so that Weapon/Force Type can no longer be set to 17 when the injury type and Aggravated Assault/Homicide Circumstances match the rule conditions, matching Ohio's implied edit.
  • The Ohio NIBRS validation rule for ORC 2903.08 (Aggravated Vehicular Assault / Vehicular Assault) has been corrected so that Weapon/Force Type must be 35 - Motor Vehicle. Other weapon/force values are no longer accepted for this code, matching Ohio's implied edit.
  • An Ohio implied edit validation for ORC 2903.07 offenses has been added requiring the incident date to be on or before March 23, 2000. Previously, users could enter a current incident date for this offense without receiving a validation error. Users will now see a validation error during report writing if the incident date is after March 23, 2000.
    • No action is required. The validation rule will be applied automatically.
  • The Ohio NIBRS validation rule for weapons offenses (ORC 2923.12, 2923.121, and 2923.122) has been corrected so that Weapon/Force Type can no longer be set to 99 - None. Because these offenses require a weapon, the report will now show a validation error if Weapon/Force Type is left as None, preventing state rejections for this implied edit.

Oklahoma organizations

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

  • An issue has been resolved where Oklahoma organizations received a false NIBRS validation error when reporting stolen marijuana plants on a Burglary/Breaking & Entering (220) offense. When Property Status was Stolen, Property Type was Drugs/Narcotics, Drug Type was Marijuana, and Quantity Unit was NP (Number of Plants), the system incorrectly displayed: "Quant. Units: The Number of Plants value is only valid for Marijuana, Opium, or Hallucinogens" even though Drug Type was already set to Marijuana. Users can now enter stolen marijuana plant property on non-drug offenses such as Burglary without receiving this validation error.
    • No action is required. The corrected validation behavior will apply automatically.

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

  • A new Oklahoma NIBRS validation rule now requires Attempted/Completed on each offense. Per the Oklahoma (ONIBRS) specification, Attempted/Completed is mandatory for every offense, and Oklahoma rejects submissions when it is missing. Users will now see a validation error during report writing if Attempted/Completed is left blank on an offense.
    • No action is required. The validation rule will be applied automatically.

Pennsylvania organizations

The following update will be applied to the production environments of all Pennsylvania organizations on July 15, 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 organization 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.

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 July 28, 2026. Contact your Axon representative or Axon Support to activate it for your organization.

  • You can now copy information from an Axon Records incident report directly into a new Axon Standards event report (Use of Force/R2R, Vehicle Pursuit, Vehicle Collision, Internal Complaint, or Citizen Complaint), eliminating duplicate data entry across the two products.
    • Incident date/time, location, people, and vehicles are pre-filled in the new Standards event, with demographic and sensitive fields intentionally excluded to support unbiased review.

Case Management

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

  • You can now share cases directly from Axon Records and Axon Standards without switching to Axon Evidence. The new Share case experience lets you create, view, update, and stop case shares with external partners such as your DA office.
    • When sharing, you can choose to share the entire case, a specific folder, or a selected subset of evidence. Additional sharing methods — including a secure download link and direct individual access — are also available.

Audit Log

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

  • A new version of the Audit Log Tool is now available where, administrators can filter using multiple combined criteria at the same time, including date range, actors, targets, event types, and audit types. This update makes it easier for administrators to find the exact audit data they need in a single export, without manually filtering exported audit files or combining data from multiple files.
    • Previously in the Audit Log Tool in the Administrator Console, administrators could only filter audit logs by date range and one additional criterion, such as one actor, one target, or one specific event type, including Print and DataStore Access.
    • Additionally, unlike in the old version of the tool, the filtered results are displayed directly within the Audit Log Tool, so administrators can preview them before exporting them to CSV or PDF.
    • For example in the new tool, an administrator can export audit logs for actions a user took on a specific report within a week, export audit logs for multiple reports within an incident, or export all privilege update events for a specific date.
  • The Event Type filter in the new Audit Log Tool lets administrators view several new events:
    •   Create/Update restriction classification: These events are recorded if a restriction classification is created or updated from the Restrictions tool in the Administrator Console.
    • Add privilege to team/Remove privileges from team: These events have always been tracked in the audit log but were only viewable when administrators exported an audit log for specific actors. With the new Audit Log Tool, these events now can be viewed from the Event type filter, even if the administrator does not know the specific actor who made the privilege change.

Standards general release

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

Search

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

  • Now, Event search results in Axon Standards can be configured to 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 July 28, 2026.

  • Previously, when exporting Event or Vehicle search results to a CSV file, a date range was automatically applied to the result set. Now, a date range is no longer automatically applied. You can instead use date range search filters to refine which search results are included in your CSV export.
  • Event search results now display linked persons and vehicles along with the roles they played in the event.

Case Management

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

  • You can now receive an email notification when a case task on your case is marked as complete. This update is available in both Axon Records and Axon Standards for organizations with the Case Task workflow enabled.

Analytics

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

  • Analytics users can now get daily, weekly, or monthly email snapshots of their Analytics dashboards delivered right to their inboxes.
    • Simply configure the dashboard filters you want to see, then use the new Actions > Manage subscriptions option to schedule when and how frequently you’d like the email to be sent to you.
    • You can set the email to include a link to the dashboard or a downloadable export (PDF, PNG, PPT).

Early Intervention System (EIS)

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

  • EIS alerts now retain their assigned reviewer when a new qualifying incident triggers an alert recalculation, preventing alerts from silently losing ownership during the recalculation process.

Audit Log

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

  • Events related to multiple targets during a report update are now tracked as multi-target events in the audit log. This allows the same event to appear when exporting audit logs by report or by related entities, such as person or location.
    •  As a result, admins can see all actions related to a specific entity, such as a person or location, in a single export.
    • Previously in audit logs, events related to multiple targets during a report update, such as adding a person or location to a report, were only tracked at the report level. Administrators could only see these events when exporting audit logs for a specific report. They would not see these events when exporting audit logs for a person or location. This behavior made it difficult for administrators to track all activity related to a specific person or location, especially when they did not know which reports the person or location had been added to.
  • Three new Open events have been added to audit logs to help administrators see when a report, incident, or Standards event was opened and its full content accessed.
    • Previously, audit logs only showed “View Document,” “View Incident,” and “View Event” events. These events do not clearly indicate whether the user viewed partial information (in search results or breadcrumbs) or accessed the full content of the report, incident, or event.
    • The new Open events include:
      • Open Document
      • Open Incident
      • Open Event
    • Additionally, search keywords now appear in audit logs so administrators can see exactly what users were searching for when they viewed the document, incident, or event.
  • Previously, the View events were frequently duplicated in audit logs. With this update, duplicate View events have been removed to ensure audit logs are easier to review.
  • Two new columns now appear in audit logs in compliance with CJIS Security Policy AU-8.B in CJISSECPOL v6:
    • Device Name
      • Because Axon Records and Standards are SaaS-based and run in browsers, machine-level device information can’t be captured. However, browser-level information associated with where the action was taken is captured.
    • IP Address
  • 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.

Form Builder

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

  • You can request that Axon Support or your Axon representative customize the metadata displayed at the top of printed reports and sub-documents.
    • You can define exactly which fields appear in the header, their display order, and whether each field displays dynamic report data (author, date, etc.) or static text.

Standards resolved issues

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

There are no resolved issues for the Axon Standards in July.

Axon Notes Module preview release

Note

The Axon Notes Module is currently only available for use by Canadian organizations. Contact your Axon representative or Axon Support if you are a non-Canadian organization interested in using this feature.

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

Axon Notes Module general release

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

Offline notes

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

  • An issue has been resolved where offline edited notes did not sync to the cloud upon network restoration.

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.