The Building Safety Regulator has made Gateway 2 a hard stop, and the digital submission is where many projects feel it. It’s not about shiny dashboards; it’s whether your software can prove a controlled design, show who is competent to do what, and make change management unmistakable. Teams that treat the tech as a document bucket tend to get bogged down in follow-up queries. The kit that passes scrutiny is opinionated about structure, permissions and audit trails — and is configurable enough to mirror your contractual and information requirements without weeks of bespoke work.
TL;DR
/>
– Choose a CDE and connected tools that enforce metadata, permissions and immutable audit logs aligned to ISO 19650 and your Gateway 2 evidence plan.
– Map Gateway 2 deliverables to specific workflows, fields and approvals; don’t rely on free-text or ad‑hoc folders.
– Prove change control: baselines, revisions, decision records and traceable links between models, drawings and the fire strategy.
– Secure data ownership, export formats and retention terms in the contract to protect the golden thread long after PC.
– Rehearse a dry-run submission pack early, with the Principal Designer and key specialists, to expose gaps before the regulator does.
Specifying digital tools that stand up to Gateway 2 questions
/> Procurement starts with what the regulator will ask for: evidence that the design is coherent, competent people are named, and changes are controlled. Reflect that in the specification. Require the CDE to support ISO 19650 naming and metadata templates out of the box, with project-level mandatory fields for discipline, status, classification and revision. Mandate immutable audit logs that record who uploaded, who approved, and what changed — including comments and mark-up histories.
Insist on robust model/file handling. Your platform should ingest common model formats used in the UK supply chain and allow federated viewing, issue pinning and sectioning without forcing every subcontractor into one authoring tool. You don’t need to prescribe a specific schema, but the ability to extract and present structured data (room numbers, fire doors, products) will save you days during queries.
Make change control a first-class requirement. Look for baselining and “transmittal packs” that freeze a Gateway 2 state against which all subsequent change requests are compared. Build in configurable approval paths that mirror your PD/PC responsibilities and design review gates, with clear role-based permissions and electronic signatures.
Competence and appointments are part of the story. Your software estate should allow you to collate and link CVs, training records, professional registrations and appointment letters to packages and design deliverables. Whether that sits in the CDE or an integrated quality system, the key is linkage and auditability, not just storage.
Don’t forget security and longevity. Ask for UK or EU data residency options, permission segregation for HRB information, and guaranteed data portability via open exports (including models, metadata and audit logs) that your client can hold post‑handover without extra licences.
Managing interfaces and risk between client, PD and contractor
/> Misalignment at Gateway 2 often shows up where duties blur: the Principal Designer (Building Regulations) role, the design manager in the main contractor, and specialist designers. Use the software to hard-wire who approves what. Build RACI into workflows so, for example, any fire-stopping detail cannot move to “approved for construction” without PD sign‑off and a linked reference back to the fire strategy.
Onboard the supply chain early and script the process. Provide naming conventions, metadata picklists and submission routes within the platform, not a separate PDF guide. Short, scenario-led training for package designers and document controllers pays back when the first design freeze approaches.
Set up model-data and document-data to talk to each other. A door schedule change in the model should prompt an issue to update the fire strategy appendix and vice versa. Where integrations aren’t native, use disciplined cross-referencing: stable IDs, consistent container naming, and a simple rule that every “approved” item cites its upstream and downstream references.
Finally, treat site capture as part of the digital thread even at Gateway 2. Field tools that tie early enabling works, hold points and mock-ups back to the approved design make it easier to evidence control when the regulator asks how you’ll prevent deviations once you break ground.
A UK site scenario: residential tower fighting a Gateway 2 clock
/> A contractor inherits a 32-storey residential tower in Manchester with an outline design and a long list of provisional sums. The client appoints a PD who wants a clear change control plan before piling starts. The design manager finds three different model viewers in play and folders full of PDFs with no consistent naming. The MEP subcontractor is still designing riser routes while the façade specialist needs anchor loads confirmed. The team sets up a single CDE workspace with mandatory metadata and creates a Gateway 2 baseline pack: architectural, structural and fire strategy all pinned to the same model views. When the riser layout changes, the platform triggers a change process to update penetrations, product data sheets and the construction control plan. The BSR case officer’s follow-up questions are answered with direct links to the change record, model snapshot and approvals — not a stitched PDF.
Measuring value under BSR scrutiny
/> Value isn’t just licence cost. It’s how quickly the team can assemble a defensible submission, how few regulator queries turn into prolonged correspondence, and how confidently you can brief the board that construction won’t be delayed by paperwork.
Track time-to-baseline for the Gateway 2 pack, the proportion of deliverables that pass internal PD approval first time, and the cycle time on change requests touching safety-critical elements. Monitor how often documents are rejected for poor metadata or missing approvals; persistent errors mean the platform configuration or training is off. Finally, measure data portability: can you regenerate the full chain of evidence from export without the vendor present?
Procurement checklist for Gateway 2 submissions
/>
– Demand ISO 19650-ready templates with enforced metadata fields and naming rules configured per project.
– Require baselining and transmittal features to freeze a Gateway 2 state with tamper-evident audit logs.
– Specify model federation and issue management that work with common UK authoring formats and IFC.
– Insist on configurable approval workflows tied to roles, with electronic signatures and permission controls.
– Include competence evidence linkage: appointments, CVs and training records connected to packages.
– Lock in data ownership, open export of files/metadata/audit trails, and retention terms beyond PC.
– Test integrations or API access for field QA tools, risk registers and product data libraries.
# Common mistakes
/>
– Treating the CDE as a dumping ground and trying to fix structure at the end. You won’t retrofit metadata the night before submission.
– Over-customising workflows so only the BIM manager understands them. Keep it standardised and teachable across the supply chain.
– Relying solely on PDFs for critical traceability. Without linked model views, IDs and audit trails, follow-up questions multiply.
– Ignoring competence records until the last week. Gathering evidence piecemeal from inboxes wastes time and frays credibility.
What to watch in the next 12 months
/> Expect more consistent regulator expectations as case officers see repeat patterns, which should make templates and checklists more standard across the market. Product data interoperability is also maturing: structured product information and clearer change triggers between model and document will reduce friction. Keep an eye on how clients are specifying golden thread deliverables at tender — that’s where your software decisions get locked in.
The bottom line: software that passes scrutiny is boring in the best way — strict on structure, predictable on approvals, and ruthless on audit trails. If your system can tell the story of your design and its changes without an extra spreadsheet, you’re on the right side of Gateway 2.
FAQ
# Do we need a single platform for everything, or can we stitch tools together?
/> Many teams use a primary CDE with connected point solutions for models, field QA and competence. What matters is clear ownership of the golden thread and reliable handshakes between systems. If you mix tools, define where the master record lives and test export/import paths early.
# Who owns the data and for how long should it be retained?
/> Contracts should state that the client owns the project information, including metadata and audit logs. Retention should reflect regulatory, contractual and safety needs, which usually means long-term access beyond practical completion. Secure an exit plan with open formats so information remains usable when licences end.
# How do smaller contractors meet Gateway 2 digital expectations without big IT budgets?
/> Focus on a right-sized CDE that enforces metadata and approvals, then add only essential extras. Use vendor-provided ISO 19650 templates, keep workflows simple, and train your document controllers and package leads well. A disciplined process will do more for compliance than a sprawling toolset.
# What model formats and standards does the regulator expect?
/> There isn’t a one-size-fits-all mandate on authoring formats. However, using interoperable formats like IFC alongside native files helps cross-discipline coordination and review. The key is that the model and documents are coherent, traceable and linked to the decisions you are evidencing.
# How should we evidence change control once construction starts?
/> Create a Gateway 2 baseline, then use formal change requests tied to specific documents, model views and affected risk controls. Each approval should be role-based with time-stamped records and a clear link back to the baseline. Ensure site QA and drawings stay in lockstep so that as-built evidence matches the approved change path.
