Department operations

NERIS vs. NFIRS: What Changed for Fire Departments? | Station Clipboard

NERIS has replaced NFIRS as the national fire incident reporting system, bringing a modernized data framework, improved interoperability, and new opportunities for fire service analytics. This guide explains the key differences between NERIS and NFIRS, what changed for fire departments, what happened to historical NFIRS data, and how departments can prepare for modern NERIS reporting with software like Station Clipboard.

By Station Clipboard12 min read
All field notes NERIS vs. NFIRS: What Changed for Fire Departments? | Station Clipboard

The way fire departments report incidents has changed.

For decades, the National Fire Incident Reporting System (NFIRS) served as the foundation for standardized fire service incident reporting across the United States. In 2026, NFIRS was decommissioned and fire department reporting transitioned to the National Emergency Response Information System (NERIS).

For departments that have spent years building workflows around NFIRS, this is more than a software change. NERIS introduces a new reporting framework, new data structures, new capabilities, and a different approach to how fire and emergency service information is collected and used.

This guide explains NERIS vs. NFIRS, what changed, what fire departments need to know, and how modern incident reporting software such as Station Clipboard can help departments manage the transition.


NERIS vs. NFIRS: The Short Version

The simplest way to understand the transition is this:

NFIRS was the legacy national fire incident reporting system. NERIS is its modern successor.

NFIRS was decommissioned in 2026. According to the U.S. Fire Administration, all fire department reporting has moved to NERIS, and NERIS does not use the NFIRS specification.

NFIRS NERIS
Full name National Fire Incident Reporting System National Emergency Response Information System
Status Decommissioned Current national system
Reporting model NFIRS specification NERIS data framework
Primary purpose Standardized fire incident reporting Modern incident reporting, data exchange, analytics and decision support
Data approach Legacy structured reporting Modernized data framework
Integration Older reporting ecosystem Designed for interoperability
Public data Historical NFIRS releases NERIS Public datasets
Current reporting No longer used for new reporting Current system for fire departments

The transition means fire departments should no longer think of NERIS as simply “NFIRS with a new name.”

It is a new system built around a different data model and a more modern approach to fire service information.


When Did NFIRS End?

NFIRS reporting ended in 2026.

The U.S. Fire Administration states that January 2026 marked the transition away from NFIRS, with 2025 being the final year for the NFIRS Public Data Release.

USFA also states that NFIRS and its associated tools were decommissioned, with fire departments moving to NERIS for incident reporting.

That makes 2025 an important historical cutoff.

What does that mean for old NFIRS records?

Existing NFIRS information does not simply disappear from history.

USFA continues to make historical NFIRS public data available, with releases covering years through 2025.

Departments should therefore think of their data in two categories:

  • Historical NFIRS data

  • Current and future NERIS data

Those two systems should not be treated as interchangeable.


Why Was NFIRS Replaced?

NFIRS served the fire service for many years, but technology and the needs of fire departments changed.

Modern fire departments collect significantly more information than simply whether a call involved a fire.

Departments respond to:

  • Medical emergencies

  • Fires

  • Vehicle incidents

  • Hazardous materials incidents

  • Technical rescues

  • Weather-related emergencies

  • Public service calls

  • Community risk events

  • Wildland and wildland-urban interface incidents

  • Other all-hazards responses

NERIS was designed to provide a more modern platform for collecting and analyzing this information.

USFA describes NERIS as an interoperable fire information and analytics platform intended to support preparedness, response, community risk reduction, resilience, mitigation and other fire service needs.


5 Major Differences Between NERIS and NFIRS

1. NERIS Uses a New Data Framework

One of the biggest differences is that NERIS does not simply use the old NFIRS specification.

USFA explicitly notes that NERIS does not use the NFIRS specification.

That matters for software vendors and fire departments because a system built specifically around NFIRS cannot simply change a label from “NFIRS” to “NERIS” and call the job finished.

Software needs to understand the NERIS data structure.

That includes how incident information is collected, validated, structured and transmitted.


2. NERIS Is Designed for Modern Integration

Modern fire departments rarely operate using one isolated system.

A department may have:

  • CAD

  • RMS

  • Scheduling software

  • Personnel management

  • Training software

  • Asset management

  • Timekeeping

  • Incident reporting

  • State reporting systems

  • National reporting systems

NERIS was designed with interoperability in mind.

USFA's NERIS information materials specifically identify integration with trusted third-party systems such as CAD and RMS as an important capability.

This is important because the goal isn't just to create another place for firefighters to type information.

The goal is to make information move between systems more effectively.


3. NERIS Is Built Around More Modern Data and Analytics

NFIRS was extremely valuable for creating a standardized national dataset.

NERIS is intended to take that concept further.

The NERIS platform is designed to support analytics and more timely information for the fire service.

USFA's 2026 National Viewpoint already publishes fire department activity based on NERIS data. For January through June 2026, the dataset represented more than 15.3 million reported fire department runs.

That's a major shift in how quickly national fire service information can become useful.


4. NERIS Enables More Timely Public Data

Another major change is what happens after information reaches the national system.

USFA launched NERIS Public in August 2026, providing public access to curated NERIS incident-level datasets. The datasets are refreshed on an ongoing basis rather than following the traditional annual NFIRS public release model.

This creates new possibilities for:

  • Researchers

  • Fire service analysts

  • Government agencies

  • Fire departments

  • Community risk reduction programs

  • Academic institutions

  • Public safety organizations

The result is a fire service data ecosystem that can become much more responsive to current conditions.


5. Fire Departments Need NERIS-Ready Software

This may be the biggest practical difference for department administrators.

If your department's reporting software was built around NFIRS, transitioning to NERIS may require more than an update.

The reporting workflow itself may need to change.

A NERIS-ready system should help your department:

  1. Create the incident

  2. Enter the required information

  3. Validate the report

  4. Identify missing or inconsistent information

  5. Review the report

  6. Make corrections

  7. Finalize the incident

  8. Submit the report

  9. Maintain the department's records

That's where modern incident reporting software becomes important.


What Does This Mean for Firefighters?

For firefighters and personnel completing reports, the biggest goal should be reducing unnecessary administrative work.

A reporting system should guide the person completing the report rather than forcing them to remember every requirement.

The best workflow is one where the firefighter can concentrate on accurately documenting the incident while the software helps identify missing information and reporting problems.

That's one of the principles behind Station Clipboard's Incident Reporting module.


How Station Clipboard Handles NERIS Reporting

Station Clipboard was built specifically for Fire & EMS organizations, and its Incident Reporting module is designed around the NERIS reporting environment.

Rather than treating incident reporting as an isolated form, Station Clipboard provides a workflow from report creation through review and submission.

Learn more about Station Clipboard Incident Reporting

The workflow

Create Incident
      ↓
Complete Report
      ↓
Validation
      ↓
Review
      ↓
Corrections
      ↓
Finalization
      ↓
NERIS Submission

Station Clipboard's Incident Reporting module provides a guided report builder, validation, auditor review, correction tracking, and PDF/JSON exports.

For departments using Station Clipboard, completed incidents can also be submitted directly to NERIS rather than requiring personnel to manually move information between separate systems.


Why Direct NERIS Integration Matters

Imagine a department completing an incident report in one system and then having to:

  1. Export the report

  2. Download a file

  3. Open another system

  4. Upload the information

  5. Check for errors

  6. Correct the original report

  7. Export it again

  8. Resubmit it

That's a lot of unnecessary administrative work.

A connected workflow can reduce those steps.

With Station Clipboard, the goal is to keep incident reporting inside the same department workspace that personnel already use for other operational tasks.

That means the same platform can connect:

  • Personnel

  • Scheduling

  • Time

  • Training

  • Assets

  • Communications

  • Documents

  • Incident Reporting

  • Department administration

Station Clipboard describes this approach as one connected workspace for Fire & EMS departments.


NERIS vs. NFIRS: What Departments Should Do Now

If your department is still thinking about the transition, there are several practical steps worth taking.

1. Confirm Your Reporting Software Is NERIS Ready

Ask your software provider:

  • Does the platform support NERIS?

  • Is it using the NERIS data framework?

  • Can reports be validated before submission?

  • Can reports be corrected and reviewed?

  • Can the software submit directly to NERIS?

  • How are NERIS updates handled?

  • Can historical NFIRS records remain accessible?

Don't assume that software supporting NFIRS automatically supports NERIS.


2. Review Your Current Reporting Workflow

Look at what happens from the moment a unit clears an incident until the report is finalized.

Where does information get entered?

How many systems are involved?

How many times is the same information manually entered?

Where do errors normally occur?

This is a good opportunity to simplify the entire process.


3. Preserve Historical NFIRS Information

NFIRS is no longer the current reporting system, but historical NFIRS information can still be important.

Departments may need historical information for:

  • Audits

  • Department statistics

  • Grants

  • Historical analysis

  • Community risk reduction

  • Insurance documentation

  • Administrative records

  • Long-term trend analysis

USFA continues to provide historical NFIRS public data through 2025.


4. Train Your Members

Moving from NFIRS to NERIS isn't only a software migration.

It's a workflow change.

Make sure everyone involved in reporting understands:

  • What changed

  • What information needs to be collected

  • How reports are reviewed

  • How corrections work

  • Who is responsible for final approval

  • How reports are submitted

A good reporting system should make that training easier by guiding users through the process.


Common NERIS Transition Mistakes

Treating NERIS as NFIRS 2.0

NERIS is not simply a redesigned NFIRS interface.

It uses a different data framework, so departments and vendors need to account for the underlying changes.

Waiting Until the Last Minute

The transition affects reporting workflows, software and training.

Departments should not wait until a reporting problem occurs to evaluate their system.

Manually Moving Data Between Systems

Every manual transfer creates another opportunity for:

  • Typographical errors

  • Missing information

  • Duplicate data

  • Incorrect values

  • Delayed submissions

Integration can reduce unnecessary manual work.

Ignoring Data Quality

Sending a report somewhere doesn't necessarily mean the report is good.

Departments should have validation and review processes before final submission.

Forgetting About Historical Data

Your NFIRS records still have value.

A transition to NERIS should not mean abandoning the department's historical reporting data.


NERIS Is More Than a Reporting Change

It's easy to look at NERIS and think:

“We just need a new way to submit our incident reports.”

The bigger picture is much more important.

NERIS is part of a larger effort to modernize fire service data.

Better data can help departments understand:

  • What types of calls they receive

  • Where incidents are occurring

  • What resources are being used

  • What risks exist within their communities

  • How emergency response patterns change

  • Where prevention efforts may have the greatest impact

USFA's stated goals for NERIS include supporting preparedness, response, community risk reduction, resilience and mitigation through improved information and analytics.


What Happens to NFIRS Data?

NFIRS isn't simply erased from the history of the fire service.

The system's historical data remains important.

USFA's public NFIRS data releases include information dating back decades, with the final public release covering 2025.

This creates an interesting opportunity for departments and researchers.

Historical NFIRS data can provide a long-term baseline, while NERIS provides the modern reporting environment going forward.

Think of it this way:

Historical Data
      │
      ▼
    NFIRS
      │
      │  Historical analysis
      │
      ▼
  2025 and earlier
      │
      │
      ▼
    NERIS
      │
      │  Current + future reporting
      ▼
 Modern Fire Service Data

The Future of Fire Department Reporting

The transition from NFIRS to NERIS represents one of the biggest changes to fire service incident reporting in decades.

The system is newer.

The data framework is different.

The integration opportunities are greater.

And the potential for faster, more useful fire service analytics is significantly expanded.

But departments don't need to manage that transition alone.

The software used to create incident reports should make the process easier—not add another layer of administrative work.

That's the philosophy behind Station Clipboard.


Station Clipboard and the NERIS Transition

Station Clipboard is a Fire & EMS operations platform designed to keep department work connected.

Its Incident Reporting module provides a structured workflow for creating, validating, reviewing and managing incident reports, with NERIS submission capabilities built into the platform.

Instead of building your department's workflow around disconnected systems, Station Clipboard brings incident reporting together with the rest of your department's operations.

One department. One connected workspace.

Explore Station Clipboard


Frequently Asked Questions

Is NERIS replacing NFIRS?

Yes. NFIRS was decommissioned in 2026, and fire departments now report incidents through NERIS.

Is NERIS the same as NFIRS?

No. NERIS does not use the NFIRS specification. It introduces a new data framework designed for modern fire service reporting and interoperability.

When did NFIRS end?

NFIRS was decommissioned in early 2026. USFA identifies 2025 as the final year for the NFIRS Public Data Release.

Can fire departments still access historical NFIRS data?

Historical NFIRS data remains available through USFA's public data resources, including releases covering years through 2025.

Does Station Clipboard support NERIS?

Yes. Station Clipboard's Incident Reporting module is designed around NERIS-oriented reporting, and Station Clipboard can submit completed incidents directly to NERIS.

Does NERIS replace the need for fire department reporting software?

No. NERIS is the national reporting platform. Fire departments can use software that helps create, validate, review and submit their incident reports.

Why is NERIS important?

NERIS provides a modern national framework for fire service incident data and is intended to support improved analytics, interoperability, preparedness, response, community risk reduction and resilience.


Final Takeaway

NFIRS was the foundation. NERIS is the next generation.

For fire departments, the transition isn't simply about learning a new reporting system. It's an opportunity to rethink how incident information is collected, reviewed, submitted and used.

The departments that benefit most will be the ones that treat NERIS as more than a compliance requirement.

They'll treat accurate incident data as an operational resource.

And with modern software like Station Clipboard, departments can build NERIS reporting directly into the workflow they already use to manage their people, schedules, training, assets and daily operations.

The future of fire service reporting is connected, standardized and data-driven.

And NERIS is a major part of that future.


Sources & Further Reading

Related Station Clipboard reading: