Gateway 2 has pushed higher-risk building projects to show their working, not just the end design. The submission is an evidence pack that proves the design is sufficiently developed, coordinated and under control, with people and products traceable. Software can take the pain out of collating this, but only when it mirrors how UK projects actually run: fragmented design teams, rolling changes, conflicting deadlines and a regulator who wants clear responsibility lines.
TL;DR
/>
– Use a common data environment with structured metadata and approval workflows tied to Gateway 2 evidence headings.
– Drive design sign-off through role-based tasks for the principal designer and principal contractor, not email chains.
– Validate models and documents against project information requirements before they hit the submission folder.
– Treat change control as a configured workflow with audit trails, not a spreadsheet on the side.
– Build a response pack format early so regulator queries can be answered from linked sources, quickly.
Gateway 2-ready software in plain English
/> Think of Gateway 2 software as a disciplined way to point all design and assurance threads at a single, organised output. At its heart is a common data environment (CDE) where the design team, principal designer (PD) and principal contractor (PC) contribute, with versioning that makes it obvious what is current, what is under review and what’s been superseded. It adds structured metadata to every file and model so each item knows its discipline, package, status, responsible party and how it maps to the submission contents.
Workflow is the second pillar. Instead of sending PDFs around, approvals run through configured steps with role-based gates. For example, a fire strategy update can’t progress to “submission-ready” until the PD has recorded a design risk decision and the PC has confirmed constructability implications. Audit logs make decisions and dates visible for later scrutiny.
Third, there’s validation. Gatekeeping rules check files and models for completeness against the employer’s information requirements: drawing naming, required schedules and registers, completeness of fire and structural references in model data, product documentation attached to critical elements, and links back to risk registers. Issue tracking ties clashes, unresolved RFIs and assumptions to clear owners and due dates.
Finally, the system produces the submission in a clean structure that aligns to the regulator’s expectations: design intent and coordination evidence, key strategies, schedules, competency and accountability information, and a change management plan. Export formats are consistent so the team doesn’t scramble at the last minute. Nothing here is magic—just the admin burden taken off inboxes and into a framework that holds up under questioning.
How it works on real UK sites delivering HRBs
/> Scenario: A 22-storey build-to-rent scheme in the Midlands is racing to lock its facade order before a crane removal date. The design manager is stuck between late MEP revisions and a fire engineer who wants more compartmentation detail. The PD is pushing for a clear line of responsibility on riser layouts; the PC is worried about programme drift if the submission comes back with queries. The facade subcontractor has changed a tested system due to lead times, prompting a knock-on to cavity barrier specs. The regulator’s case officer has already asked how changes post-approval will be controlled. Everyone agrees the pack must show control, but files are spread across drives, emails and point tools.
In a Gateway 2-ready setup, the project team moves from “file collection” to “evidence assembly”. Discipline leads publish into the CDE’s review state with mandatory fields filled: package code, drawing status, related risks, and whether it impacts fire or structure. Model checks run overnight to flag missing classification, absent product evidence for critical elements, or inconsistencies between the 3D model and schedules. The PD’s approval workflow forces a recorded decision on key risk items and routes anything with buildability impact to the PC before it can be marked submission-ready. Changes to tested products trigger a specific workflow requiring test evidence, performance statements and updated details from the subcontractor.
On site, the PC uses the same environment to capture constructability notes and constraints that could clash with design assumptions: delivery window limitations, access routes, or temporary works interfaces. These notes are linked to drawings and models as evidence that buildability was considered pre-approval. When the submission date approaches, the export simply pulls the “submission-ready” items, their linked decisions and the change management framework into a coherent pack.
# Configuration checklist for smoother Gateway 2
/>
– Map the submission structure into your CDE as a set of folders, metadata tags and automated views.
– Define role-based approval routes for PD and PC, with hold points for fire- and structure-related content.
– Set validation rules for file naming, mandatory fields, and model or schedule completeness against information requirements.
– Configure a change control workflow with triggers for product swaps and design deviations, including required evidence.
– Link risk registers and design assumptions to drawings, models and minutes within the same environment.
– Standardise a response pack format so regulator queries can be answered with live links rather than rework.
Pitfalls and fixes when configuring digital delivery
/> The most common failure is assuming general document control is enough. Gateway 2 asks for accountability and reasoning, not just documents. If your system can’t show who decided what, when and on what basis, expect delays answering questions. Fix: make approval tasks capture decisions in structured fields, not buried in comment threads.
Another trap is leaving subcontractor evidence outside the core system. When facade, MEP or fire-stopping suppliers provide test data or installation constraints by email, the golden thread breaks. Fix: require subcontractors to submit via the CDE with minimum metadata, or have a dedicated intake route that tags and files it automatically.
Teams also struggle with model-to-document inconsistency. Drawings say one thing; schedules or models say another. Fix: run automated checks and force resolution to a single source of truth before content can be marked submission-ready.
Finally, change control often lives in an uncontrolled spreadsheet. When programme heat rises, that sheet drifts. Fix: configure change control as a formal workflow with IDs, roles, evidence attachments and auto-notifications, tied to packages and the risk register.
# Common mistakes
/>
– Building a beautiful folder tree but skipping metadata and workflows. Without structured fields and approvals, you can’t slice data for the submission or prove control.
– Letting “final” PDFs bypass the PD/PC gates. It feels faster until you’re asked who approved it and why.
– Treating the model as visual only. Gateway 2 scrutiny often relies on data in the model; empty parameters equal rework.
– Ignoring competence and responsibility records until the end. Capture roles, appointments and competence declarations alongside design content from day one.
What to watch next is tighter interoperability. Expect pressure for machine-readable exchanges between your CDE, BIM tools and client systems, and stronger links between product traceability and design approvals. The bottom line: build a submission engine early, run it daily, and treat every decision as future evidence.
FAQ
# Which roles need access to the Gateway 2 configuration in the CDE?
/> At minimum, the principal designer, principal contractor, design discipline leads and document control need full participation. Subcontractors should have a controlled intake path so their evidence arrives with the right metadata. Give the client read access to submission-ready views if that helps decisions without causing editing risk.
# How should subcontractor product changes be handled digitally?
/> Set a change workflow that triggers when a product field changes or a supplier uploads an alternative. Require supporting test data, performance statements and updated details before approval can proceed. Route the task to PD and PC roles with clear timestamps and comments captured as part of the record.
# Do we need a specific BIM standard for Gateway 2 submissions?
/> There isn’t a single mandated standard across all projects, but a consistent approach to classification, model parameters and schedule links makes validation possible. Align your model data with the project’s information requirements and make sure file naming and status codes are enforced. The goal is traceability between models, drawings and narrative documents.
# How do we manage regulator queries after submission without derailing the programme?
/> Build a query response workspace in the CDE that references the same “submission-ready” items. Assign each query to an owner with a due date and link back to the exact evidence or decision log. Avoid creating duplicate files; provide a controlled addendum that preserves the original pack and adds clarifications.
# Who owns the data and audit trail created for Gateway 2?
/> Ownership typically follows the contract, with the client usually entitled to the project record at handover. Make this explicit in appointments so PD, PC and designers understand retention and access obligations. Keep personal data limited to what is necessary for accountability to avoid avoidable redaction later.
