Gateway 3 sign-off is increasingly about demonstrating, not declaring. For UK projects under closer scrutiny, the burden is to prove what was installed, where, by whom, and against which approved design. That means digital evidence capture: photos, test certificates, installation records, and sign-offs that carry context and can be traced to drawings, rooms, components and approvals. Paper folders, loose USB sticks, and end-of-job photo dumps no longer survive client, regulator or insurer questions. A workable approach starts in procurement, runs through package management, and lands in a common data environment with a clean audit trail. Done well, it reduces rework, compresses close-out, and de-risks handover.
TL;DR
/>
– Treat evidence as structured data with metadata: location, time, installer, drawing/version, and hold-point status.
– Set hold points for “concealment” moments and require photo/video evidence plus sign-off before works continue.
– Use a common data environment with permissions, naming conventions, and immutable audit history.
– Train subcontractors to capture to a standard and audit weekly; don’t leave it to the last fortnight before completion.
– Link evidence to assets and rooms via QR or location codes so it can be surfaced quickly at Gateway 3.
Digital evidence capture that stands up at Gateway 3
/> In plain English, digital evidence is a verifiable record that shows an element has been installed and tested as intended. It’s not just a photo; it’s the photo plus where it is on the plan, who took it, when, which system or asset it belongs to, and what it proves. Typical artefacts include installation photos before concealment, inspection and test plans, commissioning sheets, material provenance (certificates, DoPs), and sign-offs from competent persons. For fire-critical works, the evidence narrative should link each penetration or fire-stopping item to a product system, a location reference, and a timestamped approval.
Metadata is the make-or-break. Site teams should tag by floor, gridline, room/zone, and asset ID or system code. Geolocation can help outdoors, but indoors you’ll need strict room numbering and plan-based pinning. An audit trail that shows who changed what, and when a record was accepted or rejected, is essential. The common data environment (CDE) holds the single source of truth; site devices capture records offline and sync into the CDE with the right permissions and version controls.
On UK jobs, roles typically split as follows: package managers set hold points and define evidence standards; supervisors enable capture on devices and coach subcontractors; a digital coordinator manages templates and integration into the CDE; the Clerk of Works or independent inspector reviews samples for quality; commercial teams align evidence milestones to payment triggers. Keep legal and IT in the loop for data retention and privacy, especially where faces or residences appear in images.
From pour to pass-off: how it runs on real sites
/> On real programmes, the safest route is to treat evidence capture as part of the method, not an add-on. For each package, define the points where work can’t proceed without proof: reinforcement before pour, services before ceilings close, fire stopping before boarding, and plant before energisation. Push simple mobile forms to the workforce with dropdowns for location codes, asset IDs and work types, so the data is consistent. Require two clear images (context and detail) and a scan of the material label or QR where relevant. A supervisor approves or rejects on the spot; rejections carry reasons so installers can put it right while access is open. Data syncs nightly to the CDE; dashboards show what’s missing per zone to drive the daily briefing.
Scenario: A 12-storey residential block in Leeds is up against a tight completion date after a delayed façade delivery. The MEP fit-out and fire-stopping trades are overlapping, with ceilings programmed to start next week. The package manager sets a hold point on all riser penetrations: no ceiling grid until each penetration has two photos (wide and close), the product system reference, and a signature from the fire-stopping supervisor. The team codes locations using floor/zone/penetration IDs pre-printed on QR stickers stuck to the slab edge. When rain halts external works, the supervisor walks levels with a tablet, approving acceptable records and flagging four missing certificates for the east core. By the time the building control inspector visits, the evidence bundle is filtered to “Level 8 east core” with product documentation and timestamps, avoiding the usual scramble. The ceiling grid proceeds without a late-weekend reopening for remedials.
Tie the evidence to programme. If the lookahead shows concealment activities, the morning briefing should call out the evidence requirement and the standard (e.g., photo angles, required tags, signatory). Commercially, align interim payment milestones with verified evidence, not just progress notes, to incentivise subcontractors. At close-out, pre-structure the Gateway 3 pack by area and system, so the review is about completeness rather than discovery.
Pitfalls and fixes on UK projects
/> The common failure is a giant, unstructured photo library with no link to the works. Fix this by using templates with mandatory fields and naming conventions that include zone, asset/system, and revision. Another trap is version drift: evidence tied to an outdated drawing. Solve with a CDE rule that only current-for-construction drawings can be picked in the field form, and archive superseded versions out of selection lists.
Avoid privacy and safety breaches. Train teams to frame shots away from faces and personal effects, and never capture risky behaviours for the sake of “proof”. Where occupied retrofit is in play, agree a photo protocol and signage with the client early.
Interoperability matters. If you tag assets in the BIM or asset register, ensure the IDs match the field forms and QR labels. Export formats should be open or at least preservable long-term; Gateway 3 is not the moment to discover a licence expired and locked your records.
# Common mistakes
/> Treating every photo as equal. Without location and purpose, images become noise and are easily challenged at sign-off.
Leaving capture to the last weeks. Attempting a retroactive evidence pack typically exposes gaps behind closed walls and costs weekends in rework.
Relying on one champion. When a single digital coordinator leaves site, standards collapse unless supervisors and subcontractors are trained.
Ignoring change control. If a specification shifts, failing to update forms and QR labelling leads to mismatched product evidence and avoidable disputes.
# Field-ready checklist for Gateway 3 evidence capture
/>
– Define hold points by package (e.g., before concealment) and require evidence plus sign-off to pass each one.
– Pre-issue location codes and QR/label packs per floor and zone so installers can tag evidence consistently.
– Standardise capture templates with mandatory fields: location, asset/system, drawing/revision, installer, and purpose.
– Set image standards (two angles, lighting, include scale/reference) and an approval SLA for supervisors.
– Lock forms to current-for-construction drawings through the CDE and purge superseded options from field devices.
– Audit weekly with a sample-per-zone approach and brief findings in the daily stand-up to correct drift early.
The direction of travel in the UK is clear: evidence that is trustworthy, structured and findable. Ask at your next progress meeting: Are our hold points real or theatre? Can we surface proof by room in under five minutes? Who is checking that today’s evidence lines up with the latest design?
FAQ
# What counts as “good” digital evidence at Gateway 3?
/> Good evidence shows what was installed, where, by whom, and against which approved information. Pair images with clear location codes, asset or system references, timestamps, and a named approver. Include supporting documents like product certificates or commissioning sheets where relevant. If a third party needs to find it fast, you’ve probably done it right.
# Do subcontractors need special apps or devices to capture evidence?
/> Not necessarily, but the process must be simple and consistent. Many teams use mobile forms on standard smartphones with offline capability and QR scanning. What matters is that the data lands in your CDE with the required fields and audit trail. If multiple apps are used, agree interoperability and naming standards early.
# How should we manage drawings and revisions so evidence isn’t tied to the wrong version?
/> Control starts in the CDE: define “current for construction” status and restrict selection in field forms to those versions only. Superseded drawings should be archived out of pick-lists on site devices, and lookaheads should flag when key revisions affect upcoming hold points. A short weekly sync between design management and the digital coordinator helps catch drift. Treat any design change as a trigger to update templates and location labels.
# Who owns the evidence and how long should it be kept?
/> Ownership and retention are commercial and contractual matters that should be set out at procurement. Typically, the principal contractor or client will expect the evidence to form part of the project record, with access defined in the contract. Make sure data rights, export formats, and retention periods are agreed before works start. For occupied buildings, also consider privacy obligations when storing images.
# What’s the quickest way to start on a live project that’s already mid-fit-out?
/> Start by defining two or three critical hold points where concealment is imminent and stand up simple capture templates for those. Issue location codes and a one-page guide to supervisors and key trades, and run a 48-hour audit cycle to stabilise quality. In parallel, map evidence to the CDE structure you’ll use at handover so nothing gets lost. Don’t try to retrofit the whole job at once; focus where risk is highest.
