What it is, what changed, what your department must do now, and how to stay ahead of grant deadlines — in plain language.
NERIS — the National Emergency Response Information System — is the new federal standard for emergency incident reporting, developed by the Fire Safety Research Institute (FSRI) on behalf of the U.S. Fire Administration.
It isn't an NFIRS upgrade. It's a complete rebuild around three things NFIRS could never do well:
Every department that reports to the USFA, applies for AFG/SAFER grants, or participates in state fire reporting programs is subject to NERIS. The mandate has been in effect since January 1, 2026.
Read the full NERIS 101 guide →
Every incident must include complete data from all six modules. Missing any required field makes the record non-compliant.
Fundamental identification and timestamps. The baseline for every call.
Standardized address plus mandatory GPS coordinates — the biggest change from NFIRS.
Injuries and fatalities for civilians and firefighters. Zeros must be explicitly recorded — blank is non-compliant.
What was done at the scene. The most frequently skipped module in real-world audits.
Required for all fire-type incidents. Captures cause, origin, and building characteristics.
Whether mutual aid was given or received, and between which agencies.
From development to full enforcement — the NERIS transition in five milestones.
The data model, API, and submission process — what your RMS vendor implements, and what you need to know.
Unlike NFIRS file uploads, NERIS uses a REST API. Your RMS submits incident records as structured JSON payloads in real time or in batch. You don't upload CSV exports — the RMS talks directly to the NERIS endpoint.
POST /api/v1/incidents
API access uses OAuth2 client credentials flow. Each department gets a Client ID and Client Secret from the USFA/FSRI portal. Your RMS uses these to obtain an access token before submitting records.
grant_type: client_credentials
Records are structured JSON objects, not flat CSV rows. Each incident is a nested document containing the 6 mandatory module objects as sub-fields, making the data schema self-describing and easier to validate.
Content-Type: application/json
Every incident must include a geocoded location — street address plus GPS latitude/longitude. NERIS validates coordinate precision. This is the single biggest data collection change from NFIRS for most departments.
"lat": 38.897, "lon": -77.037
Incident types follow a hierarchical code system: Group → Sub-group → Incident type. This allows precise classification without rigid numeric codes. EV fires, WUI incidents, and new EMS types all fit naturally.
FIRE / STRUCTURE_FIRE / ...
Every reporting department is assigned a unique NERIS ID — a countrywide unique identifier that replaces state-scoped NFIRS FDIDs. Your NERIS ID is tied to your API credentials and attached to every record you submit.
neris_id_agency: "NERIS-XXXXX"
How departments are identified in NERIS — and why it matters for your data, your grants, and your API credentials.
A NERIS Department ID (sometimes called a NERIS Agency ID) is a countrywide unique identifier assigned to every fire and emergency services department that reports through NERIS. It replaces the NFIRS FDID (Fire Department ID), which was only unique within a single state.
This is a meaningful change. Because NFIRS FDIDs were state-scoped, the same number could refer to different departments in different states — making national data aggregation unreliable. NERIS IDs are globally unique across all 50 states and territories.
Your NERIS ID is assigned when your department registers in the NERIS portal at neris.fsri.org. If your department is already registered (via your RMS vendor), your ID appears in your portal credentials and in your RMS configuration. If you're unsure, contact your state fire reporting coordinator or your RMS vendor — they handle registration for most departments.
NERIS uses a 3-tier hierarchical code system to classify every incident. Rather than the fixed numeric codes NFIRS used for 30 years, NERIS codes are human-readable strings organized in a tree: Group → Sub-group → Incident type.
This structure allows precise classification across a much wider range of incident types — including EV battery fires, wildland-urban interface calls, and nuanced EMS categories — without forcing everything into a rigid legacy taxonomy.
The coding principle: classify by what actually happened, not the worst-case outcome you feared. A smoke investigation that turned out to be nothing is a hazardous situation investigation, not a fire. A lift assist is public service, not medical, unless the patient required transport.
Read the full codes guide →
Field-level detail for compliance officers, grant writers, and company officers.
Upload your incident export and 5AlarmData runs a field-by-field NERIS compliance audit — showing which modules are failing and what to fix first.