Gateway 2 is the point where the regulator asks, “Are you really ready to build this safely?” For contractors on higher‑risk buildings, that translates to presenting a controlled plan for construction, a proven process for change, and a reliable “golden thread” of information that can be checked and trusted. The spreadsheets and PDFs of old won’t cut it by themselves. To land permission to start, teams need digital tools that make design intent unambiguous, evidence capture routine, and accountability visible across the programme.
TL;DR
/>
– Use a CDE as the single source of truth with clear status codes, revision control and permissions aligned to roles.
– Link model views, drawings and product data to field evidence so the regulator can see design intent turning into controlled work on site.
– Formalise change control digitally: track design changes, substitutions and RFIs with approvals, impacts and reasons.
– Build a construction control plan around digital ITPs, hold points, competence logs and inspection photos/videos with timestamps and locations.
– Prepare an exportable evidence pack with an audit trail showing who did what, when, and under which procedure.
Plain-English digital building blocks for Gateway 2
/> – One information backbone: a Common Data Environment is the project’s library and post room combined. It needs naming rules, status codes (work-in-progress, shared, published), transmittals and a clear route from design to approval. Without this, nothing else holds together.
– Models that talk to records: a federated model or coordinated drawing set should anchor the submission. Viewpoints, sheets and tags must point to approved details, risk notes and product records so reviewers can navigate from a fire-stopping detail to its evidence with two clicks, not twenty emails.
– A construction control plan you can operate: this is not a PDF. It’s a structured set of procedures and forms that live in your system: ITPs with hold/witness points, method statements linked to specific locations, and permit-to-start gates that won’t open until competence and design checks are in.
– Change control you can see: a request is raised, impacts on safety, schedule and cost are recorded, the principal designer and relevant specialists sign off, and only then does it flow to procurement and site. The tool should watermark superseded docs, flag downstream dependencies and store the reason for change.
– Product evidence that survives audit: keep declarations, installation instructions, fire performance data, and maintenance requirements in one place, tied to zones and systems. Captured installation records should show batch, installer, test results and photos tagged to a drawing or model location.
– Field capture that proves reality: site apps for forms, photos, as-builts and test certificates must date/time-stamp and, ideally, geolocate. The key is consistency: the same checklist every time, the same data fields across subcontractors, and clean exports.
How the tools actually move a project to “permission to start”
/> – Start with an information standard. Before you flood a CDE, agree file naming, approval codes and RACI for each workflow: design, change, RFIs/TQs, submittals, quality records. Train package managers and subcontractors on how to submit and where to find published details.
– Lock down “design intent” views. The design team should publish a set of drawings/model views marked as “for regulatory review”, with clear scope notes. Each safety‑critical element—compartmentation, structure, means of escape, MEP penetrations—gets a linked evidence folder in the CDE.
– Build the digital construction control plan. Convert ITPs into live forms with hold points that require document references and signatures. Include competence verification so the gate won’t pass unless the named installer or supervisor is logged as qualified per the plan.
– Wire up change control to procurement and site. Any substitution request or drawing revision triggers checks: does it change fire strategy, structural performance, or access? The tool should cascade updated documents to affected work packs and freeze works in those areas until approvals land.
– Prepare the submission pack as a curated export, not a dump. Use CDE reports to list the documents, revisions and approvals included. Add an index with hyperlinks and a short narrative showing how the plan will continue to generate traceable evidence once spades hit the ground.
# A live UK scenario: mixed-use HRB under pressure
/> A principal contractor is mobilising a 28‑storey mixed‑use tower in Birmingham with residential floors above a retail podium. The design manager is chasing last‑minute clarifications on façade interfaces while the commercial lead is pressing to lock packages. The BIM coordinator has a federated model but façade and MEP penetrations clash on two levels. The QA manager has paper ITPs ready, but the regulator has asked how fire‑stopping evidence will be tied to locations. A drylining subcontractor wants to propose an alternative system due to lead times. Site access windows are tight, and the programme shows piling starting in three weeks. With a structured CDE, the team pins down approved façade details, routes the substitution through a digital change workflow that flags fire implications, and builds location-based ITPs so installers capture photos and batch data directly against zone tags. The submission proves not just intent but the mechanics of control under real programme pressure.
Minimum digital toolset to assemble a credible Gateway 2 pack
/>
– A Common Data Environment with role-based permissions, naming standards, transmittals and immutable audit trails.
– Design coordination tools that produce fixed, navigable views and issue logs linked to risk notes for safety‑critical areas.
– A field management app for ITPs, permits, inspections, photos/videos and test certificates with timestamps and location references.
– A change control workflow that links RFIs/TQs, design revisions, product substitutions and approvals to affected work packs.
– Product data management to store and tie performance evidence, installation instructions and batch records to systems/zones.
– A competence and training tracker that links people to tasks, certificates and sign-offs inside the construction control plan.
– Reporting/export functions that build indexed submission packs and dashboards showing status, overdue actions and hold points.
# Common mistakes
/>
– Treating the submission as a document bundle rather than proving a live process that will govern site works. Regulators want to see how controls operate day to day.
– Letting subcontractors operate their own parallel systems. Fragmented records make traceability slow and approvals uncertain.
– Relying on model screenshots without linking to approved details and product evidence. Static images don’t stand up to change or audit.
– Bolting on change control late. If procurement and site aren’t wired in, unapproved substitutions and drawings slip through under programme pressure.
Pitfalls and the fixes that keep you moving
/> – Pitfall: Model and drawing status confusion across teams. Fix: Limit “publish” rights, align status codes across all disciplines, and issue a weekly published set with a machine-readable index so no one guesses what’s current.
– Pitfall: Evidence capture varies by subcontractor and breaks the golden thread. Fix: Mandate standard digital forms and photo requirements in subcontracts, run onboarding sessions, and spot-check early lots to set expectations.
– Pitfall: Product changes derailing reviews. Fix: Pre‑define substitution pathways with technical reviewers, set SLA targets, and require impact notes on fire/structure for any change request before it enters approval.
– Pitfall: Last‑minute collation before submission. Fix: Create a running “submission shelf” in the CDE with live reports that mirror the expected pack, so gaps are visible weeks ahead of the review.
The market is converging on fewer, better‑integrated tools rather than sprawling stacks. Expect increasing scrutiny on how digital change control ties to procurement and site gates, not just tidy file trees.
FAQ
/>
What is the practical role of a CDE for Gateway 2?
A CDE is the controlled home for all project information, from models and drawings to ITPs and product evidence. For Gateway 2 it proves you can lock design intent, track approvals and maintain an audit trail as work progresses. Choose a platform that supports status codes, permissions and exportable reports so you can assemble a clear submission pack.
# How do subcontractors fit into the digital workflows?
/> Bring subcontractors into the same environment with role-based access and standardised forms. Include digital submission requirements in their contracts and run early onboarding that covers naming, approvals and evidence capture. If a specialist must use their own system, define how and when data is pushed into the main CDE to preserve traceability.
# What evidence is expected for safety‑critical installations?
/> Aim to show design intent, product performance data, competence, and proof of correct installation. That usually means approved drawings or model views, manufacturer information, installer qualifications, and time-stamped photos or test results tied to specific locations. The key is consistency and the ability to follow a thread from design through to install and inspection.
# How should change control be set up for Gateway 2 readiness?
/> Use a digital workflow that captures the reason for change, technical impacts, required approvals and downstream effects. Link change requests to affected drawings, specifications, and work packs so unapproved work cannot proceed. Make sure the process includes the principal designer and relevant specialists for safety‑related decisions.
# Who owns the data and how is access managed after submission?
/> Clarify data ownership and access rights in appointments and contracts at the start. The principal contractor typically curates the CDE during construction, but dutyholders and the client will expect continued access to the golden thread after handover. Set retention policies and handover formats early so there are no surprises at close-out.
