> For the complete documentation index, see [llms.txt](https://docs.riskbase.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riskbase.uk/fire-strategy/the-riskbase-fire-strategy.md). # The RiskBase Fire Strategy The RiskBase Fire Strategy is a **workflow-based product, underpinned by a benchmark library and structured building data**. Rather than starting with opinion, every strategy is built on the data RiskBase already holds about the building — captured through building-level fields, asset records, and prior surveys — and anchored to a recognised benchmark. This page describes how the RiskBase Fire Strategy is structured: the philosophy, the workflow stages, the section framework, the lifecycle, and how the produced document is reused across the platform. For background on Fire Strategies in general, see *What is a Fire Strategy*. For step-by-step instructions on producing one, see *How To: Completing a Fire Strategy*. *** ## The data-first philosophy A traditional Fire Strategy is often produced as a standalone document, with the building described from scratch each time. This duplicates work, drifts over time, and disconnects the strategy from the operational risk assessments that follow. The RiskBase approach inverts that. The building exists in RiskBase as a structured record — fields, assets, photographs, prior survey findings. A Fire Strategy is produced *from* that record. The strategy and the operational risk work share a single source of truth, so each subsequent assessment starts from the same description of the building rather than re-describing it. *** ## The three-stage workflow The Fire Strategy is organised around three stages, each answering a different question: **1. What should be there.** The strategy is anchored to a recognised benchmark. The engineer selects the relevant Purpose Group, Building Height band, and ADB edition or amendment; BS 9991, BS 9999, or CP3 can be added instead of, or alongside, ADB. RiskBase retrieves the corresponding benchmark commentary and inserts it into each section of the strategy. **2. What is there.** The strategy describes the building as it actually exists — overall layout, means of escape, detection and alarm, smoke control, firefighting facilities, plus linked asset data (flats, fire doors, compartmentation, fire stopping, equipment). This information comes from a site survey or from data already captured in RiskBase from prior assessments. **3. Is it adequate.** For each section of the strategy, the engineer writes a professional judgement that compares what should be there against what is there. Where shortfalls exist, they are either justified by a fire engineering rationale or raised as remedial actions. *** ## Section framework Regardless of which benchmark is selected, the strategy is organised around the standard fire safety framework: * **B1** — Means of warning and escape * **B2** — Internal fire spread (linings) * **B3** — Internal fire spread (structure) * **B4** — External fire spread * **B5** — Access and facilities for the fire service The exact section numbering depends on the template selected: * **Non-residential templates** use the top-level structure — B1, B2, B3, B4, B5. * **Residential templates** break each requirement into numbered sub-sections — B1.1, B1.2, B1.3, … through to B5.x — to reflect the greater granularity of residential fire safety guidance. For each section, or sub-section, three blocks appear: 1. "Benchmark Guidance" — auto-populated from Stage 1. 2. "What Is Provided" — pulled from Stage 2. 3. "Professional Judgement" — written by the engineer. Images can be uploaded into the judgement block to support fire engineering solutions, illustrate mitigations, or evidence the conclusion reached. *** ## The benchmark library The RiskBase benchmark library currently covers Approved Document B across multiple editions and amendments, and is being extended to BS 9991, BS 9999, CP3, and other recognised guidance. **Multiple benchmarks can be applied simultaneously.** For example, a residential building can be assessed against ADB and BS 9991 in parallel, with both sets of benchmark commentary surfaced in each section so the engineer can compare provisions against each. If the benchmark library does not yet hold a required document, it can be added on request — contact the RiskBase team. *** ## Plans section The "Plans" section appears at the end of the strategy. It is generated automatically from the property's floor plans and shows **all assets that were pinned on** — fire doors, fire stopping, equipment, and any other fire safety features captured during surveys. An accompanying legend identifies each pinned feature. The result mirrors a Secure Information Box (SIB)-style document, providing a clear visual reference alongside the written strategy. *** ## Executive Summary The "Executive Summary" sits at the top of the strategy but is written last, after all sections are complete. It is a high-level narrative reflecting on the overall findings, the adequacy of the building's fire safety approach, and any key risks, limitations, or considerations. *** ## Remedial actions and action plans As with a Fire Risk Assessment (FRA), the RiskBase Fire Strategy allows the engineer to **raise remedial actions** against any finding and **generate an action plan** from the identified gaps. Once raised, these actions are available for clients to manage in the RiskBase "Task Management" interface, alongside all other action types — FRA actions, door survey actions, compartmentation actions, and so on. This turns the Fire Strategy from a static report into a structured basis for ongoing fire safety management. *** ## Lifecycle and approval RiskBase strategies use a three-step lifecycle: *In Progress*, *Submitted*, and *Approved*. Once the engineer is satisfied with the strategy, it is submitted for approval and awaits validation by the Approver within the organisation. Once approved, the strategy is finalised and forms part of the building's fire safety record. *** ## After approval: data reuse The Fire Strategy is not a dead end. The data captured during its production — building information, asset records, surveyed findings, raised actions — remains available throughout RiskBase: * It can be **included in other assessments**, so subsequent FRAs, door surveys, compartmentation surveys, and inspections start from the same source of truth rather than re-describing the building. * It can be **surfaced on the web portal,** [**Engage.RiskBase**](https://engage.riskbase.app/), where clients, responsible persons, and other stakeholders can access the building's fire safety information directly. This is the practical pay-off of the data-first approach: a single building model that strengthens every assessment built on top of it. For background on Fire Strategies in general, see *What is a Fire Strategy*. For step-by-step instructions on producing one in the app, see *How To: Completing a Fire Strategy*. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.riskbase.uk/fire-strategy/the-riskbase-fire-strategy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.