Golden Thread software is moving from “nice-to-have CDE features” to a core compliance engine under the Building Safety Act, especially for higher-risk residential projects. Procurement teams are being asked to buy platforms that don’t just store drawings but capture design intent, decisions, product provenance, change control and asset data in a way that survives into occupation. The winners won’t be the shiniest apps, but the systems that fit the programme, talk to existing tools, and withstand audit when a regulator or insurer asks, “Show me exactly why that decision was made and what was installed.”
TL;DR
/>
– Start with information requirements, not app features: define what the project must evidence and who is accountable for each data set.
– Favour platforms that integrate with your CDE, BIM tools and asset systems, with immutable logs and clear role-based permissions.
– Bake change control into the contract: product swaps, design deviations and temporary works must trigger traceable workflows.
– Budget for adoption: train principal designer and principal contractor teams first, then phase in trade subcontractors.
– Measure value by audit-readiness and handover quality, not by user logins or form counts.
Specifying Golden Thread software under the Building Safety Act
/> Set the brief around evidence, not technology. Your Employer’s Requirements and the information requirements for the job should outline what needs to be demonstrated at each stage: design provenance, approved products, fire and life-safety stratification, control of change, testing and commissioning records, and the handover of enduring asset information. If you don’t specify these outputs clearly, you either buy the wrong tool or misconfigure the right one.
Name the dutyholder responsibilities and map them to the workflows. The principal designer and principal contractor must be able to propose, assess and approve changes with an audit trail that cannot be edited. The accountable person or building owner will need enduring access to a usable, secure record for occupation, not just a zipped O&M file. Specify role-based permissions aligned to dutyholder roles and a process for transferring control after practical completion.
Insist on open data routes. Your golden thread won’t survive if it’s locked in a format your asset team can’t use. Ask for structured exports that can populate your asset register, align to your organisation’s classification system, and link model objects to product data and certificates. Point solutions that can’t hand over structured data will create friction and risk at Gateway handover and during safety case preparation.
Build in security and provenance. Sensitive building safety information should be access-controlled, with clear audit who, what, when. Make version history immutable. Stipulate UK-hosted data or appropriate assurances if that’s a client policy, and make sure the supplier can outline disaster recovery arrangements in plain English.
Interfaces and risk across design, build and occupation
/> Golden Thread capability sits across several moving parts: your CDE, BIM authoring, field capture on site, commissioning snag lists, and the asset system that the operator will live in. Procurement needs to ask how data flows through these layers: who originates it, how it gets validated, and how it lands in the final “source of truth” for occupation. Without that map, the platform risks becoming yet another disconnected repository.
Site scenario: a council-led recladding of an occupied tower in the Midlands. The site manager is balancing mast climber slots, resident access windows and a volatile materials market. A steel bracket becomes unavailable mid-programme and the façade subcontractor proposes an alternative. The design manager needs to assess structural and fire performance, the fire engineer wants evidence of test data equivalence, and the resident liaison officer must confirm the change won’t extend noisy works beyond agreed hours. In the Golden Thread platform, the change request captures the proposed product, reason for deviation, engineering notes, approvals and links to the original design intent. Once agreed, the site team scans QR tags as the actual brackets arrive and installs them, pinning batch certificates to locations. At handover, the accountable person can trace from the safety strategy through each approved deviation to the exact component installed on each elevation.
Think about transitional risk. During construction, your principal contractor typically curates the record. Post-completion, the building owner or managing agent becomes custodian. Make the transfer an explicit deliverable with acceptance criteria: named datasets, defined file structures, user training, and a date when admin rights shift. The handover is not just a data dump; it is a change of responsibility that must be visible and controlled.
Don’t forget residents and operations. For occupied works and after completion, safety information must be intelligible to the people who live with the building. Some platforms include resident-facing portals; others rely on separate channels. Whichever route you choose, ensure messaging and versions stay synchronised with the authoritative record, so what’s communicated publicly matches the approved position.
# Common mistakes
/>
– Treating the Golden Thread as a document folder. It’s a set of structured data and decisions with lineage, not just PDFs arranged nicely.
– Leaving configuration until after start on site. Workflows, fields and approval paths need to be set before the first design freeze and procurement packages.
– Ignoring subcontractor onboarding. If trades can’t submit product data or capture install evidence easily, the whole chain breaks.
– Assuming the asset team will “figure it out” at handover. If the operator’s system can’t ingest the data, you’ll be exporting spreadsheets for months.
# Procurement checklist: Golden Thread readiness
/>
– Define the building safety information you must prove at each stage and map it to named fields, workflows and responsibilities.
– Require immutable audit trails for design decisions, product substitutions, inspections and sign-offs, aligned to dutyholder roles.
– Select a platform that captures asset-level data and links it to models and locations, with QR/serial capture on mobile.
– Mandate open export paths into your asset management system, with a pilot transfer before PC to de-risk the final handover.
– Include structured change control that ties into programme management, so approved changes update lookaheads and procurement status.
– Budget time for configuration and user training, starting with principal designer and principal contractor, then cascading to trades.
– Agree data retention, security, and admin transition terms in the contract, including ongoing access for the accountable person.
Measuring value beyond the licence price
/> Value shows up when evidence is easy to find and stands up to scrutiny. A strong Golden Thread setup shortens the time it takes to locate the latest approved design, confirm what was installed, and demonstrate why a change was justified. You’ll see fewer late-stage surprises, clearer sign-offs, and a handover package that doesn’t bounce back from building control or the owner’s compliance team.
Pick practical metrics. Track the average turnaround on change requests from proposal to approval. Monitor the proportion of field records that are properly tagged to locations and assets. Measure how many times teams escalate because they can’t find the current fire strategy or product certificate, and how quickly evidence packs are accepted without rework. For the operator, assess how smoothly the data lands in the asset system and whether maintenance teams can locate safety-critical asset histories without calling the contractor.
Consider whole-life cost. An apparently cheaper tool that locks data into custom structures can become costly when you try to populate an asset register, prepare a safety case or respond to a new inspection regime. Conversely, a platform that supports open classifications and predictable exports reduces friction throughout the building’s life. Procurement should weigh these downstream impacts alongside subscription fees and setup costs.
What’s next to watch? Expect closer alignment between product data templates and golden thread records, so substitutions can be assessed against consistent attributes. Also look for clearer market expectations on competence logs within the platform, linking tasks to demonstrable qualifications for key roles. If you’re heading into procurement this quarter, ask three questions: Who will steward the Golden Thread after completion, what system will they use, and how will today’s data land there intact?
FAQ
# Is a CDE enough to deliver a Golden Thread, or do I need a separate platform?
/> A capable CDE can underpin much of the Golden Thread, but only if it supports structured data, change workflows and robust audit histories. Many teams layer specialised modules or add-ons to manage asset attributes, change control and field capture. Start with your information requirements and confirm whether your current CDE can meet them without heavy workarounds.
# How should I involve subcontractors without overwhelming them with admin?
/> Keep the process simple and consistent: one route for product submissions, one route for installation evidence, with clear acceptance rules. Provide mobile-friendly forms and QR/location tagging so evidence is captured in the flow of work. Build onboarding into pre-start meetings and include expectations in subcontracts to avoid last-minute gaps.
# Who owns the data and who pays for access after completion?
/> Contracts should state that the building owner or accountable person has enduring rights to the Golden Thread data and practical access to it. Clarify whether ongoing platform licences are required, or whether data will be transferred into the owner’s system. Budget for a managed transition so there isn’t a cliff-edge when the contractor demobilises.
# How do I handle product substitutions under programme pressure?
/> Use a formal change workflow that captures the reason for substitution, technical equivalence evidence, and approvals from the right roles, including fire engineering where relevant. Tie the approved change back to procurement and installation activities so the field team knows exactly what to use and how to evidence it. Avoid email-only decisions that are hard to trace later.
# What’s the minimum I need in place before start on site?
/> Have configured workflows for design approvals and change control, role-based permissions for dutyholders, and a clear data model for safety-critical assets. Ensure mobile capture is set up with location structures, and that the principal designer and principal contractor know how to use the system. Pilot one package from design to install to prove the path before wider rollout.
