Gateway 3 is the moment where promise meets proof. It’s the point at which a contractor must show, not tell, that the completed asset is safe, compliant and buildable as-run — and that its operation can be supported from day one. That proof is overwhelmingly digital now: structured records, linked to real components, that create a visible thread from design intent to what is actually installed and tested on site.
TL;DR
/>
– Gateway 3 is about demonstrating as-constructed truth, with digital evidence that ties products, installation and commissioning to specific locations and assets.
– Evidence must be structured and traceable: models, asset registers, certificates, photos, test results and change logs linked in a common data environment.
– Start at procurement: set digital deliverables for packages, define metadata standards and require evidence at hold points before payment.
– Build traceability for fire and life-safety systems first — doors, dampers, sprinklers, alarms, cavity barriers and smoke control.
– Expect to export machine-readable asset data for the client’s CAFM, alongside O&Ms and a clear handover narrative.
Gateway 3, in plain English
/> Contractors often talk about handover as O&Ms and keys. Gateway 3 goes further: it is a formal checkpoint for completion and safety, where the client and regulators expect robust evidence that the building matches the approved design and can be safely occupied. That evidence must be more than a dump of PDFs. It needs to be structured so anyone can navigate from a space, to a system, to a component, and see the product details, installer, test results, certificates and sign-offs.
Think of a “golden thread” as the organising idea. The thread starts with design intent, runs through procurement and product selection, continues into installation records and inspections, and finishes in commissioning and asset handover. The model (IFC/Revit/Navisworks), the asset register (often COBie or a client-specific schema), and the document set (O&Ms, certificates, warranties, Declarations of Performance, UKCA/CE evidence) are three pillars of that thread. Photos, videos, and marked-up drawings complement them — but only if they’re linked by metadata: location, system, asset tag, and date.
A common data environment (CDE) isn’t just a file store. It’s the workflow spine: package-level submittals, RFI/change control, version history, and approvals. For Gateway 3, it’s where the evidence set is frozen, curated and signed off by the right dutyholders so it can be handed to the client and, where required, presented to building control or the safety regulator.
Turning site activity into evidence
/> Gateway 3 success is built months earlier. Start by translating the client’s Exchange Information Requirements (EIR) and Asset Information Requirements (AIR) into package scopes and prelims. Every trade that touches a safety-critical system needs explicit digital deliverables: what data, what format, what photos, what tests, and how it’s tagged to an asset. Payment applications and practical completion for packages should be tied to evidence milestones, not just physical progress.
On site, make evidence capture part of the method, not an afterthought. Field tools that generate timestamps, GPS or plan-location pins, and QR/UID scans make it easy to tie installation photos and inspections to exact assets. Inspection and Test Plans (ITPs) with digital hold points stop work until product certificates and installation sign-offs are logged. For MEP and life-safety, treat commissioning as a data product: capture results against named assets, keep cause-and-effect matrices up to date, and attach factory and site test sheets to the register.
Model-to-asset alignment makes or breaks the handover. Freeze a “for construction” coordination set, then maintain “as-installed” updates as changes happen, with an auditable log of substitutions and design departures. When a fire door type changes or a damper is relocated, the model, the product record, the test evidence and the drawing need to move as one. Weekly “evidence sprints” — short bursts focused on closing loops on a system-by-system basis — stop the end-of-job scramble.
Scenario: A 28-storey residential block in Manchester is six weeks from practical completion. The principal contractor’s digital engineer flags that only half the fire doors have full evidence chains: some photos lack door leaf labels, several installer qualifications aren’t attached, and a handful of dampers tested by the ductwork subcontractor aren’t visible in the asset register. The commercial manager is pressing to release retention on the interiors package, while building control wants clarity on smoke control commissioning before scheduling a final visit. The MEP coordinator has cause-and-effect results, but they’re in spreadsheets not linked to asset IDs. A weekend “catch-up” is proposed, but the drylining gang has moved to another job. The project team decides to run two evidence sprints: one floor-by-floor on doors, one system-led on smoke control, with installers back on site and a clerk of works walking with the QR-tagging app to close each loop. Progress is tracked in the CDE dashboard and linked to payment release.
Checklist: Gateway 3 digital evidence pack essentials
– A federated as-constructed model aligned to space and system zones, exported in the client’s requested format (often IFC) and matched to asset IDs.
– A complete asset register with required fields (location, manufacturer, model, serial/batch, installation date, warranty, maintenance regime), exportable to the client’s CAFM.
– Product provenance for safety-critical items: DoPs, UKCA/CE evidence, declarations of substitution where relevant, and compatibility statements for system components.
– Installation records: timestamped photos/videos tied to asset tags and drawings, plus competence details for installers where required by scope.
– Commissioning and verification: calibrated test results per asset, cause-and-effect matrices signed, and third-party certifications attached where applicable.
– Change control: an auditable log of design changes and product swaps, cross-referenced to revised drawings/models and revalidated calculations.
– H&S file and O&Ms: structured, indexed, and linked back to the same asset IDs and zones used in the model and register.
Pitfalls that sink Gateway 3 — and how to fix them
/> The most common failure is treating evidence as “document control” rather than “data control”. Dumping mixed PDFs at the end won’t satisfy a requirement to show how a component in Flat 12B Bedroom 1 was selected, installed and tested. Fix: set a minimal metadata standard at tender — location, system, asset ID — and require every upload to carry it.
Discontinuity between the model and the register causes chaos. If the dampers live in the model but not in COBie (or vice versa), commissioning reports won’t map. Fix: appoint a single owner for the “ID spine” so tags are consistent across model, register and CDE folders, and run weekly reconciliations.
Untracked substitutions are a flashpoint. A like-for-like claim may hide a performance shift that invalidates previous calculations or test methods. Fix: run product swaps through formal change control with impact notes, approvals, and updated evidence before installation proceeds.
Package silos undermine the golden thread. Firestopping photos might sit in one system, door certificates in another, and commissioning on someone’s laptop. Fix: require all safety-critical uploads to live in the project CDE under a shared taxonomy, with dashboards showing completeness by system and floor.
# Common mistakes
/>
– Leaving installer competence records until handover, then discovering expired cards or missing authorisations. Capture competence evidence at pre-start and link it to each inspection.
– Using generic photo dumps without labels, making it impossible to prove where an image was taken. Use QR/UID tags and room plans so photos bind to spaces and assets.
– Ignoring client CAFM data needs until the end, forcing a frantic reformatting job. Map fields and formats early and test a sample export before halfway through the programme.
– Treating commissioning as a single event, not a data process. Segment by system, record progressively, and tie re-tests to the same asset IDs to preserve traceability.
What to watch next: clients and regulators are moving toward machine-readable submissions and closer scrutiny of product traceability for fire safety systems. Expect tighter expectations on change logs, competence records and the link between digital models and the physical asset — plan your information spine accordingly.
FAQ
# What counts as acceptable digital evidence at Gateway 3?
/> Acceptable evidence is anything that can be traced from a space or asset to the product used, how it was installed, and how it was verified. In practice that means models and registers, certificates, declarations, test results and photos, all tagged with consistent IDs and locations. Unstructured file dumps are likely to trigger queries because they don’t prove traceability.
# When should a contractor start gathering Gateway 3 evidence?
/> Begin at tender by defining digital deliverables in the prelims and scopes. During construction, capture evidence at hold points and as each floor or system is completed, rather than saving it for the last weeks. Progressive collection reduces rework and avoids chasing subcontractors who have left site.
# Do all subcontractors need to work in the CDE or BIM tools?
/> Not every subcontractor needs to model, but they do need to deliver data and documents in the agreed structure. Smaller trades can use simple upload portals or mobile apps to tag photos and certificates with the right metadata. The principal contractor should provide templates and support so evidence is consistent across packages.
# Who signs off the digital evidence and how is ownership handled?
/> The principal contractor typically curates the evidence set, with package leads and competent persons signing their parts, and the principal designer or building control reviewing where required. Ownership of data usually transfers to the client at handover under contract terms. Keep approvals and signatures within the CDE so the audit trail is clear.
# How should product substitutions be handled without breaking traceability?
/> Treat substitutions as a formal change with impact notes, approvals and updated documents before installation. Update the model, asset register and test plans so the new product flows through to commissioning and O&Ms. Attach the old and new records in the CDE so anyone can see what changed and why.
