NERIS Reporting: What Every Fire Officer Needs to Know About Incident Documentation

Nobody joins the fire service because they love paperwork. I get it. But incident reporting is one of the most important responsibilities a fire officer carries, and if you are cutting corners on your reports, you are putting your crew, your department, and yourself at risk. The National Emergency Response Information System, commonly known as NERIS, is the framework that the vast majority of fire departments in the United States use to document their emergency responses. Understanding how to use it properly is not optional for anyone wearing a bugal or expecting to.

I spent plenty of years early in my career filling out reports as fast as possible just to check the box. Then I got named in a lawsuit, and I realized that the three-sentence narrative I wrote at 2 AM was going to be read by an attorney, a judge, and potentially a jury. That changed my perspective permanently. Your reports are legal documents. They are the official record of what happened, what you did, what you found, and what decisions you made. Treat them accordingly.

What NERIS Actually Is

NERIS is a national database maintained by the United States Fire Administration, which is part of FEMA. Fire departments across the country voluntarily submit their incident data to NERIS, and that data is used to analyze fire trends, allocate resources, develop fire prevention programs, and support research into firefighter safety. When national statistics say that there were a certain number of structure fires in the country last year, or that cooking is the leading cause of residential fires, that data comes from NERIS.

The system uses a modular approach. Every incident starts with a basic module that captures the fundamentals: incident type, date, time, location, actions taken, and personnel involved. Depending on the type of incident, additional modules may be required. A structure fire triggers the fire module and the structure fire module. An EMS call triggers the EMS module. A hazmat incident triggers the hazmat module. Civilian casualties trigger the civilian casualty module. Firefighter injuries trigger the fire service casualty module.

Each module has specific data fields with standardized codes. NERIS uses numerical codes for incident types, property use, actions taken, contributing factors, and dozens of other data points. The coding system allows data to be aggregated and analyzed at the local, state, and national level. When you code an incident as a 111, that means a building fire. A 611 is a medical assist. A 700 is a false alarm. These codes matter because they drive the analysis that shapes policy, funding, and training priorities.

The U.S. Fire Administration at usfa.fema.gov/nfirs/neris/ is the central resource for everything related to the NERIS system, including the complete reference guide, code definitions, training materials, and data submission tools. Every fire officer should be familiar with this site. If your department has not updated its reporting practices in a while, the USFA site is where you go to ensure you are current.

Why Accurate Reporting Matters

There are three main reasons your reports need to be thorough and accurate: legal protection, funding, and data integrity.

Legal protection comes first. Every time your crew responds to an incident, there is a possibility that someone involved, whether it is a patient, a property owner, a bystander, or even a member of your own department, may file a claim or a lawsuit. Your incident report is the primary document that establishes what happened. If your narrative says "arrived on scene, extinguished fire, cleared" and someone later claims your crew caused property damage, failed to provide adequate patient care, or used excessive force during a rescue, you have nothing to support your version of events. A thorough narrative that documents your observations, your actions, and the conditions you encountered is your best defense.

Funding is the second reason. Many departments receive grant funding, insurance ratings, and budget allocations based on their call data. If your department responds to 5,000 calls a year but only reports 4,000 because officers are not completing reports for certain call types, your data underrepresents your workload. That can cost your department staffing, equipment, and station upgrades. ISO ratings, which directly affect insurance premiums in your coverage area, are influenced by department response data. Accurate reporting supports accurate ratings.

Data integrity is the third reason. The national fire data that drives research, training curriculum development, and safety initiatives depends on departments submitting accurate information. When a study says that residential sprinkler systems reduce fire deaths by a certain percentage, that finding is based on data submitted by departments like yours. Garbage data produces garbage conclusions, and garbage conclusions lead to policies and standards that do not reflect reality.

Writing an Effective Narrative

The narrative section of your incident report is where most officers fall short. The NERIS codes capture the quantitative data, but the narrative tells the story. A good narrative follows a chronological structure and covers the following elements.

Start with dispatch information. What were you dispatched for, and what was the initial report? Note the time you were dispatched, the time you responded, and the time you arrived on scene. Many records management systems auto-populate these timestamps, but verify them for accuracy.

Describe conditions on arrival. What did you see when you pulled up? For a structure fire, note the type of building, the number of stories, the construction type, the location and extent of visible fire and smoke, and any exposures. For an EMS call, describe the scene, the patient's initial presentation, and any hazards or bystanders.

Document your actions in order. What did you and your crew do? Be specific. Do not write "performed fire suppression." Write "deployed a 1 and 3/4 inch attack line through the front door to the seat of the fire in the kitchen. Crew performed a primary search of the first floor while suppression operations were underway." Do not write "provided patient care." Write "assessed patient and found a 65-year-old male conscious and alert with chief complaint of chest pain. Vital signs were blood pressure 180/100, pulse 92, respirations 20, SpO2 94 percent on room air. Initiated cardiac monitoring, administered aspirin per protocol, and established IV access."

Note the outcome. Was the fire extinguished? Was the patient transported? Was the alarm determined to be false? What was the disposition of the incident? Who did you transfer care to? When were you cleared and back in service?

Document anything unusual. If something went wrong, if there was a near miss, if you encountered unexpected conditions, if a piece of equipment malfunctioned, put it in the report. These details matter for after-action reviews, safety investigations, and continuous improvement.

Common Reporting Mistakes

The most common mistake I see is the bare-minimum narrative. Officers write two or three sentences and call it done. That tells me nothing useful and protects nobody.

The second most common mistake is inconsistent coding. Officers select the wrong incident type code, the wrong property use code, or the wrong action taken code because they are rushing through the dropdown menus. Take the time to select the right codes. If you are not sure which code applies, look it up. Your records management system should have a reference guide, and the NERIS code manual is available online.

The third mistake is delayed reporting. The longer you wait to write your report, the less you remember. Details fade, times blur together, and your report becomes less accurate. Write your reports as close to the incident as possible. If you run multiple calls during a shift, make notes on each one as you clear so you can write accurate reports later.

Making Reporting a Priority in Your Company

As a company officer, you set the tone. If you treat reports as an afterthought, your crew will do the same. If you take them seriously, write thorough narratives, and review your crew members' reports for accuracy and completeness, you build a culture of accountability.

I recommend reviewing your reports periodically to look for patterns. Are you consistently coding incidents the same way? Are your narratives detailed enough to stand up to scrutiny? Are you capturing all of the data fields that your state and national reporting programs require?

Incident reporting is not glamorous. It will never make a highlight reel. But it is a fundamental part of the job, and doing it well protects your crew, your department, and the communities you serve. Take it seriously.

StruckBox helps fire officers build the skills and habits that define professional leadership. From fireground decision-making to administrative responsibilities, our platform gives you tools to grow. Start at struckbox.com and lead from the front.