Coincidence and Double-Knock Detection Explained
Coincidence detection — commonly called double-knock — is a useful tool for reducing false alarms and for confirming a fire before firing high-consequence outputs. It is also one of the easier tools to misuse, because anything that makes the system wait for a second confirmation can, if applied wrongly, delay the response to a real fire. This guide sets out what coincidence detection is, where it belongs, and the firm limits that keep it safe.
The theme throughout is that double-knock trades a small confirmation delay for fewer false alarms, and that trade is only acceptable where the fire strategy allows it.
Who this is for
This is for competent fire alarm engineers who configure or maintain coincidence detection. The experience level assumed is competent engineer. Use it for the principles; whether and how to apply double-knock comes from the fire risk assessment, the fire strategy, BS 5839-1 and the cause and effect.
What coincidence detection is
Coincidence detection requires two separate detector operations before a defined action occurs, rather than acting on the first detector alone. That action might be the full evacuation signal, or a specific output such as releasing suppression. It is configured in the cause and effect within the panel and is a recognised technique for reducing unwanted alarms and for confirming fire before high-consequence actuation, applied within BS 5839-1. The essential idea is confirmation: the system waits for corroboration before committing to the defined response.
When it is appropriate
Double-knock is appropriate where a single detector operation has a meaningful chance of being a false alarm and a short confirmation delay is acceptable, or where an output should only ever fire on a confirmed fire. It is a targeted measure for specific areas or outputs, decided by the fire risk assessment and the fire strategy against BS 5839-1. It is not a general default and should never be applied blanket-fashion across a system simply because false alarms are a nuisance.
The life-safety limit
Here is the limit that must never be crossed: coincidence detection must not delay warning to occupants beyond what the fire strategy permits. Requiring two operations inherently slows the response, so where it is used for the alarm signal it is typically bounded — for example with a time limit after which a single detector escalates, and with clear rules about which areas may use it. From field experience, the dangerous misuse is applying double-knock to mask a system that is generating false alarms for reasons that should instead be fixed at source.
Verifying the logic
Because coincidence logic lives in the cause and effect, it must be verified against the documentation, not assumed. Confirm the panel's configuration matches the documented cause and effect, that any time limits and single-detector fallbacks work, and that it has not crept into areas where it would unacceptably delay warning. Re-test after any cause-and-effect change, and record what is configured and the justification for it so the arrangement can be defended.
Common points to check
Recurring issues include double-knock applied to areas where it delays warning unacceptably, missing time limits or single-detector fallbacks, and coincidence logic used to hide a false-alarm problem that should be solved at source. Confirming the logic matches an appropriate, documented cause and effect is the key check.
When not to rely on this alone
When not to use this article: do not use it to decide where coincidence detection should be applied on a specific system. That comes from the fire risk assessment, the fire strategy and BS 5839-1, applied by competent professionals.
Relevant standards
Coincidence detection is addressed within BS 5839-1, a code of practice, within the building's fire strategy and cause and effect; suppression actuation additionally follows the relevant release standards. The legal duty for fire precautions 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 fire strategy, the cause and effect, or competent judgement. Verify coincidence arrangements against current documentation.
Related documentation
Use this with the current BS 5839-1, the fire risk assessment and fire strategy, and the system cause and effect. Record coincidence configuration and its justification, and re-prove it after any change.