Fire Alarm Zone Schedule: What to Include and How to Format It
A zone schedule is one of the most referenced documents you'll hand over after commissioning. Building managers use it to identify which area an alarm is coming from. Engineers use it when testing, modifying, or diagnosing faults. It's also the document an assessor will ask for first when auditing the system.
Despite how fundamental it is, zone schedules are frequently incomplete, out of date, or formatted in a way that makes them hard to use on site.
What a Zone Schedule Is
A fire alarm zone schedule (sometimes called a zone chart or zone list) maps each alarm zone on the panel to the physical area it covers. On an addressable system, it often goes further — listing every device address, device type, and location.
BS 5839-1:2017 requires that the following records be kept at the premises or accessible to those responsible for the system:
- A schematic of the system, showing zones
- A list of devices with their locations
- Operation and maintenance manuals
- Certificates and test records
The zone schedule is the practical working document that satisfies the first two requirements.
What to Include
Minimum fields for a zone-based schedule
| Column | Notes | |---|---| | Zone number | As shown on the panel display | | Zone label | The text label programmed into the panel | | Area covered | Plain-English description (e.g. "Ground floor offices, rooms 101–108") | | Detector types | Heat, smoke, multi-sensor, beam, etc. | | Device count | Number of detectors/MCPs in the zone | | Sounder zones triggered | Which sounder zones activate on alarm in this zone | | Floor/building | For multi-floor or campus sites |
Additional fields for addressable systems
| Column | Notes | |---|---| | Loop number | Which detection loop the zone devices are on | | Address range | e.g. addresses 001–024 | | Device type | Full model reference (e.g. Apollo Discovery Optical Smoke Detector) | | Device address | Individual unit address within the loop | | Physical location | Specific location within the zone (room, corridor, plant room) |
For large sites, it's common to split this into two documents: a zone summary (one row per zone) and a device schedule (one row per device, grouped by zone).
Common Formatting Issues
Zone labels that don't match the panel
The zone schedule says "2nd Floor East Wing" but the panel shows "ZONE 14." When an alarm activates, the person checking the panel can't match the panel display to the paperwork.
Fix: either programme descriptive labels into the panel so they match the schedule, or format the schedule with the panel's zone number prominently alongside the description.
No indication of what devices are in each zone
A zone schedule that says "Ground Floor Reception" with no other detail is only useful for identifying approximate area. When a fault is raised on Zone 3, an engineer on site needs to know whether there are 4 smoke detectors or 40, and where they are, before they start walking.
Fix: include device count and general device positions. For addressable systems, include the full device list.
Out of date after modifications
Zone schedules become stale quickly after system modifications — new zones added, detectors moved, zones renamed. If there's no formal change management process, the paperwork doesn't get updated.
Fix: add a revision table to the zone schedule with version, date, and brief change description. Make updating the zone schedule part of the commissioning sign-off for any modification.
No cause-and-effect reference
For larger systems, engineers and building managers need to know not just which zone has activated, but which sounders, outputs, or interfaces that zone triggers. If the cause-and-effect matrix lives only in the panel configuration software and not in any paper document, someone will face a situation where they don't know whether a silent alarm output has activated during testing.
Fix: include a cause-and-effect column or a separate cause-and-effect matrix alongside the zone schedule.
Zone Schedule Template
Here is a straightforward template structure you can adapt:
Site: [Site name and address] Panel manufacturer and model: [e.g. Notifier ID3000] Revision: [Rev 1.0 — July 2026] Prepared by: [Company name]
| Zone | Panel label | Area description | Floor | Devices | Sounder zones activated | |---|---|---|---|---|---| | 01 | GRD RECEP | Ground floor reception and lobby | Ground | 4× optical smoke, 1× MCP | All zones | | 02 | GRD OFFI | Ground floor open-plan office | Ground | 8× optical smoke, 2× heat, 3× MCP | All zones | | 03 | GRD PLANT | Ground floor plant room | Ground | 2× heat detector | Zone 03 only (staff alert) | | 04 | 1ST OFFI | First floor open-plan office | First | 10× optical smoke, 2× MCP | All zones | | ... | | | | | |
Device Schedule (Addressable Systems)
For addressable systems, a separate device schedule referenced from the zone schedule is best practice:
| Zone | Loop | Address | Device type | Location | Notes | |---|---|---|---|---|---| | 01 | 1 | 001 | Optical smoke | Reception ceiling, above main desk | | | 01 | 1 | 002 | Optical smoke | Reception, south corner | | | 01 | 1 | 003 | Optical smoke | Lobby, above entrance doors | | | 01 | 1 | 004 | Optical smoke | Lobby, above lift doors | | | 01 | 1 | 005 | MCP | Reception desk | Red break-glass | | ... | | | | | |
Keeping It Current
A zone schedule is only useful if it reflects the current state of the system. Practical steps to keep it current:
At commissioning: Complete the zone schedule before sign-off. It should be part of the handover documentation package alongside the commissioning certificate (Form CP-01 per BS 5839-1 Annex L).
After modifications: Any change to the system — added zones, renamed zones, moved devices — should trigger an update to the schedule. The modification commissioning certificate (Form CP-02) should note that the zone schedule has been updated.
Annual service: Check the panel configuration against the zone schedule. Even if no formal modification has been done, it's common for devices to have been swapped by other parties or for panel labels to have been changed without paperwork being updated.
Digital vs Paper
Keeping the zone schedule as a PDF in a site file and a digital copy accessible to the fire alarm monitoring company and the responsible person gives the best coverage. For sites using a digital logbook system, the zone schedule and device list should be part of the system record — not a separate document that lives only in someone's email.
For large or multi-site organisations, the zone schedule feeds into the broader fire safety record required under the Regulatory Reform (Fire Safety) Order 2005 — which requires the responsible person to keep records of the fire safety arrangements and make them available to enforcement officers.