Gateway 2 demands a level of information control that most teams only discover they needed once the clock is already ticking. A well-set CDE is the difference between a tidy Golden Thread and a scramble through email chains when the Building Safety Regulator asks for clarification. Think of it less as “somewhere to store drawings” and more as the living engine room for design completeness, change control, and accountability across client, Principal Designer (Building Regulations), Principal Contractor and specialists.
TL;DR
/>
– Build your CDE around ISO 19650 states, locked naming conventions and metadata that makes life easy for BSR reviewers.
– Tie your deliverables (MIDP/TIDP) to approval workflows and a visible change control path that differentiates minor design shifts from safety-critical changes.
– Control permissions by role, not by person, and keep fire and life-safety information properly segmented.
– Automate transmittals, approvals and audit trails so you can evidence who decided what, when, and on what basis.
– Dry‑run a Gateway 2 pack extraction to prove you can assemble, check and issue within programme.
Plain-English building blocks that make a CDE fit for Gateway 2
/> A Common Data Environment should be a single, structured location for all project information with role-based permissions and clear states: Work in Progress, Shared, Published, and Archive. Use the UK Annex of ISO 19650 to lock file naming, status codes and revisions so every model, drawing and document can be identified without opening it. Metadata matters: fields like discipline, volume/area, location zone, deliverable type, Uniclass classification and approval status make search, reporting and Gateway 2 pack assembly fast.
Approval workflows should match your RACI: originator, checker (technical), approver (design lead/PD(BR)), with a route to Published. Tie deliverables to your Master Information Delivery Plan (MIDP) and Task Information Delivery Plans (TIDP), so the workflow knows what “complete” looks like against programme. Change control must live in the CDE too: a standard form, explicit impact assessment on compliance and fire strategy, and a status that shows whether the change requires BSR oversight. Keep life-safety documents, model views, and method statements in controlled areas with stricter permissions; ISO 19650-5 (security-minded information management) is a useful lens.
Include model coordination routines so clashes and design conflicts are tracked and closed before items move from Shared to Published. Structured links between drawings, models, specifications, calculations and test evidence help show completeness. Finally, automate transmittals and maintain a clean audit trail; Gateway 2 is as much about showing control as it is about the underlying design.
How the workflow runs on real UK sites aiming for Gateway 2
/> Here’s a typical scenario. A design‑and‑build team on a 20‑storey student accommodation block is racing to line up façade procurement while locking down the fire strategy. The PD(BR) leads a weekly “Publish board” in the CDE, where MEP, architectural and structural leads push WIP to Shared after coordination. The façade subcontractor uploads test evidence and installation proposals into a secure Shared area linked to the fire stopping strategy. Procurement wants an early order on riser doors; the fire consultant insists on more detail on smoke control zones. The CDE flags any deliverable tied to those zones as “pending approval” across disciplines, preventing conflicting publications. When a late change to plant selection affects power loads and shaft sizes, the change request is raised within the CDE, impact assessed against compliance and programme, and only then allowed through to Published for inclusion in the Gateway 2 pack. The same record logs who agreed, when, and the basis for the decision.
On the ground, site prelims are being procured and logistics planning is underway. The Principal Contractor uses the CDE to surface a one‑page dashboard: “Gateway 2 readiness” shows outstanding deliverables, approval bottlenecks, and any unresolved interface items that could trigger BSR questions. When the client asks, “What exactly are we sending and why?”, the CDE can generate a transmittal with a traceable index, aligned to the information protocol agreed at contract.
Pitfalls and fixes when targeting Gateway 2 approval
/> A lot goes wrong because teams try to retrofit structure onto an already busy document hoard. Setting your CDE up with discipline-specific templates, status codes, and a Gateway 2 view from day one keeps you out of that trap. Equally, don’t rely on manual policing; assign system rules that block publishing without required metadata, approvals or linked evidence.
Align your RFI and NCR processes with change control inside the CDE. If a change affects fire, means of escape, compartmentation, load paths or services routing, it should trigger a different route and visibility than a purely aesthetic adjustment. Avoid mixing personal cloud links with official records; everything that informs the design goes through the CDE or it doesn’t count when the regulator asks.
# Common mistakes
/>
– Treating the CDE as a filing cabinet rather than a workflow tool. Without enforced states and approvals, you just have faster chaos.
– Weak metadata and naming discipline. If users can bypass fields, your search, dashboards and submissions won’t hold together.
– One-size-fits-all permissions. Sensitive life-safety content should not be universally accessible or editable.
– No dry-run of the submission. Teams discover missing links, dead references and unapproved content the week of the deadline.
Practical configuration checklist for your CDE before submission
/>
– Lock the ISO 19650 naming convention and required metadata; make fields mandatory for all containers expected in Gateway 2.
– Configure approval workflows reflecting PD(BR), design lead and PC sign-offs, with status codes that map to Published outputs.
– Build a Gateway 2 deliverables view driven by the MIDP/TIDP, showing completeness, approvals and linked evidence.
– Stand up a change control template with impact tags for compliance, fire strategy, structure, and services; route critical changes through heightened approvals.
– Segment life-safety information into secure areas with role-based permissions and monitored download logs.
– Integrate model coordination results so clashes must be closed or dispositioned before moving to Shared/Published.
– Script a submission pack export that auto-generates an index, transmittal and audit report, and test it against a realistic deadline.
What to watch as BSR practice beds in
/> Expect more scrutiny on how decisions are made, not just what the latest drawing shows. Structured data and auditable history will carry more weight than narrative. Many clients are starting to require alignment with fire information management guidance and to verify supplier competence through the CDE, not email chains. Interoperability will matter too: consistent metadata, open formats for model views, and traceable links between model, drawing, specification and test evidence will reduce back‑and‑forth. The teams that simplify onboarding for subcontractors, with templates and light training, will cut weeks off their submission cycle.
Bottom line: a Gateway 2‑ready CDE is a governance machine, not a storage bin. Ask whether your system can filter, approve, and evidence the story of how your design will be built safely—and do it under programme pressure.
FAQ
# Does every project need a full ISO 19650 CDE for Gateway 2?
/> Not every scheme is the same, but the closer you get to ISO 19650’s structure, the easier it is to assemble a credible submission. Using states, naming and metadata gives you predictable outputs and better auditability when the regulator asks for clarifications.
# How should subcontractors be onboarded into the CDE?
/> Provide discipline-specific templates, a short naming guide, and a 30‑minute induction that shows where to put WIP, how approvals flow, and what “Published” really means. Keep permissions tight at first and open up as competence is demonstrated, so you don’t dilute control in the early weeks.
# What counts as acceptable evidence in the CDE for Gateway 2?
/> Evidence should be traceable, current and linked to the relevant design elements: drawings, models, specifications, calculations, test certificates and method statements. Avoid external links that can change or expire; store the source documents in the CDE and relate them via metadata.
# How do we handle late design changes after a submission has been made?
/> Log the change through the CDE’s change control process, including impact on compliance and programme, and maintain a clear chain of approvals. Depending on the significance, you may need to inform the regulator, so keep the pack of affected items easy to extract and justify.
# Who owns the data and access after Gateway 2?
/> Data ownership usually follows the contract, but operationally the client will expect a maintained Golden Thread across the build. Agree early who administers the CDE, how access is managed through phases, and how information will be handed over so there’s no scramble at Gateway 3.
