Fire Investigation Job Performance Requirements (NFPA 1033)
What this domain tests
This domain assesses whether you can apply the job performance requirements (JPRs) in NFPA 1033, not just recite fire-cause labels. The exam presents an investigator task - scene examination, documentation, evidence handling, interview, or post-scene report - and asks which performance requirement, knowledge area, or sequence applies. Questions often pivot on sequencing and on the difference between observation, hypothesis, and conclusion. NFPA 1033 is a qualifications standard; NFPA 921 is the investigative guide it points to. Keep the roles separate.
Core rules
- NFPA 1033 requires the investigator to use the scientific method and to remain current in fire science, fire dynamics, and investigation technology.
- Scene examination: identify, preserve, and document the scene before destructive actions; evaluate origin hypotheses against all available data.
- Documentation: contemporaneous notes, photographs, sketches, evidence logs, and chain-of-custody records are JPRs, not optional paperwork.
- Evidence: collect, package, label, and transfer items so identity and integrity are demonstrable.
- Interviews and reports: separate fact from opinion; the report must show the data and reasoning that support the conclusion.
- Scene safety and legal authority are prerequisite JPRs: do not enter an unsafe structure or exceed lawful access just to reach evidence.
Worked example
A burn pattern on a floor is irregular and appears "poured." A candidate marks "accelerant" and collects a sample immediately. Correct reasoning: the JPR sequence is to document the pattern in place, record observations, and test alternative hypotheses (e.g., fallen debris, flashover, ventilation effects). NFPA 1033 does not make the pattern itself proof; the investigator must collect data, analyze it, and select the hypothesis that survives testing. The sample may still be collected, but only after documentation and with chain of custody.
Traps
- Treating NFPA 1033 as a cause-classification manual; it is a performance standard.
- Calling a pattern "proof" before hypothesis testing.
- Skipping documentation or chain of custody because the cause seems obvious.
- Confusing negative evidence (absence of expected damage) with no evidence.
- Using the first hypothesis as the final one without testing alternatives.