Master Charge Tool

The Master Charge Tool lets you manage the charge list that appears in your agency's incident reports. This list is managed via CSV export and import. Using this tool, you can:

• Add new charges
• Update existing charges
• Expire charges

Users with specific privileges can access this tool by opening the Administrator Console and selecting Master Charge Tool from the tool list.

Hover over any truncated text to reveal the full text of that field. View the full charge list with the following options:

• Horizontal Scroll Bar: Use the bar at the bottom of the screen to view additional columns.
• Results Per Page: Choose between 10, 20, and 50.
• Page Numbers: Use the arrows or page numbers to skip between pages

Add and update charges

To add new charges or update existing ones, take these steps:

1. Open the Master Charge Tool and select Update Charges.
2. Select Export Charges to download a list of the charges in your agency's Master Charge Table then select
3. Follow the instructions for updating the Master Charge Table file that downloaded to your computer. Update existing charges and add new charges to the file, including information for each of the required fields.
   Warning

   To prevent auto-formatting issues, do not use Excel to open or edit the file. Instead, use a plain text editing tool, such as Notepad.

4. After you've made all edits to the file, save it, return to the Master Charge Tool and click Select File. Choose the file you updated and saved.
   
5. If any fields in your file do not match the field requirements, a list of errors displays, directing you to the rows and fields within that row that caused the error. Hover over the red error text to find additional information about that error.
   
6. Fix the errors in the file and re-upload it. Once your file doesn't contain any errors, you can select Next.
   
7. A list of all new and updated charges will display, allowing you to review before importing the new charge table. Purple highlighting marks updated fields. Select Update Charges when you are ready to update the charge table.
   

After adding a charge to the Master Control Table, the default retention period for any property assigned with that charge or role is set to 90 days. To change the amount of time an item is held, see Customize retention dates.

Expire charges

Because items added to the Master Charge Tool cannot be deleted, the Valid To Time field should be used to expire an item to ensure it is no longer used. To expire a charge, follow the steps outlined in the previous section (Add and update charges), including a past date for all charges that need to be expired.

Charge fields

Each charge in the Master Charge Table (MCT) is made up of sixteen pieces of information, or fields.

Select View Charge Field Requirements to view a list of these fields and how each field must be formatted to import correctly. Select View Details to find more information about each field.

External ID

The External ID field contains the item's "Friendly ID," a user-friendly, unique identifier. This is a required field that must be unique. It must be formatted as "CHG" followed by a unique value of 8 numbers.

This field only appears in the Master Charge Tool.

Example: CHG00021572

Section

The Section field is the code or statute the item appears in. This is a required field that does not need to be unique. It does not have any formatting requirements.

This field appears as a prefix in the lists of offenses and charges users select from when writing incident reports, as well as in the incident name in search, in task inboxes, and on incident profiles.

Example: 4421

Description

The Description field provides additional information about the item. This is a required field that does not need to be unique. It does not have any formatting requirements.

This field appears as a prefix in the lists of offenses and charges users select from when writing incident reports, as well as in the incident name in search, in task inboxes, and on incident profiles. This field is also displayed in Axon Analytics.

Example: SET FIRE WITHOUT PERMISSION PUBLIC RESOURCE CODE

Short Description

The Short Description field is a short version of the Description field. This is a required field that does not need to be unique. It does not have any formatting requirements.

This field is used by search to let users look for a specific charge or offense without needing to know the full description.

Example: SET FIRE W/OUT PERMISSION

NIBRS Codes

The NIBRS Codes field (appears as nibrsUCRCodes in the MCT update template) is used to map an item to a National Incident-Based Reporting System (NIBRS) rule when providing summary reporting to the state. This is a required field that does not need to be unique. This field must match one or more of the specific shortcodes listed in the table below. If more than one shortcode is needed, insert a single space between each shortcode. Using commas or other characters to separate shortcodes will cause validation errors.

To differentiate between Group A and Group B offenses:

• Group A priority: Use a 4-digit code other than 9999 or a code that does NOT start with 90.
• Group B priority: Leave the field empty, use 9999, or start the code with 90.

If your agency uses UCR reporting, enter "NOT_APPLICABLE" in this field.

This field appears in reports when a NIBRS mapping is required and in NIBRS reporting to the state/FBI.

Example: 26A 26C

Shortcode	Description	Shortcode	Description
09A	Murder & Non-negligent Manslaughter	39D	Sports Tampering
09B	Negligent Manslaughter	40A	Prostitution
09C	Justifiable Homicide	40B	Assisting or Promoting Prostitution
11A	Rape	40C	Purchasing Prostitution
11B	Sodomy	64A	Human Trafficking, Commercial Sex Acts
11C	Sexual Assault With An Object	64B	Human Trafficking, Involuntary Servitude
11D	Fondling	90A	Bad Checks
13A	Aggravated Assault	90B	Curfew/Loitering/Vagrancy Violations
13B	Simple Assault	90C	Disorderly Conduct
13C	Intimidation	90D	Driving Under the Influence
23A	Pocket-picking	90E	Drunkenness
23B	Purse-snatching	90F	Family Offenses, Nonviolent
23C	Shoplifting	90G	Liquor Law Violations
23D	Theft From Building	90H	Peeping Tom
23E	Theft From Coin-Operated Machine or Device	90I	Runaway
23F	Theft From Motor Vehicle	90J	Trespass of Real Property
23G	Theft of Motor Vehicle Parts or Accessories	90Z	All Other Offenses
23H	All Other Larceny	100	Kidnapping/Abduction
26A	False Pretenses/Swindle/ Confidence Game	120	Robbery
26B	Credit Card/Automated Teller Machine Fraud	200	Arson
26C	Impersonation	210	Extortion/Blackmail
26D	Welfare Fraud	220	Burglary/Breaking & Entering
26E	Wire Fraud	240	Motor Vehicle Theft
26F	Identity Theft	250	Counterfeiting/Forgery
26G	Hacking/Computer Invasion	270	Embezzlement
35A	Drug/Narcotic Violations	280	Stolen Property Offenses
35B	Drug Equipment Violations	290	Destruction/Damage/Vandalism of Property
36A	Incest	370	Pornography/Obscene Material
36B	Statutory Rape	510	Bribery
39A	Betting/Wagering	520	Weapon Law Violations
39B	Operating/Promoting/ Assisting Gambling	720	Animal Cruelty
39C	Gambling Equipment Violations	NOT_ APPLICABLE	NOT APPLICABLE

Source

The Source field indicates where the item was sourced from (e.g., FED, UCR, LOCAL). This is an optional field that does not need to be unique. It does not have any formatting requirements.

This field only appears in the MCT and is not displayed to users in Axon Records.

Example: FPD (Federal Public Defender)

Valid From Time / Valid To Time

These fields determines when the item starts appearing (Valid From Time) and when it is removed (Valid To Time) from the lists of offenses and charges users can select from when writing reports.

These are required fields that do not need to be unique. Dates can take one of the following formats:

• YY-MM-DD-T00:00:00-08:00
• YYYY-MM-DD
• YYYY/MM/DD
• MM-DD-YYYY
• MM/DD/YYYY
• DD MMM YYYY
  • MMM: The first three letters of the month (Jan, Feb. etc.)
• DD MMMM YYYY
  • MMMM: The full month name spelled out (January, February, etc.)

When including a time, use a 24-hour clock and use the UTC time zone.

To expire an item, enter a past date in the Valid To Time field. The charge will no longer appear as an option for new reports. Existing reports will be unaffected.

Example: To indicate that a charge is valid starting at midnight on January 1, 2024, you would enter: UTC: 22-01-01-T00:00Z.

Severity

The Severity field indicates the severity of the item. This is a required field that does not need to be unique. It can only include one of the following shortcodes:

Shortcode	Description
F	Felony
I	Infraction
M	Misdemeanor
C	Civil
LO	Local Ordinance
NA	Not Applicable

If there is not a severity for this charge, enter NOT_APPLICABLE. Any item marked as NOT_APPLICABLE or left blank, will appear in Analytics as "not a crime".

This field appears in incident reports once a user has selected a charge or offense, as well as in the incident name in search, in task inboxes, and on incident profiles.

Code

The Code field indicates the type of code the item belongs to. This could be Penal, Criminal, Group A, Group B, Person, Property, Society, etc. This is an optional field that does not need to be unique. It does not have any formatting requirements.

This field appears in incident reports once a user has selected a charge or offense.

Example: PR

Summary Code

The Summary Code field indicates how the item is mapped to the Unified Crime Reporting (UCR) Summary Reporting System (SRS). This is an optional field that does not need to be unique. It does not have any formatting requirements and supports multiple codes. Insert a space between each code.

This field only appears in reports when a UCR mapping is required and in UCR reporting to the state/FBl.

Example: 60 70

CJIS Code

The CJIS Code field maps the item to the Criminal Justice Information Services code. It is usually supplied by the state DOJ. This is an optional field that does not need to be unique. It does not have any formatting requirements.

This field only appears in the MCT and is not displayed to users in Axon Records.

Example: TM140

Hierarchy Number

The Hierarchy Number field is to sort and prioritize the item for various Axon Records integrations (e.g., DataStore, Data911).

This is an optional field that does not need to be unique. It can be any number value.

This field only appears in the MCT and is not displayed to users in Axon Records.

Example: 143400

UCR

The UCR field is a legacy field used to map an item to a Unified Crime Reporting (UCR) rule when providing summary reporting to the state. This is a required field that does not need to be unique. It does not have any formatting requirements. The default value for this field is 9999.

If your agency uses NIBRS reporting, this field is not required.

Example: 9999

Offense Categories

The Offense Categories field is used to group types of items. Automated rules can be set based on offense categories, such as creating a case from the incident, transitioning the incident report's state, or changing its district.

This field is used to route cases to specific case inboxes. For example, if a case is created for an incident with an offense categorized as TRAF, the case will route to the Traffic inbox. Contact your Axon representative to configure these offense categories and case routing rules.

This field also appears in Analytics. If your agency uses Analytics, this field is required.

This is an optional field that does not need to be unique. It does not have any formatting requirements and supports multiple categories. Insert a space between each category.

Example: VICE MANS

Charge Type

The Charge Type field determines if the item is a charge, an offense, or both a charge and an offense. This is a required field that does not need to be unique. It can only include one of the following shortcodes:

Shortcode	Description
O	Offense
C	Charge
B	Both

This field determines whether the item appears in the Offense dropdown, the Charge dropdown, or both.

State Offense Code

The State Offense Code field indicates coded offenses that apply at a state level but NOT a federal level. This is an optional field that does not need to be unique. It does not have any formatting requirements.

Example: 9A.32