ICC F3 common mistakes
ICC F3 · Understand the traps and how to avoid them.
Scales egress travel distance, dead-end corridor length, or exit width directly off the overall floor plan sheet with a ruler and never records the drawing scale or checks the dimensioned architectural sheet.
Plans look dimensioned and candidates eyeball distances under time pressure; scaling a reduced print feels faster than hunting for dimension strings.
What to do instead
Do a legend-and-scale pass first, write the stated scale on the worksheet, measure only from sheets that carry dimension strings, and annotate each measurement with the method and sheet number used.
Reviews only the fire protection sheets for sprinkler, alarm, and egress layout and never cross-references architectural, structural, and mechanical sheets for rated assemblies, shafts, and equipment penetrating rated construction.
Candidates treat plan reading as a single-discipline task and focus on the sheets that look most like fire protection drawings.
What to do instead
Use a multi-sheet coordination checklist: for every rated assembly or penetration shown on the fire protection sheets, locate the corresponding architectural/structural detail and confirm the assembly, rating, and protection match.
Writes findings as general conclusions such as 'sprinkler system deficient' or 'egress obstructed' without the location, the observed condition, the adopted code section, and the correction required.
Inspectors write for themselves and assume the reader shares their context; narrative habits carry over from field notes to formal reports.
What to do instead
Use a fixed entry format for every deficiency: code citation, exact location, observed condition, required correction, and date/time; write entries during the inspection, not from memory afterward.
Applies the current adopted code edition to an existing building without first identifying the edition in force at the time of construction and the applicable existing-building provisions.
Candidates memorize the latest edition and assume one code governs every building regardless of age or permit history.
What to do instead
Before judging compliance, establish the applicable code edition, the occupancy and construction date, and whether the work is new, alteration, or existing; then apply the correct chapter set and document the basis in the report.
Evaluates egress, sprinkler thresholds, and fire-flow requirements before determining the occupancy classification, mixed-use relationships, and accessory occupancies.
Egress and sprinkler tables are concrete and easy to apply, so candidates jump to them before resolving the classification question that controls which tables apply.
What to do instead
Classify the occupancy first using the code's occupancy chapters, resolve mixed-use and accessory relationships, then apply egress, sprinkler, and fire-flow thresholds; record the classification reasoning in the inspection file.
Starts the walk-through without first reviewing prior inspection reports, open permits, and the system test/maintenance records, so repeat deficiencies and unresolved items are missed.
Time pressure pushes inspectors straight to the field, and records review feels like paperwork rather than inspection procedure.
What to do instead
Build a desk-review step into every inspection: pull prior reports, permits, and test/maintenance records, list open items and repeat deficiencies, and carry that list into the field for verification.
Accepts a fire-rated assembly because a label is present, without checking that the label matches the listed assembly, that penetrations and joints are protected, and that the installation matches the manufacturer's instructions.
A label is salient and looks authoritative, so candidates treat its presence as proof of compliance rather than as one element to verify.
What to do instead
Verify the label against the listing/assembly number, inspect penetrations, joints, and edge conditions, and compare the installed configuration to the manufacturer's installation instructions before accepting the assembly.
Witnesses an acceptance test for a fire pump, alarm system, or suppression system and records only 'passed' without recording the measured values and the acceptance criteria they were compared against.
The test ends and the inspector records the outcome, not the data, because the values seem like the contractor's responsibility.
What to do instead
Record each measured value (for example churn, flow, voltage, or pressure), the acceptance criterion from the standard or manufacturer's data, and the pass/fail comparison; require the contractor's signed test form to match your field notes.
Issues a notice of violation without a specific compliance date and without logging the re-inspection date, then discovers the deadline has lapsed with no documented follow-up.
Caseload pressure and no tickler system cause the notice to be treated as the end of the process rather than the start of a tracked compliance cycle.
What to do instead
Put a compliance date and a scheduled re-inspection date on every notice, log both in the case system at issuance, and document every contact and re-inspection attempt until the case is closed or escalated.
Cites a department policy or local SOP as the legal basis for a violation instead of citing the adopted code section, or blends policy requirements into the code compliance finding.
Internal guidance is more familiar and easier to recall than code text, and candidates use it as a shortcut.
What to do instead
Separate authority from process in every report: cite the adopted code section for the violation and reference policy only for inspection procedure or administrative steps; verify the citation against the adopted code before issuing.