Skip to main content
Back to blog
Maintenance4 min read

Fire Alarm System Takeover: Adopting an Existing Installation

What to check before taking on maintenance of an existing fire alarm system — documentation, condition, non-compliances and recording limitations — for UK engineers.

By Incognito Fire & Security · 28 July 2026

Editorially reviewedVersion 1medium confidence

Last updated 28 July 2026.

Sources used

3

Review sources and evidence basis

Source labels describe the evidence basis; current manufacturer documents and licensed standards remain authoritative. Professional disclaimer

Fire Alarm System Takeover

Taking on the maintenance of an existing fire alarm system is one of the riskier things a company does, because you inherit whatever the previous designer, installer and maintainer left behind — good or bad, documented or not. Do it casually and you can quietly become responsible for someone else's non-compliances. This guide covers how to adopt an existing installation properly: what to check, how to record what you find, and how to handle problems.

The theme is due diligence and honesty — know what you are taking on, and record it truthfully.

Who this is for

This is for competent fire alarm engineers and companies adopting existing systems as a new maintainer. The experience level assumed is competent engineer. Use it for the principles; the specifics come from BS 5839-1, the system's own documentation and the responsible person.

Why takeover matters

When you take over a system, you take on responsibility for maintaining it and for advising the responsible person about it. If that system has hidden non-compliances, undocumented modifications, or poor previous workmanship, those become your concern the moment you sign up. A structured takeover — rather than simply turning up for the first service — is what stops you inheriting problems blind. It protects you, and it gives the responsible person an honest baseline of what they actually have.

The takeover inspection

A proper takeover starts with the documentation: certificates, the cause and effect, as-fitted drawings and zone plan, and the log book. Then inspect the system's condition and configuration against that documentation and against BS 5839-1 — the panel, the coverage, the devices, obvious modifications. The aim is a clear picture of what has been installed, how it is configured, and where it departs from the standard or from its own records. Gaps in the documentation are themselves a finding worth noting.

Recording limitations honestly

You will not be able to verify everything on a first visit — drawings may be missing, areas inaccessible, cause and effect unknown. The essential discipline is to record those limitations clearly rather than implying you have confirmed something you have not. Stating plainly what was and was not verified sets honest expectations, flags what needs follow-up, and protects you if an unverified area later proves faulty. Overstating what you checked is both dishonest and a liability.

Handling non-compliances

Where you find a departure from the relevant recommendation, note it factually and report it to the responsible person, who can then decide on remedial action against their risk assessment — a duty that sits with them under the Regulatory Reform (Fire Safety) Order 2005. It is not the incoming maintainer's place to quietly absorb undocumented issues, nor to carry out unagreed remedial work. Clear, factual reporting puts the decision where it belongs and keeps you on solid ground.

Common points to check

From field experience, the recurring findings on takeover are missing or out-of-date documentation, undocumented modifications, and previous work that does not match the drawings. Approaching the first visit as a structured takeover, not just a service, is what surfaces these before they become your problem.

When not to rely on this alone

When not to use this article: do not use it as a substitute for a full takeover procedure or for judging a specific system's compliance. Those come from BS 5839-1, the system documentation and competent assessment, applied to the specific installation.

Relevant standards

Taking over, inspecting and maintaining an existing system is addressed within BS 5839-1, a code of practice. The responsible person's legal duty to maintain fire precautions in most non-domestic premises sits under the Regulatory Reform (Fire Safety) Order 2005, with Building Regulations statutory guidance in Approved Document B applying to building work. Separate the legal duty from the recommended methods when advising a client, and always work to current editions.

Professional disclaimer

This is an educational and workflow resource for competent engineers and does not replace the current British Standards, the system documentation, or competent judgement. Verify takeover and compliance assessments against current documentation.

Related documentation

Use this with the current BS 5839-1, the system's certificates, cause and effect, drawings and log book, and the fire risk assessment. Record the takeover inspection, including all limitations and non-compliances, and report them to the responsible person.

Frequently asked questions

What should you check before taking over maintenance of a fire alarm system?

Before adopting an existing system, review the available documentation (certificates, cause and effect, drawings, log book), inspect the system's condition and configuration, and identify any obvious non-compliances or limitations. You are taking on responsibility for maintaining it, so you need a clear picture of what you are inheriting. Record what you find, including anything you could not verify.

Why does adopting an existing system carry risk?

You become responsible for maintaining a system someone else designed and installed, often with incomplete records. If there are hidden non-compliances, undocumented modifications or poor previous work, they become your problem once you take over. A structured takeover inspection and honest recording of the system's state protect both you and the responsible person.

How should limitations be recorded on takeover?

Where you cannot verify part of a system — missing drawings, inaccessible areas, unknown cause and effect — record the limitation clearly rather than implying you have confirmed something you have not. Honest recording of what was and was not verified is essential; it sets expectations, flags what needs follow-up, and protects you if an unverified area later proves faulty.

What if the system you are adopting is non-compliant?

Note the non-compliance factually against the relevant recommendation, and report it to the responsible person so they can decide on remedial action against their risk assessment. It is not for the incoming maintainer to quietly accept or fix undocumented issues without the responsible person's knowledge. Clear, factual reporting lets the right decisions be made.

Related tools and references