As of January 1, 2026, incident data submission is exclusively through NERIS. NFIRS will no longer accept new data, and the system will be fully unavailable after February 2026 (USFA NFIRS Sunset). For departments that embraced the transition early, this milestone is a checkpoint. For those that delayed, it's a deadline.

Either way, the past year has produced a wealth of practical lessons. This article captures what fire chiefs across the country have learned — what worked, what didn't, and what every department should prioritize as NERIS becomes the permanent standard for fire incident reporting.

At-a-Glance Summary

It's been a full year since NERIS began replacing NFIRS as the national fire incident reporting system. As of January 1, 2026, all incident reporting is exclusively through NERIS — NFIRS is permanently gone. The five biggest lessons from year one: 

1. The transition window went faster than expected
2. NERIS exposed data quality problems departments didn't know they had
3. RMS integration was the make-or-break factor for a smooth experience
4. Timestamp accuracy matters far more under NERIS
5. Training was universally underestimated. 

Departments that invested in automated data capture, precise timestamping, and early vendor coordination had dramatically smoother transitions than those that relied on manual processes.

A Quick Refresher: What NERIS Is and Why It Matters

For those still getting familiar with the platform, NERIS is a cloud-based, all-hazards emergency reporting system developed by the Fire Safety Research Institute (FSRI) in partnership with the U.S. Fire Administration (USFA) and the Department of Homeland Security's Science and Technology Directorate. It replaces the 40-year-old NFIRS platform with a modern solution designed to deliver timely intelligence, advanced analytics, and seamless interoperability (FSRI NERIS Program).

The system was purpose-built to address the limitations of NFIRS:

• Outdated data architecture that couldn't keep pace with modern reporting needs
• Limited analytical capabilities that left departments without actionable insights
• Inability to address evolving threats like lithium-ion battery fires and increasing wildland-urban interface incidents
• Minimal integration with CAD systems, GIS platforms, and IoT devices

NERIS captures more granular incident data and provides near-real-time analytical tools that departments can use for resource allocation, risk assessment, and community risk reduction.

A basic stand-alone version of NERIS is available at no cost to local fire and EMS departments. However, the real power of the system is unlocked when it integrates with a department's existing records management system (RMS) and computer-aided dispatch (CAD) infrastructure. RMS vendors have been adapting their products to achieve NERIS data exchange compatibility, and the FSRI maintains an official list of vendors that have earned the "NERIS V1 Data Exchange Compatible" badge.

For a foundational overview of the NFIRS-to-NERIS transition, see NFIRS to NERIS Transition: What Fire Chiefs Need to Know for 2025.

Lessons Learned After Year One

The phased rollout that unfolded throughout 2025 provided a national laboratory for fire service technology adoption. Some departments transitioned smoothly; others hit significant turbulence. The following lessons represent the most consistent themes that have emerged from departments at every stage of the process.

Lesson 1: The Transition Period Was Essential — And It Went Fast

Throughout 2025, NFIRS remained operational as departments onboarded to NERIS by FEMA region. The phased approach followed this general timeline:

• Late 2024: Early adopter departments began beta testing
• February 2025: Phase 2 onboarding commenced with expanded regional rollouts
• Mid-2025: Additional FEMA regions brought online (e.g., Texas in July, Nebraska in August)
• Fall 2025: Later regions joined (Massachusetts in October, Illinois in November)
• January 1, 2026: NERIS became the exclusive reporting platform
• January 31, 2026: Final deadline for all NFIRS edits and data submissions

(Illinois OSFM NERIS Page)

For departments that engaged early, this parallel period provided a crucial safety net. They could experiment with NERIS while still maintaining their NFIRS reporting obligations, discovering workflow issues and training gaps before the old system disappeared. But many departments reported that the transition window felt shorter than expected. Setting up department profiles, configuring stations and units, training personnel, and coordinating with RMS vendors all consumed more calendar time than anticipated.

The key takeaway: departments that treated the transition as a phased, months-long project — rather than a switch to flip — reported significantly smoother experiences.

Lesson 2: Data Quality Issues Didn't Disappear – They Were Exposed

One of the most commonly reported surprises was that NERIS's enhanced data fields and validation requirements revealed just how much incomplete or inaccurate data departments had been submitting through NFIRS for years. Fields that were optional or loosely enforced in NFIRS became required or more rigorously validated in NERIS.

This was not a technology failure — it was a transparency success. NERIS is designed to improve data quality and timeliness, and part of that improvement involves making poor data practices visible so they can be corrected.

The departments that transitioned most smoothly shared a few common characteristics:

• They already captured accurate timestamps from field devices rather than dispatcher estimates
• They maintained complete incident documentation with minimal missing fields
• They used automated data capture from apparatus tablets to reduce manual entry errors
• They had an established data review process before reports were finalized

The lesson is clear: data quality is not a NERIS problem or an NFIRS problem. It's an operational discipline that starts in the field.

Lesson 3: RMS Integration Is the Make-or-Break Factor

This was perhaps the single most decisive variable in transition success. Departments using the free, stand-alone NERIS reporting tool quickly discovered the burden of manual data entry into yet another platform. For departments already stretched thin on administrative capacity — particularly smaller and volunteer organizations — adding another data entry requirement was unsustainable.

In contrast, departments whose RMS vendors had achieved NERIS data exchange compatibility experienced a dramatically different transition. The difference came down to automation:

• With RMS integration: Incident data (addresses, alarm times, dispatch times, call types) flows automatically from field devices to the RMS and then to NERIS — no manual re-entry required
• Without RMS integration: Personnel must manually enter the same data into both their local system and the NERIS platform, doubling the administrative workload and the opportunity for errors

Systems that automatically create incident reports, transfer precise unit status timestamps into the appropriate RMS fields, and export data in standardized formats (XML or JSON) made NERIS compliance a natural extension of existing workflows rather than an additional administrative task. StreetWise CADlink, for example, integrates with records management software to automatically populate incident reports with location, dispatch time, call type, and unit status data before crews even return to the station (StreetWise Feature Comparison).

Lesson 4: Timestamp Accuracy Became a Bigger Deal Than Anyone Expected

NERIS places significantly greater emphasis on granular, accurate response data than NFIRS ever did. The system's analytical capabilities are built on the assumption that the underlying data is reliable, which means the old practice of having dispatchers approximate unit status times is no longer adequate.

Departments that relied on dispatcher-entered timestamps found meaningful discrepancies when they compared those records with device-level data from field units. In some cases, the gaps were large enough to meaningfully distort response time analysis and, by extension, resource allocation decisions.

The solution that proved most effective was one-touch status buttons on apparatus tablets and smartphones that record precise unit times directly to the server:

• Crew members tap En Route, Arrived, or Available — the exact timestamp is captured at the moment it occurs
• Dispatchers are bypassed entirely for status tracking purposes, freeing them to focus on their primary responsibilities
• Timestamps are automatically transferred into RMS incident reports and, from there, into NERIS-compatible data submissions
• Incident benchmark buttons capture First Water Applied, Patient Contact Made, PAR Check Conducted, and other critical event times

If your department has overworked dispatchers capturing inaccurate unit timestamps that cause response time reports to be skewed, addressing this issue should be a top priority. The quality of your NERIS data — and the decisions made from it — depends directly on the accuracy of your timestamps.

Lesson 5: Training Was Underestimated Across the Board

Nearly every department that participated in the early phases of NERIS rollout reported that they underestimated the training lift required. This wasn't a reflection of NERIS's complexity — the platform is mobile-first and generally intuitive — but rather the breadth of personnel who needed orientation:

• Line firefighters needed to understand any changes to data capture workflows
• Company officers needed to review and approve incident reports in the new format
• Administrative staff needed to navigate the NERIS dashboard and data management tools
• Department leadership needed to understand the analytical capabilities and reporting differences
• IT coordinators needed to manage vendor integrations and user accounts

Departments that designated a dedicated NERIS point person (or small team) and built training into regular shift schedules adapted faster than those that treated training as a one-time event. The most successful approach was identifying the department's most tech-savvy company officers as NERIS champions who could support their peers through the transition on a day-to-day basis.

USFA and FSRI have published training videos, educational briefings, and onboarding guides that are freely available (USFA NERIS Resources). Departments that made use of these materials early — before their scheduled onboarding date — reported higher confidence levels and fewer operational disruptions.

What Chiefs Wish They'd Done Differently

In conversations and reports from departments that have completed their transitions, several regrets come up repeatedly. These aren't failures — they're lessons that can benefit departments still refining their NERIS operations:

• Started transition planning six or more months before their scheduled onboarding date
• Audited existing NFIRS data quality before migrating, rather than discovering problems during the transition
• Invested in automated data capture technology earlier to reduce the manual entry burden from the outset
• Established baseline performance metrics under NFIRS to enable meaningful before-and-after comparisons with NERIS data
• Downloaded and secured historical NFIRS data well before the January 31, 2026 cutoff, rather than rushing at the deadline
• Coordinated earlier with their RMS vendor to confirm NERIS compatibility and resolve integration issues before the switchover

Best Practices for Departments Still Refining Their NERIS Operations

Whether your department transitioned months ago or is still getting its bearings, these best practices will help strengthen your NERIS operations going forward:

1. Audit your current data. Run reports on the completeness and accuracy of your initial NERIS submissions. Identify fields that are consistently incomplete or contain default values, and trace those gaps back to their source.
2. Evaluate your RMS vendor's NERIS readiness. Confirm that your vendor has earned the NERIS V1 Data Exchange Compatible badge from FSRI. If they have not, explore alternative vendors or supplementary solutions that can bridge the gap.
3. Automate what you can. Incident data, timestamps, and benchmarks should flow from the field to the report without manual re-entry wherever possible. Every manual step is an opportunity for error and delay.
4. Designate a transition lead and build a realistic training calendar. Ongoing training is more effective than a single orientation session, especially as NERIS continues to release updated features and secondary schemas.
5. Establish data governance standards. Decide who is responsible for reviewing and approving incident reports, how frequently data quality is audited, and what the escalation process looks like when issues are identified.
6. Secure your NFIRS historical data. If you haven't already, ensure your department's historical NFIRS records are downloaded and stored according to your local records retention policy. The NFIRS system will be permanently unavailable after February 2026.

How NERIS Positions Departments for the Future

Beyond compliance, NERIS represents a genuine opportunity to build a more data-informed fire department. The platform's near-real-time analytical tools give departments access to insights that were simply not possible under NFIRS, including:

• Incident pattern mapping for identifying geographic risk concentrations
• Resource utilization analysis for optimizing deployment strategies
• Community risk scoring for proactive prevention planning
• Deployment optimization based on actual performance data
• Accreditation support through enhanced data granularity for CPSE documentation

For departments that depend on federal grant funding, NERIS compliance is becoming increasingly important. Departments receiving Assistance to Firefighters Grant (AFG) awards must agree to provide information to NERIS for the grant's performance period, beginning January 1, 2026 (NERIS and AFG Requirements, NC OSFM).

The integration capabilities of NERIS also extend beyond traditional RMS connections. The platform is designed to incorporate data from CAD systems, GIS platforms, and IoT devices, creating a more complete picture of incident dynamics than any previous reporting system. As these integrations mature, departments with clean, automated data pipelines will be best positioned to take advantage of emerging analytical capabilities.

Perhaps most importantly, NERIS creates a national dataset that benefits departments of all sizes. When small rural departments and large metropolitan agencies are contributing to the same data ecosystem, the resulting insights on resource deployment, risk patterns, and best practices become available to everyone. Better data across the entire fire service lifts all departments.

Frequently Asked Questions

Is NFIRS still available for departments that haven't transitioned to NERIS?

No. As of January 1, 2026, all new incident data must be submitted through NERIS. The NFIRS system accepted final edits to calendar year 2025 data through January 31, 2026, and is now permanently unavailable. Departments that have not yet onboarded to NERIS should contact the NERIS Help Desk immediately to begin the process.

Does NERIS cost anything for fire departments?

A basic stand-alone version of NERIS is available at no cost to local fire and EMS departments. However, departments that want to streamline their reporting through RMS integration will need to ensure their RMS vendor supports NERIS data exchange. Some vendors may charge for NERIS-compatible upgrades or features. The investment in RMS integration typically pays for itself through reduced manual data entry and improved data quality.

What's the biggest challenge departments face with NERIS implementation?

The three most commonly reported challenges are:

• Data quality adjustment — adapting to NERIS's more rigorous validation requirements
• Training breadth — getting all levels of personnel comfortable with new workflows
• RMS integration coordination — ensuring your vendor's NERIS compatibility is fully functional before you need it

Departments that address all three proactively, rather than reactively, experience significantly smoother transitions.

How can technology help ease the NERIS transition?

Technology platforms that automate data capture and transfer are the most effective tools for reducing NERIS transition burden. Specifically, look for solutions that:

• Automatically create incident reports with pre-populated fields (location, dispatch time, call type)
• Capture precise unit status timestamps through one-touch status buttons
• Export data in XML or JSON formats compatible with NERIS-ready RMS systems
• Transfer incident benchmarks and tactical actions directly into report narratives

The less manual data entry your department performs, the cleaner your NERIS data will be.

Conclusion

The first year of NERIS has been, as expected, a learning experience for the entire fire service. The departments that fared best were those that treated the transition not as a simple software swap but as an opportunity to strengthen their data infrastructure from the ground up. They audited their existing data quality, invested in automation, trained their people, and engaged their vendors early.

The lessons from year one all point in the same direction: automation, accuracy, and preparation are what separate smooth transitions from painful ones. NERIS is not just a reporting requirement. It is a platform that, when fed clean and complete data, gives departments analytical capabilities that were unimaginable under NFIRS.

As secondary schemas and additional modules roll out in the coming months, the departments with the strongest data foundations will be the first to benefit. The investment in getting your data right today will pay dividends for years to come.

If your department wants to explore how automated data capture, precise timestamping, and seamless RMS integration can strengthen your NERIS compliance and unlock better operational insights, contact the StreetWise team to schedule a free demonstration.