3.1 Completing Basic Incident Reports (JPR 5.2.1)
Key Takeaways
- NFPA 1001 JPR 5.2.1 requires a Firefighter II to complete a basic incident report so that all pertinent information is recorded accurately and the report is complete before submission.
- The National Fire Incident Reporting System (NFIRS) Basic Module (NFIRS-1) is the national foundation for fire incident data; most departments use NFIRS-compatible software such as PennFIRS in Pennsylvania, but the Authority Having Jurisdiction (AHJ) determines the exact form and required fields.
- Incident type must reflect conditions found on arrival—not only the dispatch type—and mandatory NFIRS Basic Module fields include FDID, state, incident date/number, exposure number, location type, aid given or received, alarm and arrival times, actions taken, resources, casualties (or "None"), and property use.
- A complete narrative answers who was involved, what happened, what assignments crews performed, and what outcomes resulted; obtain missing data from interviews, dispatch records, apparatus logs, and scene documentation, then secure required signatures (preparing member and officer in charge) before finalizing.
- Inaccurate or falsified reports can trigger disciplinary action, civil liability, criminal charges, loss of grant funding, and corrupted national fire statistics that misdirect training and resource allocation.
3.1 Completing Basic Incident Reports (JPR 5.2.1)
Quick Answer: NFPA 1001 JPR 5.2.1 requires a Firefighter II to complete a basic incident report, given report forms, guidelines, and incident information, so that all pertinent information is recorded, the information is accurate, and the report is complete. At the national level, the U.S. Fire Administration's National Fire Incident Reporting System (NFIRS) defines the standard data model most departments follow through NFIRS-compatible software. Your Authority Having Jurisdiction (AHJ)—state fire commission, municipal department, or county reporting system—may add fields, deadlines, and signature rules beyond the national minimum.
Incident reporting is not administrative busywork. Accurate reports document what your department did, support after-action reviews, protect members during investigations, and feed state and national databases used to allocate training funds, apparatus grants, and community risk-reduction programs. A Firefighter II is expected to complete reports with minimal supervision, which means you must understand both what to record and how to verify it before signing.
Purpose and Usefulness of Accurate Incident Reports
Every response generates a permanent record. That record serves multiple audiences simultaneously:
| Stakeholder | How Accurate Reports Are Used |
|---|---|
| Department leadership | Staffing analysis, training gaps, apparatus maintenance trends, SOP revision |
| State fire agencies | Grant eligibility, LOSAP/point tracking (where applicable), statewide risk mapping |
| U.S. Fire Administration (NFIRS) | National fire loss statistics, code adoption research, equipment standards development |
| Legal and insurance entities | Liability defense, workers' compensation claims, subrogation investigations |
| Fire investigators | Origin-and-cause analysis, evidence preservation documentation, timeline reconstruction |
When reports are complete and consistent, command staff can answer basic questions months later: Who responded? When did the first unit arrive? What actions were taken? Were there injuries? What was damaged? Incomplete reports force leadership to reconstruct events from memory—a process that is unreliable under stress and unacceptable for legal proceedings.
NFIRS and Department Reporting Systems
NFIRS is the federal framework maintained by the U.S. Fire Administration. Most U.S. fire departments report through NFIRS-compatible state or local systems rather than paper NFIRS forms. In Pennsylvania, for example, the Office of the State Fire Commissioner (OSFC) administers PennFIRS, which captures NFIRS data and transmits it nationally; departments reporting through PennFIRS do not file a separate national report.
Regardless of software brand, the NFIRS Basic Module (NFIRS-1) is required for every incident type from fire to medical assist to false alarm. Additional modules (Fire, Structure, EMS, HazMat, Wildland, etc.) attach when incident conditions warrant them. Your department SOP will specify which modules your role must complete.
Pennsylvania OSFC-Style Example: What "Complete" Looks Like
Pennsylvania's PennFIRS system illustrates the level of detail AHJs expect. While field labels vary by state, the following NFIRS Basic Module elements are representative of what a complete basic report contains. Treat this as a completeness checklist, not a universal form—your AHJ may require additional entries.
| NFIRS Basic Section | Representative Required / Expected Fields | Firefighter II Reporting Notes |
|---|---|---|
| Section A — Identification | FDID, state, incident date, incident number, exposure number | Exposure number distinguishes a primary incident from damage caused by a primary event (e.g., exposure fire) |
| Section B — Location | Location type, address or geo point, directions/vicinity | Use the physical incident location, not only the mailing address if they differ |
| Section C — Incident Type | Incident type code | Code for what you found on arrival, not only the original dispatch type |
| Section D — Aid | Aid given or received (or "None") | Document mutual aid, automatic aid, and agency assist accurately |
| Section E — Times | Alarm, arrival; controlled and last-unit-cleared per incident rules | Times must be logical (alarm before arrival; arrival before controlled) |
| Section F — Actions Taken | Up to three primary actions in Basic Module; more in apparatus module | Select codes matching actual tactics: search, ventilation, extinguishment, etc. |
| Section G — Resources & Loss | Apparatus/personnel resources; estimated dollar loss for fires | Loss estimates should be reasonable and documented if challenged |
| Section H — Casualties | Civilian and fire service casualties, or check "None" | Never leave casualty fields blank—explicitly record zero casualties |
| Section J — Property Use | Property use code | Distinguishes single-family dwelling, multi-family, commercial, vehicle, etc. |
| Section L — Narrative | Free-text incident narrative (strongly encouraged nationally) | Where the "story" of the incident is told with factual precision |
AHJ form variance: Some departments use supplemental pages for personnel accountability, exposure tracking, billing, or grant compliance (PennFIRS includes staff activity, daily logs, and shift scheduling beyond core NFIRS). Always use the current department-approved form or software workflow and follow SOP for submission deadlines—many states require monthly or annual submission for grant eligibility.
Common Report Fields Every Firefighter II Must Understand
Even when software automates coding, you remain responsible for the underlying facts.
Location and Property
Record the incident address, cross streets, GPS coordinates if available, and location descriptors ("rear of structure," "highway mile marker 42"). Property use and location type codes classify the incident for statistical analysis. Misclassifying a commercial warehouse as a residential property corrupts risk data for your community.
Times and Apparatus
Dispatch (alarm) time, arrival of first unit, controlled time, and last unit cleared establish response benchmarks. Apparatus entries should list each unit that responded, staffing levels, and water/supply details when relevant. Cross-check times against dispatch audio, mobile data terminals (MDTs), and apparatus electronic logs—conflicting times are a common audit finding.
Casualties and Injuries
Document civilian and fire service injuries and fatalities explicitly. Include treatment, transport destination, and whether injuries occurred during suppression, overhaul, or a secondary event. If no injuries occurred, select "None" rather than leaving the section empty. An empty casualty field creates ambiguity that investigators read as incomplete reporting.
Actions Taken
Action codes summarize tactics: fire attack, search and rescue, ventilation, salvage, overhaul, EMS, forcible entry, and more. The Basic Module typically allows three primary actions; additional actions may be recorded at the apparatus or personnel level. Your entries must match what your crew actually did—not what you wish had happened.
Narrative Quality: Who, What, Assignments, Outcomes
The narrative is where coded fields gain context. A strong narrative is factual, chronological, and concise. Use the Who / What / Assignments / Outcomes framework:
- Who: Units and key personnel (by role, not unnecessary personal detail), property owner/occupant status if known, other agencies on scene.
- What: Initial conditions on arrival—smoke showing, fire location, hazards, weather, occupancy.
- Assignments: Division/sector tasks, hose line placement, search areas, ventilation points, water supply established.
- Outcomes: Fire controlled time, extension found or not, rescues effected, injuries, displacement of occupants, law enforcement or investigator notifications.
Weak narrative: "Responded to a fire. Put water on it. Cleared the scene."
Strong narrative: "E-12 arrived at 0342 to a two-story single-family dwelling with fire showing from Division 2 Side C. Captain Smith assigned Engine 12 to a transitional attack through Side A while Truck 5 ventilated the roof. Primary search of Division 1 was negative. Fire controlled at 0358; no civilian or firefighter injuries. Red Cross notified for two displaced occupants."
Avoid speculation, blame, and opinion. Record observable facts. If information is unknown, state that it is unknown and note follow-up rather than guessing.
How to Obtain Necessary Information
Firefighters rarely have every answer at the keyboard. Use multiple sources before finalizing:
| Information Need | Primary Sources |
|---|---|
| Dispatch times and incident type | Computer-aided dispatch (CAD) printout, dispatch recording |
| Unit arrival and clearance | MDT timestamps, officer logs, PAR records |
| Tactics and assignments | Company officer interview, tactical worksheet, ICS 214 |
| Casualties and EMS | EMS run report, hospital destination, patient care forms |
| Property owner / occupancy | Occupant interview, assessor records, investigator |
| Dollar loss / damage | Officer estimate, insurance contact, pre-incident plan values |
If a fact cannot be verified before the reporting deadline, document your attempts to obtain it and update the report when information arrives. Never invent data to close a screen.
Required Signatures and Approval Workflow
Department SOP defines who must sign or approve an incident report. Typical requirements include:
- Preparing member — the firefighter or officer who entered the data.
- Officer in charge (OIC) — the company officer or incident commander who verifies accuracy.
- Administrative review — training officer, fire prevention bureau, or records clerk in larger departments.
Your signature attests that the report is truthful to the best of your knowledge. Signing an incomplete report to meet a deadline transfers liability to you. If you disagree with an entry, resolve it before signing or document the discrepancy per SOP.
Consequences of Inaccurate or Incomplete Reports
Reporting errors carry consequences far beyond a corrected form:
- Disciplinary action for falsification, gross negligence, or repeated omissions.
- Civil liability when inaccurate records undermine injury claims or defense against negligence allegations.
- Criminal exposure in extreme cases involving intentional falsification during death or arson investigations.
- Grant ineligibility when state systems like PennFIRS show chronic non-compliance.
- Corrupted analytics that misdirect code enforcement, staffing models, and public safety investments.
From a Firefighter II perspective, treat the incident report as part of closing out the incident with the same professionalism as stowing hose and replenishing SCBA cylinders. The JPR is explicit: pertinent information recorded, accurate, and complete.
According to NFIRS Basic Module guidance, how should the incident type code be selected when the conditions found on arrival differ from the original dispatch?
Which set of NFIRS Basic Module elements is always required to uniquely identify an incident in national reporting systems?
What is the most appropriate action when no civilian or firefighter casualties occurred at an incident?