If your department was still running NFIRS calls in late 2025, you already know the shift happened fast. As of January 2026, NERIS — the National Emergency Response Information System — is the official reporting standard for fire incident data in the United States. NFIRS is done.
For a lot of departments, this wasn’t just a software update. It meant retraining crew members, rethinking how reports get completed, and figuring out what happens to the data you’ve been pulling for years. If your EOY call stats looked different this year, NERIS is probably part of the reason.
This guide walks through what actually changed, what it means for how your department operates day-to-day, and how to get your crew onboarded the right way — without making it harder than it needs to be.
What Changed and Why NERIS Replaced NFIRS
NFIRS had been around since the mid-1970s. That’s not a typo. For nearly 50 years, it was the country’s primary system for capturing fire incident data and sending it to the U.S. Fire Administration. It worked — but it was showing its age.
The core problem was data quality. NFIRS used a rigid, code-based structure that made consistent reporting difficult. Different departments filled out the same fields differently, and incident types relied on 3-digit codes that varied in interpretation. The result was a national dataset that was hard to trust and even harder to analyze at scale.
NERIS was built to fix that. It replaces code-heavy fields with structured, standardized data. It supports real-time submission directly to FEMA instead of batch disk submissions. And it separates the immediate incident report from follow-up analysis — meaning your crew’s post-incident paperwork is actually simpler, not more complicated, once you’re set up correctly.
The big picture goal: give fire service leadership better, more actionable data at the department level while building a national picture that actually reflects what’s happening on the ground.
What’s Different from NFIRS: The Changes That Affect Your Crew
If you’ve been running NFIRS for years, here are the specific changes that will affect how your firefighters complete reports after a call:
Incident types no longer use 3-digit codes. NFIRS relied on a code lookup that your crew had to know (or look up). NERIS uses descriptive categories and subcategories instead. The first time through feels different, but most departments find it faster once members are familiar.
Location is now GPS-based. NFIRS used street address and district fields. NERIS captures latitude and longitude coordinates for every incident.
Property value and loss moved out of the main report. In NFIRS, estimated property loss was part of the core incident record — and notoriously inconsistent because firefighters completing reports right after a call aren’t always in the best position to estimate dollar values. NERIS moved this to a separate “Incident Analysis” layer that can be completed later, by the right person, with more context. The initial report your crew fills out is actually shorter as a result.
Submission is real-time, not batch. Under NFIRS, departments submitted data periodically — sometimes on disk, sometimes via upload. NERIS submits directly to FEMA when you hit submit on a completed incident. You can also track submission status inside your records system, so there’s no more wondering whether your data actually got there.
Your NFIRS records don’t go away. Everything your department submitted under NFIRS is still accessible. The two systems run in separate modules — NERIS handles new incidents going forward, and your historical NFIRS data stays right where it is.
How NERIS Changes Your Year-End Reports
This is the one that catches departments off guard if they’re not expecting it.
Your annual call stats — total incident count, call type breakdowns, response times, fire loss data — have historically been pulled from your NFIRS records. Starting with incidents submitted after the NERIS cutover, that data now lives in NERIS, not NFIRS.
What this means practically:
Your 2026 EOY data will likely span two systems. Incidents before your transition date are in NFIRS. Incidents after are in NERIS. If you’re generating annual reports, you’ll need to pull from both and combine them — or work with your RMS vendor to automate that reconciliation.
Call type categories changed. Because NERIS uses a different incident type structure than NFIRS, year-over-year comparisons need to account for the reclassification. A call that was coded one way in NFIRS may map to a different category in NERIS. This doesn’t mean your data is wrong — it means you need to understand the mapping before drawing conclusions from a side-by-side comparison.
The practical advice here: talk to your RMS vendor before your first EOY reporting cycle under NERIS. Know how your system handles the transition-year data gap, and know what your reports will look like before you’re presenting them to the mayor or the fire board.
How to Onboard Your Department to NERIS: A Step-by-Step Approach
Getting your department set up in NERIS isn’t a one-afternoon project, but it’s also not the months-long ordeal some departments feared. Here’s a reasonable sequence:
Step 1: Confirm your RMS vendor is NERIS V1 certified. This is the foundation. If your records management system isn’t certified to submit NERIS data, nothing else matters until that’s resolved. RedAlert is NERIS V1 certified, which means the reporting infrastructure is already built — your department doesn’t have to wait for your vendor to catch up.
Step 2: Get your NERIS Entity ID. Every fire department that submits NERIS data needs an Entity ID registered with FEMA. If you haven’t done this yet, it’s the first operational step. Your RMS vendor should be able to walk you through the registration process if you haven’t been through it already.
Step 3: Configure your incident types and local data fields. NERIS has a standard structure, but departments have some flexibility in how they configure local categories and custom fields within their RMS. Work with your vendor to make sure your setup reflects how your department actually runs calls — before the first incident gets submitted under the new system.
Step 4: Train your crew on the new report format. Don’t skip this. The single biggest source of NERIS data quality problems is crew members who are completing reports the NFIRS way out of habit. The training doesn’t have to be long — most departments can cover the key changes in a single shift briefing — but it needs to happen to ensure consistent reporting.
Step 5: Run a test incident before going live. Submit a test record through the full workflow: complete the report in your RMS, submit it, and confirm receipt and status in NERIS. Catch any configuration issues before they affect real incident data.
Step 6: Establish a quality check process. NERIS data quality matters more than NFIRS data quality did, because the system is designed for real-time analysis. Build in a review step — whether that’s a supervisor check before submission or a weekly audit of submitted records — so errors don’t compound over time.
What Your RMS Should Handle for You
A lot of the NERIS transition complexity sits at the software layer — and your RMS should be absorbing most of it, not passing it down to your crew.
Specifically, your records management system should be handling GPS coordinate capture automatically, mapping NFIRS legacy data to NERIS fields during the transition, providing real-time submission status tracking, and giving you access to both NFIRS historical records and NERIS current records in one place.
If your current system is making your crew do manual data entry to accommodate NERIS requirements that your software should be handling, that’s worth a conversation with your vendor. RedAlert Desktop manages the NERIS workflow end-to-end — from incident creation through submission and status tracking — so your firefighters are filling out a report, not navigating a compliance exercise.
For a detailed walkthrough of how NERIS works inside RedAlert specifically, the NERIS in RedAlert: From Setup to Submission webinar covers the full workflow with a live demo.
Frequently Asked Questions About NERIS Onboarding
Does NERIS replace NFIRS completely, or do departments still submit both?
NERIS fully replaces NFIRS for new incidents. As of 2026, NFIRS is no longer the submission standard. Your historical NFIRS records remain accessible, but all new incident reporting goes through NERIS.
What happens to our NFIRS historical data after the transition?
If you are using an RMS, it stays in your RMS. NFIRS records are preserved in a separate module alongside your NERIS records — you don’t lose access to past incidents. For departments using RedAlert, both are accessible from the same platform.
How long does it take to train crew members on NERIS?
Most departments can cover the core changes in one to two briefings. The structural differences from NFIRS are real but not overwhelming — the biggest adjustment is breaking habits around incident type codes and learning the GPS location workflow.
Will our year-end call statistics look different this year?
Likely yes, at least for transition-year comparisons. Because NERIS uses different incident type categories than NFIRS, direct year-over-year comparisons need context. Work with your RMS vendor before your first annual reporting cycle to understand how to handle transition-year data.
What if our department hasn't completed NERIS onboarding yet?
Get in touch with your RMS vendor now. Departments that are behind on NERIS setup are at risk of reporting gaps that affect compliance and internal analytics. If you’re a RedAlert customer, reach out to our team and we’ll walk you through exactly where you stand and what needs to happen next.
Navigating the NERIS transition and want to see how RedAlert handles it for your department? Book a quick demo — no pressure, just a real look at what it can do.
