Gateway 2 is where promises about the “digital golden thread” meet the realities of programme, procurement and change. It is not just a document dump to building control; it’s proof that the design is coordinated, the safety-critical decisions are locked down, and there’s a live mechanism to manage substitutions and deviations without losing control. In practice that means setting up a common data environment that people actually use, structuring data so it can be interrogated, and proving that what gets bought and built is what was approved.
TL;DR
/>
– Gateway 2 expects a coordinated design, defined responsibilities, and a working change-control route for safety-critical elements.
– Set up a CDE aligned to ISO 19650 principles with clear naming, metadata and approval states.
– Tie procurement submittals, RFIs and site inspections to specific model elements and drawings to maintain traceability.
– Lock product performance early; manage substitutions through formal change with fire/structural impact statements.
– Train site and supply chain on how to evidence compliance digitally, not just with paper packs.
What the digital golden thread demands at Gateway 2
/> Plain-English: the golden thread is a reliable, accessible and up-to-date record of information that shows how fire and structural safety are secured through design, procurement and build. At Gateway 2, you need to demonstrate the design you intend to construct, how you’ll control changes, and who is competent to make and sign off decisions. The output isn’t just models and drawings; it includes your change protocol, inspection/testing plans, product performance information, and lines of responsibility between client, Principal Designer and Principal Contractor.
Operationally, you’re building three layers of information. First, design intent: coordinated models and drawings with safety-critical details resolved. Second, control: documented processes for design change, product substitution, temporary works, and interface risks. Third, evidence: how you will capture and store submittals, approvals, test certificates, commissioning results and marked-up as-built records in a way that links back to the approved design.
Most teams centre this in a CDE set up with structured containers, metadata and version control. Use naming conventions, approval codes and status fields consistently so anyone can see what’s “for information”, “for construction” or “approved”. Model information should be queryable: if a door set is fire-rated, the model/object carries that rating and links to the specification, test evidence and manufacturer data sheet. Crucially, the golden thread is live: when a change is raised, it leaves a digital trail from RFI/TQ through design review to reissue, then to procurement and site installation.
How Gateway 2 plays out on live UK sites
/> Picture a town-centre high-rise residential scheme with a retail podium and two basement levels for plant and parking. The Principal Designer has pushed a design freeze to hit the Gateway 2 submission, but the Principal Contractor is staring at steel and MEP lead times. The façade subcontractor flags supply chain issues for the specified fire-stopping system; procurement propose an “equivalent” product to recover programme. Meanwhile, the fire engineer wants assurance that riser doors remain rated after late changes to cable routes. Building control is expecting clarity on how such changes are handled.
In a working golden thread, that façade substitution is not decided on email. A formal change is raised in the CDE against the façade package and the relevant model elements. The fire engineer uploads a short impact statement; the Principal Designer records the design decision and updates the coordinated model and drawings if accepted. The new product’s test evidence, classification report and fixing method statements are attached to the same record. Once approved, procurement places the order referencing the change ID; site installation photos and inspection records tag the exact location and element IDs. When the Clerk of Works does a spot check, they can see on a tablet both the original approval and the evidence that what was fitted matches it. If building control asks later, the thread is visible end-to-end without trawling through email archives.
Practical fixes that keep projects moving
/> Make data structure your ally. Align CDE containers to work packages and building zones so approvals and evidence are easy to locate. Use a standard metadata set for safety-critical items: discipline, location, element ID, fire/structural classification, approval status, change reference and revision. This is what turns a pile of PDFs into a usable golden thread.
Build competence into the process, not just CVs. The Principal Designer needs a repeatable design-acceptance workflow that documents safety reasoning, while the Principal Contractor embeds it into procurement gates and site QA. Every substitution or deviation needs an impact note, not a sales leaflet. Tie ITPs to specific model elements and drawing references so site inspections and test results can be correlated to design intent.
Don’t ignore the “last metre” of data capture. Site teams often default to photos on phones and paper sign-offs. Give them a simple mobile route to push photos, barcodes, and serials into the right CDE container with the right tags. If it’s fiddly, it won’t happen and your Gateway 2 plan will unravel the minute work starts.
Gateway 2-ready digital thread checklist
/>
– Define responsibilities: who raises, reviews and approves design changes, product substitutions and safety-critical decisions.
– Configure the CDE with clear containers, naming, metadata and approval statuses aligned to project work packages.
– Lock performance specs for fire and structure; record rationale and evidence for any agreed variance.
– Map procurement submittals to model elements and specifications; require test evidence with every “equivalent” offer.
– Issue ITPs and commissioning plans that reference drawing/model IDs and acceptance criteria.
– Enable mobile capture for install photos, serials, labels and on-site test results with location tagging.
– Train supply chain on file naming, metadata and approval routes; reject non-conforming submittals consistently.
# Common mistakes
/>
– Treating Gateway 2 like a one-off approval pack rather than establishing a live change-control workflow. The pack passes; the process often doesn’t.
– Allowing product swaps to be agreed verbally on site to save time. It burns more time later when evidence can’t be traced.
– Dumping PDFs into the CDE without metadata or element links. You create a digital landfill, not a golden thread.
– Leaving the Principal Designer out of late design tweaks during procurement. Design responsibility becomes blurred and accountability collapses under scrutiny.
The technology is now the easy part; the discipline of linking decisions, data and delivery is where projects stand or fall. The teams that treat Gateway 2 as the start of evidence-led delivery, not the end of design, will move faster and spend less time in defensive admin.
FAQ
/>
What information should actually be ready in the CDE at Gateway 2?
Aim for coordinated models/drawings for fire and structural elements, performance specifications for key systems, and a documented change-control plan. Include who is responsible for design decisions, what constitutes a notifiable change, and how evidence will be captured. You don’t need a complete O&M set, but you do need a clear route to build one from day one.
# How do we handle subcontractor product substitutions without stalling programme?
/> Define a short, standard change template that includes performance comparison, test evidence and a brief safety impact note. Route it through the Principal Designer and relevant specialists with clear turnaround times. Tie any approval to a change ID so procurement, installation and inspection can follow the same thread.
# Do we need full BIM to deliver the golden thread at Gateway 2?
/> You need structured, controlled information; BIM makes that easier but isn’t the only route. If you’re not model-heavy, use disciplined document control with strong metadata, approval states and element/location references. Aligning to ISO 19650 principles helps create order even if parts of the supply chain are 2D.
# Who owns and maintains the golden thread during construction?
/> The client ultimately needs a usable asset record, but the Principal Contractor typically maintains the construction-phase golden thread with the Principal Designer controlling design intent. Agree in the contract who hosts the CDE, how data is structured, and what handover format is required. Make sure the client has access and rights to export throughout, not just at the end.
# What counts as acceptable evidence for safety-critical installations?
/> Use a mix of manufacturer data, third-party classifications, installation method statements, calibrated test results, and geo-located photos tied to drawing/model references. Certificates alone are rarely enough if they don’t match the exact product and context. The key is traceability: anyone should be able to follow the link from requirement to installation to verification without guesswork.
