You’re usually reading about commissioning fire alarm systems at one of two moments. Either the install looks finished and handover is looming, or something on site already feels off. A panel is showing faults, devices aren’t reporting where they should, or the client is asking for certificates before the system has been properly proven.

That’s where good projects separate from risky ones. In practice, commissioning isn’t the last quick task after first fix and second fix. It’s the point where an installed system is tested against the design, the cause and effect, and the reality of the building. In London properties, that reality often includes mixed-use layouts, phased refurbishments, awkward containment routes, legacy wiring, and tenants who cannot easily vacate while you test.

A compliant handover under BS 5839-1 depends on more than getting sounders to ring. It depends on proving the system works as intended, recording what was tested, resolving faults properly, and leaving the responsible person with documents they can rely on.

Table of Contents

• Why Proper Commissioning Is a Non-Negotiable Final Step
  • What commissioning actually proves
  • What doesn’t work on site
• Pre-Commissioning Checks for a Solid Foundation
  • Prove the wiring before the panel sees it
  • Check the installed system against the design information
  • Keep a working record, not a tidy fiction
• A Step-by-Step Guide to Functional Testing
  • Power up and verify the panel first
  • Test every device the right way
  • Prove the cause and effect
  • Confirm fault monitoring and standby operation
• Essential Documentation and Client Handover
  • What the handover pack needs to include
  • What to show the client before you leave
• Troubleshooting Common Commissioning Failures
  • When the panel shows a loop or device fault
  • When testing causes nuisance alarms and confusion
• Defining Roles and Navigating Modern Challenges
  • Who is responsible for what
  • Why modern integrations are harder to commission properly

Why Proper Commissioning Is a Non-Negotiable Final Step

A fire alarm installation can look complete and still be nowhere near ready for handover. The panel may be mounted neatly, the detectors may be in place, and the cabling may test fine electrically. None of that proves the building will respond correctly in a fire.

Under BS 5839-1:2017, commissioning is a required part of putting a fire alarm system into service in non-domestic premises. The legal duty sits alongside the Regulatory Reform (Fire Safety) Order 2005, which made this a responsibility for the responsible person. That matters because once a building is occupied, paperwork and assumptions won’t protect anyone. The system has to perform.

The cost of getting that wrong isn’t theoretical. According to the Fire Industry Association, failure to commission properly is linked to 28% of false alarms in UK commercial buildings, with an economic cost of £1.2 billion in 2022, as cited in this overview of commissioning under BS 5839-1.

What commissioning actually proves

Commissioning answers practical questions that basic installation checks do not:

• Does each device report correctly at the panel with the right address and text label?
• Do sounders and visual alarms operate in the required sequence for that building?
• Do interfaces work properly with doors, ventilation, lifts, shutters, or other connected systems where applicable?
• Can the system cope with mains failure and continue on battery backup?
• Do the records match the physical installation so future maintenance isn’t guesswork?

Practical rule: If you can’t show what was tested, how it was tested, and what the result was, you haven’t finished commissioning.

In London, the risk usually comes from assumptions made during fit-out. A retail unit becomes mixed-use. A converted townhouse gets a panel upgrade but retains bits of old wiring. A landlord wants a quick certificate before tenants move in. On those jobs, commissioning is where hidden errors surface.

What doesn’t work on site

Some habits cause problems again and again:

A proper commission isn’t box-ticking. It’s the final proof that the system installed in that actual building matches the design intent and can be trusted in service.

Pre-Commissioning Checks for a Solid Foundation

A London office fit-out is due for handover on Friday. By Wednesday afternoon, the panel is still showing faults, two call points are labelled to the wrong stair core, and an interface has been landed on the wrong circuit after a late design tweak. None of that gets fixed quickly if the groundwork was rushed.

Under BS 5839-1, commissioning only stands up if the installation has already been checked properly. Pre-commissioning is the point where you prove the cabling, devices, records, and layout are ready for live testing. On refurbishment jobs, especially across older London stock, this is usually where mixed wiring methods, undocumented alterations, and poor labelling show up.

Prove the wiring before the panel sees it

Before any control equipment is energised, inspect and test the field wiring methodically. The aim is simple. Find faults while they are still cheap and safe to fix.

That means checking for continuity issues, short circuits, earth faults, polarity errors, unwanted voltages, and insulation damage. If a loop has been extended through an old riser, or if a tenant fit-out contractor has shared containment without telling anyone, these faults are common. I would rather lose an hour on dead testing than lose half a day fault-finding after devices and panel electronics are connected.

A sound pre-commissioning routine includes:

• Continuity checks on each circuit, loop section, and radial where used
• Insulation resistance testing where appropriate for the installed equipment and manufacturer instructions
• Earth fault checks before connecting sensitive electronics
• Polarity verification on circuits and interfaces that depend on correct termination
• Open-circuit confirmation so breaks are identified before cause and effect testing starts

The standard matters, but site conditions matter as much. In a converted townhouse or part-occupied commercial building, the drawing may show a clean route while the ceiling void tells a different story. Check the installed cable, not the cable path everyone assumed was there.

For teams tightening up their inspection discipline, broader guidance on residential and commercial electrical inspections is useful because the same principle applies. Verify what is physically present, record what you found, and do not rely on assumption.

Check the installed system against the design information

Pre-commissioning is also where the paperwork meets the building. BS 5839-1 depends on the system matching the design, and handover becomes difficult very quickly when the drawings, zone chart, device labels, and panel text all tell slightly different stories.

On site, check these points before live tests begin:

• Device location matches the drawings and any approved variations
• Device type matches the schedule and fire strategy
• Addressing and text labels are consistent at the panel, on drawings, and at the device where applicable
• Interfaces and auxiliary equipment are identified clearly, especially where lifts, vents, doors, or shutters are involved
• Terminations and containment are secure, labelled, and suitable for maintenance access
• Access for test and service is practical after occupation, not just during fit-out

London jobs frequently expose a recurring issue. A detector gets shifted to suit a ceiling feature. A call point moves because of a new partition line. An old interface is left in place because nobody wanted to open up a finished wall. If those changes are not marked and agreed before commissioning, the certificates may look tidy while the installed system does not.

Keep a working record, not a tidy fiction

Use a marked-up drawing set and update it as the checks are done. Record device addresses, loop breaks, substituted equipment, inaccessible areas, builder’s work still outstanding, and anything that needs client or designer approval. That working set often becomes the clearest evidence that the system was checked properly and that deviations were identified before handover.

Good records also help when the wider electrical package is being signed off alongside the fire alarm. On mixed-use and managed sites, that can include related safety routines such as PAT testing services where portable equipment forms part of the building’s documented compliance process.

A clean certificate at the end is useful. A clear audit trail of what was installed, checked, and corrected is what protects the client, the maintainer, and the person signing the commissioning paperwork.

A Step-by-Step Guide to Functional Testing

The part that catches people out is not usually the first alarm activation. It is the third or fourth device, when the panel text is wrong, a sounder circuit stays silent on one floor, or an AOV interface operates from the wrong zone. On London jobs, especially refurbishments and mixed-use buildings, that is common. Functional testing is where the paperwork meets the building that got built.

Once the installation checks are done, bring the system on in a set order and record each result as you go. BS 5839-1 expects commissioning to confirm that the system operates correctly in line with the design, and that means proving inputs, outputs, indications, and standby arrangements rather than just getting a bell to ring.

Power up and verify the panel first

Start at the control and indicating equipment. Before any detector or call point is tested, confirm the panel is healthy in normal condition, with no unexplained faults, disablements, missing devices, or corrupt text.

Check the basics properly:

1. Normal condition on power-up. The panel should settle without faulting for avoidable reasons such as battery polarity, loop wiring issues, or missing end-of-line devices on conventional circuits.
2. Date and time. Event logs are part of the compliance trail. If the clock is wrong, the log becomes hard to rely on during handover or later investigation.
3. Device text and zone information. Locations must be clear enough for the user and attending engineer to identify the correct area without guesswork.
4. Access levels and controls. Keys, codes, silence, reset, lamp test, buzzer silence, and disablement controls should all operate as intended.
5. Battery and charger status. Confirm the batteries are connected, charging, and reported correctly by the panel.

A tidy enclosure means very little if the programming is poor. I have seen good-looking panels in plant rooms where half the devices were described as "smoke detector" with no location detail. That is not a commissioning standard anyone should sign.

This short walkthrough helps if you want to see the testing mindset in action:

Test every device the right way

Each field device needs an individual functional test and a matching record. One detector proving on a loop does not prove that all devices are addressed correctly, labelled correctly, or reporting from the correct location.

Use the proper test method for the device type:

• Manual call points tested with the correct key or test tool
• Smoke detectors tested with approved smoke stimulus, not by pressing the head or using site dust
• Heat detectors tested with a controlled heat source suitable for the detector type
• Interfaces and input modules proved by operating the actual monitored condition where practical

For every activation, confirm three things at the panel. The correct address appears, the correct text appears, and the system responds in line with the design. If any one of those is wrong, stop and correct it before carrying on. Testing twenty more devices after finding the first addressing error only creates a larger snag list.

On larger sites, keep the sequence disciplined. Work loop by loop or zone by zone. That approach also ties in well with broader verification work such as an EICR certificate in London where traceable test records matter as much as the technical result.

Prove the cause and effect

This stage decides whether the system is fit for the building, not just whether the panel can receive an alarm. Cause and effect has to be tested against the approved schedule on site. Memory is not good enough, and old revisions are a regular source of error on phased refurbishments.

Check the actual building response, including:

• Sounders and VADs in the correct areas and sequence
• Door holders and magnetic releases dropping out and resetting correctly
• Smoke control, dampers, or HVAC shutdowns only where the design requires them
• Lift homing, gas shut-off, sprinkler interfaces, or plant shutdowns where provided
• Repeater panels, mimic panels, and remote indications showing the same event correctly
• Delays, investigation periods, or phased evacuation logic operating exactly as documented

A common failure is a system that gives some sort of alarm but not the right one. For example, a call point in a retail unit may trigger sounders in common parts but miss the landlord interface, or a detector in a flat entrance lobby may report into the wrong text group because the device was swapped late in the fit-out. Those are not minor admin issues. They affect evacuation, fire service response, and the validity of the handover paperwork.

Confirm fault monitoring and standby operation

Alarm testing is only part of commissioning. Fault conditions need proving as well. BS 5839-1 expects faults to be indicated correctly, and that includes monitoring on power supplies and field wiring where the system design provides it.

Check mains failure in a controlled way and watch the panel indication. Confirm the charger reports correctly, the batteries support the system, and restoration to normal is clean once mains is returned. Where interfaces, monitored outputs, or transmission equipment are part of the system, prove that relevant fault conditions are detected and shown clearly.

A practical testing record looks like this:

Good commissioning is repetitive by design. That repetition is what exposes the wrong label on the sixth floor, the missing interface in the basement plant room, and the output that only fails after a reset.

Essential Documentation and Client Handover

Friday afternoon in a converted London office block, the panel is showing healthy, the sounders have been proved, and everyone wants the keys signed off before tenants arrive on Monday. That is the point where weak paperwork causes real problems. If the certificate is incomplete, the zone chart is wrong, or the responsible person has not been shown how to read a fault condition, the system may be installed but the handover is still defective under BS 5839-1.

What the handover pack needs to include

BS 5839-1 expects clear records at completion, and in practice those records need to do two jobs. They need to show compliance, and they need to help the next engineer or building manager understand exactly what is on site. In London properties, that second part is where jobs often fall down. Refurbishments change layouts, devices get moved late in the project, and the drawing in the folder still shows last month’s design.

A proper handover pack should include:

• Commissioning certificate completed accurately and signed.
• Installation certificate covering the work installed.
• As-fitted drawings showing the final device positions, loop routes, zones, interfaces, power supplies, and any variations from design.
• Cause and effect documentation that matches the programmed configuration proved on site.
• Operating instructions for the control and indicating equipment, repeaters, and any specialist interfaces.
• Zone chart and device identification information where applicable, so alarms can be located quickly.
• Log book for weekly tests, faults, false alarms, disablements, maintenance visits, and system alterations.
• Details of any outstanding limitations or agreed variations so nothing is hidden at handover.

The documents must match the building as it stands on the day of handover. Tender drawings, marked-up first fix plans, and vague descriptions are no use during a fire alarm event or an audit.

For landlords and managing agents, the fire alarm file usually sits with the wider electrical safety record. That is why related certification, such as an EICR certificate in London, is often kept in the same compliance file for inspection, insurance, and tenancy management.

What to show the client before you leave

Handover is a working demonstration. The responsible person should not be left with a panel key, a stack of certificates, and guesswork.

Show them the panel in normal condition first. Then show them what a fire condition looks like, what a fault looks like, and what a disablement looks like. Those three states are regularly confused by site staff, especially in mixed-use buildings where reception teams, caretakers, and managing agents all touch the system at different times.

Cover these points before leaving site:

• How to identify fire, fault, and disablement indications on the panel display and LEDs.
• How to silence and reset the system if the site procedure allows authorised staff to do so.
• How weekly user tests should be arranged and recorded in the log book.
• What to do after an alarm activation, including who to contact for maintenance or investigation.
• Which controls must not be used casually, such as isolations, disablements, delays, and interface overrides.
• What areas are prone to unwanted alarms because of dust, aerosols, steam, or contractor activity.

False alarms are a handover issue as much as a maintenance issue. If the client does not understand what triggers detectors in kitchens, shower areas, loading bays, or during fit-out works, the system will be misused and confidence in it drops. The Securitec advice on alarm triggers is a useful plain-English reference for common causes, but site-specific instruction still matters more than generic advice.

One final check matters. Ask the client to repeat the key actions back to you at the panel. If they cannot explain how to recognise a fault, where the log book is kept, or who is authorised to reset after an activation, the handover is not complete.

Troubleshooting Common Commissioning Failures

Even on tidy jobs, commissioning throws up problems. What matters is whether you diagnose them logically or start changing parts at random.

When the panel shows a loop or device fault

A common site sequence goes like this. The panel powers up, half the loop looks healthy, then one section reports a missing device, open circuit, or loop fault. The temptation is to blame the panel configuration first. Often the fault is more basic.

Start by narrowing the problem physically, not just electronically.

• Open circuit symptoms usually point to a broken conductor, loose termination, missed return leg, or a device not landed properly.
• Short circuit symptoms often come from damaged insulation, trapped cores, polarity mistakes, or moisture in a device base.
• Earth fault symptoms can be slower to trace and may involve contact with containment, damaged cable, or contamination at terminations.

Use the multimeter to divide the circuit, prove continuity, and verify resistance on the affected section. On addressable systems, also confirm that the device fitted at that location matches the programmed address and text.

One of the most time-wasting faults is the “missing device” that isn’t missing at all. It’s there, but addressed incorrectly, fitted on the wrong loop, or labelled from an earlier revision of the drawings.

When testing causes nuisance alarms and confusion

Occupied buildings add another layer. You may be trying to commission while offices are open, tenants are in residence, or a caretaker is phoning every few minutes because someone heard sounders in the wrong area.

That’s why test notifications, zoning clarity, and temporary management arrangements matter. False or nuisance activations during commissioning don’t always come from technical faults. They can come from poor coordination, dusty work areas, detector contamination, or users misunderstanding what is being tested. For a straightforward overview of common false-alarm triggers, Securitec advice on alarm triggers is a useful reference.

“If a building is occupied, control the people around the test as carefully as the test itself.”

A few practical habits reduce site friction:

The engineer who stays calm and methodical usually solves commissioning failures faster than the one who looks busiest.

Defining Roles and Navigating Modern Challenges

A lot of commissioning disputes start the same way. The panel is live, interfaces are half-proved, the client wants a certificate, and nobody agrees on who was meant to define the cause and effect in the first place. On London jobs, especially refurbishments, that confusion is usually what slows handover more than the testing itself.

Under BS 5839-1, roles need to be clear before anyone starts trying to prove the system. If design responsibility is blurred, the installer ends up making engineering decisions on site, the commissioning engineer is pushed to approve work that is still incomplete, and the responsible person receives a system that may operate but is not properly documented. That is how avoidable non-conformities end up in the handover pack.

Who is responsible for what

On a well-run project, each party has a defined job.

• The designer sets the system category, detector and sounder strategy, zoning, interfaces, and cause and effect. Those decisions need to be specific enough to install and specific enough to test against.
• The installer puts in the system to the drawings, manufacturer instructions, and BS 5839-1 requirements, while recording any site-driven changes properly.
• The commissioning engineer proves the installed system operates as intended, records variations, identifies defects, and refuses sign-off where life safety functions have not been demonstrated.
• The client, duty holder, or responsible person needs to attend handover, receive the correct certificates and records, and understand what ongoing inspection, testing, and logbook control involve.

That sounds straightforward. On site, it often is not.

The common failure is scope drift. A room use changes late in the fit-out, a door release is added after first fix, or a smoke control interface is assumed to be "by others" with no one taking ownership. By commissioning day, the panel text is out of date, the drawings no longer match the installed heads, and the cause and effect matrix exists only in email chains. If that happens, stop and correct the record before handover. A clean certificate attached to poor information does not protect the client.

Where projects involve wider design coordination, the same lesson applies outside fire alarms. Early decisions on responsibility, interfaces, and specification usually decide whether testing is orderly or chaotic later on. Even in broader building projects, discussions around procuring MEP engineering services reflect the same problem. If coordination is weak at design stage, the defects appear during commissioning.

Why modern integrations are harder to commission properly

A conventional panel with clear zoning is one thing. An addressable system tied into lifts, access control, air handling plant, smoke dampers, and remote monitoring is another.

Each interface adds a point of failure and a point of dispute. I often see the fire alarm side tested thoroughly while the interfaced system is unavailable, isolated, or still under another contractor's control. The result is a partial test dressed up as a full commissioning exercise. For BS 5839-1 compliance and a defensible handover, the records need to show what was tested, what was witnessed, what could not be tested, and what remains outstanding.

This matters even more in London properties. Older buildings converted for new uses often combine modern addressable devices with legacy containment, undocumented alterations, mixed tenancy areas, and poor access to risers or ceiling voids. Wireless devices can solve some installation problems, but they still need stable communication paths, sensible device siting, and proper signal verification under real site conditions. They do not remove the need for disciplined commissioning.

Large venues add another layer because multiple life safety and electrical systems are interacting at once. On that type of project, contractors with experience in electrical services for stadium environments are often coordinating alongside the fire alarm team, and the standard of interface scheduling needs to be high from the start.

Three things prevent most late-stage problems. A cause and effect matrix that has been approved. As-fitted drawings and device text that match the building as it stands today, not two revisions ago. Access to the right trades and system owners while testing is happening, so faults and failed interfaces can be proved and closed out there and then.

If those pieces are missing, commissioning becomes guesswork. That is not acceptable on a life safety system.