"Fire alarm" reads like one line in most tables of contents — a Division 28 section, sometimes folded into Division 26, one price. In practice it's four separate jobs, each requiring a different skill set, and on plenty of real Canadian ICI tenders each assigned differently — sometimes to two parties, sometimes to four, and sometimes not assigned to anyone at all. Device installation and wiring are field labour any competent electrical crew prices without blinking. Panel programming and system verification are specialty work that needs manufacturer training or third-party certification most electrical contractors don't carry in-house — and they're the two duties that go missing from every bid on the job at once, often enough that it's practically a pattern rather than an accident.
This isn't a code reference — for the actual verification requirements on a specific building, read the standard the spec cites. It's a breakdown of what each of the four duties involves, why the two specialty ones disappear together so reliably, and the one question worth asking before a fire alarm scope gets priced at all.
1. Device installation
Mounting pull stations, smoke and heat detectors, horn-strobes, duct detectors, and the monitor and control modules that watch sprinkler flow and tamper switches — coordinated against the ceiling grid, the drywall schedule, and the duct routing that's usually still moving when this work happens. Spacing and placement follow the applicable code, mounting height and clearance from diffusers and structural obstructions matter, and a detector hung in the wrong spot fails inspection regardless of how clean the wiring behind it is. This is the part of "fire alarm" that looks and feels like ordinary electrical trade work — a box, a bracket, a device — and it is: on nearly every tender it's assigned without argument, usually straight to the electrical contractor or to a fire alarm sub working under the electrical umbrella.
2. Wiring
Conduit and cable from every initiating and notification device back to the panel, whether the circuit topology is Class A (looped, survives a single break) or the simpler Class B (home-run), riser wiring between floors, and the physical separation the code requires between fire alarm circuits and ordinary power wiring so a fault in one can't compromise the other. Fire-rated cable goes in where conduit doesn't, wire gauge and circuit counts follow the panel manufacturer's own installation manual as much as the code does, and every circuit gets landed at the panel labelled in a way the next duty can actually work with. Like installation, this reads as straightforward electrical labour, and it's assigned just as reliably.
3. Panel programming
This is where "fire alarm" stops being generic electrical work. Every device gets addressed and mapped to a zone or point, and every input gets tied to the outputs the building's actual sequence of operations requires — a stairwell smoke detector releases the door hold-opens on that floor, a duct detector shuts down its air handler, a sprinkler flow switch triggers general alarm and elevator recall, one zone sounds a different tone in a patient-care area than in a mechanical room. None of that is generic. It's written into the panel's own configuration software, which is proprietary to the manufacturer — Simplex, Notifier, Edwards, Mircom, whichever brand the spec names — and doing it correctly needs factory training on that specific platform, not a general electrical licence. Most electrical contractors don't carry that training in-house for every brand they might run into, which is exactly why this duty routinely gets carved out as its own line item — if it gets carried at all.
4. Verification and commissioning
Once the system is wired and programmed, someone has to prove it actually does what the sequence of operations says it does — every initiating device triggers, every notification appliance sounds and strobes at the right output, every programmed response fires when it should, and every result is logged in a formal report. This is the ULC/NFPA-style step the authority having jurisdiction wants in hand before signing off, and it's typically performed by a certified verification technician rather than whoever installed the system — because the entire point of verification is an independent check that the work is right, not a restatement that the installer says it is. It's licensed, specialty work in its own right, and on plenty of jobs it's the one duty nobody named at all.
Why programming and verification fall through the cracks
Device installation and wiring look like installation work — a box goes up, a wire gets pulled — so whoever's pricing the electrical scope carries them without a second thought. Programming and verification look like specialty services somebody else performs, and that assumption is exactly where the gap opens. An installing electrical contractor who isn't factory-trained on the specified panel brand assumes the manufacturer's own local representative handles programming — the rep sold the equipment, after all, and often does the startup on other jobs. The rep, in turn, is usually quoted to supply and start up the panel rather than carry ongoing programming labour under a construction contract, and assumes it's bundled into the electrical installer's scope, because that's how other jobs are often structured. Verification follows the identical shape one level up: the installer assumes it's someone else's testing responsibility — a commissioning agent, or the fire alarm sub if that's a separate contract — and a commissioning agent scoped broadly for mechanical and electrical systems often assumes ULC verification specifically is fire-alarm specialty work outside their own certification. Two duties, two identical blind spots, and neither shows up until somebody goes looking for the report.
What happens when nobody has it
The building finishes on schedule, the GC calls for the occupancy inspection, and the fire department asks for the verification report and the as-programmed cause-and-effect matrix. Neither exists — the tender's Division 26/28 language covered devices and wiring in enough detail to price cleanly, named a panel and a manufacturer, and never explicitly assigned programming or verification to anyone, so nobody carried the labour and nobody's scope of work names a verification technician's fee. The inspection fails, or never gets booked at all, and occupancy sits behind a scramble to find a certified verification tech, get the panel programmed to the sequence of operations the drawings show, and produce a report — usually on an accelerated schedule at a premium rate, eating a margin nobody set aside because nobody priced it as a live risk. It's an expensive way to discover a scope gap a five-minute read at bid time would have caught.
The question to ask on every tender
Don't accept "fire alarm" as a single line item, in the spec or in your own head. Read Division 26 and Division 28 — wherever the consultant filed it this time — looking for all four duties by name, and treat any duty the tender doesn't explicitly assign as a duty nobody has priced, including the ones buried inside what looks on paper like one bullet point. The question that actually protects the bid: which of these four — device installation, wiring, panel programming, verification — does this contract assign, in writing, and to whom. If the answer to any one of them is silence, that silence is the finding, and it belongs in an RFI before the number leaves the office, not in a change order after occupancy.