HI Fire Alarm common mistakes
HI Fire Alarm · Understand the traps and how to avoid them.
Treating the fire alarm code and the electrical code as interchangeable, so the candidate cites NFPA 72 for conductor ampacity or installation methods, or cites NFPA 70 for detector spacing and coverage.
Both documents are open-book and both are quoted in the same study material, so candidates memorize clause numbers without anchoring which document actually governs which question. Installation wiring methods, conductor sizing, overcurrent protection, and grounding live in NFPA 70; initiating device spacing, notification appliance mounting and audibility, and inspection/testing intervals live in NFPA 72.
What to do instead
Build a two-column sort of every clause you memorize: 'NFPA 70 governs...' versus 'NFPA 72 governs...'. Before answering any code question, ask which document the stem is testing. For any stem about wire, conduit, box fill, or grounding, default to NFPA 70; for anything about devices, circuits, or test intervals, default to NFPA 72.
Conflating the definitions of 'initiating device', 'notification appliance', and 'supervising station' equipment, then mis-sorting a device into the wrong circuit category on questions that hinge on the definition.
The definitions chapter is short and candidates skim it, assuming the terminology is obvious. It is not: a waterflow switch, a tamper switch, and a smoke detector are all initiating devices but sit on different circuit types with different supervision requirements, and a remote annunciator is not a notification appliance.
What to do instead
Write the definition of each key term from memory, then check it against the code text. Group devices into three lists: initiating (detection and system-status inputs), notification (audible and visible outputs), and control/interface (relays, transponders, annunciators). Rehearse the sort until you can classify an unfamiliar device on sight.
Assuming a detector's listed spacing is the same as its actual coverage area, and applying a single spacing figure to smoke, heat, and duct detectors alike.
Candidates memorize one number (often the 30-foot smoke detector spacing) and apply it everywhere. Heat detectors, projected-beam smoke detectors, and air-sampling detectors each have different spacing and coverage rules, and spacing interacts with ceiling height, ceiling configuration, and the 0.7 multiplier for smooth ceilings.
What to do instead
For each detector type, memorize three separate facts: listed spacing, coverage area, and the conditions that modify them (ceiling height, slope, beams, ventilation). Practice calculating the number of detectors for a rectangular room with a stated ceiling height, and state which modifier you applied and why.
Treating notification appliance audibility and visible coverage as a single 'is it loud/bright enough' judgment rather than applying the separate dB-above-ambient and candela-per-square-foot criteria with the correct measurement conditions.
The two criteria are taught together and candidates blur them. Audibility is measured relative to ambient sound with the appliance sounding, at a specified distance and with doors open or closed as the code requires; visible coverage depends on room size, mounting height, and the candela rating, and the required candela changes with ceiling height and room dimensions.
What to do instead
Memorize the audibility rule and the visible coverage table as two independent facts. Work through a room-size-to-candela calculation and a dB-above-ambient calculation separately, and for each state the measurement conditions (ambient level, distance, door position) that the code specifies.
Confusing the different circuit classes and styles, and applying the survivability or supervision requirement of one class to a circuit that does not need it.
Class and Style designations look like arbitrary letters and numbers, so candidates memorize them as a list rather than as a set of physical properties (whether an open or ground fault annunciates, whether the circuit survives a single fault, whether it can be tapped). Questions then test the property, and the memorized list does not answer it.
What to do instead
Build a matrix: rows are circuit types (initiation and notification), columns are the properties (fault annunciation, single-fault survivability, tapping permitted, shielding required). Fill it from the code text, then answer practice questions by reading the property the stem requires rather than by recalling the label.
Assuming the control unit's standby battery calculation only needs the alarm load, or only the quiescent load, and forgetting to apply the required safety margin and the correct standby duration for the occupancy.
Candidates do the arithmetic they remember rather than the arithmetic the code requires. Standby duration depends on whether the system is protected by an automatic sprinkler system and on whether a dedicated branch circuit or generator supplies the panel, and the calculation must combine quiescent current for the full standby period with alarm current for the alarm period plus a derating margin.
What to do instead
Write the battery formula as a template with labelled slots: (quiescent current x standby hours) + (alarm current x alarm hours), then multiply by the required margin. For each practice problem, first state the standby duration you selected and the code basis for it, then plug in the numbers.
Mixing up the inspection, testing, and maintenance intervals, so a candidate assigns the annual test to a device that requires semiannual or quarterly attention, or applies a visual inspection interval to a functional test.
The interval tables are dense and organized by device type, and candidates study them as a flat list of numbers. The tables also distinguish visual inspection from functional testing, and some items have different intervals for each, which a flat list erases.
What to do instead
Rebuild the tables as a device-by-interval grid with separate columns for visual inspection, functional test, and maintenance, and include the code basis for any item with a special condition (such as sprinkler-system-controlled systems). Test yourself by naming a device and reciting all three intervals.
Treating recordkeeping as paperwork and answering documentation questions from general good practice rather than from the specific records the code requires, including who must retain them and for how long.
Candidates deprioritize the documentation domain because it feels less technical, so they never learn the required contents of the record of completion, the inspection and test reports, or the retention expectations. Questions that ask what must be recorded, or who must keep it, then get a plausible but wrong answer.
What to do instead
Make a one-page inventory of every required record and, for each, note the required contents, who prepares it, who retains it, and any retention or transfer requirement. Rehearse by describing a completed installation and listing, from memory, every document that must exist before the system is accepted.
Ignoring the safety and impairment procedures that apply when a system is taken out of service for testing or maintenance, and answering as if testing can proceed with the system left fully operational or fully disabled.
Candidates focus on the test itself and skip the surrounding procedure. The code requires notification of the authority and occupants, a fire watch or other mitigation while the system is impaired, and restoration and verification afterward, and exam stems test those steps as often as the test method.
What to do instead
Memorize the impairment sequence as an ordered checklist: notify, mitigate, disable only what is necessary, test, restore, verify, and document. For any scenario question involving taking a system offline, walk the checklist in order before choosing an answer.
Reading a layout or spacing stem for the arithmetic only and ignoring the stated occupancy, ceiling construction, or system type, then applying the default rule when the stem set up an exception.
Candidates under time pressure scan for numbers and skip the qualifying clause. Many layout questions are written so the default spacing is wrong and the correct answer depends on a stated condition such as a sloped ceiling, a beam pocket, a high-airflow area, or a sprinkler-protected occupancy.
What to do instead
Adopt a fixed reading routine for every stem: underline the occupancy, the ceiling description, the system type, and the question actually asked before touching the numbers. Then state aloud which rule the conditions trigger. Practice on stems that contain a deliberate distractor condition until the routine is automatic.