Skip to main content
Back to blog
Commissioning4 min read

Cause and Effect in Fire Alarm Systems

What a fire alarm cause and effect matrix is, why it matters and how it is used in design, commissioning and testing — for UK fire alarm engineers and duty-holders.

By Incognito Fire & Security · 14 August 2026

Editorially reviewedVersion 1medium confidence

Last updated 14 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

Cause and Effect in Fire Alarm Systems

When a detector operates, what should happen next? On a small system the answer might be "everything sounds", but on anything more complex — phased evacuation, plant shutdown, door release, links to other systems — the answer needs to be written down precisely, and that document is the cause and effect. It is one of the most important pieces of paper in a fire alarm project, because it turns the building's fire strategy into an exact, testable description of how the system must behave. This guide explains what it is and how it is used.

The central point is that a cause and effect matrix defines each input (cause) against each required output (effect), turning the fire strategy into a specification the system can be programmed to and tested against.

Who this is for

This is for fire alarm engineers involved in design, commissioning or testing, and for responsible persons who want to understand how their system's behaviour is defined. The experience level assumed is a competent engineer or an informed duty-holder. It explains the purpose and use of cause and effect; the detailed requirements for design, commissioning and documentation sit within the current BS 5839-1 and the building's fire strategy, applied by competent professionals.

What cause and effect means

A cause and effect matrix is a grid that pairs inputs with outputs. Down one side are the causes — the things that can happen, such as a detector or call point operating in a particular zone or area, or a specific fault condition. Across the other are the effects — what the system should do in response, such as sounding alarms in defined areas, releasing held-open doors, operating or shutting down plant, or signalling to an alarm receiving centre. Filling in the grid states, unambiguously, which effects each cause should produce. That explicitness is the whole value: behaviour that would otherwise be assumed becomes something you can programme, check and prove.

From fire strategy to matrix

The matrix does not appear from nowhere; it is derived from the building's fire strategy and system design. The fire strategy sets out how the building is intended to respond to a fire — how people are warned and evacuated, how compartmentation and plant behave — and the cause and effect translates that intent into specific system inputs and outputs. This is why it is produced by competent designers in consultation with the relevant stakeholders rather than left to the installer's default settings. A phased evacuation, for instance, only works if the matrix defines exactly which areas sound and when, in line with the strategy.

Using it in commissioning and testing

Once agreed, the matrix drives two practical activities. In commissioning, the engineer configures the system so that each cause produces the defined effects, using the matrix as the specification. In testing, each cause is triggered in turn and the engineer confirms that the correct effects — and only those effects — occur, working through the matrix systematically. From field experience, this is where errors surface: an output mapped to the wrong zone, an effect missing, or an unintended action. Recording the results against the matrix means any deviation is caught and corrected before the system is relied upon, and gives a clear record that the system behaves as the strategy requires.

Keeping it current

A cause and effect is only useful while it reflects the building. When the system is extended, the layout changes, or the use of the premises changes, the matrix must be reviewed and updated, and the system re-tested against the new version. Kept with the system records alongside the design and certification, it supports the general duty to maintain appropriate fire precautions under the Regulatory Reform (Fire Safety) Order 2005 by ensuring the system's behaviour remains defined and verifiable throughout its life, not just on the day it was commissioned.

When not to rely on this alone

When not to use this article: do not use it to write or modify a specific cause and effect. That must be derived from the building's fire strategy and design by competent professionals, in line with the current BS 5839-1. This guide explains the concept and its use, not the content of any particular matrix.

Professional disclaimer

This is an educational resource for competent engineers and informed duty-holders. It does not replace the current British Standards, the building's fire strategy or professional judgement. Confirm cause and effect requirements against the current BS 5839-1 and the fire strategy for the building.

Related documentation

Use this with the current BS 5839-1 and the building's fire strategy. Define each cause against its required effects, commission to the matrix, and test against it systematically.

Frequently asked questions

What is a cause and effect matrix in a fire alarm system?

A cause and effect matrix is a document that defines what the fire alarm system should do when something happens. Each 'cause' is an input — for example a detector or call point operating in a particular zone — and each 'effect' is an output the system should produce, such as sounding alarms in defined areas, releasing door holders, signalling to a remote centre or operating plant. Setting the causes against the effects in a grid makes the intended behaviour explicit so it can be programmed, checked and tested.

Why is cause and effect important?

It turns the fire strategy for the building into a precise, testable specification of system behaviour. Without it, the way a panel responds to an event can be assumed rather than defined, which risks the system doing the wrong thing — or nothing — when it matters. A clear cause and effect matrix lets the designer, installer, commissioning engineer and responsible person all agree on and verify exactly how the system should behave.

Who produces the cause and effect?

The cause and effect is derived from the building's fire strategy and system design by competent designers, in consultation with the relevant stakeholders. It is then used by the commissioning engineer to configure the system and by everyone testing it to confirm the system behaves as intended. It should be documented, agreed and kept with the system records, and updated whenever the system or the building's use changes.

How is cause and effect tested?

Cause and effect is verified during commissioning and at subsequent tests by triggering each defined cause and confirming that the correct effects — and only those effects — occur. Working through the matrix systematically confirms the programming matches the intended behaviour. The tests and results should be recorded against the matrix so any deviation is identified and corrected before the system is relied upon.

Related tools and references