What NFPA 1500 and NFPA 1582 require
NFPA 1500 is the Standard on Fire Department Occupational Safety, Health, and Wellness Program, and it's the document that obliges a department to run the program this software supports. It requires a written risk management plan, an occupational medical program, and records that are kept for the duration of a member's service and afterward. NFPA 1582 sits alongside it and governs the medical evaluation side, setting the medical requirements a member is assessed against.
Read together, the two standards ask for something most departments can't produce from paper: an exposure history per member that survives their career. NFPA 1500 doesn't name a vendor and doesn't require software at all. Neither does NFPA 1582. What both require is a record that can be produced on demand, which in practice means one system rather than a filing cabinet, three spreadsheets and a retired captain's memory.
The gap between the standard and daily reality is where most of these products earn their keep. A department can be fully compliant with NFPA 1500 on paper and still be unable to answer the only question that matters when a claim lands: what was this member exposed to, when, and who else was on that call. The standard itself is worth reading before any demo, because it tells you what to ask vendors to show you.
Critical incident stress management, and where software stops
Critical incident stress management is a structured peer and clinical response to traumatic calls, usually built on defusing, debriefing and referral. None of the systems on this page deliver it. What they do is record that a critical incident happened, note who was on it, and trigger the referral to the people who are qualified to respond.
That boundary is worth being clear about before you shortlist anything, because vendors in this category use wellness language loosely. Critical incident stress management is a clinical and peer discipline with its own training, its own standards and its own practitioners. The OSHA critical incident stress guide and the CDC NIOSH guidance on traumatic incident stress both describe the response; neither describes a software product.
Where software genuinely helps critical incident stress management is the trigger and the pattern. A defusing only happens if somebody knows the call happened and knows who was on it. A member accumulating traumatic calls across shifts, stations and years is invisible to any single officer and obvious to a system that counts. That's the job: notice, notify, and hand off to people who are trained for the rest.
The two layers: record and clinical
Departments buying in this space are usually looking at two different product categories without realizing it. The record layer documents exposures and critical incidents and lives with the department. The clinical layer delivers counseling and peer support and lives with the member. A complete program needs both, and neither vendor set does the other's job well.
This page ranks the record layer. The clinical layer is a real and separate market: Lexipol runs Cordico and PowerLine, and Alli Connect, PeerConnect, CrewCare and ResponderRel8 all provide some mix of anonymous peer matching, self assessment and around the clock clinical access. Judging those against a records system on exposure capture would be meaningless in both directions.
There's a third option worth knowing about that belongs to neither layer. The IPSDI Exposure Tracker, built by the International Public Safety Data Institute, a 501(c)(3) founded in 2019 by Dr. Lori Moore-Merrell, gives the exposure record to the firefighter rather than the department. Members log their own exposures, keep the record after they retire, and can opt in to share it with the National Firefighter Cancer Registry and other studies. It's not something a chief procures, so it isn't ranked here, but it's the right answer for a member who doesn't trust the record to survive their department.
What NERIS changes for fire department records management software
NERIS, the National Emergency Response Information System, is replacing NFIRS as the national incident reporting standard. Its Health and Safety schema is in development for release in 2026 and will extend the incident record to exposures themselves, documented at the incident level in a standardized way. That turns exposure capture from a vendor feature into a reporting expectation.
The practical consequence for anyone buying fire department records management software this year is that exposure fields stop being a differentiator and start being table stakes. A system that can't attach an exposure to an incident in a standard shape will be doing migration work in eighteen months. Every vendor on this list is publicly working toward NERIS, and the useful demo question is not whether they support it but what happens to the exposures already in their system when the schema lands.
It also raises the value of the record you already hold. Departments that have been logging exposures against incidents for years will have something to map into the new schema. Departments whose fire department records management software has only ever held incident data will be starting from the date they switch, which is precisely the wrong outcome for a record whose whole purpose is to reach backwards.