NFIRS Coding - Wrong Location

NFIRS - NFIRS Codes - NFIRS Examples

Responserack helps Volunteer Fire Departments get to NERIS & thrive.

Adam Jack, Responserack

‘Wrong Location’ Incident Coding

How do I code an incident at the wrong location?

Note: Excludes malicious false alarms.

Wrong Location, No Emergency Found Group

These are some of the values in the wrong location / no incident found group:

• 621 - Wrong Location (e.g. maybe wrong fire district.)
• 622 - No Incident Found On Arrival At Dispatch Address
• 600 - Good intent call, other.

Wrong Lcoation verses Unable To Locate (UTL)

A wrong location incident is when the fire department are dispatched to a mistaken address. If an incident occured maybe it was not in this department’s district. However, unable to locate is when nothing can be found at or in the area of the incident report at a location. Use unable to locate (UTL) when nothing can be found.

Good Intent verses Wrong Location

Good intent is when dispatched to an scene that, upon investigation, wasn’t the danger or problem that the reporting party was concerned about. However, if dispatched but perhaps because the scene was actually in a neighboring district or there was an addressing or location error that mistakenly placed it in district, then use wrong location

Need other NFIRS coding help?

  See more NFIRS coding examples for quick “how to” coding snippets:

For more information see the NFIRS / eNFIRS training and contact Responserack if you would like more help with NFIRS or eNFIRS.