Running a fire alarm maintenance contract on a single site is a diary entry. Running them across 50 or more sites is a logistics problem, and the consequences of getting it wrong are not a missed MOT reminder.
When the fire authority investigates after an incident, they examine whether the system was maintained according to BS 5839-1. They look at dates, zone test rotations, and whether the detector sample cycle was completed. If your records show gaps, the question of liability gets uncomfortable very quickly.
This article covers how to build a scheduling structure that holds up to that scrutiny, whether you're managing 15 sites or 150.
The scheduling obligation under BS 5839-1
Before setting up any scheduling system, it helps to be precise about what you're scheduling.
For most commercial and industrial premises, BS 5839-1 Section 45 requires a minimum of two contractor visits per year. However, the standard's requirements don't reduce neatly to "two visits", the scope of each visit is defined by what's due, not just by the fact of showing up.
The quarterly contractor visit scope (applicable to higher-risk premises and often written into contracts as standard) includes:
- Testing a 25% sample of automatic detectors, rotating through the full inventory over four quarters
- Testing all manual call points
- Testing all sounders and visual alarms
- Inspecting cabling and containment for physical damage
- Verifying cause-and-effect against as-installed drawings
The annual visit adds the load test of the standby battery (72-hour supply confirmation per Clause 25.2), full cause-and-effect matrix verification, and ARC signalling confirmation.
If your scheduling system doesn't track which detectors were tested on which quarter, you cannot demonstrate compliance with the 25%-per-quarter rotation requirement. That's not an administrative nicety, it's the central evidence requirement.
Why the 25%-per-quarter rotation creates a scheduling problem
Most fire alarm panels on commercial sites contain between 20 and 200 detectors. On a small office building, 25% is five devices. On a hospital wing or a warehouse, it might be 50.
The rotation requirement means your engineer on the Q1 visit must know:
- Which detectors were tested at Q3 and Q4 of the previous year
- Which detectors form the Q1 sample for this year
- Whether any detectors were missed in a previous quarter (requiring catch-up)
On a single site, a paper log or a spreadsheet column works. Across 50 sites, the same approach produces a maintenance manager who spends more time auditing their own records than managing the work.
The failure mode is predictable: engineers default to testing the same accessible detectors every visit because there's no list telling them which 25% is due. The panel looks fine. The log records a visit. But the full detector inventory hasn't been exercised in two years.
Zone test cycling across multiple sites
Weekly zone tests are the responsibility of the site's designated responsible person under BS 5839-1, not the maintenance contractor. But contractors inherit the gap risk when a responsible person leaves, a new tenant takes over, or the site's logbook goes missing.
As a multi-site contractor, your quarterly visit is typically the point where you verify whether weekly tests have been happening, and whether they've been rotating through zones correctly.
The cycling requirement is explicit in the standard: every manual call point and every zone must be exercised at intervals that allow detection of any systematic failure. An inspector reviewing a logbook where Zone 1 was tested 52 times in a year while Zone 5 shows no tests will draw the obvious conclusion.
When you manage zone test verification across a portfolio, the practical question is: how do you know the responsible person at Site 32 has been rotating correctly? Without a system that records which zone was tested when, you can't answer that question until you're on site, reviewing a paper logbook that may or may not be complete.
Building a multi-site inspection schedule that holds up
A workable multi-site fire alarm schedule has four components.
1. Site register with system inventory
Every site needs a record of: the panel type and address count, the total detector count by type (optical, heat, beam, aspirating), the zone layout, and the contract type (bi-annual or quarterly). This is the base data your scheduling depends on. Without an accurate detector count, you can't calculate what 25% means for that site.
2. Detector rotation tracking at asset level
Each detector, not each visit, needs its own test record. That record should show: the date of last test, which visit it was attributed to (Q1, Q2, etc.), the sensitivity reading if it's an analogue-addressable system, and whether the device passed or was flagged for follow-up.
When a follow-up visit happens, it needs to be linked back to the original defect record, not treated as a new entry.
3. Visit scheduling by due date, not calendar slot
The common mistake is scheduling visits by month: "Site A gets a visit in March and September." The problem arises when a March visit slips to April, then the September visit stays in September, the Q2 detector sample never happened, Q3 runs on schedule, and you've completed three out of four rotation quarters with a gap that the records can't explain.
Scheduling by due date means the system calculates when each site's next visit is due based on the last visit date, not the calendar target. A March visit that happened in April generates an August due date, not a September one.
4. Overdue flagging before the visit, not after
A reactive approach, discovering overdue inspections during an audit or after a client complaint, is operationally expensive. Each overdue site requires a priority visit, which disrupts the existing schedule and costs more than a planned visit.
Flagging overdue inspections 4-6 weeks before they become overdue gives the scheduler time to arrange a visit in the normal run of work. The flag needs to be visible across the whole portfolio, not buried in a site-specific spreadsheet tab.
Managing contract scope variations across your portfolio
No two fire alarm maintenance contracts are identical, and that variation creates scheduling complexity that a calendar alone can't handle.
A 200-site portfolio might include:
- 60 sites on bi-annual contracts (Category L1 systems, commercial offices)
- 40 sites on quarterly contracts (sleeping risk premises, hospitals, care homes)
- 15 sites requiring monthly contractor visits (high-risk industrial, heritage buildings)
- Sites under BS 5839-6 for residential blocks with different maintenance obligations for common areas vs individual dwellings
Each variation means a different visit frequency, a different scope checklist, and different documentation requirements. A scheduling system that treats all contracts identically will either over-service low-risk sites (unnecessary cost) or under-service high-risk sites (compliance failure).
When scheduling at portfolio level, the contract scope needs to drive the visit frequency, not the other way around.
The defect backlog problem at scale
Single-site contractors close defects quickly because the responsible person is usually in regular contact. Multi-site contractors accumulate defect backlogs because:
- Defects are logged on paper during the visit
- The engineer returns to the office, the report is filed
- The follow-up visit is scheduled separately
- The link between the original defect and the follow-up is broken
BS 5839-1 Clause 45.2 requires written notification to the responsible person for any defect that impairs system performance. That notification is your legal protection as well as the client's right.
At 50 sites, a defect backlog of 20-30 open items is normal if there's no system tracking them. The problem isn't that defects occur, it's that open defects without tracked follow-up expose you to liability. If a system with an unresolved defect fails during a fire, and your records show the defect was raised but never closed, the question of whether the system was in a fit state is already answered against you.
What digital scheduling changes in practice
Paper-based scheduling creates a specific failure mode: the gap you don't know about. Digital scheduling creates a different default state, the gap that shows up as a warning before it becomes a compliance failure.
The practical difference for a multi-site fire alarm contractor:
Detector rotation: Instead of an engineer arriving on site and deciding which detectors to test, the system presents the Q2 detector list for that site, pre-populated from the asset register and the previous visit records. The engineer works through the list. Any detector not tested during the visit is flagged as outstanding.
Zone verification: The responsible person's weekly test log is visible before the contractor visit. If Zone 3 hasn't been tested in six weeks, the engineer knows before opening the panel.
Overdue portfolio view: The scheduling dashboard shows every site with a visit due in the next 30 days, every site overdue, and every site with an open defect. The maintenance manager sees the full picture without opening 50 site folders.
Automatic defect notifications: When an engineer logs a defect, a heat detector reading 78°C threshold instead of the expected 58°C, or a sounder measuring 62 dB when the minimum is 65 dB, the responsible person receives a written notification automatically. The defect stays open in the system until a follow-up visit closes it.
RemoteOps structures fire alarm assets by site and panel: each detector is a tracked device, each visit generates a record against those devices, and the quarterly rotation is calculated automatically from the asset register. A maintenance manager overseeing a 60-site portfolio can see which sites have rotation gaps without pulling individual visit reports.
Frequently asked questions
How many detectors should be tested on each quarterly visit?
BS 5839-1 recommends testing approximately 25% of automatic detectors per quarter, completing the full inventory over 12 months. For a panel with 80 detectors, that's 20 per quarterly visit. The rotation should be documented at device level so any audit can confirm the full set was exercised within the year.
What happens if a quarterly visit is delayed and the detector rotation falls behind?
The gap needs to be made up in the following visit. If Q2 was missed, the Q3 visit should cover the Q2 and Q3 samples. This increases the on-site time for that visit and must be reflected in the visit report. Gaps that are not documented and made up represent a compliance shortfall that an auditor will identify.
Does the zone test rotation apply to contractor visits or to the responsible person's weekly tests?
Both. The responsible person's weekly tests must cycle through all zones and all manual call points over time, not test the same zone every week. The contractor verifies this during scheduled visits by reviewing the site logbook. If the rotation is not evidenced, the contractor should advise the responsible person in writing and note the omission in the service record.
How should defects found during a quarterly visit be tracked?
Each defect must be written in the service record and notified in writing to the responsible person before the engineer leaves site. The defect should be classified by severity: whether the system remains fully functional, partially impaired, or unable to fulfil its intended purpose. A follow-up visit or contractor-issued remedial recommendation should be agreed at the time of notification, not left open-ended.
What documentation should a multi-site contractor keep at company level vs at site level?
BS 5839-1 Clause 45.1 requires the site log book to be kept at the protected premises. The contractor should keep copies of all service records, defect notifications, and certificates in their own management system. The two records should agree, if the site log shows a visit that's not in your company records, or vice versa, that discrepancy needs explaining.