Gateway 2 is the point where the Building Safety Regulator wants confidence that you’re ready to build a compliant higher-risk project and keep it that way through change. It’s not a glossy design-stage milestone; it’s a test of discipline. The decision will turn on whether your evidence is complete, structured and traceable, not how many drawings you can upload at the eleventh hour. That means a digital trail tying the design intent, product choices, roles, and quality controls together so a regulator – or your own leadership – can see how risks are being managed.
TL;DR
/>
– Build a single evidence chain linking design intent, fire and structure strategies, product data, competence, quality controls and change records.
– Use a proper CDE with metadata, version control and permissions; don’t rely on email and shared drives.
– Lock down product decisions early, tag them in models and schedules, and attach certificates, test reports and installation instructions at source.
– Prove your change control works: decisions, reasons, risk impact and re-approvals all visible and timestamped.
– Map your construction quality approach with digital ITPs, hold points and photographic verification tied to model locations.
Gateway 2 digital evidence in plain English
/> The regulator is looking for proof you understand the risks in your building and have a system to manage them from design freeze into build. In practice that means demonstrating three things: the design is coherent and coordinated; the people and processes are competent and controlled; and any change can be understood, authorised and recorded with its impact on safety features clear.
Think of the “golden thread” less as a slogan and more as a data discipline. Every safety-significant element – structure, fire and smoke control, facades, compartmentation, doorsets, penetrations, lifts, sprinkler and alarm systems – needs design intent, product choice and install/inspection evidence that belong to each other. If your model or drawings don’t line up with your schedules, and your schedules don’t line up with product data sheets, the chain is broken.
You don’t need to buy exotic tools. You do need to make your existing BIM environment, document control system and field QA app behave like one joined-up record with consistent naming, tagging and approval statuses. If a regulator or client can open your model, click a fire door, and immediately see its specification, certificate and inspection photo, you’re on the right path.
From design office to site: making the evidence work
/> On a UK residential tower with a retail podium, the pre-construction team is under pressure. The principal designer pushes for design freeze while the façade subcontractor wants product swaps to shave weeks off lead times. The MEP coordinator is holding clashes at Level 14, the fire engineer is still querying smoke control zoning, and procurement is warning about volatile pricing on doorsets. The design manager’s inbox is a blizzard of “final” PDFs. Gateway 2 submission is scheduled for next week, but the evidence is scattered across three platforms and twelve email threads. The site team, not yet mobilised, is already asking for inspection test plans to lock procurement. If this sounds familiar, the fix is not more PDFs; it’s stitching the story together so it stands up under scrutiny.
What does that look like on real projects?
– Start with a coordinated model set (2D/3D) clearly aligned to the fire and structural strategies. Push discipline leads to tag safety-significant components with agreed metadata fields: fire rating, acoustic rating, product ID, certification reference, installation method.
– Build a “single view” of products. For doors, cavity barriers, dampers, firestopping and facades, attach manufacturer data, third-party certifications where applicable, and installation instructions directly to the tagged objects and schedule lines in your CDE. Avoid orphaned PDFs.
– Define competence in documents, not job titles. Upload appointment letters, role descriptions, relevant training records and CVs for dutyholders and leads. If a specialist designer is carrying a critical detail (e.g. smoke control panel), make that responsibility explicit and findable.
– Map your quality regime. Digitise ITPs with hold points and sample sizes. Place them against model locations or zones so inspections are not abstract lists but geo-located tasks. Enable photo and video capture with timestamps and user IDs.
– Operationalise change control. Set up a decision log that ties RFIs, design change notices and product substitutions to risk assessments and re-approvals by the right people. The moment a fire door spec changes, the model tag, schedule, installation guide and ITP must change with it.
# Digital evidence pack: quick checklist
/>
– Coordinated models and drawings aligned to the fire and structural strategies, with safety-significant items tagged consistently.
– Product datasets for critical elements (certificates, test reports, installation instructions, warranty terms) attached at source in the CDE.
– Clear appointments and competence evidence for dutyholders and key designers, plus supply chain capability statements for safety-critical trades.
– A documented quality management approach: digital ITPs, hold points, sample plans and geo-tagged verification methods.
– A live change log linking RFIs, design decisions, product swaps and risk impacts, with re-approvals captured.
– Interface matrices identifying ownership at junctions (e.g. façade-to-slab firestopping, shaft penetrations, riser doors) and how evidence will be shared.
– A mobilisation plan for records: who captures what on site, on which device/app, named roles for review and sign-off, and storage locations in the CDE.
Pitfalls and fixes across the programme
/> Two realities derail Gateway 2 evidence more than any other: late product decisions and fragmented record paths. If products aren’t locked down, your tags and schedules become guesswork. If decisions live in email, you lose auditability. The fix is to bring procurement and design management into one evidence cadence: weekly reconciliations between model, schedules and product data; a single status dashboard for safety-significant components; and a rule that no substitution lands without linked risk notes and re-approvals in the CDE.
Field verification is another pressure point. Photos without context are almost useless. Push for QR or location-linked capture so photos, videos and test sheets stick to the object or zone. Tie ITP holds to programme activities so trades cannot progress without digital sign-off on defined elements.
Handover often gets attention, but Gateway 2 is tested well before that. Treat it as a rehearsal for build governance: if you can’t show who is deciding what, when and why at design stage, you’re unlikely to control changes when cranes arrive.
# Common mistakes
/>
– Dumping untagged PDFs into a folder and calling it a “submission”. Without metadata and cross-links, evidence is brittle and slow to verify.
– Treating the fire strategy as a report on the shelf rather than a live reference driving tags, schedules and ITPs.
– Letting product substitutions run through procurement alone, with no digital risk note or re-approval recorded.
– Assuming the site team will “pick it up later”. If the capture method and responsibilities aren’t fixed before start on site, gaps appear immediately.
The bottom line: Gateway 2 isn’t an admin hurdle; it’s your governance model under a spotlight. If your evidence chain is coherent, your build will run with fewer disputes, fewer reworks, and a clearer route to final certification. The next few months will likely bring tighter scrutiny on change control and competence records—worth asking now: do we know our safety-critical products by tag, do our decisions live where others can see them, and can we prove our quality holds without digging through inboxes?
FAQ
# What counts as “digital evidence” for Gateway 2 in practice?
/> Think of evidence as linked artefacts, not just files. Coordinated models/drawings, product data and certifications, competence documents, QA plans and change logs should be connected through a common environment with clear versioning and approvals. If someone can trace a safety element from design intent to product choice to inspection proof in a few clicks, you’re close.
# Do we need a specific BIM standard or software to satisfy the regulator?
/> No single tool is mandated. What helps is adopting consistent naming, metadata and approval workflows so information flows cleanly between disciplines and into field apps. ISO-style conventions are widely used in the UK and make it easier to demonstrate control, but the outcome—clarity and traceability—matters more than the brand of software.
# How should subcontractors provide product and install records?
/> Set clear employer’s requirements and trade scopes that specify deliverables: tagged product data in agreed formats, installation instructions, test and commissioning results, and geo-referenced photographic evidence. Provide access to your CDE and a simple upload protocol, and appoint someone to validate submissions against model tags and schedules before approval.
# What’s the right way to manage product substitutions under programme pressure?
/> Run every substitution through a visible change pathway that captures the reason, risk assessment and the re-approvals from the right designers and dutyholders. Update the model tags, schedules, installation guides and ITPs at the same time so the field team isn’t working off stale information. Avoid accepting “like for like” claims without written technical justification stored in the CDE.
# Who owns the data and where should it live?
/> The client usually expects a maintained information environment, but day-to-day control often sits with the principal contractor and design manager. Clarify ownership and access rights in contracts, including how data will be archived and handed over. Keep everything in a managed CDE rather than personal drives so audit trails, permissions and retention are controlled.
