Digital fire safety information used to be a jumble of PDFs and handover binders. BS 8644-1 changes the expectation: organise fire-critical data so it is structured, traceable, and useable from design through to operations. For UK teams working under the Building Safety Act environment and the “golden thread” principle, the standard gives a practical way to structure information exchanges, define roles, and avoid gaps between drawings, product selections and what gets installed on site.
TL;DR
/>
– Treat BS 8644-1 as the operating system for the fire information model: define attributes, responsibilities, status codes and acceptance criteria early.
– Run your digital fire information through the project CDE with clear naming, versioning, and location references so evidence is findable at handover.
– Tie product selections and any substitutions to a formal change route that captures performance, approvals and installation evidence.
– Make field capture simple: unique asset IDs, QR tags, photos tied to zones, test results linked to equipment and dates.
– Expect more rigour from clients and regulators: consistent data schemas, auditable change logs, and live records during commissioning.
Core ideas behind BS 8644-1 in plain English
/> At its heart, BS 8644-1 asks teams to manage fire safety information as a living model, not a static file dump. That model brings together geometry (where things are), non-graphical data (what they are and how they perform) and evidence (how they were installed, tested and maintained). It encourages projects to specify information requirements up front: what attributes a fire door, damper, cavity barrier, detector or pump must carry; how locations are referenced (levels, zones, rooms); and how documents are named and approved.
The standard sits comfortably with ISO 19650 methods: a common data environment, clear status codes for WIP, shared and published information, and disciplined version control. Teams typically align classification with a UK scheme like Uniclass so assets can be filtered and scheduled reliably. The Fire Information Model spans packages: architecture (compartmentation, doorsets), MEP (active systems), façades (cavity barriers), and fire stopping across trades.
Roles matter. The client or asset owner sets high-level information needs, the Principal Designer leads coordination of design intent and risk information, the Principal Contractor plans delivery and evidence capture, and specialists supply product and installation data. A change route is essential: when a product variant or detail shifts, the digital record moves with it, with the fire engineer and designer recording the basis for acceptance.
Turning the standard into site practice
/> On live projects, BS 8644-1 becomes a set of behaviours and tools. Start by defining the fire-critical asset list with the fire engineer and supply chain: doorsets, dampers, fire stopping systems, control panels, devices, sprinklers, risers, penetration seals, smoke shafts, cavity barriers and signage. Agree the attribute sets for each class: performance rating, product reference and certificate, manufacturer, installer, batch or serial, location code, unique asset ID, installation date, commissioning status, witness details, and links to photos and drawings.
Build those requirements into the Task Information Delivery Plans so each subcontractor knows what to submit and when. In the CDE, set templates for file naming and asset metadata, and decide how location references will be captured: grid/zone, space ID, elevation reference or model GUID. Use mobile forms to capture installation evidence on first fix, not at the end. Tag assets physically with QR or barcodes so the record can be recalled quickly during snagging and commissioning.
Don’t rely purely on 3D models for evidence. Photos that show scale, labels, sealant backing, and surrounding context matter, especially for concealed work. For active systems, time-stamp commissioning, record witness names, and store test sheets alongside panel cause-and-effect matrices. At handover, the published set should let a building operator understand exactly what was installed, where it is, and how it performs, without trawling a thousand-page PDF.
# Scenario: high-rise mixed-use fit-out under programme squeeze
/> A Principal Contractor is delivering a 24-storey mixed-use fit-out in Manchester. The façade contractor is chasing access to complete cavity barriers, while MEP is installing dampers and risers on nights to keep pace with the programme. The digital lead has set up asset IDs and QR tags, but a late product swap on fire doors has landed via email, not the change control route. The fire engineer spots the discrepancy during a level 12 walkthrough when the frame labels don’t match the model schedule. At the same time, the drylining gang has started fire stopping around temporary openings, but photos aren’t tied to room references. Handover for the lower floors is three weeks out, and the client wants a live view of commissioning status. The project halts downstream plastering in those rooms for one shift, aligns the change form with new door certificates, and issues a quick training huddle: scan the tag, capture two angles plus a scale card, and link to room ID and zone.
Pitfalls and fixes aligned to digital fire information
/> Packages often create their own asset lists, which breaks traceability. Fix this with a single master register in the CDE that assigns unique IDs and location codes ahead of installation, then share it in a format subs can actually use.
Substitutions creep in through procurement pressure and end up as redline notes, not structured approvals. Fix it with a mandatory change form that captures performance criteria, fire engineer acceptance, affected drawings, and updates to the register before anything lands on site.
Photos live in phones or chat threads and never make the CDE. Fix it by insisting all evidence is captured through the site form with auto-upload, and tie the upload to the asset ID using QR scans.
Commissioning data sits in vendor portals and won’t export cleanly at handover. Fix it by specifying export formats in the subcontractor order and running a mid-commissioning data drop to flush issues early.
# Common mistakes
/>
– Capturing evidence at practical completion instead of at first fix, resulting in missing photos for concealed fire stopping. By then, you’re cutting holes to prove what was done.
– Letting location references drift between drawings and models, so a “Room 12A” becomes “Space L12-012a” and the evidence can’t be matched. One agreed location schema avoids this.
– Treating the CDE as a file store only, with no metadata. Without attributes and status codes, handover becomes a search exercise, not an audit trail.
– Forgetting temporary fire strategy changes during phases and decants. Temporary routes and protection should be recorded with dates and drawings, then closed out.
On-site checklist to keep the fire information model live
/>
– Lock down the fire asset classes and attribute sets with the fire engineer before first deliveries, and embed them in package scopes.
– Allocate unique asset IDs and location references to planned installations by floor and zone ahead of programme, so tags and forms can be prepared.
– Issue a simple mobile capture flow: scan tag, pick asset class, auto-fill location, attach two photos with context, and confirm installer and date.
– Mandate a substitution route in procurement that updates the register, uploads certificates, and notifies the design team prior to installation.
– Schedule weekly 30-minute coordination between digital lead, QA and package supervisors to reconcile the register against what’s physically in.
– Export commissioning status snapshots at each level-gate, linking test sheets to asset IDs and cause-and-effect documentation.
– Publish a “ready for witness” list in the CDE with room IDs, asset IDs and evidence links before calling the fire engineer or client to site.
The result of following BS 8644-1 principles is not a prettier set of folders; it is faster, cleaner decision-making when the inevitable programme pressure hits. If the data is structured, location-aware and approved through a single route, you can defend choices, prove compliance, and avoid ripping out finished work.
A likely next step in the UK market is closer alignment between product data templates and site capture apps, cutting rekeying and inconsistency. Also watch for clients demanding live dashboards of fire-critical progress, turning the fire information model into a day-to-day management tool rather than a handover chore.
FAQ
# Is BS 8644-1 mandatory on every UK project?
/> It is a British Standard that many clients and dutyholders now use to shape fire information under the golden thread. Whether it is mandated depends on the contract, sector and building risk. Even when not contractually required, aligning processes to it tends to de-risk handover and future safety case work.
# What should go into the Fire Information Model during construction?
/> Include asset registers for fire-critical items, product information and evidence of installation and commissioning. Tie everything to clear location references and unique IDs, and store approvals and change decisions alongside. Keep status visible so the team knows what is planned, installed, snagged, commissioned and ready for witness.
# How do subcontractors practically contribute their data?
/> Set out attribute requirements and file formats in the order, and provide simple capture tools that work offline. Assign IDs before they arrive, give them QR tags and a one-page guide, and agree when data drops will happen. Make it part of valuation or progress meetings so it is treated as deliverable, not admin.
# What happens when a product substitution is proposed late?
/> Route it through a formal change process that captures performance comparisons, approvals and drawing updates. Only update the register once acceptance is recorded, then push the change to affected trades so installation and evidence match the new product. Avoid installing on “subject to” emails that never make the CDE.
# How should evidence be structured for handover?
/> Aim for a published set in the CDE where each asset can be filtered by location, type, status and linked evidence. Provide navigation by floor and zone for the operator, and ensure test sheets and certificates are readable outside specialist software. The pack should support ongoing maintenance, not just a compliance audit.
