Skip to main content
Back to blog
Compliance4 min read

Fire Alarm As-Built Drawings and System Documentation

Why accurate as-built drawings and system documentation matter, what they should contain, and how to keep them current — for UK fire alarm engineers.

By Incognito Fire & Security · 1 August 2026

Editorially reviewedVersion 1medium confidence

Last updated 1 August 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 As-Built Drawings and System Documentation

Good documentation is what turns a fire alarm system from a black box into something others can understand, operate and maintain safely. As-built drawings and records tell the next engineer what is actually installed and how it is meant to behave. When they are accurate, every future task is easier; when they are missing or wrong, everything becomes slower and riskier. This guide covers why as-builts matter, what documentation a system needs, and how to keep it current.

The theme throughout is that the documentation must describe the system as it actually is, not as it was once designed.

Who this is for

This is for competent fire alarm engineers producing or maintaining system documentation. The experience level assumed is competent engineer. Use it for the principles; the specific documentation requirements come from BS 5839-1 and the project requirements.

Why as-builts matter

As-built drawings record what was actually installed — device locations, zones, cabling routes, panel and interface positions — rather than what was originally designed, because installations rarely match the first drawing exactly. They are essential for maintenance, fault finding, modification and for demonstrating what protects the building. Inaccurate or missing as-builts make every future task harder and more error-prone, and can lead to devices being missed or misunderstood. Maintaining accurate documentation is part of good practice under BS 5839-1 and supports the responsible person's duties.

What documentation is needed

A well-documented system has, as applicable, as-built drawings, a zone chart, the cause and effect, the design and category basis, commissioning and handover certificates, the log book, and operating and maintenance information. Together these let others understand how the system is arranged, what it does on a fire, and how to look after it. The specific documentation follows BS 5839-1 and the project requirements, and should be kept with the system — near the panel where appropriate — so it is available to whoever needs it.

Keeping records current

Documentation is only useful if it stays true. Records are kept current by updating them whenever the system is modified — devices added or moved, zones changed, panels replaced — so the documentation always reflects the installed system. This is an integral part of change control: a modification is not really complete until the records are updated. From field experience, out-of-date drawings and an un-updated zone chart are among the most common and avoidable causes of confusion and error, and keeping them current follows BS 5839-1.

Servicing and documentation

Servicing is a natural checkpoint for documentation. Confirm the as-built drawings, zone chart, cause and effect and log book are present, legible and match the installed system, and that changes since the last visit are reflected. From field experience, records that quietly drift out of step with the system are the norm rather than the exception, so this deserves real attention. Where the documentation no longer matches reality, flag it and arrange for correction rather than working around it. Record what documentation exists and any gaps found.

Common points to check

Recurring issues include as-built drawings that no longer match the system, an un-updated zone chart after modifications, and missing cause-and-effect or log-book records. Confirming the documentation reflects the installed system is the essential check.

When not to rely on this alone

When not to use this article: do not treat it as a specification for a particular project's documentation. That comes from BS 5839-1 and the project requirements, applied by competent professionals.

Relevant standards

Documentation and records follow BS 5839-1, a code of practice, within the project requirements. The legal duty to maintain fire precautions and records 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, 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 project requirements, or competent judgement. Verify documentation against current standards and the installed system.

Related documentation

Use this with the current BS 5839-1, the project requirements, and the system's own drawings, zone chart, cause and effect and log book. Update the as-built records whenever the system changes, and record any documentation gaps found during service.

Frequently asked questions

Why do fire alarm as-built drawings matter?

As-built drawings record what was actually installed — device locations, zones, cabling routes, panel and interface positions — as opposed to what was originally designed. They are essential for maintenance, fault finding, modifications and demonstrating what protects the building. Inaccurate or missing as-builts make every future task harder and riskier. Maintaining accurate documentation is part of good practice under BS 5839-1 and supports the responsible person's duties.

What documentation should a fire alarm system have?

A system should have, as applicable, as-built drawings, a zone chart, the cause and effect, the design and category basis, commissioning and handover certificates, the log book, and operating and maintenance information. Together these let others understand, operate and maintain the system correctly. The specific documentation follows BS 5839-1 and the project requirements, and should be kept with the system and updated as it changes.

How are as-built records kept up to date?

Records are kept current by updating them whenever the system is modified — devices added or moved, zones changed, panels replaced — so the documentation always reflects the installed system. This is part of proper change control: a modification is not complete until the records are updated. Out-of-date drawings are a common and avoidable source of confusion and error, and keeping them current follows BS 5839-1.

What should be checked about documentation during service?

Confirm the as-built drawings, zone chart, cause and effect and log book are present, legible and match the installed system, and that changes since the last visit are reflected. Missing or outdated documentation should be flagged. Where the records no longer match reality, note it and arrange for them to be corrected. Record what documentation exists and any gaps.

Related tools and references