The Building Safety Act has pushed “Golden Thread” from nice-to-have to central workflow for UK project teams, particularly on higher-risk residential work. That means choosing software that can actually carry design intent, change control, product provenance, inspections and handover data through the messy reality of procurement and site delivery, not just store PDFs. Buyers now need to specify outcomes, manage interfaces with existing CDEs and field tools, and prove value with auditable records that stand up to gateway scrutiny and later occupation.
TL;DR
/>
– Treat Golden Thread software as an operational system, not a document vault: define data structures, roles and change workflows up front.
– Prioritise open formats, API connectivity, offline mobile capture and immutable audit trails aligned to duties under the new regime.
– Map your deliverables to plan-of-work stages and gateway submissions; avoid duplicate datasets across CDE, QA and asset tools.
– Bake product provenance and change control into procurement: submittals must link to approved design and the in-situ asset record.
– Measure value by how quickly you can assemble a safety case pack and how few unverified changes reach site, not by licence counts.
Specifying Golden Thread software under UK procurement routes
/> Start with what the regulator and your client will expect: a clear, accurate, up-to-date thread of information about the building’s fire and structural safety, traceable from design through construction into occupation. Convert that into an outcome-based specification instead of a shopping list of features. You want to describe the behaviours you need: structured asset data; controlled change; verified product and system information; time-stamped inspections; and a handover dataset that can be maintained by the dutyholder.
Base the specification on recognised information management principles. Align roles and responsibilities to your project’s information delivery plan, so the Principal Designer, Principal Contractor and key subcontractors know exactly which fields they must populate and when. Require open, non-proprietary formats for long-term retention, with the ability to export the whole dataset without extra fees. Make API connectivity a must-have so the Golden Thread can pull from, and push to, your existing CDE, field QA app, and asset/facilities systems rather than duplicating inputs.
Spell out site realities. The platform must work offline on live projects with patchy connectivity and sync safely without overwriting records. It needs granular permissions so specialist designers and trade contractors can contribute only to their packages, with the Principal Designer/Contractor able to accept or reject submissions. Look for immutable audit trails that capture who changed what and why, including formal change approvals where products or details deviate from approved design.
Don’t forget the end game. The long-term dutyholder will inherit this dataset; ensure hosting, data residency and access are acceptable for the building’s life, with clear terms on data ownership and continuity if the vendor or main contractor exits. If the building includes resident-facing obligations, plan for a read-only or curated view that can surface relevant safety information without exposing sensitive records.
# Site scenario: occupied recladding in a London estate
/> A registered provider commissions recladding and fire-stopping upgrades on a 20-storey occupied block. The Principal Designer finalises details under programme pressure while the Principal Contractor juggles delivery windows, mast climber slots and resident liaison. The façade subcontractor proposes a substitute insulation board mid-procurement, citing availability and cost. The Golden Thread software records the proposed change, links it to the original design intent, and routes it to the fire engineer and PD for impact assessment. On site, the supervisor captures installed fixings and cavity barriers with geo-tagged photos tied to location grids. At handover, the client asks for a single pack proving conformance of installed systems to the approved design; the dataset assembles without a last-minute chase through email and messaging apps.
Interfaces and risk across design, build and occupation
/> Golden Thread software is rarely the only digital tool on a job. Interfaces with the CDE, BIM authoring tools, QA inspection apps and asset registers can make or break adoption. Clarify the boundaries:
– Design: models and drawings often live in the CDE, while the Golden Thread holds the structured safety-critical data and controlled “as-designed” records. Require a simple mechanism to snapshot approved design for gateway use without locking entire models.
– Procurement: submittals, approvals and product data sheets should link to the relevant system or space in the Golden Thread, not drift in email. Insist that substitutions can’t be issued to site until the change workflow is complete and recorded.
– Construction: inspections, TQ/RFI outcomes and test certificates must be captured against the exact asset, location and system. Prefer push-button capture on mobile with QR-coded locations to reduce mis-tagging risk.
– Handover: O&M content should be an export of the live dataset, not a manual recompile. Define structured asset types and attributes early so packages like fire doors, dampers and fixings aren’t reduced to scanned PDFs.
– Occupation: the dutyholder needs an easy process to update records after refurb or maintenance. Ensure the software supports role changes and ongoing edits without breaking the original audit trail.
Checklist for a robust procurement
– Define the data model: asset types, attributes, location schema, and mandatory fields for fire/structural systems.
– Require documented change control: from proposal to impact assessment, approval, and site issue, with reason codes.
– Specify offline-first mobile capture with secure sync, photo/video evidence, and QR/NFC tagging options.
– Mandate APIs for CDE, field QA and CAFM integration; avoid re-entering the same data in three tools.
– Set export and retention requirements: open formats for the entire dataset, with no additional fees to extract.
– Include permission schema by role (PD, PC, subcontractor, fire engineer, dutyholder) and evidence of audit logging.
– Request a sample “safety case pack” build in tender demonstrations using your template and a realistic scenario.
# Common mistakes
/>
– Buying a document library and expecting it to run change control. Without structured data and workflows, substitutions slip through.
– Leaving asset taxonomy to handover. Late classification turns months of work into unsearchable attachments.
– Ignoring offline capture. Site teams then stash evidence in phone galleries and WhatsApp, breaking the thread.
– Assuming the client will “sort the data later”. Without clear ownership and export rights, the dataset becomes hostage to a licence.
Measuring value from Golden Thread delivery
/> Value shows up when you can answer tough questions fast. How many fire doors are installed, where, by whom, with which certificates? Which changes were accepted and what was the justification? The right platform reduces the time to assemble gateway submissions and safety case packs, and cuts the number of unverified changes reaching site.
Track indicators that matter to project controls and compliance:
– Time to assemble a regulator-ready submission from approved records.
– Percentage of safety-critical assets with complete attributes and linked certificates.
– Number of changes implemented without recorded approval, and time taken to close them out.
– Alignment of site inspections and test evidence to location grids, not just generic photos.
– Effort saved at handover: fewer manual chases and rework to fill gaps in O&M and asset registers.
In occupied buildings, the real test is month twelve, not practical completion. If the dutyholder can update the record after a repair without breaking traceability, you’ve done it right.
# Next 7 days: put structure behind your Golden Thread choice
/>
– Map three safety-critical systems on a live project and write the exact attributes each needs from design to handover.
– Sit PD, PC and your fire engineer in one room and sketch the change workflow, including who approves and what evidence is stored.
– Ask shortlist vendors to build a mini safety case pack from your sample drawings, submittals and photos within a time-boxed demo.
– Pilot mobile capture on one floor or zone with real supervisors and subcontractors, then adjust the tagging and location schema.
– Draft contract clauses ensuring data ownership, export rights and continued access for the dutyholder after project close.
The Golden Thread is an operational discipline first and a software decision second. Pick tools that respect UK site realities and make it hard to do the wrong thing; the rest is governance and practice that your teams can actually live with under programme pressure.
FAQ
# Is the Golden Thread just a BIM requirement?
/> No. BIM can help, but the Golden Thread is about accurate, accessible, and accountable information on fire and structural safety throughout the building’s life. It includes documents, structured asset data, approvals and evidence from site. Think of BIM as one source, not the whole thread.
# Who should own the software during and after construction?
/> During delivery, the Principal Contractor often operates the platform, with the Principal Designer and trades contributing. After completion, the dutyholder needs enduring access and the right to update records. Set this out in contracts so data ownership and hosting responsibilities are clear.
# How does this fit with our existing CDE and QA apps?
/> Use the CDE for collaboration on design deliverables and formal issue of drawings/models. Use the Golden Thread platform to hold the approved design intent and the structured safety-critical data, plus change and evidence records. Integrate with QA apps so inspections are tagged to exact assets and locations rather than floating in photo folders.
# What about product substitutions when supply chains are tight?
/> Your software should enforce a change workflow that links the proposed product to the original design, captures the assessment by competent people, and records the approval before site issue. If substitutions are pushed through via email, expect gaps in traceability. Build this requirement into subcontract orders and submittal procedures.
# How do we avoid overloading site teams with data entry?
/> Design the data model to match real tasks and locations, use drop-downs and templates, and enable quick mobile capture with photos tied to QR codes or grids. Assign responsibilities by role so trades only fill what they own. A short pilot on one zone will expose friction points before full rollout.
