If your department has used Informant for UCR reporting and is transitioning or has already transitioned to NIBRS reporting, there are a few key differences to be aware of when entering records that may require slight adjustments to how you enter records in Informant.


Table of contents



PA NIBRS reporting differences


Pennsylvania's version of NIBRS has a few additional data collection requirements that are not part of the federal NIBRS specification, which translates to specific workflow changes in Informant that are needed to comply with the PA NIBRS specification.


Incident records must include latitude and longitude


Unlike with UCR, Pennsylvania's NIBRS standard requires all incidents to include latitude and longitude information. In practice, this means all incidents that will be reported to NIBRS must have a master index Location record linked to them, and each master index Location needs to have the Latitude and Longitude fields filled in with valid coordinates reflecting the location of the incident, as accurately as possible.


Informant's Geocoding feature assists with this requirement by providing an option in Location records to automatically fill in latitude and longitude based on the address information in the record.


Note: If you are not creating location records and linking them to incidents, and are typing locations directly into the Location field in your Incident records, you will need to switch to creating and linking Location records in Incident records, which supports collecting standardized addresses with latitude and longitude to meet this PA NIBRS requirement.

In Informant, you can link (and create) Location records by clicking Find next to the Location field in an Incident record.


Each incident must specify the jurisdiction where the incident occurred


For PA NIBRS, each incident must include the 5-digit PSP jurisdiction code specifying the municipality where the incident occurred. In Informant, this means the Jurisdiction field should reflect the jurisdiction where the incident took place, and not the jurisdiction where the agency is located, as is the case with UCR reporting.


If your users are used to specifying your agency's jurisdiction in all Incident records, they will need to begin selecting the jurisdiction where the incident took place once your agency is certified to submit NIBRS data. If your agency provides police coverage for multiple jurisdictions, an administrator may need to add any additional jurisdictions covered by your agency in Administration in the Jurisdiction Number selection list if your agency has not previously added those jurisdictions there. Each jurisdiction's Display Code must be set to the 5-digit jurisdiction number assigned by the Pennsylvania State Police (PSP) for that municipality.


Note: If you are currently using jurisdiction names or are using a shorthand 3-digit muncipality code for your jurisdiction, you'll need to update your Jurisdiction Number selection list in Administration to use the full 5-digit PSP jurisdiction code for each jurisdiction that your agency covers. If you are unsure of what jurisdiction numbers to use, contact the PSP or the PA UCR/NIBRS Helpdesk to get the correct codes.


NIBRS reporting differences applicable to all states


Certain NIBRS requirements are part of the federal NIBRS specification and therefore apply to all states.


NIBRS codes vs. UCR codes in selection lists and offense definitions


Several selection lists in Informant, as well as offense definitions, have a UCR code assigned to them to map a user's choices in Informant to the appropriate UCR codes needed for UCR reporting.


The NIBRS reporting standard uses its own set of codes that often differ from and generally expand upon the codes used in UCR reporting. As a result, various selection list entries will need to be mapped to corresponding NIBRS codes in Administration as part of your transition to NIBRS, and offense definitions in Informant also need to be assigned a NIBRS code either in Administration or when entering an Incident record. In some cases, you may need to create new selection list values to properly map the available NIBRS codes to the selection list values in your database.


Justifiable homicides must be entered as separate incidents


If a crime occurs that involves one or more justifiable homicide offenses (NIBRS code 09C), federal NIBRS reporting rules require creating one incident containing the offenses that led up to the justifiable homicide(s), with separate incidents entered for each justifiable homicide.


Although the natural inclination is to enter any justifiable homicides within the context of the inciting incident, the FBI wants to count each justifiable homicide as a separate and distinct incident for crime reporting purposes. Consequently, justifiable homicides must be entered in their own incident records, separate from the original incident. The NIBRS reporting system will actively reject incidents that contain other offenses alongside a justifiable homicide.


Other NIBRS considerations


Informant handles the NIBRS "$1" property value rule for you


You may hear that NIBRS doesn't allow blank entries or $0.00 to be entered for property values, and that it requires that unknown values be reported as $1. While this is true in the context of the NIBRS standard, Informant still allows blank or $0.00 to be used when a property has an unknown value. Informant's NIBRS extract will automatically report these as $1, without you or your users needing to change how they enter property values in the system.


This means you do not have to change how you enter unknown property values in Informant.