Official websites use .gov

A **.gov** website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS

A **lock** () or **https://** means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

Skip to main content

Visit the U.S. Fire Administration homepage

HotelsLibraryPublicationsBlogImage GalleryPodcastsAboutContact

            - Fire Academy - Courses
- Programs
- Admissions
- On-Campus Students
- About
- 
- Fire Academy Home

            - NFIRS - eNFIRS Applications
- Documentation
- Training
- Coding Help
- Reporting Guidelines
- Vendor Information
- Data Quality
- Access Data
- About NFIRS
- NERIS
- 
- NFIRS Home

            - Prevention - Home Fires
- Arson & Youth Firesetting
- Hotels & Vacation Rentals
- Outdoor Fires/Wildfires
- Vehicle Fires
- Workplace Fires
- Life Safety Hazards
- Fire Is Everyone’s Fight®
- Fire Prevention Officials
- 
- Fire Prevention Home

            - Statistics - Reports
- Death & Injury Risk
- Residential Fires
- Nonresidential Fires
- Outside & Vehicle Fires
- Firefighter Fatalities
- Fire Department Registry
- State Statistics
- Data Sets
- 
- Statistics Home

            - EMS
            - Wildfire - Training
- Cohesive Strategy
- Fire-Adapted Communities
- Outreach Materials
- Healthy Landscapes
- Data
- Research & Technology
- Wildfire & WUI Blog
- 
- Wildfire Home

            - A-Z Index
            - 

- Fire Academy... - Overview
- Courses
- Programs
- Admissions
- Campus Life
- About

- NFIRS... - Overview
- eNFIRS Applications
- Documentation
- Training
- Coding Help
- Reporting Guidelines
- Vendor Information
- Data Quality
- Access Data
- About NFIRS
- NERIS

- Fire Prevention... - Overview
- Home Fires
- Arson & Youth Firesetting
- Hotels & Vacation Rentals
- Outdoor Fires/Wildfires
- Vehicle Fires
- Workplace Fires
- Life Safety Hazards
- Fire Is Everyone’s Fight®
- Fire Prevention Officials

- Statistics... - Overview
- Reports
- Death & Injury Risk
- Residential Fires
- Nonresidential Fires
- Outside & Vehicle Fires
- Firefighter Fatalities
- Fire Department List
- State Statistics
- Data Sets

- EMS
- Wildfire... - Overview
- Training
- Cohesive Strategy
- Fire-Adapted Communities
- Outreach Materials
- Data
- Research & Technology
- Wildfire & WUI Blog

- A-Z Index

            - Hotels
            - Library
            - Publications
            - Blog
            - Image Gallery
            - Podcasts
            - About
            - Contact

- Home
- NFIRS
- Documentation
- Specification Enforcement

# NFIRS Notice of Specification Enforcement

      - Share on:
      - 
      - 
      - 

          - NFIRS Log In or Register 
          - Forgot username?
          - Forgot password?

##### In this section

                - eNFIRS Applications
                - Documentation
                - Training
                - Coding Help
                - Reporting Guidelines
                - Vendor Information
                - Data Quality
                - Access Data
                - About NFIRS
                - NERIS

To improve data quality and consistency, we now enforce several 2015 specification cycle rules previously not enforced by the National Fire Incident Reporting System (NFIRS) validation process. Enforcement began with the October 2020 release of the U.S. Fire Administration's NFIRS applications.

##  Important points

#### Need help?

                -  Ask your question online

 Responses to online questions submitted to our Help Desk may be delayed.

## Relational edits

Failure to follow the specification for the following relational edits will result in a critical error and an invalid incident status.

## Software-related items to verify

          -   Users must be able to upload fire department information data files separately from incident data files when importing data into the national database.
          -   Conversion-only codes for 4.1 data are not allowed. Using them will result in an invalid status for the incident.

## Reminders

### General

          -   A delete incident transaction type code (2) should be used only when an incident needs to be permanently removed from the NFIRS national database.
          -   To submit an update for an existing incident in the national database, the file can contain the change transaction type code (1), OR, the file can contain all incidents as “add” transactions (blank transaction type code), and the user uploading the file can select “Overwrite Existing Incidents.” Many states and users prefer this and are accustomed to using the USFA Bulk Import Utility's overwrite existing incidents method.
          -   Codes in NFIRS fields that are not in the NFIRS data dictionary (national length codes sets) will fail import when uploaded to the national database. This includes codes for yes/no flag fields (for example, the Resource Forms Used acceptable values are Y, N or blank only).

### Record format

          -   Mutual Aid Assisted FDID and Incident Number records (1020 record): transmit only when Aid Type is code 3 or 4 (aid given). The Assisted FD's Incident Number field is maximum length 7 (this has always been the specification for Incident Number).
          -   An incident should contain a single Remarks record (1040) and not contain excessive or repetitive text.
          -   Incidents that include Apparatus (1810) records must contain at least one parent transaction (1800). Child records must have an associated parent record present.
          -   Data files should not contain records without data, such as empty Arson Module (1900) records.

### Field level

          -   The Street Type must be from the data dictionary contained within the NFIRS Design Documentation. Other entries will fail validation. The available codes will be reviewed for a future specification change cycle.
          -   The Fire Module's Acres Burned field (1100 record) is numeric only and not a decimal value.
          -   The Basic Module's Entity Involved field (1050 record) Business Name maximum field length is 25. This field length will be reviewed in a future specification change cycle.
          -   The Personnel Module's Rank field (1810 record) maximum length is 10. This field length will be reviewed in a future specification change cycle.
          -   Telephone Numbers must be 10-digit numeric. Don't use parenthesis or dash characters.
          -   ZIP code length is 5 or 9 number, no dashes.
          -   A Special Study Code must be present if the Special Study ID is present.

Page last reviewed: Dec. 15, 2021

Be prepared.Be informed.Be safe.

            - 
            - 
            - 
            - 
            - 

Contact USFA

Information for
                - College/university educators
                - On-campus students
                - Off-campus students
                - Online students
                - NFA instructors
                - Public information officers

                - Public fire educators
                - Researchers
                - State training officials
                - Volunteer fire service
                - Wildland firefighters

About USFA
            - Leadership
            - Events
            - Position statements
            - Strategic plan
            - Job announcements
            - Send us your photos
            - Doing business with us
            - Subscribe to email lists

----

16825 S. Seton Ave.Emmitsburg, MD21727USA

800-238-3358

 Fire Is Everyone’s Fight®

USFA.FEMA.govAn official website of the Federal Emergency Management Agency

          - Accessibility
          - Accountability
          - Careers
          - Civil Rights
          - Contact FEMA

          - FOIA
          - Glossary
          - No FEAR Act
          - Plug-Ins
          - Privacy

          - Report Disaster Fraud
          - Website Information
          - DHS.gov
          - USA.gov
          - Inspector General

Current Advisories