Blame
| 993e57 | R. Bishop | 2025-09-19 19:14:14 | 1 | # Certification (BS 5839-1:2025) |
| 2 | ||||
| 3 | ## Overview |
|||
| 4 | ||||
| 5 | BS 5839-1:2025 requires formal **certification at every stage** of a fire detection and fire alarm system. Certificates provide evidence of compliance with the standard and form part of the legal fire safety documentation under the **Regulatory Reform (Fire Safety) Order 2005** and the **Building Regulations**. |
|||
| 6 | ||||
| 7 | Certificates must be issued by the **organisation responsible for that stage of the work**, signed by a **competent person**. They demonstrate that design, installation, commissioning, acceptance, and any later modifications comply with the standard. |
|||
| 8 | ||||
| 9 | --- |
|||
| 10 | ||||
| 11 | ## Certificate Types and Responsibilities |
|||
| 12 | ||||
| 13 | | Certificate Type | Purpose | Signed By | |
|||
| 14 | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | |
|||
| 15 | | **Design Certificate** | Confirms that the design meets BS 5839-1 (coverage, category, zoning, detector type, audibility, cause & effect). | Competent designer, consultant, or company responsible for the design. | |
|||
| 16 | | **Installation Certificate** | Confirms the system was installed in accordance with the design and BS 5839-1 workmanship standards. | The installing contractor or organisation, signed by an authorised representative. | |
|||
| 17 | | **Commissioning Certificate** | Confirms programming, cause & effect, device testing, battery sizing, and system functionality comply with BS 5839-1. | Competent commissioning organisation/engineer. | |
|||
| 18 | | **Acceptance Certificate** | Confirms handover of the system, documentation, and user training. | The purchaser or **Responsible Person** (not the installer). | |
|||
| 19 | | **Verification Certificate** | Used for independent verification of large or complex systems before handover (Clause 41). | Independent verifier or third-party organisation. | |
|||
| 20 | | **Extensions/Modifications Certificate** | Confirms alterations or extensions to an existing system comply with BS 5839-1 and do not invalidate prior certification. | The organisation responsible for the modification; others (e.g. original designer) sign if their scope is affected. | |
|||
| 21 | ||||
| 22 | --- |
|||
| 23 | ||||
| 24 | ## Modification Certificates |
|||
| 25 | ||||
| 26 | ### When Acceptable |
|||
| 27 | ||||
| 28 | A **Modification Certificate** (Annex G.7) may be issued where: |
|||
| 29 | ||||
| 30 | * The existing system has valid original certification (design, installation, commissioning). |
|||
| 31 | * The works are **alterations or extensions**, not a complete new installation. |
|||
| 32 | * The scope of works is **clearly defined and limited** to the changes made. |
|||
| 33 | * The untouched parts of the system remain compliant. |
|||
| 34 | ||||
| 35 | **Examples:** |
|||
| 36 | ||||
| 37 | * Adding detectors, call points, or sounders to an existing loop. |
|||
| 38 | * Extending coverage into a new building area. |
|||
| 39 | * Replacing a control panel where devices/wiring are retained. |
|||
| 40 | * Changing cause & effect programming (e.g. evacuation delays). |
|||
| 41 | * Converting a conventional zone to addressable detection. |
|||
| 42 | ||||
| 43 | ### When NOT Acceptable |
|||
| 44 | ||||
| 45 | **A Modification Certificate cannot be used where:** |
|||
| 46 | ||||
| 47 | * No original certificates exist. |
|||
| 48 | * The system has been wholly replaced (devices, wiring, or zoning). |
|||
| 49 | * Works are so extensive the system is effectively new. |
|||
| 50 | * Modifications fundamentally alter the design (e.g. re-zoning or changing system category). |
|||
| 51 | ||||
| 52 | --- |
|||
| 53 | ||||
| 54 | ## Key Clauses (BS 5839-1:2025) |
|||
| 55 | ||||
| 56 | * **Clause 38 - Documentation:** Certificates are mandatory for each stage. |
|||
| 57 | * **Clause 39 - Certification:** Each stage must be certified separately, even if the same company performs multiple roles. |
|||
| 58 | * **Clause 40 - Handover:** Certificates form part of the required documentation at handover. |
|||
| 59 | * **Clause 41 - Verification:** Large or complex systems may require independent verification. |
|||
| 60 | * **Clause 45 & 46 - Extensions and Modifications:** Modifications must be certified using the Annex G.7 form; scope and extent of liability must be defined. |
|||
| 61 | * **Annex G - Model Certificates:** Provides templates for design, installation, commissioning, acceptance, verification, servicing, and modifications. |
|||
| 62 | ||||
| 63 | --- |
|||
| 64 | ||||
| 65 | ## Practical Guidance |
|||
| 66 | ||||
| 67 | * Certificates should be **retained in the logbook** for the life of the system (Clause 40, Annex H). |
|||
| 68 | * Always **state the scope of responsibility** clearly (e.g. “Design of extension only”). |
|||
| 69 | * If original certificates are missing, a **Verification Certificate** (Clause 41) may be required before issuing new certificates. |
|||
| 70 | * Certificates can be adapted in format, but must include the **same information and declarations** as Annex G. |
|||
| 71 | * Certificates are signed **on behalf of the responsible organisation**, unlike BS 7671 electrical certs which require individual signatures. |
|||
| 72 | * The **Responsible Person** always signs the **Acceptance Certificate**, not the contractor. |
|||
| 73 | ||||
| 74 | --- |
|||
| 75 | ||||
| 76 | **In summary:** |
|||
| 77 | Certificates under BS 5839-1:2025 provide a complete compliance trail. |
|||
| 78 | ||||
| 79 | * **Design → Installation → Commissioning → Acceptance** cover new systems. |
|||
| 80 | * **Verification** applies to large/complex projects. |
|||
| 81 | * **Modification Certificates** cover alterations or extensions, provided original certification exists and the system is not effectively new. |