Gateway 3 is where the talk about the “golden thread” becomes very real. By the time you’re asking for completion sign-off on a higher-risk or complex building, you’ll be expected to evidence what was actually installed, the decisions taken, and how life-safety systems can be maintained. The right software won’t write your processes, but it will make or break your ability to gather, verify and present the record under programme pressure. Choosing a platform is less about shiny dashboards and more about procurement discipline: specify outcomes, manage interfaces, and prove value with measurable, auditable evidence.
TL;DR
/>
– Define the evidence you need at Gateway 3 and make software selections prove they can capture, verify and present it to your acceptance criteria.
– Treat golden thread capability as a project requirement with roles, RACI and deliverables, not a bolt-on tool.
– Prioritise integrations with your CDE, design models and field QA so photos, inspections and approvals link to assets and locations.
– Run a live pilot on a real package to test workflows, mobile capture and export before awarding.
– Measure value through data completeness, traceability, and reduction of rework and late handover friction.
Specifying golden thread capability for Gateway 3
/> Start with the outcomes. List the evidence artefacts you’ll need for sign-off: product data for safety-critical systems, installation certificates, location-tagged photos, commissioning sheets, approvals, and change history. Then require any golden thread solution to show how those artefacts are captured, validated, and surfaced in a structured way against assets, spaces, and systems. Keep procurement language tied to information outcomes, not vague claims.
Interoperability matters. Many teams already use a CDE for drawings and models, a field QA app for inspections, and separate snagging tools. Your golden thread shouldn’t live in a silo; it should connect to where information is generated. Look for open exports, clear APIs, and the ability to reference the same asset tags and model coordinates so you don’t double-handle data or lose context.
Governance needs designing in. Define the permission model (who can submit, verify, publish), the audit trail (who changed what and when), and the acceptance criteria for “evidence complete”. Ensure the platform supports immutable records for approvals, keeps decisions traceable, and allows you to package data for regulators and the client without marathon manual collation.
Golden thread is not just for handover week. Procurement should require progressive capture: evidence logged when a firestop is installed, not weeks later; commissioning data stored per asset and zone, not left in a PDF annex. Test how the platform handles offline site conditions, naming conventions, versioning, and late design changes.
Checklist for specifying a golden thread platform
– Define your asset breakdown and classifications early, and require the platform to store evidence at that level (system > asset > location).
– Specify integration points: CDE linking, model references, field QA, and document control handshakes with common file types.
– Mandate offline-capable mobile capture with timestamp, location, and user attribution embedded automatically in submissions.
– Require configurable workflows for submit–verify–approve with role-based permissions and an auditable, read-only approval state.
– Insist on open exports to common formats to avoid vendor lock-in and to support client asset information models.
– Set out naming conventions, metadata fields, and evidence templates for high-risk items, with supplier onboarding requirements.
– Include a sample “Gateway 3 pack” export in the tender response, using your artefact list and acceptance criteria.
Managing interfaces and risk across the project team
/> Here’s a typical UK scenario. A principal contractor is delivering the recladding and MEP upgrade of a 20-storey residential block in the Midlands. The programme is tight because winter weather has already bitten and access is limited to one goods hoist. The principal designer is reissuing details after intrusive surveys throw up hidden defects on several levels. Firestopping and MEP containment trades are working in the same risers, and a clerk of works is sampling installations daily. The document controller is drowning in email submissions of certificates and photos, and the client team wants weekly assurance dashboards. Gateway 3 is three months away, and everyone is anxious about the completeness and verifiability of evidence. A golden thread system exists, but half the supply chain hasn’t logged in, and QR tags for assets are only partially deployed.
This is an interface problem, not a software problem. The solution is to hardwire golden thread delivery into package scopes and site routines. Trade contractors need asset IDs in their drawings and method statements; their supervisors need a simple mobile flow to capture photos against those IDs at point of install. The principal designer’s changes must cascade into updated acceptance templates so evidence reflects the latest detail, not last month’s revision. The clerk of works should verify evidence in the same system, not in a separate spreadsheet.
Adopt a weekly cadence. Each package lead should report on evidence completeness by level/zone, not just on installation progress, with blockers escalated early. Make it visible: a wallboard or dashboard that shows, for example, “riser 12: 16/20 firestops evidenced, 12 verified”. Train the supply chain in short bursts at site induction and back it up with laminated QR cheat sheets at riser doors.
Technology choices should support site reality. Offline capture is non-negotiable where signal is weak. Barcodes or QR labels on assets speed up reliable tagging. Photo capture should embed time, user and location, and prompt for the right metadata. Integration with the CDE means a drawing or model view can be opened from within the evidence record; it reduces hunting around and bad decisions.
# Common mistakes
/>
– Treating the golden thread as a document bundle compiled at the end. Evidence assembled late loses traceability and drives rework when auditors push back.
– Buying a tool and assuming adoption will follow. Without package-level requirements and training, trades default to email and WhatsApp.
– Ignoring change control. If design revisions don’t update evidence templates and acceptance criteria, you’ll collect the wrong proof.
– Overcomplicating metadata. Too many mandatory fields slow capture and lead to poor-quality entries; focus on the few fields that matter for sign-off.
Measuring value and proving you’re Gateway 3-ready
/> Value isn’t the number of licences bought; it’s the friction removed at sign-off and the confidence you give the client and regulator. Put metrics in your procurement. Ask vendors to demonstrate how you can track evidence completeness per system and location; how a verifier can sample installations quickly; and how change history for a safety-critical element can be shown without stitching three systems together.
Run a live pilot on one high-risk package during tender evaluation. Pick a riser or façade bay, create the asset list and acceptance templates, and have the subcontractor capture real evidence for one week. Observe how long it takes to submit, how many submissions reach “verified” state, and what breaks under poor connectivity. Export the outputs as if for Gateway 3 and let your information manager, the principal designer and the clerk of works critique it.
Commercially, avoid lock-in. Require open exports and clarify data ownership in your contract so the client can take the golden thread into operations. Push for a clear RACI: who raises, who verifies, who publishes, and who signs the final pack. Confirm how the platform will be priced for late-joining trades and whether training and support are included during peak commissioning.
To keep momentum, set internal milestones: a mid-stage evidence review per system, a pre-Gateway 3 rehearsal with sampled areas, and a formal freeze on acceptance criteria two weeks before final handover packs. Treat the golden thread as part of quality management, not a parallel admin stream. When the site is under pressure, make the right way the easy way: scan, capture, submit, verify.
What to watch next: stronger client briefs for post-occupancy and maintenance-ready data, and closer alignment between models and field evidence. Take three questions into the next meeting: which packages have evidence deliverables embedded in scope? how will design changes update acceptance templates within 48 hours? what is our weekly evidence completeness score by level and system?
FAQ
# Is golden thread software the same as a CDE?
/> Not necessarily. A CDE holds drawings, models and documents, but golden thread software is focused on capturing and verifying install and decision evidence against assets and spaces. Some platforms combine both, but many teams integrate a golden thread layer with their existing CDE. The key is that evidence links reliably to the latest design context.
# Who should own the golden thread process on a project?
/> Ownership sits with the project leadership, typically the principal contractor with input from the principal designer and client. Day to day, an information manager or digital lead should run workflows, while package managers drive adoption in their trades. Make responsibility explicit in the RACI and include it in subcontract scopes.
# How can subcontractors be onboarded without derailing the programme?
/> Keep onboarding short and practical: a 20-minute induction focused on scanning asset IDs and capturing photos correctly. Provide ready-made templates per package and put QR job aids at workfaces. Follow up in the first week with spot checks and quick coaching, and make evidence completeness part of weekly progress reviews.
# What about existing tools we already use for QA and snagging?
/> Leverage them if they can link to assets and export cleanly; otherwise, integrate them with the golden thread platform. The goal is one place where verifiers can see a complete record with traceability. If two tools are used, define exactly which captures what and how records are cross-referenced to avoid duplication and gaps.
# How do we handle changes when designs are still moving late in the programme?
/> Tie design change control to your evidence templates. When a revision lands, update acceptance criteria and notify affected trades through the platform, not just by email. Mark older evidence as superseded where relevant and ensure verifiers check against the current revision, keeping the audit trail intact.
