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

  • August 11, 2026
  • August 25, 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.

There are no preview release items for Records in August.

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 August 11, 2026.

  • The Files list in Report Writer now displays an ID column for attached files. When reviewing or attaching evidence in a report, you can see each item's ID directly in the list without leaving Report Writer to look it up elsewhere.

Axon App

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

  • Reviewers can now review and edit incident reports directly from the Axon App, matching the desktop workflow.

Printing

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

  • When printing an incident from the incident profile page, you can now redact data from the generated PDF. Once redaction is finalized, the redacted PDF opens in a new tab and can be downloaded.
    • For more information about redaction, see Redaction.

Profiles

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

  • Now, when searching to add someone to an incident report, the person’s race, sex, and ethnicity are shown on search results (if available). This improvement makes it easier to ensure you add the correct people to your reports.

Notifications

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

  • If your organization is configured to send weekly digest emails to supervisors, the digest now includes unassigned report information to ensure unassigned reports are managed.

Case Management

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

  • The column widths on the Files tab of case profiles has been improved to increase visibility of evidence titles in the Title column.
  • The header on incident profiles now displays the Report purpose field from the incident report. This improvement lets you quickly see what type of incident occurred directly in the incident profile header, without needing to open the full incident report.

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

  • People included in the People section on incident and case profiles now display a Race field when that information is available for that person.
    • The Race field appears after Date of Birth and Sex in the format used by your organization (for example, W - White). If race data is not available for a person, the Race field is not shown (no blank placeholder appears).
    • This improvement lets you quickly see race information about a person involved in an incident without having to open their profile.

Property Management

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

  • You can now delete standalone reports once all property items have been removed from them.
  • The Property Notes feature is now separate from the notes that appear in the chain of custody.
    • You can use an Add note action on property profiles to add internal property notes to property items. These notes are stored independently of chain of custody records. When you add notes while updating a property’s status, these notes are recorded only in the item’s chain of custody. These notes do not appear on the property profile as internal property notes.

Personnel

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

  • The Export CSV action for Feedback Notes in the Personnel module now works as expected
    • To use this feature, open a feedback note, select More actions […] > Export CSV. A CSV file downloads that contains the note's details, including Type, From, To, Date, Content, Created by, Expiration date, and Acknowledgement status.

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

  • The Demographics section in the Personnel module now includes a Contact & Personal Info section for highly sensitive fields, including SSN/National ID, home/mailing address, personal email, personal phone number, and emergency contacts.
    • You can limit access to this new section to a trusted group (e.g., HR and Internal Affairs) by using a new set of View and Edit privileges. Users who currently have access to the general demographics information (e.g., rank, assignment, work phone) do not lose their access.

Records resolved issues

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

Report Writer

The following issues will be resolved on August 25, 2026.

  • Previously, locations were not displayed on the incident report and/or DataStore after the report was finalized. This issue has been resolved, and locations now display as expected.
  • An issue has been resolved where the Vehicle make dropdown menu failed to property display all available vehicle makes. This issue has been resolved, and the Vehicle make field now behaves as expected.

Printing

The following issue will be resolved on August 11, 2026.

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

Personnel

The following issue will be resolved on August 11, 2026.

  • An issue has been resolved in the Personnel module where a tooltip appearing on hover could cover the More actions [⋯] menu, preventing users from clicking it. This issue has been resolved, and the menu is now reliably clickable regardless of browser, window size, or zoom level.

Training

The following issue will be resolved on August 11, 2026.

  • An issue has been resolved in the Training module where a course with 10 or more enrolled learners displayed only a subset — regardless of the Results per page setting (10/20/50). This issue has been resolved, and all enrolled learners for a course now appear correctly.

NIBRS

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

Louisiana organizations

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

  • Resolved an issue affecting Louisiana NIBRS submissions 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. The submission file now includes segment data only when it is permitted for the associated NIBRS code, so agencies can keep collecting that information on the report without it being transmitted when it doesn't apply.
    • No action is required — the corrected behavior applies automatically to future submissions.

Maryland organizations

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

  • Resolved an issue 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 agency has received this error, please 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 August 11, 2026.

  • A regression has been resolved where Michigan NIBRS validation failed on larceny offenses 23003–23007 only when a vehicle was linked on the Vehicle card. Users entering stolen trailers, watercraft, or aircraft on the Vehicle card saw "This Offense requires an associated Property" and could not finalize the report. A vehicle entered on the Vehicle card now satisfies the offense requirement for these larceny offenses.
    • No action is required. The corrected validation behavior will apply automatically.
  • An issue has been resolved where a victim could have Victim Circumstances set to 02 – Assault on Law Enforcement Officer while that victim's Victim Type was not Police Officer / Law Enforcement Officer. The report could be finalized, but the submission was then rejected by the state with MICR Error 540. Axon Records now validates this combination during report writing so the mismatch is caught before submission.
    • No action is required. The validation rule applies automatically.
  • An issue has been resolved where Michigan NIBRS submissions were rejected with MICR error 607 (Domestic Violence Indicator cannot be Entered). The submission file was including the Domestic Violence Indicator when the victim's Victim-Offender Relationship did not allow it, such as non-DV relationships (for example, Otherwise Known or Stranger), unknown offenders, or multi-victim incidents where only some victims had a DV-type relationship. The Domestic Violence Indicator is now included or omitted for each victim based on that victim's exported relationship, rather than the value entered in the report alone.
    • If your organization has received rejections for this error code, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.
  • An issue has been resolved where Michigan NIBRS submissions did not link organization victims — such as a Business or Religious Organization — to their offenses in the submission file, even though the victim type was entered correctly on the report. Affected incidents passed validation in Axon Records but were rejected by the state for missing victim information. Organization victims are now correctly linked to their offenses in the submission file.
    • If your agency received these state rejections, please contact Axon Support or your NIBRS Customer Support Specialist to resubmit affected incidents.
  • A regression has been fixed where adding a property item with status “N/A – Do Not Report” incorrectly triggered the validation error "Property Status: A value is required for the selected offense" on property-mandatory offenses (such as 12000 – Robbery), even when another property item on the report already satisfied the requirement. You can now add Do Not Report property to keep evidence on the report without sending it to the state, as long as another property item meets the offense's property requirement.
    • No action is required. The corrected validation behavior applies automatically.
  • An issue has been resolved where Michigan NIBRS submissions for certain property offenses — Entering without Permission, Fraud/Swindle/Confidence Game, Retail Fraud – Theft, and Organized Retail Crime — could be submitted without a victim, resulting in MICR error 1001 ("No Corresponding Victim Record for Offense File Class"). A person or organization victim must now be linked to these offenses before submission, and Type of Victim can no longer be set to Society for offenses where MICR prohibits it.
    • If your agency has received MICR error 1001 on a prior submission for these offenses, please contact Axon Support or your NIBRS Customer Support Specialist to have it updated and requeued.

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

  • An issue has been resolved where a stolen structure property type (such as Single Occupancy Dwelling, Storage, or other structure types 29–35) could be entered on offenses that didn’t permit it, resulting in an MICR Error 941 rejection after the report was submitted. A validation error now appears while writing the report when a stolen structure property type is entered without a qualifying completed offense on the incident, so the mismatch is caught before submission.
    • No action is required. The validation rule will apply automatically.

North Carolina organizations

The following update will be applied to the production environments of all North Carolina organizations on August 11, 2026.

  • An issue has been resolved where the Estimated Drug Quantity field on drug property records allowed more than three digits after the decimal point. North Carolina NIBRS submissions only accept three decimal places, and the extra digits caused the state to reject the submission file. Entry is now limited to three decimal places, and previously stored values with extra precision are truncated (not rounded) when the submission file is generated.
    • No action is required for most organizations. Previously rejected submissions should resubmit successfully after this update.

Ohio organizations

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

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

Oklahoma organizations

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

  • An issue has been resolved where NIBRS submissions with Drugs/Narcotics property (Property Type 10) incorrectly included an extra Drug Type X tag when every drug property on the report listed the same drug type. Affected submissions could be excluded from FBI crime statistics. Submissions now include Drug Type X only when it is explicitly entered at the report level.
    • No action is required. Corrected submission behavior will apply automatically.

Pennsylvania organizations

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

  • A regression has been fixed where Pennsylvania NIBRS submission files incorrectly formatted the Offense Segment (Level 2) at 88 characters instead of 63 or 71 characters. Affected submissions were rejected with Error 284 and Error 201. The Offense Segment now uses the correct length based on bias motivation reporting (63 characters when only Bias Motivation #1 is reported, or 71 characters when Bias Motivations #2–#5 are reported). The Administrative Segment continues to use the 88-character format for agencies reporting Cargo Theft.
    • If your agency was experiencing these rejections, please 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.

There are no preview release items for Standards in August.

Standards general release

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

Printing

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

  • When printing an incident from the event profile page, you can now redact data from the generated PDF. Once redaction is finalized, the redacted PDF opens in a new tab and can be downloaded.
    • For more information about redaction, see Redaction.

Profiles

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

  • Now, when searching to add someone to Standards event report, the person’s race, sex, and ethnicity are shown on search results (if available). This improvement makes it easier to ensure you add the correct people to your reports.

Notifications

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

  • If your organization is configured to send weekly digest emails to supervisors, the digest now includes unassigned report information to ensure unassigned reports are managed.

Case Management

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

  • The column widths on the Files tab of case profiles has been improved to increase visibility of evidence titles in the Title column.

Personnel

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

  • The Export CSV action for Feedback Notes in the Personnel module now works as expected
    • To use this feature, open a feedback note, select More actions […] > Export CSV. A CSV file downloads that contains the note's details, including Type, From, To, Date, Content, Created by, Expiration date, and Acknowledgement status.

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

  • The Demographics section in the Personnel module now includes a Contact & Personal Info section for highly sensitive fields, including SSN/National ID, home/mailing address, personal email, personal phone number, and emergency contacts.
    • You can limit access to this new section to a trusted group (e.g., HR and Internal Affairs) by using a new set of View and Edit privileges. Users who currently have access to the general demographics information (e.g., rank, assignment, work phone) do not lose their access.

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 August 25, 2026.

  • An issue has been resolved where the Vehicle make dropdown menu failed to property display all available vehicle makes. This issue has been resolved, and the Vehicle make field now behaves as expected.

Personnel

The following issue will be resolved on August 11, 2026.

  • An issue has been resolved in the Personnel module where a tooltip appearing on hover could cover the More actions [⋯] menu, preventing users from clicking it. This issue has been resolved, and the menu is now reliably clickable regardless of browser, window size, or zoom level.

Training

The following issue will be resolved on August 11, 2026.

  • An issue has been resolved in the Training module where a course with 10 or more enrolled learners displayed only a subset — regardless of the Results per page setting (10/20/50). This issue has been resolved, and all enrolled learners for a course now appear correctly.

Axon Notes Module preview release

Note

Contact your Axon representative or Axon Support if you are interested in enabling the Axon Notes Module for your organization.

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

Axon Notes Module general release

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

There are no general release items for the Axon Notes Module in August.

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.

Updates

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

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