BS 8644-1’s 2024 amendment lands at a time when UK projects are being asked to prove – not just promise – that fire safety information is complete, consistent and traceable from design through to operation. It pushes the industry further towards structured, machine-readable records, linked to assets and accessible in a Common Data Environment, aligning with the “golden thread” expectations now embedded in client briefs and regulatory culture. For site teams, it means less tolerance for vague O&M bundles and more focus on standardised data, verified products, and clean handover packages that a building safety manager can actually use.
TL;DR
/>
– The 2024 amendment tightens expectations for structured, digital fire safety information aligned to the golden thread.
– Success depends on early information requirements, a configured CDE, consistent classification, and verifiable product data.
– Principal Contractor and Principal Designer need a joined-up plan for capture, assurance and change control across trades.
– Aim for model-linked schedules, barcode/QR tagging of key fire assets, and approvals workflows that leave an audit trail.
– Watch file conventions, version control, and late design changes; they break traceability and can stall completion.
Market change: what the 2024 amendment signals
/> The amendment is widely read as a nudge from documents to data. It points towards structured information sets for fire safety – not only drawings and reports, but attributes you can filter, query and carry into operation. That covers items like fire doorsets, dampers, cavity barriers, service penetrations, fire stopping systems, and alarms, all with provenance, approvals, and installation evidence.
In practice, this reinforces three things. First, declare fire information needs upfront at tender stage, so bidders price the workflows and tech, not just the product. Second, classify and containerise data so anyone can find it in the CDE and trust its status. Third, treat changes as data events: if a route, product or detail changes, the fire strategy, model, schedules and certificates must move together.
Clients are starting to specify IFC and COBie extracts, Uniclass classification, and naming conventions that match BS 8644-1’s spirit. Insurers and funders are asking whether fire data is accessible, consistent and assured. The Building Safety Regulator’s culture is also driving rigour, particularly on higher-risk buildings, but the direction of travel is bleeding across commercial, education and healthcare programmes too.
Operational reality on site: where this lands
/> On site, the shift is less about fancy apps and more about joined-up basics. The Principal Contractor’s quality plan needs to map each fire-critical element to a capture method (photo, test cert, installer record), a data schema (fields, classification, status), and an approvals route. Subcontractors need induction on data expectations as much as on RAMS. The fire engineer and Principal Designer should be part of a live change process, not a periodic reviewer of as-builts.
A very UK scenario: A design-and-build residential block in the Midlands is racing towards a phased handover. A late services coordination change pushes a riser through a compartment line, forcing a different penetration system and altered damper spec. The drylining contractor installs what they had in stock, the MEP team submit a partial certificate set, and the PC’s document controller tries to compile an O&M section from email trails. The fire engineer flags a mismatch between the recorded product and the approved detail. The client’s building safety lead asks for a clean register of affected assets with installation references and sign-offs. With a configured CDE and model-linked schedule, the PC could have triggered a controlled change, linked to updated details and product data, pushing a single source of truth to trades. Instead, the team burns a week reconciling model, drawings and product sheets, and completions slip.
What good looks like under BS 8644-1
/> You don’t need a perfect BIM utopia; you do need repeatable patterns. Start with clear Fire Information Requirements that identify the who, what, when and format for design, construction and in-use phases. Make sure the CDE has containers, metadata and status codes that separate “for construction”, “as installed”, and “accepted for handover”. Use classification consistently. Push structured asset data from models and schedules into something your client can maintain. And give trades a simple, guided way to capture evidence at the point of work.
– Define Fire Information Requirements at RIBA Stage 3–4: assets in scope, data fields, file types, naming, approval status, and handover deliverables.
– Configure the CDE with fire-specific containers, approval gates, and a change log that links RFIs, design changes and product swaps.
– Standardise classification (e.g., Uniclass) and assign unique IDs that follow each fire-critical asset from model to field to handover.
– Select capture tools that work offline on site; enforce barcode/QR tags for doors, dampers and penetration systems to tie photos and certs to asset IDs.
– Mandate product data sheets, ETA/BS approvals and installer competence evidence, stored alongside details and test references.
– Generate model-linked schedules (IFC/COBie where required) and reconcile them against field records before each sectional completion.
– Train document controllers and package managers on status codes and change workflows so approvals leave an auditable trail.
# Common mistakes
/>
– Treating the amendment as “BIM admin” rather than updating procurement, programme and QA allowances. That leaves no time or budget for structured capture.
– Letting each trade create its own spreadsheets. You end up reconciling columns, naming and IDs when the pressure is highest.
– Capturing photos without context. Images without asset IDs, location and installer details can’t be trusted or searched later.
– Pushing a model with unverified product proxies into handover. If the installed product differs from the model object, the data misleads the operator.
What to watch next in the UK market
/> Expect closer alignment between project information standards and in-use asset management, with clients asking for data dictionaries that carry into CAFM and safety case files. Manufacturers are improving digital product data and approvals documentation; teams that plug this into the CDE via standard fields will save time. There’s growing interest in digital product passports and QR-linked fire door inspection trails, plus remote monitoring of fire doors and dampers in high-occupancy buildings, though these won’t replace disciplined installation records.
Procurement will shift too. Preliminaries are beginning to define information roles, data deliverables and acceptance criteria with teeth, including staged payments linked to information quality. NEC and JCT amendments in the market often include explicit information obligations and status codes. Teams that actively plan for this, rather than leaving it to the document controller in month 22, are the ones handing over on time.
Three questions for your next project meeting: Have we nailed the fire information fields and IDs we’ll carry from design to operation? Are our change routes linking model, drawings, product data and approvals automatically? Which packages are most at risk of untraceable substitutions, and how are we closing that gap early?
FAQ
# Does BS 8644-1 apply to every project, or only higher-risk buildings?
/> It’s a British Standard, not legislation, but its direction aligns with how clients, insurers and regulators want to see fire safety information handled. Many teams now apply its principles across most building types because the benefits at handover and in operation are clear.
# What file formats should we plan for when digitising fire information?
/> Most clients expect a mix: PDFs for reports and certificates, plus structured data like IFC models and COBie or similar schedules. The key is consistency and traceability—use standard naming, classification and status so the operator can query, filter and maintain the data later.
# How do we deal with subcontractors who aren’t tech-heavy?
/> Keep the workflow simple. Provide standard forms, QR labels and a mobile-friendly capture route with clear prompts for asset ID, location, product reference and installer competence. Induct them on the why, and make information acceptance part of progress valuation.
# Who owns and maintains the fire safety data after handover?
/> Ownership and maintenance responsibilities should be set in appointments and contracts. Typically, the client or building owner becomes the custodian in operation, but the project team must hand over a coherent, validated set that the building safety manager can keep live.
# What’s the best way to manage late design changes that affect fire compartments?
/> Treat changes as data events. Route RFIs and design updates through a workflow that updates the model element, the detail, the product data and the approval status in one place, then notify affected packages. Log the superseded items clearly so auditors can see what changed and why.
