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

  • November 3, 2026
  • November 17, 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.

Locations

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

  • You can now record an incident location using latitude and longitude for places that do not have a valid street address such as rural areas, waterways, and mile markers. Arbitrary coordinate locations are available in the map widget and Report Writer.

Property Management

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

  • You can now split an existing property item into separate property when part of an item or a quantity of an item needs to be managed independently. This feature gives you a more accurate way to manage property when items that were originally recorded together need to follow different storage, disposition, or evidentiary paths.
    • You can chose to split property by quantity or by item. For example, 2 of 3 bullet casings can be split into their own item (quantity split) or a phone case can be split from its associated cell phone (item split). Each split creates a new child property record with its own unique property ID, while maintaining a clear relationship to the original property. When you split a property item, a custom form is created, tracking the details of the split. This form appears as a related document on the incident profile of the parent property.
    • With Split Property, users can:
      • Maintain associations: The original offense and related people of the parent property are carried into the child property.
      • Track parent and child relationships: View whether a property item was created from a split and access its related parent or child property records.
      • Maintain chain of custody: The new child property item inherits chain-of-custody history up to the point of the split and records its own activity going forward.
      • Continue managing split property independently: Child property records can be moved, released, disposed of, or otherwise managed separately from the original property.
      • Split again when needed: A property created from a split can also be split further.
  • The Axon mobile app now supports key property workflows, allowing officers and property staff to manage property while working in the field or in the property room without requiring a desktop computer.
    • Users can scan one or more property barcodes using their phone camera or a supported handheld scanner and complete the following workflows:
      • Intake: Scan and intake one or more property items.
      • Move: Move one or more property items to a different storage location.
      • Check in: Check property items back into custody.
      • Check out: Check out one or more property items while maintaining chain of custody.
      • Quality Control: Review and complete quality control tasks.
      • Update Disposition: Update the disposition of one or more property items.
      • Release: Release one or more property items.
      • Property Profile: Open an individual property profile to review property details (Associations and media are not currently displayed in the mobile experience and can continue to be accessed from the desktop experience).
    • The mobile scanning experience can be used with either the phone camera or in combination with a supported handheld scanner, giving organizations flexibility based on how they manage property today. Actions completed on mobile update the Axon Property module and are recorded consistently with the desktop experience, helping maintain accurate property records and chain of custody.

Profiles

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

  • You can now use an new person profile layout which shows every recorded past value in clear history tables. This layout helps you view previous names, dates of birth, addresses, phone numbers, IDs and other details at a glance, without hovering over each field.
    • The profile layout includes the following features:
      • Person summary: A compact summary at the top of the profile shows DOB, Description, Address, Phone, ID and Alias. A history icon on a row means earlier values exist; hover over it to see them.
      • History tables: Each section of the profile has its own table with the current value and every recorded change, newest first.
      • Layout: Flags appear on their own row under the person's name, with a history icon next to the name. See Associations and Follow stay above the summary, and the photos and View all photos sit to the right of the header.

Records general release

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

General UI and navigation

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

  • As part of ongoing software improvements, some design elements across Axon Records and Axon Standards are being updated. You may notice small changes to fonts, text sizing, and capitalization in some areas. These updates are visual only, and there are no changes to functionality.

Form One

Form One is now generally available for all US-based AI Era Plan customers. Form One makes completing the majority of web-based forms easier and reduces the amount of information officers must manually enter and re-enter as they move through their reporting workflows.

With Form One, officers can fill out forms by narrating, importing information from another screen, scanning IDs, or using transcripts from evidence uploaded to Axon Evidence. Form One is delivered through a browser extension and can be used with supported web-based forms across both Axon and third-party systems.

Learn more about Form One.

Report Writer

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

  • Now, when you search to add a person to a report then create a new person, the middle name entered in search, by hand or through an NCIC import, now carries over into the Middle Name field of the new person. Previously the middle name was dropped, so you had to type it again after adding the person.

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

  • Now, when you enter hyperlinks to internal and external sources in text fields, the links are clickable. These clickable links appear in the following field types:
    • Description
    • String
    • Text Area
    • Rich Text Editor (such as Narratives)

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

  • When searching for a vehicle to add to a report, the Model field now shows a list of options to choose from, just like the Make field.
  • 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.

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

  • When an user adds an arrest to a person in an incident report, the arrest charges for that same person from other reports linked to the incident, such as a standalone UCC, now fill the new arrest's charge fields automatically.
    • Only the charge itself is copied (statute, code and severity). Fields such as Counts, Drug Weight/Amount, Warrant Number, Judge, Date Issued and Bail Amount stay blank.
    • A charge listed on more than one linked report is copied once, and charge fields the user has already filled are not overwritten.
    • Charges from other General Offense reports in the incident are not copied, so a supplement does not repeat the original report's charges.
  • You can now move arrest charges from a current incident to a past incident directly from the incident report in Report Writer, so past incidents stay updated with the latest arrest information for NIBRS compliance. Once the current report is finalized, Axon Records automatically creates supplements for both incidents for Records to review and finalize.

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

  • You can now view your search results on a map.
    •   In Search, select the map icon to display a map alongside your search results. Map view is available when searching for reports, people, locations, organizations, calls for service, and events. Results with an associated address appear as pins on the map, and selecting a pin highlights the matching result in the list. The map updates as you change your search terms, filters, or results page.
    • For more information, see Map view.

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

  • You can now use the top search bar to find people by an alias date of birth. Searching an alias birth date in the person search returns the matching person.

Notifications

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

  • Axon Records and Axon Standards can now be configured so that your existing email notifications also appear in-app in the Notification Center.
    • For more information about the types of notifications that can appear in the Notification Center, see Rules and automations.

Case Management

The following feature will be available for all organizations to use in their production environments on November 17, 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 in the same dialog.
    • To use this feature, your organization must also be using the redesigned Axon Evidence experience.
    • For more information, see The redesigned Axon Evidence overview.

Form Builder

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

  • When you add a phone number to a person in a report, the phone number type now automatically uses the default value set for that field in Form Builder, instead of always starting as Home.
    • Form Builder administrators can now set a default phone type for a phone number field, such as Mobile, so report writers no longer need to change the type on every number they enter. If no default is set, phone number fields default to Home.
    • If users have set a phone number type for existing reports, these reports are not affected.

Records resolved issues

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

Report Writer

The following issue will be resolved on November 3, 2026.

  • Previously, on mobile, when a report had more than one Location Search field, entering an address or adding or removing a unit in one field also changed the other location fields.
    • This issue has been resolved and each Location field now keeps its own address, so changing one no longer changes the others.

Search

The following issue will be resolved on November 17, 2026.

  • Previously, when a user started typing in the search bar right after switching between search tabs, the search text could be replaced by a previously saved search. This issue has been resolved.
    • Text typed in the search bar is now kept and treated as the start of a new search. Loading a saved search from the dropdown, refreshing the page, and going back after viewing a search result still restores the saved search as expected.

Printing

The following issue will be resolved on November 3, 2026.

  • Previously, when printing citations or subdocuments containing multiple people, empty values or another person’s values would print instead of the selected person’s values.
    • This issue has been resolved and the correct values are now printed. Options with no value to display now show a numbered name (for example, "SubDocument 1") instead of a blank row.

The following issue will be resolved on November 17, 2026.

  • Previously, printing some reports could fail with an error when a field contained an invalid hidden character, such as in a charge's law summary. This issue has been resolved. Printing now removes characters that cannot be written into the document, so the PDF is produced.

Profiles

The following issue will be resolved on November 17, 2026.

  • Previously, for organizations that use both Axon Records and Axon Standards, a profile opened from Axon Records sometimes opened in Axon Standards instead, and vice versa.
    • This issue has been resolved, and profiles now open in the same product (Axon Records or Axon Standards) you opened them from, even if the other product is open in another browser tab.

Analytics

The following issue will be resolved on November 3, 2026.

  • An issue has been resolved where scheduled dashboard email subscriptions set to “Dashboard Link only” lost their applied filters when recipients clicked “View in Analytics” from the subscription email. Filters are now retained, matching the behavior of PDF and PPT downloads.

Warrants

The following issue will be resolved on November 17, 2026.

  • Previously, custom court papers created in the Warrants module did not appear on the person's profile. This issue has been resolved.
    • Custom court papers with and without a warrant entity now show in the Warrants section of the person profile, along with regular warrants.

NIBRS

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

Manual submission organizations

The following updates will be applied to the production environments of all organizations who use the Compliance module to perform manual IBRS submissions on November 3, 2026.

  • You can now use the following features:
    • Exclude from file generation: Instead of filtering reports out of submission-file generation, you can choose which reports to exclude. When excluded reports are ready for submission, they can be moved back into Ready and included in the file generation.
    • Edit notes of generated file: When generating a submission, you can now add notes. These notes can later be edited if additional tracking information needs to be captured.
  • When a Records specialist reverts finalization on a report, the Compliance module now tracks that and keeps the report out of the next submission file.
    • Generate File: The report count in the Generate File pane and the submission file it creates no longer include reports whose finalization was reverted.
    • Labels: When a report in a submission file was reverted afterward, the report view shows the Finalization Reverted label.
    • Ready tab: A report that was already in a submission file and is then reverted is moved to the Ready tab with a Finalization Reverted label, so it can be included in a future submission file once it is finalized again.
    • Status: A revert or finalize takes a few seconds to be recorded. A Reverting (Ready tab and takeover view) or Finalizing (Ready tab) status are displayed while this process takes place.

Florida organizations

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

  • An issue was resolved where Florida Uniform Arrest Affidavit (UAA) submissions could send a driver license or ID card number in the State Identification Number field, which FDLE rejects because the value is not a Florida State Identification Number. Those numbers are no longer sent in that field. Class E license variants and motorcycle licenses are also now reported with the correct driver license class.
    • No action is required for new reports. Submissions previously rejected for this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

Louisiana organizations

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

  • An issue was resolved where a 13A (Aggravated Assault) offense could be saved with Weapon/Force set to None when the Injury Type was not None. Louisiana rejected those submissions because Weapon/Force cannot be None when the Injury Type is other than None. None can no longer be selected as Weapon/Force on Aggravated Assault unless the Injury Type is None.
    • No action is required for new reports. Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

Maryland organizations

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

  • An issue has been resolved where Maryland NIBRS reports could pass validation in Axon Records but be rejected by the state when the Report Date Indicator was used to submit the Report Date instead of the incident date.
    • Validation for related dates — including arrest date, property recovery date, and clearance date — now compares against the Report Date when the indicator is enabled, matching what's sent in the submission file, and a report dated before the agency's NIBRS submission start date is correctly flagged and won't be submitted.
    • No action is required. The updated validation behavior applies automatically.

Michigan organizations

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

  • An issue was resolved where Victim Circumstance for offense 09002 allowed values other than 30 through 34, and those codes were missing on some reports. Michigan rejected the submissions with MICR error 547 (Circumstance must be 30 to 34 for Offense 09002).
    • When a victim is connected to 09002, only circumstances 30 through 34 can be selected: Child playing with weapon, Gun-cleaning accident, Hunting accident, Other negligent weapon handling, and Other negligent killings.
    • Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.
  • An MICR error 946 was resolved where a recovered automobile, bus, other motor vehicle, recreational vehicle, or truck could be connected to a 28000 (Stolen Property) offense. Those vehicle types are not valid on Stolen Property when the vehicle status is Recovered. Connect a recovered motor vehicle to 24002 (Motor Vehicle as Stolen Property) instead.
    • Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.
  • An issue was resolved where Michigan NIBRS required LEOKA fields for every law enforcement officer victim.
    • Type of Activity, Assignment Type, and ORI Other Jurisdiction now appear only when that officer is connected to 09001 (Murder/Non-Negligent Manslaughter), 13001 (Aggravated Assault), 13002 (Simple Assault), 13003 (Intimidation/Stalking), or 13004 (Non-Fatal Shooting). Type of Activity and Assignment Type are required in those cases. They stay hidden, and are not required, when the officer is connected only to another offense.
    • If the same officer is connected to one of those five offenses and another offense, the fields still show and remain required.
    • No action is required. The updated fields apply on new and reopened reports.
  • An issue was resolved on Michigan reports that include both a property offense, such as 23001, and 35001 (Drugs/Narcotics). Drug Type Suspected could appear on a property item whose only loss type was None or Unknown, and the list had no options.
    • The field now stays hidden on that property, even when another property on the report is linked to the drug offense.
    • No action is required. The updated field applies on new and reopened reports.

Minnesota organizations

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

  • An issue was resolved where a Minnesota NIBRS report could not be finalized when the location was along the southern border of the state. Latitude and longitude were limited to a range that excluded those locations. Accepted values now match the bounds provided by the Bureau of Criminal Apprehension (BCA): latitude 43.0 to 49.5 and longitude -89.0 to -97.5.
    • No action is required for new reports. Reports that were previously blocked by the old latitude or longitude range can now be completed.
  • An issue was resolved where the Multiple Arrestee Segments Indicator was left blank for an arrestee charged only with a Group B offense on a report that also included a Group A offense. The FBI rejected those submissions because the indicator was missing.
    • The indicator is now required on every arrestee when the report includes a Group A offense, and it is still left blank on a Group B-only report.
    • Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

New Mexico organizations

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

  • An issue has been resolved where New Mexico monthly submissions kept an 87-character Administrative Segment after the agency began reporting Cargo Theft. New Mexico rejected those incidents with error 178: Segment Length for the Administrative Segment (Level 1) must be 87 characters (not reporting Cargo Theft) or 88 characters (reporting Cargo Theft). Once Cargo Theft reporting is on, every Administrative Segment is 88 characters and includes the Cargo Theft indicator.
    • Monthly files previously rejected for error 178 can be regenerated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

New York organizations

The following updates will be applied to the production environments of all New York organizations on November 3, 2026.

  • Resolved an issue where New York NIBRS incidents with a 90Z (All Other Offenses) offense were submitted without a Society victim, causing the state to reject them with error 642 (At least one Victim Segment is required for an Initial Active or Replace Active Incident) and error 678 (Every Offense Segment must be linked through a VICTIM/OFFENSE LINK to at least one Victim Segment). These incidents now include a Society victim linked to the offense, and an arrest is not required.
    • No action is required for new reports. Reports previously rejected for error 642 or 678 can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.
  • An issue was resolved where a 13A (Aggravated Assault) offense could be submitted without a valid Weapon/Force value. New York rejected those submissions with error 206 (Weapon/Force is required in the first occurrence for person crimes, robbery, extortion, and weapons offenses). A valid Weapon/Force value is now required before the report can be completed, and None/Not Applicable is not accepted as the first Weapon/Force value for Aggravated Assault.
    • No action is required for new reports. Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.
  • An issue has been resolved where the Attempt Indicator after the NYS Law code on an Arrest Charge was left blank. New York rejected those submissions with error 564: The Attempt Indicator following the NYS Law code in the ARREST CHARGE must be C for Completed or A for Attempted. The submission now writes C when the offense is completed and A when it is attempted.
    • Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

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

  • A validation was added for New York NIBRS incidents so every reportable offense, including Group B offenses (such as 90Z - All Other Offenses), requires at least one associated Offender, even if the offender is Unknown. Offenses without one now show "This Offense requires an associated Offender" on the NIBRS UCR Code field. Previously these incidents were submitted and rejected by the state with error 634 (An Initial or Replace Active Incident must include at least one Offender Segment).
    • Reports previously rejected for error 634 can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

Ohio organizations

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

  • An issue has been resolved where a victim age of 16 was allowed on ORC 2907.04 (Unlawful Sexual Conduct with a Minor). Ohio requires the victim to be 13 or older and under 16. A victim age of 16 now shows: Age must be 13 or older, but less than 16.
    • Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

Oklahoma organizations

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

  • An issue was resolved where Type Weapon/Force on offense 210 (Extortion/Blackmail) did not allow NO. NO can now be selected when no weapon or force was involved. The field is still required.
    • 210 offenses that were previously blocked from completion can now be completed.

The following updates will be applied to the production environments of all Oklahoma organizations on November 17, 2026.

  • An issue has been resolved where Oklahoma submissions included property description, comments, and quantity when Property Status was None (1) or Unknown (8). Oklahoma rejected those files with an XSD schema error and with NIBRS error 352: DATA ELEMENTS 15 - 22 MUST BE BLANK WHEN PROPERTY LOSS CODE = 1 OR 8.
    • For None or Unknown, the submission now includes only the property loss code. Description and comments can still be entered on the report.
    • Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.
  • An issue has been resolved where an Oklahoma submission changed the Recovered Value of property items. On a property item with Value of $1 and Recovered Value of $0.50, the submission sent a Recovered Value of $2, and Oklahoma rejected the file. The submission now sends the Recovered Value entered on the report.
    • Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

Texas organizations

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

  • Texas NIBRS validation now follows the updated 2023 Texas specification for Fondling (11D) offenses.
    • When the victim is under 17, the offense must have Texas sex offense code 01 (Continuous Sexual Abuse of Young Child (under 14 years old) or Disabled Individual), 02 (Indecency with a Child by Contact), or 07 (Indecent Assault); when the victim is 17 or older, it must have 01 or 07. Reports that do not meet these rules show an error on NIBRS UCR Code.
    • Existing reports that trigger these errors can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

Virginia organizations

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

  • An issue was resolved where selecting None for Type of Security caused Virginia incidents to be rejected with Error 204: VA Security Type must contain a valid data value when it is entered. The submission file now reports the correct value for None.
    • No action is required for new reports. Reports previously affected by this issue can be updated and resubmitted. Contact Axon Support or your NIBRS Customer Support Specialist if you need assistance.

Washington organizations

The following update will be applied to the production environments of all Washington organizations on November 3, 2026.

  • Washington agencies can now use the WASPC 2025.0 NIBRS updates in Axon Records.
    • The update adds or renames the following:
      • Fondling (11D) is now called Criminal Sexual Contact.
      • Unfounded is now an option for Offense Attempted/Completed. A property item linked to an Unfounded offense can only be reported as Do Not Report.
      • Drone/Unmanned Aircraft System is now an option for Offender Suspected of Using.
      • Stolen Firearm and Conspiracy are now options for Type of Criminal Activity. Gang Information is now entered in its own fields, Was Gang Activity Involved? and Type of Gang Information.
      • Gunshot Wound is now an option for Type of Injury.
      • Cohabitant, Foster Parent, and Foster Child are now options for Victim to Offender Relationship. Common-Law Spouse is not valid in Washington.
      • Validation messages and the submission file were updated to match, including the Type of Injury requirement for 09A, 09B, and 09C and the age check for Foster Parent and Foster Child relationships.
    • Contact your Axon representative to have the 2025.0 update turned on for your agency. Existing forms keep their current options until they are republished.

Canadian organizations

The following update will be applied to the production environments of all Canadian organizations on November 17, 2026.

  • Form Builder Preview and Print Preview for CAN UCR forms now show the spec's built-in rules, the same as in a real report. This includes required fields, date-order checks, and UCR Violation filtering. Previously, Preview showed only the agency's custom rules.

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.

Locations

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

  • You can now record an incident location using latitude and longitude for places that do not have a valid street address such as rural areas, waterways, and mile markers. Arbitrary coordinate locations are available in the map widget and Report Writer.

Profiles

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

  • You can now use an new person profile layout which shows every recorded past value in clear history tables. This layout helps you view previous names, dates of birth, addresses, phone numbers, IDs and other details at a glance, without hovering over each field.
    • The profile layout includes the following features:
      • Person summary: A compact summary at the top of the profile shows DOB, Description, Address, Phone, ID and Alias. A history icon on a row means earlier values exist; hover over it to see them.
      • History tables: Each section of the profile has its own table with the current value and every recorded change, newest first.
      • Layout: Flags appear on their own row under the person's name, with a history icon next to the name. See Associations and Follow stay above the summary, and the photos and View all photos sit to the right of the header.

Standards general release

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

General UI and navigation

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

  • As part of ongoing software improvements, some design elements across Axon Records and Axon Standards are being updated. You may notice small changes to fonts, text sizing, and capitalization in some areas. These updates are visual only, and there are no changes to functionality.

Form One

Form One is now generally available for all US-based AI Era Plan customers. Form One makes completing the majority of web-based forms easier and reduces the amount of information officers must manually enter and re-enter as they move through their reporting workflows.

With Form One, officers can fill out forms by narrating, importing information from another screen, scanning IDs, or using transcripts from evidence uploaded to Axon Evidence. Form One is delivered through a browser extension and can be used with supported web-based forms across both Axon and third-party systems.

Learn more about Form One.

Report Writer

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

  • Now, when you search to add a person to a report then create a new person, the middle name entered in search, by hand or through an NCIC import, now carries over into the Middle Name field of the new person. Previously the middle name was dropped, so you had to type it again after adding the person.

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

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

Search

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

  • You can now view your search results on a map.
    •   In Search, select the map icon to display a map alongside your search results. Map view is available when searching for reports, people, locations, organizations, calls for service, and events. Results with an associated address appear as pins on the map, and selecting a pin highlights the matching result in the list. The map updates as you change your search terms, filters, or results page.
    • For more information, see Map view.

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

  • You can now use the top search bar to find people by an alias date of birth. Searching an alias birth date in the person search returns the matching person.

Notifications

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

  • Axon Records and Axon Standards can now be configured so that your existing email notifications also appear in-app in the Notification Center.
    • For more information about the types of notifications that can appear in the Notification Center, see Rules and automations.

Case Management

The following feature will be available for all organizations to use in their production environments on November 17, 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 in the same dialog.
    • To use this feature, your organization must also be using the redesigned Axon Evidence experience.
    • For more information, see The redesigned Axon Evidence overview.

Early Intervention System (EIS)

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

  • You can now export an EIS alert activity log to PDF.
    • To export this log, open the alert and select More actions […] > Export Alert Activity Log. The log includes a report with the officer, alert date, policy, group, assignee, and final alert status. The report also includes every activity log entry with its full notes and comments, and who made it and when.
    • This feature makes it easier to keep records for accreditation reviews such as CALEA.

Administrator Console

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

  • An issue has been resolved where the author of a Standards report could delete their own report while it was in Draft, even when their “Delete in-progress Standards reports” privilege was set to Prohibit.
    • Deleting a Draft Standards report now requires this privilege for every user, including the report’s author. Users without this privilege can no longer delete their own drafts, and administrators can grant this privilege to anyone who should keep have ability.
    • Users who already have the privilege see no change, and deleting Records reports is not affected.
    • This updates helps organizations rely on their privilege settings to protect records and keep audit trails complete.

Form Builder

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

  • When you add a phone number to a person in a report, the phone number type now automatically uses the default value set for that field in Form Builder, instead of always starting as Home.
    • Form Builder administrators can now set a default phone type for a phone number field, such as Mobile, so report writers no longer need to change the type on every number they enter. If no default is set, phone number fields default to Home.
    • If users have set a phone number type for existing reports, these reports are not affected.

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 November 3, 2026.

  • Previously, on mobile, when a report had more than one Location Search field, entering an address or adding or removing a unit in one field also changed the other location fields.
    • This issue has been resolved and each Location field now keeps its own address, so changing one no longer changes the others.

Search

The following issue will be resolved on November 17, 2026.

  • Previously, when a user started typing in the search bar right after switching between search tabs, the search text could be replaced by a previously saved search. This issue has been resolved.
    • Text typed in the search bar is now kept and treated as the start of a new search. Loading a saved search from the dropdown, refreshing the page, and going back after viewing a search result still restores the saved search as expected.

Printing

The following issue will be resolved on November 3, 2026.

  • Previously, when printing citations or subdocuments containing multiple people, empty values or another person’s values would print instead of the selected person’s values.
    • This issue has been resolved and the correct values are now printed. Options with no value to display now show a numbered name (for example, "SubDocument 1") instead of a blank row.

The following issue will be resolved on November 17, 2026.

  • Previously, printing some reports could fail with an error when a field contained an invalid hidden character, such as in a charge's law summary. This issue has been resolved. Printing now removes characters that cannot be written into the document, so the PDF is produced.

Profiles

The following issue will be resolved on November 17, 2026.

  • Previously, for organizations that use both Axon Records and Axon Standards, a profile opened from Axon Records sometimes opened in Axon Standards instead, and vice versa.
    • This issue has been resolved, and profiles now open in the same product (Axon Records or Axon Standards) you opened them from, even if the other product is open in another browser tab.

Analytics

The following issue will be resolved on November 3, 2026.

  • An issue has been resolved where scheduled dashboard email subscriptions set to “Dashboard Link only” lost their applied filters when recipients clicked “View in Analytics” from the subscription email. Filters are now retained, matching the behavior of PDF and PPT downloads.

Axon Notes Module

Note

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

General release

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

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

  • Notes search results now display a Matching reports section that lists the reports in that note (the original note and its supplements) that contain the keywords that were searched for. Select a Report ID to open that report. You will only see reports you have access to view.
    • Additionally, the date and time on each Notes search result is now labeled Created, more clearly indicating what the date indicates.

Resolved issues

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

The following issue will be resolved on November 3, 2026.

  • Previously, even if the organization was configured to prevent users from finalizing notes that contain validation errors, users could still sometimes finalize notes that contained errors.
    • This issue has been resolved, and the Finalize button is now disabled until all validation errors on the form are fixed. This update applies to both notes and shift details.

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.