Digital evidence packs for Gateway 3 are becoming the make-or-break moment for Higher-Risk Buildings in the UK. They are not just tidy folders of PDFs. They are structured, traceable records that prove what was designed, procured, installed and tested, with the golden thread intact from concept to commissioning. Done well, they shorten approval cycles and de-risk handover; done badly, they turn the last month of the programme into a scramble that burns contingency and goodwill.
TL;DR
/>
– Treat the evidence pack as a live, structured dataset built progressively, not a last-week document dump.
– Align scope and naming with your CDE, BIM model, ITPs and the building’s safety case to avoid gaps.
– Capture concealed works early with geo-tagged photos, QR-linked assets and signed ITP steps.
– Tie product selection and substitutions to clear change control including DoPs and competence logs.
– Rehearse the pack with an internal audit before lodging with the building control authority.
What a digital evidence pack really is
/> At Gateway 3, the relevant authority expects compelling proof that the HRB is safe to occupy and that dutyholders can manage it. The digital evidence pack is your structured submission: asset data, as-built information, commissioning outcomes, product provenance and records of who did what, when and under what approval. Think of it as the operational spine of the golden thread, organised so that any item can be traced from requirement to installed reality. It spans O&M manuals, fire strategy implementation, test and inspection records, manufacturer declarations, competence evidence and change logs, all linked to spaces, systems and products.
Format matters. A stack of unlabelled PDFs is not a digital pack. The market is shifting towards CDE-driven structures, BIM-linked asset registers and standardised fields, often aligning to Uniclass classifications and COBie-type attributes. Photos and drawings must be anchored to locations, zones and assets; sign-offs tied to named roles; and version history visible. The aim is that a building control officer or safety team can navigate from risk to resolution in a few clicks.
How the pack gets built on a live HRB site
/> On site, the pack grows through progressive assurance. The Principal Contractor sets the structure in the CDE, tied to the federated model breakdown and the inspection and test plans. Package managers plan evidence capture into the method statements: before-close-up photos of fire stopping, cavity barrier stamps, damper tagging, pressure test results, witness signatures and commissioning sheets. Mobile capture apps pull the lot into the right container automatically through QR or barcode scans, with timestamps and user IDs.
Product provenance is a hotspot. Subcontractors upload manufacturer information, UKCA or CE details, DoPs and installation instructions at submittal stage. Any substitution is logged through the change process, with the Principal Designer and fire lead commenting on impacts. Once installed, the asset gets its label, serial and location pinned to the model or asset register, and any training, calibration or warranty detail is attached. When systems are commissioned, cause-and-effect matrices, witness records and trending plots are added in the same thread.
The document controller or digital engineer enforces naming rules and metadata so that searches return the right item the first time. The QA lead triggers hold points so concealed works cannot proceed without evidence. The client’s FM representative reviews a sample early to ensure the eventual O&M set is usable on day one. By the time practical completion is in sight, the evidence is already 90 per cent present and internally verified, not queued in email inboxes.
Scenario: last weeks on a high-rise residential handover
/> A 22-storey residential block in a regional city is two months from completion. The site manager is chasing façade snagging while the MEP subcontractor is pushing to close risers. The clerk of works flags missing photos for fire collars on soil stacks at Levels 8–12, which are now sealed behind finishes. The document controller can’t match half the uploaded images to locations because they were named “IMG_3456” without QR scan. The Principal Designer asks for proof that a door hardware change didn’t alter the fire strategy assumptions. Meanwhile, the client’s FM lead wants the asset register in a format their CAFM can ingest, not another PDF copy of a spreadsheet. With Gateway 3 looming, the team has to reconstruct evidence for concealed works, align the asset data to classification codes, and close substitution approvals, all while trying not to slip the programme.
Common mistakes
/>
– Treating the pack as admin at the end. Evidence must be built progressively with hold points; leaving it late guarantees gaps and rework.
– Flooding the CDE with unlabeled files. Without mandatory metadata, you will not be able to trace items to spaces, assets or revisions.
– Ignoring product provenance. Substitutions without clear approvals and DoPs create risk and invite scrutiny at handover.
– Forgetting the FM user. Asset data that won’t map to the client’s CAFM or BIM parameters will be rejected or cause long-term friction.
Checklist before lodging a Gateway 3 application
/>
– Confirm the evidence taxonomy mirrors the building breakdown: zones, systems and assets aligned to the model and ITPs.
– Lock a naming and metadata convention so every file carries space, system, asset ID, role and status fields.
– Map each fire-critical element to photographic evidence, test results and approval notes, including penetrations and cavity barriers.
– Configure mobile capture with QR-linked locations and forms for concealed works, commissioning and witness sign-offs.
– Define the RACI for approvals and change control, making sure the Principal Designer and fire lead are embedded in the workflow.
– Run an internal audit on a sample floor and system, tracing requirements to as-built evidence and back again, and fix the pattern issues found.
Pitfalls and fixes on real sites
/>
– Unstructured O&M handovers: Swap generic manuals for asset-level records with serials, install dates, warranties and link-back to the BIM object or register entry.
– Weak commissioning trails: Publish cause-and-effect, test scripts, witness sheets and trend logs as a consistent set per system, not scattered attachments.
– Photo proof that proves nothing: Set minimum image standards, require a location QR in-frame, add a scale or tag, and capture both pre- and post-close-up states.
– Model and data drift: Freeze the coordination model used for evidence mapping and control revisions; push any changes through the same change control that governs products.
What to watch across UK projects next
/> Expect greater demand for structured data that can be interrogated, not just read. Contractors are already piloting asset tagging that connects physical labels to digital twins and resident information, and aligning digital packs with emerging guidance on building safety information frameworks. Clients are moving payment milestones to evidence gates, and public sector bodies are asking for stronger product traceability. The direction of travel is clear: proof over narrative, data over documents.
The next HRB you deliver will be judged as much on its digital record as its physical finish. Ask yourself: is the evidence pack a true golden thread, or just a tidy folder with nice covers?
FAQ
/>
What does a “digital evidence pack” actually contain for Gateway 3?
It typically includes as-built records, asset registers, commissioning and test results, product provenance, competency and training logs, and O&M information. Everything should be traceable to locations, systems and assets, and linked to approvals and changes. The scope varies by project, but fire-critical elements usually attract the most scrutiny.
# Who is responsible for assembling the pack on a UK HRB project?
/> The Principal Contractor usually leads, with the document controller or digital engineer managing structure and quality. The Principal Designer and fire lead contribute to approvals and risk controls, while subcontractors supply installation and product evidence. The client’s FM team should be engaged early to ensure data is usable post-handover.
# How should subcontractors provide evidence without slowing the programme?
/> Build capture steps into method statements and ITPs so evidence is produced as work proceeds. Use mobile tools with QR codes to tag photos and forms to locations and assets, cutting admin and misfiling. Agree naming and metadata before works start, and align submission timing to payment milestones to keep momentum.
# What format should asset data be in for handover?
/> Aim for a structured dataset that can feed the client’s CAFM or digital twin, not only PDFs. Many UK clients prefer COBie-style exports or fields aligned to Uniclass and their internal asset standards. Test a sample export with the client mid-construction and iterate rather than waiting until the end.
# How do we handle product substitutions in the evidence pack?
/> Record the reason, approval pathway and any impact on design assumptions, especially for fire performance. Attach manufacturer information, DoPs and installation instructions to the affected assets and locations. Keep the change log linked to drawings, models and ITPs so the trail is clear to reviewers.
