5.2 Inspection, Testing, and Maintenance Distinctions

Three Activities, Three Schedules

Many NICET FAS misses happen before the candidate reaches a code number: the question says inspect, test, or maintain, and the candidate answers a different task. NFPA 72 separates these with different methods and different frequency tables.

Inspection answers what condition exists? Table 14.3.1 sets visual inspection frequencies. A technician looks for blocked access, painted detector openings, missing labels, physical damage, environmental or occupancy changes, and devices that no longer match the space. Inspection does not prove function — it flags what looks acceptable, questionable, or deficient.

Testing answers does it work as intended? Table 14.4.3.2 sets test frequencies. The technician causes or simulates an input, observes the fire alarm control unit (FACU) response, verifies notification output and supervision, confirms off-premises reporting where the plan requires it, and records the result. Pressing a button is not a test unless you know the expected response and recognize a mismatch.

Maintenance answers what keeps or returns it to reliable service? Cleaning, replacing, adjusting, repairing, retesting, and updating records. Crucially, NFPA 72 ties maintenance frequency to the manufacturer's published instructions and environmental conditions — not to a fixed code interval.

Inspection Frequencies (Table 14.3.1)

The weekly-versus-monthly split is a classic exam trap: a system whose alarm and trouble signals are transmitted to a constantly attended supervising station may be inspected monthly instead of weekly, because off-premises supervision substitutes for frequent on-site eyes.

Testing Frequencies (Table 14.4.3.2)

Reading the Requested Deliverable

For NICET scenario guidance, underline what the prompt actually asks for:

1. Identify the system part involved (device, circuit, function, power source).
2. Decide whether the prompt describes condition (inspection), operation (test), correction (maintenance), or recordkeeping.
3. Choose the action matching the technician's level of authority.
4. Avoid design changes unless the scenario grants design authority.
5. Confirm restoration and documentation are complete.

If a smoke detector is blocked by new storage racks, that is an inspection finding. If the detector was activated and the FACU did not annunciate the point, that is a test failure. If the detector was replaced and the system returned to normal, that is maintenance plus restoration documentation.

Traps to Watch

A visible defect is not automatically a test failure — a missing label is an inspection deficiency, while a failure to transmit the intended signal is a test problem. A second trap is using "maintenance" as a vague catch-all when the question wants the specific next step after a failed test (usually: classify, correct within authority, then retest). And remember the sensitivity-test nuance: a smoke detector arrangement that signals a trouble at the FACU when its sensitivity drifts outside its listed range is itself an accepted means of meeting the sensitivity requirement, which can change the correct answer.

Why the Schedules Differ

The schedules are not arbitrary. Visual inspection is cheap and non-disruptive, so high-consequence, easily-degraded items (control-unit indicators, primary power, batteries) get inspected often. Functional testing is disruptive — it can dispatch responders and interrupt the building — so most functional tests settle on an annual cycle, with a handful of waterborne or supervisory devices on shorter cycles in some editions. Sensitivity testing sits on its own track because a drifting smoke detector is a slow failure that an annual functional test would not catch.

A worked example shows how the tables combine. Consider a single photoelectric smoke detector in an office monitored off-premises:

1. Visual inspection — monthly (the building is monitored for alarm and trouble, so the control-equipment/inspection cycle relaxes from weekly to monthly).
2. Functional test — annually, by introducing listed aerosol and confirming alarm at the FACU.
3. Sensitivity — within one year of install, then every alternate year, unless a listed self-monitoring arrangement reports out-of-range sensitivity as a trouble.

Three different obligations, three different intervals, one device.

Maintenance Is the Outlier

Maintenance has no master frequency table. NFPA 72 directs it to the manufacturer's published instructions and the equipment's operating environment — a detector in a dusty industrial bay needs cleaning far more often than one in a clean office, even though both share the same inspection and test intervals. Exam answers that try to pin maintenance to a fixed code interval are wrong; answers that reference the manufacturer's instructions and environment are right. This is also why a thorough record notes environmental conditions: they justify the maintenance interval the technician chose.