NFIRS served the American fire service for nearly 50 years. As of February 2026, it’s gone. The National Fire Incident Reporting System that your department fed incident data into since the 1970s has been fully retired, and in its place is NERIS – the National Emergency Response Information System. This isn’t a future deadline to plan around. It already happened. By December 2025, departments that had already made the switch had logged more than one million incident reports through the new platform.
So what is NERIS, exactly? Most chiefs know it’s required. Far fewer can clearly explain what it actually is, how it works, or why the federal government replaced a system that had been running since before many of today’s firefighters were fighting fires. That gap matters, because the departments treating this as a routine software update are the ones most likely to get caught flat-footed.
This article gives you a plain-language understanding of NERIS: what it is, why it replaced NFIRS, how your data moves through it, and the four operational changes that will actually affect how your department runs.
What Is NERIS? (The Plain-Language Definition)
NERIS is a secure, cloud-based, all-hazards incident reporting and analytics platform that replaced NFIRS as the national standard for fire incident data. It was developed through a partnership between the U.S. Fire Administration (USFA) and the Department of Homeland Security Science and Technology Directorate, and it’s managed by the Fire Safety Research Institute (FSRI), part of UL Research Institutes. It’s free for every fire and EMS department in the country.
That’s the core of it. But the word “all-hazards” is doing real work in that definition. NFIRS was built primarily around fire incidents. NERIS is designed to capture the full range of what your crew actually responds to – EMS calls, hazmat, technical rescues, wildland events, and emerging threats like lithium-ion battery fires and violence against responders. It’s a structural shift in what the national dataset is meant to represent, not just a new place to type the same reports.
If your department is just getting set up, the first practical step is registering your NERIS Entity ID, which is how FEMA identifies your department in the system. which is how FEMA identifies your department in the system.
Why NFIRS Was Replaced and Why It Matters Now
NFIRS was replaced because it physically couldn’t do what modern fire service data demands. It launched in 1975. It couldn’t support GIS mapping, near-real-time data, or API integrations with the other systems your department already runs. Departments working inside it were often looking at national data that lagged by a year or more.
That nearly-50-year run isn’t a point of nostalgia. It’s the reason the replacement is structural rather than cosmetic. A system designed in the era of paper forms and mailed disks was never going to bend far enough to handle geospatial data, real-time analytics, or the cybersecurity expectations of a federal platform in 2026. At a certain point, you stop patching and start over.
This is the part departments tend to misread. If you treat NERIS as “the new NFIRS with a different login,” you’ll miss what changed underneath. The data model itself is different. Incident types, location capture, and how records flow to the federal level all work differently now. Understanding that before your crew starts entering calls saves you from cleaning up inconsistent data later. For a closer look at the mechanics of moving from one system to the other, see our NFIRS to NERIS transition guide.
How NERIS Works: What Happens to Your Data
Here’s the data flow most explainers skip. Your department submits incident data, NERIS geocodes that record to your jurisdiction using its GIS foundation, and the data populates near-real-time analytics dashboards you can actually use. Then (and this is the part that matters most for chiefs who are cautious about cloud systems) your department keeps full ownership of that data.
That ownership point is worth sitting on. Under NERIS, departments retain full ownership and control of how their information is managed and shared – that’s an explicit feature of the program, not just marketing language. No other department can access your PII, and aggregated data exports from the platform won’t contain it either. Where it’s worth being precise: submitting to NERIS does mean your data feeds into national-level aggregation and reporting – but that’s the whole point of the system, and it’s the federal mandate NERIS was built to fulfill. What you’re protected from is your identifiable incident data being accessed or used without authorization. For a chief who’s been burned by vendor lock-in or who’s wary of where sensitive data ends up, that’s a real distinction from a commercial RMS vendor who may actually own or hold your data hostage – and it’s one the official program pages tend to bury.
There are two ways your data gets into the system:
- Direct entry. Your crew enters incident data straight into the NERIS platform through its web application. This works, and it’s free, but it’s very manual, time consuming, and means your firefighters are working in a separate system from wherever you keep your other records.
RMS API integration. If you use a records management system, that system can submit incident data to NERIS directly through an API. Your crew completes the report once, in the software they already use, and it flows to NERIS without anyone re-typing it into a federal portal. For most departments running an RMS, this is the path that keeps reporting from becoming a second job. Our guide on how RedAlert simplifies the NERIS transition walks through what that looks like in practice.
What NERIS Means for Your Department: 4 Operational Changes
Plenty of resources will tell you what NERIS is. Far fewer tell you what it means once your department is live. Here are the four changes that show up in actual operations.
1. Near-Real-Time Data Instead of Year-Long Delays
NFIRS data routinely lagged 12 months or more. NERIS delivers analytics in near real-time. For a chief, that means incident trends, response time data, and resource gaps are visible while they’re still actionable, not 14 months after the fact, when the staffing decision they should have informed has already been made.
2. Grant Compliance Is Now Tied to Reporting
FEMA grants now require active NERIS reporting during the grant period of performance. This is a direct operational dependency NFIRS never enforced at this level. Departments that aren’t reporting through NERIS risk having an award modified or pulled. If your department runs on grant funding, your reporting status and your funding status are now the same conversation.
3. ISO Rating Impact
Incident reporting factors into your ISO score, and your ISO score affects homeowner insurance rates across your jurisdiction. Because NERIS produces cleaner, more complete data than the old code-based system, it gives you a stronger record to bring to an ISO review – a concrete, community-facing outcome that goes well beyond compliance for its own sake.
4. Data for Budget and Resource Justification
NERIS gives you an empirical basis for resource requests. Real incident data – response time trends, call volume by hazard type, documented staffing gaps – is far more persuasive in front of a city council or fire board than estimates pulled from a system that was a year behind. When you’re asking for an apparatus or three more positions, current data is leverage you didn’t reliably have before.
Frequently Asked Questions About NERIS
Is NERIS mandatory for fire departments?
Yes. As of 2026, NERIS is the sole national incident reporting system for the U.S. fire service, and NFIRS is fully retired. Every fire and EMS department that reports incident data nationally now does so through NERIS. There is no parallel system to fall back on.
Is NERIS free to use?
Yes. NERIS is free for all fire and EMS departments, State Fire Marshal offices, and emergency service agencies. The federal partners built it that way deliberately, so no department is shut out of the national reporting system for cost reasons. Note that any third-party RMS you use to feed data into NERIS may carry its own licensing.
What happened to NFIRS?
NFIRS launched in 1975 and was decommissioned in early 2026 after the transition to NERIS. New incidents can no longer be submitted to it. Historical NFIRS data remains available through the federal Public Data Release, but if your department relied on NFIRS for record storage, you should confirm your own records are retained in your RMS.
How do I know if my RMS is NERIS compatible?
Vendors that have demonstrated compatibility receive a NERIS integration designation, and FEMA maintains a list of certified integration partners. If you’re not sure where your vendor stands, ask them directly whether they’re NERIS V1 certified and whether they submit through the NERIS API. If they can’t give you a clear answer, that’s worth paying attention to.
How RedAlert Supports NERIS Reporting
Alpine Software is an official NERIS Integration Partner, and RedAlert is NERIS V1 certified. That means the reporting infrastructure is already built – your department isn’t waiting on a vendor to catch up to a deadline that’s already passed.
Departments using RedAlert submit incident data through the RMS API, so there’s no manual double-entry into the NERIS portal. Your crew fills out one report in the software they already know, and it flows to NERIS with submission status you can track. The goal is straightforward: keep your firefighters doing fire service work, not navigating a federal compliance exercise.
If you want to see exactly how that works for your department, book a quick demo — no pressure, just a real look at what it can do.
