Prepare for the FI exam by practicing three moves: classify the occupancy and hazard, locate the governing code section, and write a finding that cites it. Drill egress vocabulary, table interpretation, and correction-notice writing with timed paper scenarios.
Study the Code as a Decision Tool, Not a Reading Assignment
Read each code provision by asking what condition it regulates and what finding you would write if the condition failed. This converts passive reading into the lookup-and-apply skill that inspection work depends on.
Passive reading of a fire code produces familiarity, not fluency. Instead, take one chapter at a time and, for each section, write a one-line inspection finding that the section would support. For example, a section on exit door hardware becomes: 'Rear exit equipped with a padlock; correct by installing compliant panic hardware per [section cited].' That sentence forces you to know what the section requires, what a violation looks like, and where the authority for the finding lives.
Then reverse the exercise: take a written finding and locate the section that justifies it. If you cannot trace a finding back to citable text, the finding is an opinion rather than an inspection result. Practicing in both directions builds the two skills inspection work draws on together: locating the right provision and stating why it applies to the described condition. Keep your findings in one notebook; by the end of a chapter you will have a personal index of the code.
Means of Egress: Separating Exit Access, Exit, and Exit Discharge
Most egress questions hinge on knowing which of the three egress components a condition belongs to, because the code applies different rules to each. Master the boundaries between them before memorizing any individual requirement.
The three-part structure is the backbone of egress provisions. Exit access is the path from any occupied point in a building to the entrance of an exit. The exit itself is the protected portion, typically a stair, an exit passageway, or a rated enclosure, that carries occupants between the exit access and the exit discharge. Exit discharge is the portion between the exit and the public way. A corridor in an office is exit access; the enclosed stair you step into is the exit; the exterior path from the stair door to the street is exit discharge.
Classification matters because provisions attach to components, not to 'hallways' in general. A limit on exit access travel distance does not constrain the design of the exit stair; a prohibition on obstruction does not mean the same thing in an exit access corridor as it does at an exit discharge. When a practice question describes a door, corridor, stair, or exterior path, your first written step should be labeling which component it is. Compare the three side by side until the labels are automatic; the table in this guide is a starting template.
Occupancy Classification Drives Everything Else
Occupancy and hazard classification determine which provisions apply to a described building. Practice classifying first and looking up second, because applying a rule written for the wrong occupancy is the error the classification step exists to prevent.
A described assembly space, storage occupancy, or facility handling hazardous materials is never just scenery; it is the key that selects the applicable set of requirements. Egress capacity, protection ratings, and system requirements all vary by occupancy classification, so an answer built on the correct section for one occupancy can be wrong for another. Train yourself to underline the occupancy cues in a question before reading the rest of the stem.
Build a two-column study sheet: on the left, the classification language you would expect to see in a scenario (a room used for gatherings, a warehouse storing palletized goods, a shop using flammable liquids); on the right, the classification those cues point to and one provision that changes because of it. Where quantity matters, note that maximum allowable quantities per control area exist precisely because hazard classification can change with the amount stored, not just the material's identity. Working this sheet by hand teaches the sequence inspection decisions follow: classify, then locate, then answer.
Reading Code Tables and Exceptions Without Misapplying Them
Table-based questions test whether you can find the correct row and column for a described condition and then check whether an exception modifies the result. Practice narrating that three-step process aloud until it is a habit.
A code table is only as good as the row and column you enter it through. Before reading a value, name the condition that picks the row (occupancy, construction type, hazard category) and the condition that picks the column (a dimension, a distance, a count). Then check the footnotes and any surrounding exceptions, because a value that appears correct can be modified by a note you skipped. Say the process out loud in practice: 'Occupancy is X, so row; sprinklered condition, so column; footnote two modifies the value for this case.'
Worked example with hypothetical values for illustration: suppose a practice narrative describes a sprinklered occupancy and the table lists a 200-foot allowance for that condition, with a footnote adding 50 feet where a specific described condition is met. The correct total is 250 feet, but a reader who skips the footnote answers 200. Exceptions invert expectations the same way: the general rule applies unless the exception's specific condition is present. For each exception you encounter, write the condition that triggers it and the change it makes. When a practice answer goes wrong at the table stage, log which step failed: wrong row, wrong column, or missed modification.
Worked Scenario: The Blocked Exit Discharge
A scenario describes chained exit doors and stored pallets in an exterior discharge path. The strong answer classifies each condition, cites the governing egress provisions, and distinguishes the two violations instead of merging them.
The scenario: during an inspection of a retail occupancy, you find the rear exit doors secured with a chain and padlock, and stacked pallets narrowing the exterior path from the stair discharge to the alley. A plausible mistake is to write a single finding, 'egress obstructed,' covering both. That finding is true but weak: the chain is a locked exit issue affecting the exit itself, while the pallets are an obstruction in the exit discharge, and the code treats these conditions under different provisions with different correction language.
The better response labels the components first. The chained doors are part of the exit and raise the question of whether egress doors are readily openable from the egress side without a key or special effort; a locked exit fails that test outright. The pallets are in the exit discharge and reduce the required width of a path that must remain unobstructed. Two findings, each with its own citation, are more defensible and more useful to the building owner than one merged observation. The lesson generalizes: when a scenario presents multiple conditions in one narrative, separate them by egress component before you write anything.
Documentation: Writing Findings You Could Defend Later
Practice writing findings that identify the condition observed, the requirement it fails, and the correction expected. Vague findings are the documentation weakness this exercise targets, and precision is what makes a finding defensible later.
A usable finding has three parts: what you observed, the code provision it does not satisfy, and what compliant condition would look like. 'Fire extinguishers need attention' fails all three tests. 'Two extinguishers in the service corridor show no record of the required maintenance servicing; provide current servicing records per the applicable inspection, testing, and maintenance standard and the fire code's maintenance provisions' passes them. Note the distinction between construction provisions, which govern how a building is built, and maintenance and operational provisions, which govern how it is kept; an inspector's findings draw on both, and confusing them produces corrections aimed at the wrong party.
Also distinguish conditions requiring immediate action, such as a blocked or locked exit, from conditions corrected on a schedule, such as a lapsed servicing record. The severity of the finding and the urgency of the correction are separate judgments, and writing them separately is a skill worth rehearsing. Distinguish too between ITM-style duties, such as verification of system servicing, and the plan-review-style duty of checking a feature against a design requirement; inspection work and practice scenarios can present either.
Documentation Exercise: Turn a Narrative Into Three Findings
Write inspection findings from a short paper scenario you compose yourself, then score them against a rubric. Repeat weekly; improvement in citation accuracy and condition specificity is the expected observation.
Exercise: write a five-sentence building narrative containing at least three distinct deficiencies in different categories, such as one egress condition, one system-maintenance condition, and one operational condition, such as an accumulation of combustible storage. Then, without looking back at your code tab set, write one finding per deficiency using the three-part structure: observed condition, requirement not met, and correction expected. Finally, reopen the code and check each citation. A suggested rubric: two points if the citation is correct and current in your working code edition; two points if the observed condition is stated specifically enough that a stranger could locate it; one point if the correction is feasible and distinct from the observation; one point if you correctly separated immediate-action items from scheduled corrections.
Expected observations across repeated attempts: your first pass improves from paraphrased code language toward citable wording, and your citations cluster around the chapters you write into the scenarios, which reveals which chapters you avoid. Adapt the exercise over time by tightening the clock, for example one finding per three minutes, and by writing a follow-up finding that documents a reinspection. Use this exercise as a milestone gauge only: a rubric score you set yourself measures practice progress, not a prediction of any exam result. Administrative details of the credential, such as current eligibility and exam policies, belong to the issuing body; see ICC's site in the sources.
| Egress component | What it is | Question it answers | Typical inspection focus |
|---|---|---|---|
| Exit access | Path from any occupied point to the entrance of an exit | How far and how wide is the route to the exit? | Travel path, common path of travel, obstructions, door swing |
| Exit | Protected portion between exit access and discharge | Does the protected enclosure hold up? | Enclosure integrity, door hardware, markings, no storage |
| Exit discharge | Path from the exit to the public way | Can occupants get clear of the building? | Clear width, illumination, obstacles, no re-encroachment |
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.