Home/ Modules/ NERIS Incident Reporting
Add-On Module · Verified NERIS V1 Compatible

NERIS Incident Reporting for Fire Departments

Write the full NERIS incident report in Emergency Logs, catch missing fields before the report goes, and send it to NERIS automatically. No manual uploads, no emailed files, and the same login your crews already use for checks, inventory and gear.

NERIS V1 Data Exchange Compatible seal
Why It Matters

NFIRS Is Gone. Every Incident Goes To NERIS.

The National Emergency Response Information System (NERIS) replaced NFIRS as the national system for fire and all-hazards incident reporting. Since January 1, 2026, new incident reports go to NERIS only.

For a lot of departments that means one more system, one more login and one more place where a report can sit half finished. This module puts incident reporting in the same place as the rest of your department's records, and handles the send to NERIS for you.

The Switch, In Dates

  • 2025A hybrid year. Incidents could go to NFIRS or NERIS.
  • January 1, 2026Incident data is submitted only in NERIS.
  • January 31, 2026Last day to edit 2025 records in NFIRS.
  • February 2026NFIRS is no longer available to users.

Source: U.S. Fire Administration, NFIRS Sunset.

How It Works

Write It, Check It, Send It

Three steps from the call to NERIS, without leaving Emergency Logs.

1

Write the Full Report

Crews and officers complete the whole NERIS incident report in Emergency Logs, on a phone, tablet or station computer. No second system to learn.

2

Catch Problems First

Before a report is sent, Emergency Logs checks it for the fields NERIS requires and shows what is missing or wrong, so it can be fixed while the call is still fresh.

3

Sent to NERIS Automatically

Finished reports go to NERIS through its secure data exchange. Nobody exports a file, uploads it by hand or emails it to the state.

Reports

Response Data for ISO and NFPA 1710

The incidents you report to NERIS also tell you how fast your department responds. Emergency Logs turns them into the response reports a chief and an ISO review ask for.

ISO / NFPA 1710 Deployment

90th-percentile alarm processing, turnout, first-arriving engine travel and effective response force travel for fire incidents, by station and by month, with a data quality check. Print it as supporting records for ISO's deployment analysis (FSRS Item 561).

Response Times

Turnout, travel and total response time by unit, station, unit type, incident type, month, hour of day or day of week. Drill into any unit to list every response.

Incident Types

Incident volume and response performance by NERIS incident type, with a month-by-month count for each type.

NERIS V1 Data Exchange Compatible seal
Verified

NERIS V1 Data Exchange Compatible

NERIS runs an Integration Partner Program for the software vendors fire departments use. A vendor earns the NERIS V1 compatible badge only after completing NERIS's verification process, which tests that its data exchange works with the NERIS standards.

Emergency Logs completed that verification. For your department, that means reports leave Emergency Logs in the shape NERIS expects, and you are not the one testing whether they arrive.

  • Full NERIS incident reports, written in Emergency Logs
  • Required fields checked before anything is sent
  • Automatic submission to NERIS, no manual uploads
  • ISO / NFPA 1710 deployment, response time and incident type reports
  • The same login as your checks, inventory, SCBA and PPE records
  • Built by first responders, with 33 years in fire and EMS behind it
Pricing

An Add-On, Not A New System

Add NERIS Incident Reporting to Station Essentials for $600 a year for the first station and $200 for each added station, or to Full Suite for $400 and $150. It is included in Metro quotes. Volunteer departments take 25 percent off. No per-seat fees, no mobile license, and support is included, the same as every Emergency Logs plan.

Questions

NERIS Incident Reporting FAQs

NERIS is the National Emergency Response Information System, the national system for fire and all-hazards incident reporting supported by the U.S. Fire Administration. It replaced NFIRS. Since January 1, 2026, new incident data is submitted only in NERIS.

NERIS verifies the software vendors that send data to it through its Integration Partner Program. A vendor earns the NERIS V1 compatible badge after completing that verification. Emergency Logs has completed it, so reports sent from Emergency Logs match what NERIS expects.

No. Reports written in Emergency Logs are sent to NERIS automatically through its data exchange. There is no file to export, upload or email.

Emergency Logs checks each report for the fields NERIS requires before it is sent and shows what is missing or wrong, so it can be fixed before it leaves your department.

Yes. Your department still onboards with NERIS. Emergency Logs writes the reports and sends them to your department's NERIS account. We help you connect the two during setup. Our NERIS login and reporting guide covers sign-in, roles and the connection step.

Yes. The ISO / NFPA 1710 Deployment report takes your NERIS fire incidents and shows 90th-percentile alarm processing, turnout, first-arriving engine travel and effective response force travel, by station and by month, with a data quality check of what was left out. Print it as supporting records for ISO's deployment analysis. A Response Times report breaks turnout and travel down by unit, station, incident type and hour of day.

No. NERIS Incident Reporting is an add-on to every plan, priced per station. There are no per-seat fees and no mobile license, so every member who writes reports gets a login.

No. If your current reporting works for you, keep it. This module is for departments that want incident reporting in the same login as their truck checks, inventory, SCBA, PPE and training records.

Trouble signing in to NERIS or setting up roles? Read our NERIS login and reporting guide.

See NERIS Reporting In Emergency Logs

We will walk through a report from the first field to the send, on your schedule.