Fire Alarm Commissioning: 20-Point Pre-Handover Checklist | Finder

Fire Alarm Commissioning: 20-Point Pre-Handover Checklist | Finder

Commissioning is not a few alarm activations at the control panel. Approved drawings, device addresses, loops/zones, alarm and fault functions, standby power, audible/visual alarms, manual call points, remote transmission and all cause-and-effect interfaces such as BMS and HVAC must be verified end to end. The final step is documented closure of deficiencies and a handover package that allows the site team to operate and maintain the system safely.

Why commissioning is a separate engineering phase

A system can be well installed yet fail its intended function because of incorrect configuration, wrong labels, missing interfaces or untested fault behaviour. Commissioning proves that the approved design has been realised on site. CEN/TS 54-14:2018 addresses planning, design, installation, commissioning, use and maintenance as one lifecycle. NFPA 72:2025 also contains dedicated requirements for documentation and inspection, testing and maintenance. The project must state which standards, local regulations and authority requirements govern acceptance.

Scope note

This checklist is a general commissioning and handover guide. It does not replace the approved design, specification, manufacturer instructions, authority requirements or the project-specific acceptance procedure. Test quantities, methods, thresholds, durations and pass/fail criteria must be verified for the actual project.

1. Before testing: three gates

Gate

Check

Do not proceed until

Documents ready?

Approved drawings, device schedule, address/zone plan, cause-and-effect matrix, cable routes and current revisions are available.

Functional testing can be traced to an approved baseline.

Site ready?

Installation is complete, devices are accessible, temporary works are identified and interfacing trades are ready.

Interface acceptance can be performed safely.

Test plan approved?

Test roles, witnesses, methods, records and deficiency closure process are defined.

Handover can be evidenced and signed.

2. 20-point pre-handover test checklist

1. Approved design vs as-built

Do devices, cables, modules and interfaces match the latest approved design? Are field changes captured in as-built drawings?

Evidence and record: Revision + field record.

2. Panel configuration and backup

Panel model, firmware/software, date/time, access levels, network nodes and configuration backup verified?

Evidence and record: Config printout/backup.

3. Addresses, zones and location text

Does every address identify the correct physical location and zone at the panel/annunciator?

Evidence and record: Address list + screen record.

4. Loop/circuit/cable integrity

Any open, short, earth/ground fault or reversed connection? Shielding/earthing per approved design?

Evidence and record: Measurement/test record.

5. Detector physical inspection

Correct detector/base, position, obstruction clearance, covers removed and maintenance access available?

Evidence and record: Visual inspection form.

6. Detector functional test

Using an approved test method, does the detector produce the correct alarm, address, zone, text and event sequence?

Evidence and record: Test result + timestamp.

7. Manual call points

Does each call point operate, report the correct location and reset correctly, with suitable access?

Evidence and record: MCP test record.

8. Audible alarms / voice functions

Do sounders or voice alarm functions operate in the correct scenario and area? Where required, are acoustic/intelligibility measurements recorded?

Evidence and record: Functional/measurement form.

9. Visual alarm devices

Do visual alarm devices operate in the correct zone/scenario, with required circuit and synchronisation behaviour?

Evidence and record: Functional record.

10. Cause-and-effect matrix

Do alarm, pre-alarm, delays, confirmation, silence, reset and outputs follow the approved sequence?

Evidence and record: Signed C&E test table.

11. Fire doors and access control

Do hold-open devices, door releases, turnstiles or locks move to the intended safe state?

Evidence and record: Interface test record.

12. HVAC and smoke control

Do fan, damper, jet-fan and smoke-control commands operate for the correct zone; are feedback signals correct?

Evidence and record: Joint BMS/HVAC record.

13. Lifts and other building systems

Do lift recall, escalators, generators or other connected systems respond according to the fire strategy?

Evidence and record: Multi-trade test record.

14. Suppression and special-risk interfaces

Where applicable, are suppression panels, pre-action, gaseous systems, kitchen suppression or process shutdown I/O safely verified?

Evidence and record: Interface/I-O record.

15. Remote transmission and BMS

Do fire, fault and required supervisory signals reach security, BMS or remote monitoring with the correct priority and text?

Evidence and record: Send/receive comparison.

16. Mains failure and standby power

On loss of mains, does the system transfer to standby power correctly, indicate the fault and recover properly?

Evidence and record: Power test record.

17. Fault and isolator scenarios

Are selected open/short circuit, device loss, network fault and isolator behaviours correctly indicated and contained?

Evidence and record: Fault-scenario form.

18. Controls and access levels

Do silence, reset, disable/enable, test mode and user permissions work without allowing unsafe operation?

Evidence and record: Access/function check.

19. Event log and reporting

Are alarm, fault, disablement and reset events logged with correct time and device information; can records be exported?

Evidence and record: Event-log export.

20. Training, labelling and handover pack

Has operator training been completed and are as-builts, schedules, test reports, backups, maintenance plan and open-item status handed over?

Evidence and record: Signed training/handover record.

3. How to record a functional test

“Tested / OK” is not sufficient evidence by itself. A record should allow another technician to reproduce the test and understand what was expected and what actually occurred.

Record field

Example

Test ID

T-021 / Loop 2 / Device 034

Date and time

02 Sep 2026 10:42

Tester / witness

Technician + consultant/facility representative

Stimulus method

Approved smoke aerosol / heat tester / call-point key

Expected result

Panel alarm + zone 3 sounders + BMS fire signal

Actual result

Alarm 10:42:16; BMS 10:42:18; sounders active

Result

PASS / FAIL / N.A.

Action

For FAIL: owner, due date and retest ID

Good practice

Do not declare overall acceptance complete while failed tests remain open. After correction, repeat the same functional test and retain the original failed result with its closure evidence.

4. Cause-and-effect: the most important acceptance table

Fire alarm systems often exchange commands and status with other building systems. Acceptance is therefore not a fire-panel-only activity. Electrical, mechanical, BMS, lifts, security and suppression teams may need to attend the same test window.

Detector alarm - Zone A

Fire alarm behaviour: Alarm + correct location + programmed outputs. Interfaced system: Sounder/VAD. Feedback to verify: Correct output and area.

Car-park alarm

Fire alarm behaviour: Alarm + smoke-control command. Interfaced system: HVAC / jet fans. Feedback to verify: Command + status feedback.

Alarm - fire-door area

Fire alarm behaviour: Alarm + release output. Interfaced system: Access/door controls. Feedback to verify: Door moves to intended safe state.

Lift interface alarm

Fire alarm behaviour: Defined output/relay. Interfaced system: Lift system. Feedback to verify: Recall sequence completed.

Suppression pre-alarm

Fire alarm behaviour: Defined monitoring/warning. Interfaced system: Suppression panel. Feedback to verify: Correct signal/state.

Fire-panel fault

Fire alarm behaviour: Fault + remote indication. Interfaced system: BMS/remote monitoring. Feedback to verify: Fault received at correct priority.

5. Why power and fault tests matter as much as alarm tests

The system must make wiring and power problems visible, not only fires. Fault simulation during commissioning must be controlled, reversible and planned so that it does not accidentally trigger real suppression or critical process actions.

  • Record transfer to standby power and fault indication when mains power is removed.

  • Verify battery connection, charging and design adequacy according to the approved project and manufacturer requirements; open-circuit voltage alone is not enough.

  • Simulate selected open/short circuit faults to observe affected devices and isolator behaviour.

  • For networked systems, include panel/node loss and communication fault scenarios.

  • Record how the system returns to normal after the fault is restored.

6. Ten common commissioning mistakes

  • Testing detector alarms but skipping fault scenarios.

  • Failing to compare panel location text with the real physical location.

  • Issuing “final” as-built drawings before field changes are incorporated.

  • Accepting BMS/HVAC/lift integration on paper without joint functional tests.

  • Triggering real suppression or critical process outputs without an approved safe-test plan.

  • Treating battery voltage as a complete standby-power test.

  • Leaving devices or modules disabled at handover.

  • Deleting failed test records and keeping only a clean PASS list.

  • Failing to synchronise event-log time with BMS/security systems.

  • Reducing operator training to a signature sheet instead of practising alarm, fault, silence and reset scenarios.

7. Recommended handover package

  • Approved design + as-built drawings: Create a permanent record of the real installation.
  • Device/address/zone schedule: Support fast service and incident location.
  • Cause-and-effect matrix: Define fire-event behaviour across all interfaces.
  • Commissioning/acceptance records: Prove how each required function was verified.
  • Configuration/program backup: Enable recovery after failure or replacement.
  • Product/installation manuals: Provide maintenance and service reference.
  • Battery/power calculations: Document the basis of standby-power design.
  • Training record + quick user guide: Enable safe operation by the site team.
  • Punch-list closure records: Provide traceable evidence that deficiencies were closed.
  • Maintenance plan + service contacts: Start the post-handover lifecycle.

8. Frequently asked questions

Is commissioning the same as periodic maintenance?

No. Commissioning verifies that a new or materially modified system matches the approved design and performs correctly before acceptance. Periodic maintenance preserves performance during operation.

Must every detector be individually tested?

The scope is defined by the approved project, applicable standard, specification and authority. The commissioning plan should account for every installed device; any sampling approach must have a documented basis.

If an alarm appears on the BMS, has the interface passed?

Not by itself. Signal type, location, priority, delay, feedback and reset behaviour should be verified end to end.

Is measuring battery voltage enough?

No. Standby-power design, connections, charging, load behaviour and the project-defined standby/alarm duty must be verified together.

How should a failed test be closed?

Record the defect, owner and target date, correct the issue, then repeat the same functional test and retain closure evidence.

Does suppression integration require a real discharge test?

Not always. Safe functional verification should follow the approved manufacturer/project test procedure; a live discharge is performed only where specifically required.

Which backup files are critical at handover?

Panel/network configuration backup, as-built drawings, address schedules and the cause-and-effect matrix are core continuity records.

Which standard should be used?

Verify local regulation, contract/specification, authority requirements and the current standards explicitly adopted for the project.

Keep commissioning records useful after handover

The value of a test lies not only in the alarm obtained on the day, but in a traceable record of expected and actual behaviour. When a device address, zone, panel message and operated outputs are considered together in the test record, facility and service teams can later see the conditions under which that function was verified. The configuration backup, as-built drawings and cause-and-effect matrix should be handed over with these records.

The records are handed over to the facility team.

Sources

CEN/TS 54-14:2018 — Fire detection and fire alarm systems: planning, design, installation, commissioning, use and maintenance — https://knowledge.bsigroup.com/products/fire-detection-and-fire-alarm-systems-guidelines-for-planning-design-installation-commissioning-use-and-maintenance-1

NFPA 72:2025 — National Fire Alarm and Signaling Code — https://link.nfpa.org/all-publications/72/2025

Turkish fire safety legislation — https://www.mevzuat.gov.tr/

Current Finder product, installation, programming and service documentation — https://www.finder.com.tr/

 

 

Other Blog Posts