Gateway 2 is the construction green light for higher‑risk projects in England, and it now lives or dies on the strength of your digital submission. The Building Safety Regulator wants to see a coherent, traceable pack that proves the building can be built safely as designed, that competent people are in post, and that product and change risks are controlled. For site teams under programme pressure, it’s the moment when a vague “BIM folder” becomes a regulated deliverable. Here’s what that looks like in practice and how to keep the regulator, the client and the programme onside.
TL;DR
/>
– The regulator expects a structured digital pack linking coordinated design, fire and structural intent, construction controls, competent roles and traceable product evidence.
– Information has to be navigable, versioned and explain decisions and assumptions; product swaps need a defined change route.
– Use a single, auditable CDE with clear metadata and status control; PD and PC sign off what they own.
– Bring key specialists and suppliers into the data flow early to avoid last‑minute evidence gaps.
– Build a submission calendar that tracks design freeze and procurement realities; avoid placeholders that can’t stand up to scrutiny.
Plain-English: what the regulator is asking for at Gateway 2
/> Think of the Gateway 2 pack as a story you can follow from intent to delivery. At a minimum, it should present coordinated architectural, structural and building services information with the fire and structural strategies clearly mapped to drawings and models. The regulator is less interested in pretty visuals and more focused on whether the content is complete, intelligible and connected.
Expect to demonstrate how the building safety risks have been identified and will be managed during construction, not just at handover. That typically includes a construction control plan setting out how you’ll supervise critical activities, a change control approach to stop unapproved product swaps, and a way to escalate issues. Competence declarations for dutyholder roles and key designers sit alongside this, showing that the people signing off genuinely have the right experience.
The “golden thread” isn’t a slogan here. Your submission should make it easy to find the right version of each piece of information, to see who authored and approved it, and to understand how it relates to other documents. If you say a riser is fire‑stopped to a particular standard, the data should link through to the specification, the design detail and the product evidence without a treasure hunt.
Products and systems matter. The regulator wants to understand what you intend to install for safety‑critical elements and why those choices are suitable, with test and certification evidence attached. If you’re relying on later design-and-build procurement for parts of the solution, you’ll need to draw the line clearly: what is fixed and justified now, and what is genuinely deferred with an agreed route to approval before it hits site.
Finally, the submission is digital by design. Use formats and standards people can interrogate without exotic software, keep naming and metadata consistent, and avoid dead-end PDFs with no context. If there are grey areas, explain the assumptions up front and how they’ll be validated before breaking ground.
How a compliant digital submission actually gets built on a project
/> On real jobs, the best results come when the client, Principal Designer and Principal Contractor agree an information standard early. That means a common data environment with BS EN ISO 19650 naming and status codes, clear metadata fields (discipline, level/zone, revision, approval state), and a convention for linking models, PDFs and product evidence. The PD sets out what “complete enough for Gateway 2” looks like across each discipline; the PC defines the construction controls and change pathway; both take ownership of what they sign.
Federated models are useful, but you still need human‑readable drawings and schedules that match the model. For safety‑critical elements, create digital “evidence bundles” that sit with the relevant detail: the drawing, the specification clause, the product data sheet, the test report reference and any installation constraints. Many teams use a register approach so each critical element has a unique ID that can be tracked if a change is proposed.
Before hitting submit, run an internal technical assurance gate. Bring the fire engineer, temporary works coordinator, structural lead, MEP coordinator, document controller and the package managers into one room (physical or virtual) and walk the regulator’s likely journey through your pack. If they can’t find what they need in three clicks, re‑organise it. If a declaration says one thing and the drawing another, fix the conflict. Programme‑wise, treat that review like a major design freeze.
# A live-site scenario: city-centre resi tower faces the hard stop
/> A main contractor is two weeks out from piling on a 30‑storey build‑to‑rent scheme. The tower crane slot is booked and the neighbourly agreement locks in narrow delivery windows. The design manager thinks the Gateway 2 pack is “nearly there”, but the fire engineer flags that the smoke control strategy references a fan that hasn’t been specified, and the riser details show a placeholder product. The MEP subcontractor hasn’t uploaded test evidence because procurement is still negotiating alternates. The document controller has three versions of the same level 12 floor plan because naming wasn’t enforced, and the PD’s competence statement is still in draft. The PC calls an emergency review, creates a critical element register, freezes the relevant details, pulls the supplier’s evidence into the bundle, and rejects alternates pending formal change control. The submission lands cleanly five days later; the crane booking is moved but the site doesn’t start at risk.
Where Gateway 2 digital submissions go wrong – and fixes
/> When digital packs stumble, it’s usually not because of technology but because of ownership and timing. Treating Gateway 2 like a late-stage document dump invites gaps, conflicts and nervous regulators. Put a named lead on each content stream (design, construction controls, competence, product evidence, change) with a visible RACI and milestone dates. Expect to spend just as long curating and linking content as you do producing it.
Create a small number of curated registers rather than sprawling spreadsheets. A critical element register, a product evidence register and a change log are often enough. Make them the single references that other content points to. Build a “no orphan PDFs” rule: every item must be linked to its parent and carry status and approval metadata.
Front-load supplier engagement on safety‑critical items. Ask for digital evidence in the format you need, not a marketing pack. If a product is under consideration, bring the supplier’s technical lead into a design review so the rationale is captured early. And be honest with the client about what’s genuinely undecided at Gateway 2 and what must be fixed to proceed.
# Common mistakes
/>
– Submitting uncoordinated models and drawings. If sections, schedules and strategies don’t align, expect questions and delay.
– Hiding product uncertainty behind “contractor to propose”. The regulator wants to see how substitutions will be controlled, not a blank cheque.
– Treating competence as a CV upload exercise. Declarations should link to responsibilities, decision gates and the actual people signing things off.
– Letting the CDE sprawl. Without enforced naming, status and permissions, you’ll duplicate effort and lose the golden thread.
# Pre-submission digital pack checklist
/>
– Lock an information standard: naming, metadata fields, approval statuses and who sets them.
– Build critical element and product evidence registers with unique IDs, links and owners.
– Assemble construction control and change control plans with clear hold points and escalation.
– Capture competence declarations that tie people to decisions and safety‑critical scopes.
– Align models, drawings and strategies; include readable PDFs that match the federated models.
– Run a cross-discipline navigation test: three-click access from strategy to detail to evidence.
What to watch next for Gateway 2 digital in the UK
/> Expect more emphasis on machine‑readable evidence, not just static documents. Product traceability will tighten, especially where fire and structure intersect with MEP systems. Clients are beginning to demand that the Gateway 2 pack evolves directly into the as‑built golden thread, so choose tools and data structures you can live with through to handover. And as the regulator’s case officers see more projects, market “norms” for what’s acceptable will harden into de facto expectations.
The direction of travel is clear: demonstrable competence, controlled change and structured data you can interrogate. Teams that treat Gateway 2 as a managed data handover rather than a rush of PDFs will protect programmes and avoid rework.
FAQ
/>
What file formats and standards work best for a Gateway 2 digital pack?
Use formats people across the project and the regulator can open without niche software. PDFs for signed drawings and strategies, IFC for models, and a BS EN ISO 19650-based naming and metadata approach provide a solid baseline. Avoid scattering content across multiple file-sharing tools; one auditable CDE with versioning and approval statuses is safer. If you use spreadsheets for registers, keep them controlled and link them to source documents.
# How can SMEs and specialist subcontractors contribute without a big BIM team?
/> Give them plain templates and show them an example of a complete evidence bundle. Ask for specific files (e.g., product data sheet, test report reference, installation constraints) with agreed naming, and provide a straightforward upload route into the CDE. A short onboarding call with the document controller often saves a week of chasing. If they don’t have IFC capability, ensure their PDFs and schedules still carry the right metadata and traceability.
# Who owns the golden thread during Gateway 2?
/> The client ultimately needs a golden thread they can use, but operationally the PD and PC usually steward it through design and preconstruction. Clarify in appointments who sets the information standard, who runs the CDE, and how approvals work. Make ownership visible in the RACI so that evidence, competence and change records aren’t orphaned. Whatever the split, the regulator will expect a single source of truth.
# How should changes be handled after the submission goes in?
/> Treat every proposed change to safety‑critical elements as part of a formal process, with a log, impact assessment and approvals before site activities are touched. If you’re unsure whether something is material, raise it early and document the reasoning and route. Keep the evidence register live so new product data and revised details replace superseded items cleanly. Build hold points into the programme to avoid accidental installation of unapproved alternates.
# How do you protect the programme while waiting for Gateway 2 approval?
/> Assume approval isn’t instantaneous and build a buffer that reflects the project’s complexity and the completeness of your pack. Sequence preconstruction so you can progress low‑risk enabling activities, design assurance and procurement groundwork without committing to safety‑critical installs. Keep a live tracker of regulator queries and respond in an organised, consolidated way rather than piecemeal. Avoid locking in crane dates and major deliveries until you have clarity on any likely conditions.
