BS 5839 Explained: Fire Alarm Categories and Testing
BS 5839 is the standard behind almost every fire alarm specification and service visit in UK non-domestic buildings. This guide explains what the category codes on your system mean, what the testing regime actually requires of an FM team week to week, and why false alarm performance has become a compliance issue in its own right.
In short
BS 5839-1 is the British Standard code of practice for fire detection and fire alarm systems in non-domestic premises. It covers system design, installation, commissioning, and maintenance, and defines the category codes (M, L1–L5, P1–P2) that describe what a given system is designed to protect.
What it typically costs
£200–£900 per year for servicing on a typical commercial system
- What moves the price
- Device count and number of panels drive the cost more than floor area. Systems with remote monitoring, addressable panels, or multiple buildings under one contract sit at the upper end; a small conventional system sits at the lower end.
- Typical time on site
- Periodic servicing usually falls across two or more visits per year
Indicative UK market ranges compiled from published price guides, last reviewed August 2026. They are a planning guide, not a quotation — actual prices vary by region, building, and contractor. Always obtain quotes for your own site.
What the category codes mean
Every system has a category describing what it is designed to do, and it is worth knowing yours because it determines what coverage is actually required. Category M is a manual system — call points only, no automatic detection. The L categories protect life, running from L5 (a bespoke, risk-specific arrangement) through L4 (escape routes), L3 (escape routes plus rooms opening onto them), L2 (L3 plus defined high-risk areas) to L1 (detection throughout). The P categories protect property, with P1 covering the whole building and P2 covering defined areas.
A system can carry a combined category — L2/P2 is common — and the category should be recorded in the system's design documentation and log book. Where it is not, establishing it retrospectively is one of the more tedious jobs in FM, because a service engineer can tell you what devices exist but not what the design intent was. That distinction matters when someone asks whether a newly partitioned area needs detection adding.
- M — manual call points only, no automatic detection
- L1–L5 — life protection, from full coverage down to a defined risk-specific scope
- P1–P2 — property protection, whole building or defined areas
- Combined categories (e.g. L2/P2) are common and should be recorded in the log book
The testing regime
The routine that falls to the building's own team is the weekly test: operating a call point — a different one each week, working through them in rotation — to confirm the system responds and that the alarm is audible where it needs to be. The result goes in the fire alarm log book, which is the primary record an inspector will ask for.
Periodic servicing by a competent person is additional, and the standard's recommendation is that this happens at intervals not exceeding six months, so most sites run two or more service visits a year. Servicing covers a proportion of devices on each visit such that all devices are tested across the annual cycle, along with the panel, batteries, and cause-and-effect. Battery and standby power checks, and testing of any links to remote monitoring, form part of that regime.
- Weekly — test one call point in rotation, record in the log book
- Periodic servicing by a competent person at intervals not exceeding six months
- All devices tested across the annual cycle, not all at every visit
- Panel, batteries, standby supply, and cause-and-effect verified as part of servicing
False alarms and the log book
BS 5839 treats false alarm management as a substantive requirement rather than an annoyance. Persistent unwanted alarms erode occupant response, consume fire service resource, and in practice are the leading cause of a system being partially disabled by the people meant to be protected by it. The standard expects false alarms to be recorded, investigated by cause, and acted on where rates exceed reasonable levels — which means the log book is a management tool, not just a compliance artefact.
Everything above depends on the log book being complete and available: weekly tests, service visits, faults, disablements, false alarms and their causes, and any modification to the system. It is also the document most likely to be a paper book in a cupboard by the panel, which is precisely why it goes missing at handover or when a building changes managing agent. Keeping the system's design data, commissioning certificate, and service history somewhere searchable is what makes the category question answerable years later.
Related maintenance checklists
Related inspection checklists
Further reading
Sources
The regulatory positions on this page come from the following primary sources. Where guidance and legislation differ, the legislation governs — always confirm the requirements that apply to your own site and jurisdiction.
- Regulatory Reform (Fire Safety) Order 2005 — legislation.gov.uk
- Fire Safety (England) Regulations 2022: guidance — GOV.UK
Frequently asked questions
Keep alarm records searchable
Log books, commissioning certificates, service reports, and cause-and-effect schedules in one place — so the category and coverage question has an answer.
- Upload and organise building documentation
- AI-powered search across all your manuals
- Source-cited answers for every query
- Team collaboration and access control
- No credit card required to start