Gateway 2 is no longer a paperwork drop. The Building Safety Regulator increasingly wants structured, auditable digital evidence that shows how a higher-risk building’s design will achieve compliance in practice, and how changes will be controlled once spades hit the ground. The focus has shifted from “have you got drawings” to “can we trust the data, the decision trail and the people behind it”. That means clean models, disciplined metadata, role-based approvals and a golden thread you can navigate without phoning three different consultants to decode a filename.
TL;DR
/>
– BSR scrutiny at Gateway 2 leans on structured, navigable digital evidence that proves design intent, competence and change control.
– Expect to submit federated models, fire and structure-critical deliverables, approval logs, and a plan for product and change traceability.
– Evidence that lives in a robust CDE with ISO 19650 conventions, role-based sign-offs and auditable metadata travels better than loose PDFs.
– Weaknesses often surface around product substitutions, late coordination changes and missing supply chain competence evidence.
– Build a tight review workflow, name your accountable roles, and link every “decision” to the model view, drawing issue and specification clause it relates to.
What “digital evidence” looks like at Gateway 2
/> Think of digital evidence as the parcel of information that allows an independent regulator to reconstruct your logic. It’s not about volume; it’s about verifiability. Commonly, that includes a federated BIM model showing fire and structural strategy features, coordinated drawings and schedules tied to specifications, and a risk register that aligns with the design assurance process. The BSR also looks for who signed off what, when, and on what basis—so role-based approvals and competence records for the Principal Designer and Principal Contractor matter.
Documentation that lives in a Common Data Environment is far easier to defend if it uses sensible naming, revision control and metadata that ties the right version to the right decision. ISO 19650-style conventions are increasingly expected in practice, even if your supply chain is at mixed levels of digital maturity. Where product performance sits behind a proposed solution—firestopping, cladding systems, smoke control—a clear path from specification to candidate products and test evidence strengthens the pack.
Two cross-cutting threads need to be visible. First, the golden thread: information that remains accessible, accurate and evolves through construction and handover. Second, change control: a simple, clearly owned mechanism showing how design departures will be evaluated, recorded and approved, with impacts across fire, structure and building regs considered before anything is procured or built.
How the expectations play out on real UK sites
/> For a live project team, Gateway 2 demands push decisions earlier, particularly coordination and product strategy around fire-critical elements. Instead of promising to “tidy it during construction”, teams are finding they must prove that the layout, details and interfaces are sufficiently fixed that risk is controlled. That changes procurement conversations—tier 2 packages need to show competence and commit to performance earlier, and provisional sums with fuzzy outputs can become a drag on approval.
Evidence quality is strongest when models and drawings are navigable by someone outside the project bubble. That means discipline on level of information, well-labelled fire compartments and routes, consistent door and penetration IDs, and schedules that actually tally with the modelled kit. It also means attaching reasoning to decisions: why a certain smoke vent area was adopted, why a wall type changed, what test evidence underpins that cavity barrier location.
# A site scenario: student tower under programme squeeze
/> A 22-storey student accommodation build in Manchester is chasing a summer intake date. The design team has a neat MEP strategy, but a late RFI about riser widths collides with the fire strategy, nudging a shaft size change. The façade subcontractor is proposing an alternate insulation product due to lead times. The Principal Designer is under pressure to confirm the detail so procurement can lock orders, while the Principal Contractor wants confidence the BSR will accept the revisions. In the CDE, the model shows updated risers, but the approval log for the fire-stopping details is stuck with an unassigned task. The change note exists, but the specification cross-reference and evidence for the new insulation’s fire performance aren’t yet linked. Two days later, the team submits a tidy package: model view templates highlighting impacted zones, a change impact matrix, linked test evidence, and a signed decision record. The BSR’s queries are sharper but fewer, and the programme survives another wobble.
# Common mistakes
/>
– Treating the CDE as a file dump rather than an auditable workspace. Without metadata and approvals, you invite delays and credibility gaps.
– Submitting models that don’t expose fire and structural intent. If compartments, structural load paths, and protection measures aren’t obvious, expect questions.
– Leaving product performance to procurement “after approval”. Gateway 2 scrutiny pushes performance commitments earlier; vague specs look risky.
– Failing to show how changes will be controlled. A plan on a slide isn’t enough; the workflow needs owners, forms, and traceability.
Practical fixes that satisfy BSR and keep the programme moving
/> Map decisions to information. For any compliance-critical area—fire doors, penetrations, smoke control, structure—ensure there’s a one-click path from the model or drawing to the spec clause, approval record, and (if known) product performance evidence. That linkage reduces friction when queries land and helps internal teams avoid rework.
Set minimum data standards for your supply chain. Not every subcontractor can produce perfect BIM objects, but they can provide schedules with agreed IDs, test references and manufacturer data that aligns with your naming conventions. Short, visual guides do more than long protocols to raise the floor.
Use model view templates. BSR reviewers aren’t living in your federated model daily. Saved views for compartments, escape routes, smoke layer heights, structural frames and penetrations make the evidence legible, speeding up third-party understanding. Attach short rationale notes to these views where relevant.
Get the competence story straight. Provide concise evidence that the Principal Designer, Principal Contractor and key designers have appropriate experience for HRB work, and that designer appointments actually cover the scope in play. The BSR’s interest here is as much about how you will manage design risk as it is about CVs.
Codify change control with lightweight tools. A simple digital form that captures what’s changing, why, the affected regs, impact on fire and structure, and who approved it can live in your CDE. Link each change to model views and drawings, and tag it so it carries through to construction records and, later, handover.
# Gateway 2 digital evidence pack: a quick checklist
/>
– Federated model with named views for compartments, escape strategy, penetrations and key structure, with consistent object IDs.
– Drawings and schedules aligned to the model, with revision control and clear status (S0–A status or similar), plus a responsibility matrix.
– Specification extracts for safety-critical systems tied to candidate products or performance criteria, with test evidence where selection is proposed.
– Role-based approval logs showing who authorised what, and a short competence statement for PD/PC and core designers.
– A simple, owned change-control flow with forms, impact prompts and links to affected documents/model views.
– A risk register that references the digital evidence behind each mitigated item, not just text descriptions.
– CDE metadata and naming conventions that let an external reviewer navigate versions and understand the latest decision.
What to watch next? Expect heavier interest in product data consistency, digital product “passports” and how site inspections will verify the intent you’ve set at Gateway 2. Also watch for clients making information management a contract deliverable, pushing the golden thread from good practice into baseline expectation.
FAQ
# What counts as acceptable “digital evidence” for Gateway 2?
/> Acceptable evidence is information that a third party can navigate to understand the design logic and compliance route. That typically includes models, coordinated drawings, schedules, specifications and approval trails, not just PDFs. The strength is in the links, metadata and clarity around who approved what, when and on what basis.
# Do smaller designers and subcontractors need full BIM capability?
/> Not necessarily. The regulator wants structured, reliable information, which can come from well-organised 2D and data outputs. Agree a minimum data standard—IDs, naming, test references, revision control—and use the main contractor’s CDE to enforce it, even if models are basic or provided by others.
# How should change control be shown at Gateway 2?
/> Show that changes will be captured, assessed against building regs impacts, and properly authorised before procurement or build. A simple digital form, a register and role-based approvals inside the CDE are usually enough, provided you link to affected drawings/models and keep the log live throughout delivery.
# Who owns the golden thread during Gateway 2 and into construction?
/> The client holds ultimate responsibility for the building’s information, but the Principal Designer and Principal Contractor usually lead on organising and curating it. Make ownership explicit in appointments and scopes, and ensure the CDE setup allows the client and regulator to access what they need without hunting across platforms.
# What if a critical product changes after Gateway 2 approval?
/> Treat it as a controlled change that may need notification and additional evidence before use. Gather performance data, update the model and drawings, capture the risk implication and secure the right approvals before ordering. The earlier you involve the PD, fire engineer and PC in that discussion, the less programme shock you’ll suffer.
