Fire departments across the country completed the NFIRS-to-NERIS transition the way they handle every major operational shift. They figured it out and got it done. Vendors have their compatibility badges, and fire chiefs have one less item on the compliance whiteboard. The question the transition conversation largely skipped is what the badge actually required their vendor to build.
NERIS was designed to establish a minimum standard for incident data across the fire service and give departments the flexibility to build on top of that standard with data specific to their own operations. A compatibility badge confirms only that a vendor met the minimum. Whether departments can actually add their own data depends entirely on what the vendor chose to build beyond that floor. And the staffing data that would link those incident records to the personnel who responded lives in a separate system entirely, with no automated connection between them.
NFIRS was established in 1975. For nearly five decades, it generated inconsistent data across departments, made national comparisons unreliable, and couldn't support longitudinal analysis. Data lag between a call and a submitted report was a known operational limitation. Agencies operating on the system were working with a tool that was never designed for the scale or complexity of modern fire operations.
NERIS addresses those problems structurally. The new standard uses a modernized incident data schema, supports near-real-time submission, expands the incident type taxonomy to cover the full range of calls career departments actually respond to, and integrates with CAD systems in ways NFIRS never could. For departments that were fighting their legacy RMS just to export data, the transition is a genuine improvement.
The standard was also designed to go further than the minimum required fields. NERIS works like a conditional logic form builder. A department completes the required fields for a given incident type and can then add its own custom fields on top. The intent was that national standardization and department-level specificity could coexist in the same system. The compliance conversation that dominated 2025 focused almost entirely on the first part.
To earn a NERIS compatibility badge, vendors are required to support the minimum required data fields and demonstrate successful data exchange with the NERIS platform. There is no requirement that they build a user interface allowing departments to add custom fields beyond those minimums. The badge confirms the floor was met. Whether departments can build on top of it depends entirely on what each vendor chose to build.
Dr. Lori Moore-Merrell envisioned and led the development of NERIS as U.S. Fire Administrator, building the standard on the premise that national standardization and department-level data flexibility could coexist. The design intent was that agencies meet the required fields and then layer their own data collection on top, creating reports and tracking metrics specific to their operations.
In practice, the badge has not always reflected that intent on any reliable timeline. At least one major PE-backed vendor achieved NERIS compatibility and then went five months without delivering the ability for departments to add a single custom field. The compatibility badge was in place five months before custom field support was available. The vendor has since delivered it, but that window illustrates what the badge alone cannot tell a department. Earning a compatibility certification and fully delivering what the standard was designed to enable are two separate milestones, often on two separate timelines.
The clearest illustration of what agencies lose when custom fields are unavailable is decontamination tracking. NERIS captures what hazardous materials were present at an incident as a required field. The standard does not require tracking what happened after the incident.
Fire department exposure tracking today runs almost entirely on self-reporting. A firefighter records what they believe they encountered and submits it. There is no independent data layer that captures who was on the apparatus, what hazardous materials were logged in the incident record, and whether the post-incident decontamination protocol was completed. A significant share of exposures goes undocumented because the mechanism for capturing them depends entirely on the firefighter initiating the record.
Decontamination protocol generates a trackable record. A department can log whether protocol was followed after an incident, what type of exposure occurred, and whether gear was kept out of living quarters during the decontamination process. Software tracks whether the required steps were completed and creates a record of that completion. That record is the foundation for occupational health tracking, workers' comp documentation, and legal defense. Measuring the biological impact of an exposure is beyond what any recordkeeping system can do, and Stationwise does not claim otherwise.
Since IARC reclassified firefighting as a Group 1 occupational carcinogen in 2022, a growing number of states have enacted presumptive cancer laws, though coverage and eligibility vary significantly by state. When those laws produce a claim, a department may need to show which calls a firefighter ran, what hazardous materials were present, and whether proper decontamination protocol was followed afterward. The first two questions come from incident data, and the third requires a system that was built to capture it.
Today, the only source of individual-level exposure data in fire departments is what firefighters report themselves. When a staffing system already knows who was on each apparatus and receives NERIS incident data directly, that changes. The exposure record would build automatically from data that already exists, without anyone filling out a form. And because that record is tied to the individual rather than the department, a firefighter carries it with them regardless of where they serve or whether they've retired.
Beyond what vendors did or did not build, the standard has its own structural limitation. Personnel assignment is explicitly optional in NERIS V1. A fully compliant incident record often contains no link to the specific crew who responded. The apparatus is on record. Whether the firefighters on that apparatus appear in that same record depends entirely on whether someone entered them manually.
The limitation becomes most visible when a line-of-duty injury occurs. An investigation will want to know who was in that seat, what that firefighter was actually certified to do, and whether their training records were current in whatever system the department uses to track them. The incident record captures the scene. Qualifications, training records, and shift history are documented in separate systems, with no automated connection to the incident record.
Fatigue history is a related consideration in the same reconstruction. Dispatch timestamps in every NERIS incident record contain the data needed to calculate the maximum possible rest window a crew had between calls on any given shift. That calculation only works if you know which firefighter was on which apparatus, and that link lives in the staffing system. A department working through a line-of-duty injury investigation often has the incident record in one system, the roster in another, and training records in a third, with nothing automatically connecting them.
When a firefighter is out on an extended injury absence, the workers' comp cost shows up in the budget. What the budget line doesn't show is which crew members are absorbing backfill callouts repeatedly, at what accumulated shift load, and whether that pattern is building toward another injury or departure.
At day 28 of a workers' comp absence, a firefighter's pay code typically transitions from workers' comp to sick time, changing the department's budget line. Payroll admin and the fire chief typically learn about it from the payroll report, well after the transition has already occurred. A staffing system with integrated absence tracking can send an alert when the threshold is near, before the pay code changes. A dashboard surfaces that information when someone opens it. An alert fires when the threshold is crossed, finding the right person before the window to act closes.
Scheduling and incident reporting are the two systems every agency with two or more stations effectively has to run. They have historically come from separate vendors, with no automated connection between them. Stationwise is adding NERIS-compatible incident reporting because the workforce management infrastructure that makes incident data useful already exists on the staffing side. The staffing system already knows who was on each apparatus. Connecting it to what NERIS captures about the call is how the personnel layer gets built.
Stationwise is NERIS V1 compatible today and the full build is in active development. With both systems under one roof, exposure documentation is designed to build at the individual personnel level automatically, decontamination tracking can be captured beyond the standard hazmat fields, and sleep window analysis will run from dispatch timestamps crossed against roster data. Once live, a firefighter will be able to file an incident report from the apparatus and check the next shift's staffing from the same screen.
The goal is two systems every department has to run, done well, from a vendor that is not PE-backed and has not spread itself across a dozen product lines to get there.
Book a demo to see how Stationwise connects staffing and incident data.
