Good fire alarm maintenance combines simple checks by the building’s own staff with periodic inspection, testing and servicing by a competent contractor. Under BS 5839-1, staff check the panel daily and test a different manual call point every week, while a contractor services the system about every six months and verifies every detector, call point and sounder over each twelve months. NFPA 72 sets component-by-component frequencies in its Chapter 14, with most initiating devices and notification appliances tested annually. Every test, fault and false alarm should be recorded in a logbook.
This checklist sets out what fire alarm maintenance should include, which standard the intervals come from, and what to check in a maintenance contract. It is a practical summary, not a substitute for the standards themselves or your local authority’s requirements.
Which standard applies in Pakistan
The Building Code of Pakistan (Fire Safety Provisions 2016) refers to NFPA 72, the National Fire Alarm and Signaling Code, for fire alarm systems, so NFPA 72 is the natural starting point. Many consultants also specify systems to BS 5839-1, the British code of practice for fire detection and alarm systems in non-domestic premises. As a rule, maintain a system to the standard it was designed and certified to, and to any additional requirement of the Authority Having Jurisdiction or your insurer. Our guide to fire alarm requirements in the Building Code of Pakistan explains the code in more detail.
Check editions too. NFPA 72 is revised regularly and section numbers move between editions. BS 5839-1 was revised in 2025 and now recommends service visits at intervals of approximately six months, allowing a visit anywhere between five and seven months after the previous one, where the 2017 edition said the interval should not exceed six months.
Fire alarm maintenance checklist by frequency
| Frequency | Task | Who | Basis |
|---|---|---|---|
| Daily | Check the control panel shows normal operation and no faults; report any fault promptly | Premises staff | BS 5839-1 user guidance |
| Weekly | Operate a different manual call point, in working hours, at about the same time each week; confirm sounders operate; record the call point used | Premises staff or contractor | BS 5839-1 |
| Monthly | Repeat the test for staff who work outside normal hours, where relevant; run any automatically started standby generator serving the system on load | Premises staff | BS 5839-1 |
| About every six months | Inspection and service by a competent person: panel, power supplies, batteries, fault history, signalling to any monitoring centre, a share of device testing | Contractor | BS 5839-1 |
| Semiannually | Test waterflow and valve tamper switches on sprinkler systems that report to the fire alarm; certain battery tests depending on type | Contractor | NFPA 72 |
| Annually | Functional test of smoke and heat detectors, manual call points and notification appliances; control unit functions; cause-and-effect and interface checks | Contractor | NFPA 72; BS 5839-1 requires every device verified over twelve months |
| Within one year of installation, then every alternate year | Smoke detector sensitivity testing, which may be extended to up to five years once consecutive tests show detectors within their listed range | Contractor | NFPA 72 |
Under BS 5839-1 the device testing does not have to happen in a single annual visit; the work can be spread across the service visits as long as every call point, detector and sounder is checked within each twelve-month period.
Weekly and monthly tests: what good practice looks like
- Tell occupants a test is about to happen, and if the system signals to an alarm receiving centre or monitoring station, inform them before the test and confirm the signal afterwards.
- Use a different call point each week, working through the building in rotation. Pressing the panel’s evacuate button does not count as the weekly test.
- Keep the alarm sounding briefly: BS 5839-1 user guidance says at least five seconds and not normally more than sixty.
- Record the date, time, call point and result in the logbook.
What a service visit should cover
A periodic service is more than pressing a few detectors. A competent technician should:
- Review the logbook and the false alarm and fault history since the last visit.
- Inspect the control panel, check indicators, fuses and the time clock, and confirm fault and disablement status.
- Check mains and standby power supplies, including battery condition, charger operation and battery age.
- Functionally test the agreed share of detectors, call points, sounders and visual alarms, using the correct test equipment for each detector type.
- Confirm that each signal to the monitoring centre arrives correctly.
- Check that changes to the building, such as new partitions, false ceilings or a change of use, have not left areas without cover or blocked detectors and call points.
- Record everything, issue a service certificate or report, and list any defects with recommendations.
Batteries
Standby batteries keep the system working during a mains failure, and sealed lead-acid batteries have a finite life. NFPA 72 sets battery inspection and test intervals by battery type, and batteries should be replaced before they can no longer support the system for its required standby and alarm period. Mark the installation date on each battery and plan replacement rather than waiting for a fault.
Detector cleaning and replacement
Dust, insects and humidity contaminate smoke detectors over time, making them either too sensitive, which causes false alarms, or not sensitive enough. Sensitivity testing identifies detectors that have drifted outside their range; these should be cleaned or replaced according to the manufacturer’s instructions. Many manufacturers also state a service life for detectors, which should be reflected in your replacement plan. Cover detectors during building work and uncover them afterwards.
Cause-and-effect testing
A fire alarm rarely works alone. On alarm it may recall lifts, shut down air handling units, operate smoke dampers and extract fans, release access-controlled doors on escape routes, start voice evacuation and signal a monitoring centre. Failures often hide here: a detector can work perfectly while the relay to the AHU panel was disconnected during a renovation.
BS 5839-1:2025 recommends that a cause-and-effect matrix or description is supplied with the system documentation. Use it as the test script: at least once a year, operate devices in each zone and confirm every expected output, including lift homing, AHU shutdown and door release. Coordinate with the lift, HVAC and security contractors so the test is witnessed and the results recorded. If your building has integrated fire and life safety systems, the test should cover each of them.
Logbook and records
The logbook is the system’s history and the first thing an inspector, insurer or new contractor will ask for. It should record weekly tests, faults, false alarms with their cause, disablements, service visits and work carried out, and, under BS 5839-1:2025, any agreed variations from the standard. NFPA 72 requires inspection and test records to be kept at least until the next test of the same kind and for one year after it. Keep drawings, the cause-and-effect matrix and commissioning certificates with the logbook, and keep them up to date when the system changes.
False alarm management
Frequent false alarms train occupants to ignore the real one. BS 5839-1:2025 recommends that every false alarm is investigated and categorised, and that the false alarm rate is calculated at each service visit. It recommends a preliminary investigation when the rate over the previous twelve months exceeds four false alarms per 100 detectors per year, and an in-depth investigation for systems with more than 40 automatic detectors when the rate exceeds five per 100 detectors per year. Common causes include cooking fumes, steam, dust, insects, building work and the wrong detector type for the area; multi-sensor detectors are often the better choice where ordinary smoke detectors keep false alarming.
The 2025 revision also treats updating the panel firmware as a modification that needs a certificate, recommends safeguards for remote access to networked panels, and says fault indications should not be concealed when a repair cannot be completed.
What an AMC should include
An annual maintenance contract turns these tasks into an enforceable scope. Before signing, ask the contractor:
- Which standard and edition will the system be maintained to?
- How many visits a year, and which devices are tested at each, so that every device is covered within twelve months?
- Is detector sensitivity testing included, and with what equipment?
- Is cause-and-effect testing with lifts, HVAC and access control included, and who coordinates the other trades?
- What are the emergency response and repair times, including nights and weekends?
- Are batteries, detectors and other parts included, or charged separately?
- Are technicians trained on your specific panel, and does the contractor hold its software and spares?
- What report and certificate will you receive after each visit?
Our security system AMC checklist covers contract terms in more detail, and the difference between conventional and addressable fire alarm systems affects how testing is done and recorded.
Frequently asked questions
How often should a fire alarm system be serviced?
Under BS 5839-1, a competent person should inspect and service the system at intervals of approximately six months; the 2025 edition accepts a visit between five and seven months after the previous one. NFPA 72 sets separate frequencies for each component, with most detectors, call points and sounders tested annually.
How often should fire alarm call points be tested?
BS 5839-1 recommends a weekly test in which a different manual call point is operated each week, in rotation, and the result recorded in the logbook. NFPA 72 lists manual fire alarm boxes among the devices given an annual functional test by the service provider.
Who is responsible for fire alarm maintenance?
The building owner or occupier is responsible for making sure the system is maintained. In practice, premises staff carry out daily checks and weekly tests, and a competent contractor carries out periodic servicing and testing under a maintenance contract.
How long should fire alarm records be kept?
NFPA 72 requires inspection and test records to be kept at least until the next test of the same kind and for one year after that. BS 5839-1 expects a logbook recording tests, faults, false alarms and service visits. Many owners keep records for the life of the system.
What should we do about repeated false alarms?
Record and investigate each one, identify the cause and the detector involved, and ask your contractor to review the detector type, location and sensitivity. Persistent problems often come from cooking fumes, steam, dust or building work, and may need a different detector or a change in how the area is used.
Resco designs, installs and maintains fire alarm systems across Pakistan, with 24/7 support from our offices in Karachi, Lahore and Islamabad. Our maintenance and support team can survey your existing system and propose a testing programme. Request a proposal to get started.
