Field perspective
Where this usually goes wrong
The recurring mistake on damper and smoke-control work is treating “the relay changed” as proof that the life-safety function worked. A complete test separates the fire alarm command, equipment movement, end-switch feedback, fan status, and any firefighter control indication.
Start with the sequence of operations
Before testing, obtain the approved sequence, smoke-control matrix if applicable, control drawings, device schedule, and point list. Identify what the fire alarm system commands and what it only monitors. A damper may be controlled by a relay module, by a smoke-control panel, by BAS under a listed interface, or by local duct detection depending on the design.
Separate command from feedback
For each device, document the output command and the expected proof of position or equipment status. A relay changing state proves only the command circuit. Verify that the damper actually moves, the actuator receives power, the end switch changes, and the correct supervisory or status point is received. The same separation applies to fans: start/stop command, starter/VFD response, airflow or run status, and fault status can be different points.
Use coordinated functional testing
Smoke control and fire/smoke damper testing often requires fire alarm, HVAC/BAS, mechanical, controls, electrical, and commissioning personnel. Coordinate impairments and expected building effects before activation. Avoid forcing outputs or jumping end switches in a way that bypasses the real equipment response unless the approved test procedure specifically calls for simulation.
Troubleshoot by boundary
If the fire alarm output operates but the damper does not move, the problem is downstream of the command and may involve actuator power, mechanical binding, interlocks, or controls logic. If the damper moves but the fire alarm point never changes, focus on the end switch, monitor circuit, or programming. If neither changes, prove the initiating condition and output logic first.
Document what physically happened
A useful test record states the initiating event, commanded state, actual damper/fan response, feedback received, reset response, and any discrepancy. For large systems, maintain an asset-level list so repeat deficiencies can be tracked by damper or fan rather than by generic room description.
Common mistakes to avoid
- Calling a test complete when only the fire alarm relay changes state
- Jumping an end switch and recording the damper as operational
- Testing without the approved sequence of operations
- Changing BAS or mechanical logic to solve a fire alarm indication without cross-trade coordination
Field checklist
- Obtain sequence, matrix, drawings, and point list
- Identify command and feedback points for each asset
- Coordinate impairments and responsible trades
- Verify physical movement/run state, not just relay state
- Confirm end-switch/fan-status feedback at the correct panel
- Test reset and return-to-normal sequence
- Record asset-specific results and deficiencies
What to verify before you act
Use this article to organize the field problem, then verify the requirement or permitted method in the documents that govern the job:
- The adopted NFPA 72 edition and applicable building/fire code provisions
- Manufacturer installation, service, compatibility, and programming documentation
- Approved drawings, sequence of operations, project specifications, and AHJ direction
Important limitation
This guide is a field-oriented starting point, not a substitute for the adopted code, approved drawings, project specifications, manufacturer instructions, site safety procedures, or the authority having jurisdiction. Do not bypass a listed protection feature or leave a required system impaired without following the approved impairment process.