Fire Alarm Soak Testing and Proving Periods
A fire alarm can pass every commissioning test on the day and still misbehave a week later, when the building is in normal use and a marginal detector meets the steam from a kettle or the draught from a door. A soak test — a proving period during which the system runs and is watched — is how those real-world problems surface before the building fully depends on the system. It is the difference between "it worked when we tested it" and "it has proven itself stable." This guide covers what a soak test is and what to check.
The central point is that a proving period lets a system reveal, in real conditions, problems that a single commissioning test cannot — so they can be fixed before full reliance.
Who this is for
This is for competent fire alarm engineers commissioning and handing over systems. The experience level assumed is competent engineer. Use it for the principles; whether and how a soak period is applied follows the project requirements and good practice within BS 5839-1, tailored to the building. The aim is a system proven stable in use, not merely correct at the instant of commissioning.
What a soak test is
A soak test, or proving period, is a period after commissioning during which the system runs and is observed — before or shortly after handover — to see how it behaves in normal use and to catch problems such as nuisance alarms or intermittent faults that a single commissioning test might not reveal. It gives confidence the system is stable in the real environment, not just under test conditions. Whether and how a soak period is applied follows the project requirements and good practice within BS 5839-1, tailored to the building. The idea is simple: give the system time, in real use, to show what it will actually do.
Why proving stability matters
The value of a proving period comes from the nature of the problems it catches. Some issues only show up over time in real conditions — an occasional false alarm from a marginally-sited detector, or an intermittent fault that a one-off test misses. A proving period lets the system reveal them before it is fully relied upon, and fixing them then is far better, and cheaper, than discovering them once the building depends on the system. It is a way of proving stability, not just confirming correct commissioning at a single moment. Its use follows the project requirements and good practice within BS 5839-1. Time in real conditions is the test that a snapshot cannot replicate.
Soak testing and false alarms
A proving period is closely tied to getting nuisance under control. It can help identify detectors or areas prone to false alarms in the real environment — the kitchen doorway detector, the dusty corner — so their siting, type or configuration can be reviewed before the building relies fully on the system. From field experience, systems that skip any proving and go straight to full reliance are the ones that generate a rash of early false alarms and lose the occupants' trust. It is one tool in reaching a stable, low-nuisance state. Any changes made follow the design and BS 5839-1, aiming for a system both sensitive to fire and settled in normal use.
Checking the proving period
Making a soak period worthwhile means actually acting on what it shows. Review the event log for alarms and faults during the period, investigate any recurring events, confirm the issues found have been resolved, and check the system is stable before full reliance. From field experience, a soak period whose nuisance events are logged but never addressed, or one skipped entirely on a system that then proves troublesome, are the situations to avoid — both waste the opportunity the period offers. Record what the proving period showed, and confirm outstanding issues are closed out before handover is complete, so the system is handed over genuinely proven rather than merely time-served.
Common points to check
Recurring issues include nuisance events during the soak period left unaddressed, a proving period skipped on a marginal system, and instability not resolved before handover. Confirming the system is proven stable and issues are closed out is the essential check.
When not to rely on this alone
When not to use this article: do not treat it as a defined soak procedure for a specific project. That comes from the project requirements and good practice within BS 5839-1, applied by competent professionals.
Relevant standards
Commissioning and proving sit within BS 5839-1, a code of practice, and the project requirements. The legal duty for fire precautions in most non-domestic premises sits under the Regulatory Reform (Fire Safety) Order 2005, with Building Regulations statutory guidance in Approved Document B applying to building work. Separate the legal duty from the recommended methods, and always work to current editions.
Professional disclaimer
This is an educational and workflow resource for competent engineers and does not replace the current British Standards, the project requirements, or competent judgement. Verify soak and proving arrangements against current documentation.
Related documentation
Use this with the current BS 5839-1 and the project requirements. Record what the proving period showed, and confirm outstanding issues are resolved before handover is complete.