NIBRS
Executive Information Services
1396 NE 20th Avenue, Suite 100Ocala, FL 34470
Phone: (208) 580-0400FAX: (775) 201-7575
Internet Mail: support@goeis.net
The software described in this document is furnished under a license agreement or non-disclosure agreement. Executive Information Services reserves the right to change specifications without notice.
US GOVERNMENT RESTRICTED RIGHTS: Use, duplication or disclosure by the United States Government is subject to restrictions as set forth under DFARS 252.227-7013 or in FARS 52.227-19 Commercial Computer Software - Restricted Rights.
Correspondence regarding this publication should be directed to:
Executive Information Services1396 NE 20th Avenue, Suite 100Ocala, FL 34470support@goeis.net(208) 580-0400
January 2023
© 2023 Executive Information Services
Contents
Executive Information Services PAGEREF _Toc142292619 \h 0
Contents PAGEREF _Toc142292620 \h 2
IBR Summary PAGEREF _Toc142292621 \h 3
NIBRS Incident PAGEREF _Toc142292622 \h 3
Acting in Concert PAGEREF _Toc142292623 \h 3
Same Time and Place Rule PAGEREF _Toc142292624 \h 3
Examples of IBR Incidents PAGEREF _Toc142292625 \h 3
Jurisdiction PAGEREF _Toc142292626 \h 3
Layout Functionality PAGEREF _Toc142292627 \h 4
Facepage PAGEREF _Toc142292628 \h 4
Administrative Segment PAGEREF _Toc142292629 \h 4
Cargo Theft PAGEREF _Toc142292630 \h 4
Cargo Theft Example PAGEREF _Toc142292631 \h 5
Offenses PAGEREF _Toc142292632 \h 5
Attempted Crimes PAGEREF _Toc142292633 \h 5
Offense Segment PAGEREF _Toc142292634 \h 6
IBR Offense PAGEREF _Toc142292635 \h 6
Bias Motivated Crimes PAGEREF _Toc142292636 \h 7
Names PAGEREF _Toc142292637 \h 8
Offender Segment PAGEREF _Toc142292638 \h 8
Victim Segment PAGEREF _Toc142292639 \h 8
LEOKA PAGEREF _Toc142292640 \h 8
Name Victim Offender PAGEREF _Toc142292641 \h 9
Arrest PAGEREF _Toc142292644 \h 10
Arrest Type PAGEREF _Toc142292645 \h 10
Multiple Clearance PAGEREF _Toc142292646 \h 10
Arrest Offense PAGEREF _Toc142292647 \h 10
Armed With PAGEREF _Toc142292648 \h 10
Juvenile Disposition PAGEREF _Toc142292649 \h 10
Property / Vehicle PAGEREF _Toc142292650 \h 10
Phantom Property Note PAGEREF _Toc142292651 \h 11
Report Validation PAGEREF _Toc142292652 \h 11
IBR Summary
While NIBRS transition represents a significant change for agencies, EIS has prepared a basic IBR reference guide to help the user get familiar with the new IBR fields that are within the RMS Entry Application. If you need further assistance, please contact our support office at 208-580-0400.
NIBRS Incident
Acting in Concert
Understanding what constitutes “acting in concert” is essential in IBR reporting. NIBRS considers ALL offenders to have committed all offenses in an incident. Acting in concert requires that all offenders commit or assist in committing all crimes in an incident. Offenders not consenting but assisting in committing all offenses also act in concert.
An example to help identify acting in a concert is that two offenders robbed a bar owner. One of the offenders held a gun while the other began to assault the victim sexually. The second offender did not participate; however, they had the weapon, which prevented anyone from assisting the victim, therefore, assisted in the commission of the crime. In this incident, the offenders were acting in concert. This would be reported as one incident with two offenders. One offender is connected to the victim through robbery and rape. The second offender is associated only with the robbery. The arrest of any offender will clear the entire incident. If one or more offenders did not act in concert, report a second incident.
Same Time and Place Rule
The same time and same place rules are used to help determine whether one incident gets reported with multiple offenses or should it be multiple incidents with one offense. If there are insignificant time or space intervals, it is one incident.
Examples of IBR Incidents
Example #1
Embezzlement, same offender same victim over 18 month = one incident
Example #2
Warrant arrest. During arrest, Stolen Vehicle from last week is discovered. = different incidents
Example #3
Supplement to base case, same offender, same date, same location, different offense added = same incident
Example #4
Different offender (Not acting in concert), same victim, same location, same date, different time = different incidents.
Jurisdiction
Often, agencies inaccurately report incidents that do not occur in their jurisdiction. Use this guideline to help determine jurisdiction and prevent duplicate reporting.
Guidelines:
Federal, state, county, city, university, college, and tribal LEA should report what occurs within their jurisdiction.
County and state should report incidents that occur outside of the city limits.
Only report incidents that occur within your jurisdiction.
If stolen property occurs outside your jurisdiction and is recovered inside your jurisdiction, that incident is not reported to CAIBR. Stolen and recovered property should occur within the same jurisdiction to count them.
Any warrants made inside your jurisdiction, but the original charge warrant is from a different jurisdiction are not counted.
Only report arrests where the offenses have occurred within your jurisdiction.
Layout Functionality
Facepage
The Type of Report selected will determine the kind of incident and whether that incident will be reported to the state. When working on multiple incidents, agencies should always select the most severe incident for the Report Type.
Administrative Segment
The Administrative Segment fields are static and remain the same. Accessing help is only one click away, no matter where you are on any six segments—selecting the help button results in a return of topics containing details specific to the fields in the segment you are viewing. Tooltips are associated with fields in NIBRS segments so that when your mouse hovers over a selected area containing a visual, the tooltip gives you a quick hint.
Exceptionally Cleared – Only use these fields if a case is to be reported as “Exceptionally Cleared” by state guidelines; otherwise, leave the fields blank.
Cargo Theft – Check If the case includes any offense that would constitute “Cargo Theft,” a crime where the property is affected while in the “Supply Chain.”
Cargo Theft
They are defined as the criminal taking of any cargo. Cargo shall be deemed moving in commerce at all points between the point of origin and the destination, regardless of any temporary stop while awaiting transshipment. Two key phrases are commercial shipment and in the supply chain.
Report all offenses within a cargo theft incident.
There must be a cargo theft incident in addition to the cargo theft itself. There is not a cargo theft offense by itself. Cargo Theft Offenses:
120 = Robbery
210 = Extortion/Blackmail
220 = Burglary/Breaking and Entering
23D = Theft from Building
23F = Theft from Motor Vehicle
23H = All Other Larceny
240 = Motor Vehicle Theft
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine Fraud
26C = Impersonation
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
270 = Embezzlement
510 = Bribery
Cargo Theft Example
A truck full of television sets was heading to a business to drop off its cargo. While en-route, someone stole six television sets.
Check the box if multiple offenses occurred within an incident and one was associated with cargo theft. Any report requiring a cargo theft indicator will be auto-marked as no unless the check box is marked yes.
Offenses
Use the keyword search to look up offenses instead of entering the violation statute on the main screen because you cannot view the description before selecting it. You can enter the violation statute in the keyword section or a partial word to view descriptions.
Attempted Crimes
Attempted crimes should be reported the same as the substantive offense. Attempted murders should be reported as aggravated assaults, and all assaults should be reported as completed. There are not any attempted assaults, only completed ones.
NOTE: If you check the attempted box, then property will not be required if it is a property crime.
On attempted crimes, a C (Completed) value is required on:
09A Murder/ Negligent Manslaughter
09B Negligent Manslaughter
09C Justifiable Manslaughter
13A Aggravated Assault
13B Simple Assault
13C Intimidation
Offense Segment
Up to 10 group A offenses are reported to NIBRS. Group B offenses are ONLY reported if there is an arrest. Only arrest information (not a victim) is collected for Group B offenses. HINT: There are seven Group B offenses beginning with “90.” If no arrest segment is completed for the Group B crime, it is not reported.
Example:
An officer is investigating a Group B offense. There is a victim, and an offense, but no suspects yet. This incident is not reported because there is NO arrest made.
IBR Offense
The IBR offense field should populate the selected case offense based on the chosen state statute. All offense codes are three characters, with the first two denoting the offense category and the third character indicating the sub-category description. E.g., all assaults are a category 13 with either an “A, B, or C describing the type of assault. If there are two characters entered in a field, the IBR fields will not be visible. Be sure to select the appropriate sub-category description. Once this is added, the IBR fields will appear. See below.
IBR Location Type – The user must select the provided IBR location listing (F1) and select the most appropriate location type based on the event details.
Bias Motivated Crimes
IBR Bias Motivated Crime – Provided as a three-field collection. The Bias must be against the offense, not the incident or person. The user must enter a minimum of one value. Select the most appropriate description code from the provided IBR Bias listing (F1). The list includes two mutually exclusive values of “88” and “99”. 88 – No Bias – The officer believes there was no bias as part of the offense. 99 – Unknown Bias – The officer believes that Bias MAY be a factor; however, he cannot classify it at the time of reporting. You may not leave this field as a 99. You must change it to 88 or one of the listed biases before submitting it to the state.
Offender suspected of using: Indicates whether any of the offenders in the incident were suspected of consuming alcohol, using drugs, or using computer equipment or a handheld device such as a cellphone to perpetrate the crime.
Type of Criminal Activity:
Must be reported on Counterfeiting/forgery, stolen property, offenses, drug/narcotic violations, drug equipment violations, pornography/obscene materials, gambling equipment violations, weapon law violations, and animal cruelty. Up to three codes can be entered per offense. The data can change depending on what statute was chosen.
Method of Entry:
It is required for all burglary/breaking. Force can be the unlawful entry with a key.
Type of Weapon or Force Used: Enter the weapon or force used by the offender.
Automatic Weapon Indicator: If an automatic weapon was used, click F1 in the field beside the type of weapon and force used.
Domestic Violence: If the incident involves a Domestic Violence situation, check the box.
Names
It will simplify report entry if the reporting officer adds the offender’s information to the system BEFORE adding the victim. The victim will require the linkage to the offender, and as such, the offender must be entered before completing this linkage on the victim page. If the offender is unknown, leave the fields blank, and the system automatically links it to an unknown offender.
Offender Segment
All data fields are included in the base names already in the RMS system, so a new section will NOT appear. Age, Sex, and Ethnicity (On I and L types only) are required. Residency is required for all offenders and victims. Arrestee, Suspect, and Victim Offender are considered Offenders. Blue fields indicate that they are IBR related. All offenders and victims are required to have this data entered.
Victim Segment
Under the Victim Segment, the Offense field will only allow you to choose up to ten offenses at a time and will be displayed separately.
Do not list crimes against society. We do this in the background for you.
If the victim is unknown, you must still have a victim segment.
Only link those offenses that the victim is the victim of.
Victim’s age, sex, and ethnicity (On I and L types only) are required.
Type of Victim: If other than I or L, an offender relationship is not required.
Type of Injury: Record up to five on all crimes against persons.
Aggravated Assault/Homicide: Record up to two on all crimes against persons.
LEOKA
The officer must be 21 or older and work in an official capacity sworn with full arrest powers. They usually carry a badge or firearm and are paid from government funds.
In April 2015, the LEOKA Program included a particular role function in its definition: "An individual serving in the capacity of an LEO at the request of an LEA whose officers meet the current collection criteria."
A certified LEO must supervise the individual from the requesting agency during the incident. Still, being in the officer's physical presence while working an assigned duty is optional.
They can be victims of 09A and 13A-C only.
The LEOKA segment for IBR is displayed when a PIN is selected for Name and Type of Victim (25) is L.
ORI – Number of the agency where the officer belongs if it is an outside agency doing the investigation.
Name Victim Offender
Each victim must be associated with an offender or multiple offenders if an offender is known. Additionally, IBR requires the officer to indicate the relationship between the offender and the victim. The system allows the officer to associate up to 10 offenders with any victim. If the offender information is included as a name within the case, the offender will be available from the (F1) selection lookup. Each Victim-Offender must link a relationship back to themselves as VO.
NOTE: You must list the relationship of the other person first. Some examples of victim offenders include domestic dual arrests, bar room brawls, mutual combat situations, etc.
VO 1
VO 2
Arrest
Arrests will be reported on the RMS arrest segment attached to each case name. When an arrest is entered into the RMS, the system will display the IBR-required arrest data at the base of the arrest screen.
Arrest Type
On View Arrest – Investigation occurred, and the offender was immediately taken into custody as a result.
Summoned/Cited – Formal charges, citation was issued. Summoned/Cited is considered an arrest.
Taken Into Custody – The offender was arrested later after several steps were taken, such as not being able to find the offender, occurred several days later, a warrant was issued, etc.
Multiple Clearance
Only use multiple clearances when more than two or more cases are related to one another, and the same offender (s) have been arrested. The first incident the offender was arrested on should be marked as "count arrestee for the first case cleared." All other linked cases should be marked as multiple cases cleared. This field is seldom used and generally used by detectives.
Arrest Offense
Choose the most serious IBR offense if there are multiple offenses.
The first arrest will clear the entire incident no matter how many arrests, offenses, or names you have on your report.
Armed With
If the offender was armed at the time of the arrest, and what type of weapon they had, such as automatic, semi-automatic, etc.
Juvenile Disposition
This field is required if the arrestee is a juvenile.
Handled within the department: If your agency turned the juvenile over to their parents.
Referred to another agency: If the juvenile was turned over to probation or a juvenile detention center.
Property / Vehicle
Property and vehicles are treated in the same manner under IBR, and as such, the property/vehicle IBR elements appearing on both the property and vehicle screen function identically. The IBR property segment will only appear on the screen if the case involvement code indicates that the item should be included in an IBR report (e.g., STOLEN, BURNED, RECOVERED, etc.). Items in non-reportable involvement (e.g., safekeeping, evidence) will not display IBR fields. A property segment is required on ALL property crimes.
Type of Loss – This data value indicates why the property item is included and how it will be reported to the state. This value should automatically fill in for the officer based on the case-involvement code selected in the property involvement field.
Description Code – This data value defines the type of property being reported.
Offense Code – The offense code allows the officer to link the property item directly to the related offense. The first offense entered in the offense segment will be populated.
This is typically a required field, and all offenses requiring a property segment to clear must have a property item entered and linked to the charge.
Phantom Property Note
Some offenses in IBR require a property item to be included in the report, even if there is no actual property to report (e.g., Kidnapping and Robbery both need some property to be included). However, in many cases, no real reportable property is contained in the case. This is resolved by entering a “None” case -involvement, which will create a phantom property record that will clear the property segment when linked to the offense.
Additional Information
We have mapped the agency property involvement to related IBR codes where possible – always verify! We automatically add the offense code from the case offenses where identifiable. Yes, Stolen and Recovery in a single case is fine. Property and Vehicles are both tabulated.
Note:
a. Drug case’s – 10 is code for drug, 11 for paraphernalia – Drugs do not require a value, paraphernalia does require a value.
b. If stolen drugs do not use 6 (reserved for seized only).
Report Validation
The RMS will automatically verify the total case for IBR compliance and will respond with one or more of the following messages:
PASSED – Will indicate that the data entered in the report meets IBR report validation rules and that the case is ready for submission to the state.
ERROR Qualified – Segment/Field error displays an IBR field name and descriptive error message. In this case, the system has pinpointed the error and provided specific instructions on how the error should be resolved. Double-click the error, and the system will automatically display the record causing the error.
IMPORTANT: Clear the validation errors from the top to the bottom. Clearing items from the top may clear items from the bottom, depending on the errors.
ERROR Unqualified – General error, usually caused by a missing association. The system knows that additional information is required but cannot locate the data within the case, so it cannot provide specific detail on how to correct it. A missing association typically causes this (e.g., the victim is not linked to an offense that requires a victim.) The officer will need to locate the record and correct the association.
On the Report Validation screen, you will see the IBR results when validated.
Confidential – ©2025 Executive Information Services. All rights reserved.
This document contains confidential and proprietary information of Executive Information Services. Do not copy, share, or distribute without permission.
Source: NIBRS EIS Entry Guide 2023.docx