NERIS Resource Center
NERIS Readiness Checklist
Nine things every fire department should verify for the NERIS transition, from entity registration and FDID mapping to the two questions that tell you whether your software vendor is actually ready. Work through it in an afternoon; it prevents months of cleanup.
Key takeaways
- NERIS readiness is mostly organizational, not technical: entity registration, FDID mapping, and account ownership cause more delays than software does.
- Clean data before you transition, incomplete NFIRS records and inconsistent member rosters follow you into the new standard.
- Two vendor questions expose readiness instantly: "Is your NERIS integration certified and live?" and "What happens to our NFIRS history?"
- Multi-station and multi-FDID departments should plan extra time, NERIS entity structure hits them hardest.
The checklist
- Register your department in NERIS. Confirm your department's entity registration and who in your organization owns the NERIS account. If a former chief or admin registered it, recover access now, not during a submission deadline.
- Map your FDIDs and stations. List every FDID your department reports under and how your stations are structured. Multi-FDID departments: decide who submits for each identity, and whether your software can manage all of them from one system.
- Confirm your state's requirements. States adopted NERIS on different schedules and some kept parallel state-level requirements. Verify with your state fire marshal's office what your department must submit, where, and by when.
- Ask your RMS vendor the certification question. "Is your NERIS integration certified and live today, and can you show us a department submitting through it?" Announced roadmaps are not integrations. (RedAlert is NERIS V1 certified.)
- Ask your RMS vendor the history question. "What happens to our NFIRS data?" Your incident history backs your ISO documentation, grant applications, and legal records. It should remain searchable and reportable next to new NERIS records, not archived into a flat file you can't use.
- Clean your data before it moves. Close out incomplete incident reports, reconcile your member roster, and fix known bad addresses. A standards transition is the cheapest moment you'll ever get to clean house.
- Check your alerting and point solutions. If you run standalone alerting or reporting tools, confirm each vendor's NERIS plan. Several departments have discovered mid-transition that a point-solution vendor has no NERIS roadmap at all, better to know now.
- Brief the people who write reports. NERIS changes incident structure, not just codes. An hour of officer training before go-live beats months of kickbacks and corrections after.
- Set a validation habit. Decide who reviews submissions and how errors get caught. Software that validates before submission (RedAlert does) turns this from a monthly cleanup into a non-event.
Common questions
How long does NERIS readiness take?
For a single-station department with a ready vendor: the checklist above is an afternoon of verification. For multi-FDID departments, or departments whose vendor isn't NERIS-certified, plan weeks to months, which is why the vendor questions come fourth and fifth on the list, early enough to act on the answers.
What happens if a department just doesn't transition?
Non-reporting departments lose more than compliance: federal grant programs (like AFG) weigh incident data, state fire marshals expect submissions, and your own ISO documentation depends on defensible records. The fire service runs on data now, opting out mostly hurts the department opting out.
Can RedAlert handle our NERIS transition for us?
The software parts, yes: RedAlert is NERIS V1 certified, validates before submission, manages multi-FDID structures in one system, and preserves NFIRS history. The organizational parts (registration, state requirements, officer training) we walk departments through during implementation.
Want the vendor questions answered live?
Bring this checklist to a RedAlert demo and go through it point by point.