Inspection and Investigation
Inspection and Investigation tests the legal and technical side of code enforcement and fire cause determination. Expect questions on right of entry, due process, documentation, origin and cause methodology, and evidence handling.
Inspections and code enforcement
- Legal authority comes from statute, a warrant, consent, or exigent circumstances; know which one you are relying on before you enter.
- Process: identify the occupancy and applicable code, document conditions with notes and photographs, issue a written notice citing the violation and a correction date, re-inspect, then escalate through citations, court action, or closure with due process and appeal rights.
- Prioritize life safety: exiting, suppression, detection, storage, and electrical hazards.
Fire investigation
- Follow the scientific method as described in NFPA 921: identify the problem, collect data, develop hypotheses, test them, and eliminate those that fail.
- Establish origin before cause; do not settle on the first plausible explanation or on the most convenient one.
- Secure the scene, preserve evidence, maintain chain of custody, and document thoroughly; discarding evidence creates spoliation exposure.
- Coordinate with law enforcement, insurance investigators, and prosecutors, but keep fire-cause findings separate from criminal conclusions.
Worked example
An inspection finds a blocked rear exit and daisy-chained extension cords. Issue a written notice citing the specific code section, set a re-inspection date, educate the owner on the hazard, and escalate per ordinance if uncorrected. Reasoning: voluntary compliance first, documented due process, and enforcement proportional to the risk.
Traps
- Entering without clear legal authority.
- Declaring arson without eliminating accidental causes.
- Destroying, moving, or releasing evidence without documentation.
- Recording opinion as fact in the report.
- Missing re-inspection dates, which weakens later enforcement.