Gateway 3 puts evidence under the microscope. For high‑risk residential and other complex schemes, the Building Safety Act has shifted completion from a paperwork sprint to a demonstrable proof exercise. Reality capture—360° photography, laser scanning and mobile mapping—has become the practical way to show what’s been installed, where, when, and by whom. The tech isn’t the hard part; getting the scope, interfaces and acceptance criteria right is. If you want building control and the client’s safety team to accept your data as proof, the procurement brief must be idiom‑tight and site‑practical.
TL;DR
/>
– Define the capture types, frequency and acceptance criteria in the contract, aligned to ISO 19650 naming and the golden thread.
– Tie capture windows to programme hold points for firestopping, structure and MEP before close‑out.
– Make data custody explicit: who owns it, where it’s hosted, and the retention period post‑handover.
– Require model alignment and metadata so evidence links to zones, assets and WIs—not just pretty pictures.
– Budget for access and labour impacts: lifts, night shifts, escorts in occupied areas, and re‑captures after changes.
Specifying reality capture for Gateway 3 in UK contracts
/> Procurement needs to turn “we’ll take some scans” into a scope that will withstand regulator scrutiny. State the capture methods (e.g., static LiDAR scans in plant rooms and risers; 360° stills along corridors; external photogrammetry of façades), the intended purpose (evidence for completion, dimensional validation, or both), and the minimum spatial coverage. Avoid promising a digital twin unless you actually need model outputs; for evidence, point clouds and indexed photo tours are usually sufficient.
File formats and interoperability matter. Require neutral exports (E57/PTS for scans; JPG/EXIF for imagery; CSV/JSON for metadata), and define how the supplier will align data to the project coordinate system and gridlines for model overlay. Insist on ISO 19650 naming conventions and Uniclass classification so each capture ties to a zone, level, location code, and system. If you’re delivering COBie or asset registers, ask the supplier to map capture references to asset tags.
Decide where the golden thread lives. State the Common Data Environment (CDE) location, upload cadence, approval workflow, and security level. Hosting on a third‑party tour platform is fine, but the contract should also require archive exports so you’re not dependent on a licence at Gateway 3. Clarify data ownership and retention, particularly on occupied sites where GDPR applies.
Capture frequency is a commercial decision. Set out hold points—pre‑close of ceilings, before boxing‑in, post‑firestopping sign‑off, pre‑commissioning in plant rooms. Price recapture or variation handling: if a service is altered after evidence is taken, who pays to re‑shoot? Define acceptance tests: spot checks by the Principal Designer or quality team, pixel clarity thresholds, scan registration error bands, and the sampling plan for review.
H3: A live UK scenario: recladding and compartmentation in an occupied high‑rise
A principal contractor is recladding a high‑rise housing block while upgrading compartmentation. The programme is tight because access to flats is limited to short agreed windows. The digital engineer proposes 360° corridor sweeps and static scans in risers, with external photogrammetry of the façade during mast climber moves. The fire‑stopping subcontractor wants proof of condition before sealing, building control wants line‑of‑sight evidence per zone, and the client’s safety team insists the data sits in the project CDE. A night shift capture window is agreed for live floors, with escorts for resident privacy. Two weeks in, a late MEP route change forces ceiling re‑openings; the contract allows for a recapture allowance without dispute. Gateway 3 evidence packs pull directly from the indexed captures, linked to inspection records and location tags.
H3: Procurement checklist for Gateway 3‑ready capture
– State capture purpose by system and zone (e.g., risers/MEP/firestopping/façade), not just “site‑wide”.
– Specify coordinate system, grid alignment, and model overlay requirements for scans and imagery.
– Define hold points and capture cadence tied to programme activities before concealment.
– Require ISO 19650 naming, location codes, and metadata linking to WIs, ITPs and asset tags.
– Set data custody: CDE location, hosting approach, archive exports, ownership and retention term.
– Include acceptance criteria: clarity, registration quality, coverage checklist, and sample audit process.
– Price recapture and access logistics (escorts, out‑of‑hours, lifts, plant, harnesses) as line items.
Managing interfaces, evidence risk and programme impact
/> Reality capture only reduces risk if it is integrated with quality control. Link capture to ITPs: when a fire‑stopping inspection is signed, the photo set must reference the location code and the inspection record. For risers and service corridors, walk paths should be planned with the MEP coordinator so evidence is collected before insulation wraps and acoustic treatments obscure labelling.
Evidence risk sits across multiple parties. Make the Principal Contractor accountable for the evidence pack, but embed obligations in trade packages: fire‑stoppers to present works ready for capture; MEP to tag assets; façade teams to allow drone or mast access on agreed days. If parts of the building are occupied, bake in privacy controls—blur faces automatically and keep capture inside agreed working lines. Site inductions for capture operatives should cover hot works, working at height, public interface and PPE; you don’t want a laser tripod on a live corridor without a spotter.
Plan for change. A late RFI or coordination update can make yesterday’s evidence misleading. Set a change notice that triggers re‑capture and flags superseded images as “historic” to avoid confusion at Gateway 3. For model comparison, define a simple traffic‑light workflow: green (conforms), amber (tolerance query), red (NCR) with named reviewers and turnaround times that won’t stall the programme.
Don’t forget external scope. For façades, agree drone flight plans with site logistics and the principal designer, and check local restrictions. If drones are not feasible, specify photogrammetry from mast platforms with calibrated overlap. Keep weather in the plan; bad light and rain can render photos worthless for reading labels or sealant lines.
H3: Common mistakes
– Treating reality capture as a single “one‑off” event. Without hold points tied to concealment, you miss the evidence window.
– Leaving metadata to the end. If location codes and asset tags aren’t embedded at source, linking to the golden thread becomes a manual slog.
– Outsourcing hosting without an archive clause. If a platform licence lapses, you lose access to your evidence at the worst time.
– Using scans for design validation only. Gateway 3 needs evidential clarity, not just geometry; 360° imagery of fire collars and dampers is often the clincher.
Proving value at Gateway 3: acceptance, time and rework
/> Value is realised when reality capture shortens the review loop and reduces intrusive checks. Set KPIs around acceptance rates at first submission, the proportion of inspections closed using digital evidence, and the number of re‑opens avoided. Track how quickly building control queries are answered—being able to point to a timestamped, location‑coded image in the CDE can resolve a question in hours rather than days.
For the client and facilities team, link captures to the asset information model. A QR code on a riser door that opens the relevant pre‑close imagery has real operational value. Where you have point clouds in plant rooms, keep them aligned to the as‑built model so late changes are visible; a simple “model vs scan” view often flushes out unrecorded deviations before handover.
Commercial control benefits from predictable variation handling. If the contract has priced recaptures and access logistics, disputes are reduced when the programme shifts. At final account, the evidence pack can protect against claims of missing inspections or undocumented rework.
Two things to watch: increasing alignment between building control bodies on what “good evidence” looks like, and market movement towards standardised metadata schemas that plug straight into CDEs. The projects that get through Gateway 3 cleanly will be the ones that treat reality capture as a controlled quality process, not a glossy afterthought.
FAQ
# What reality capture mix works best for Gateway 3 evidence?
/> Most teams combine 360° corridor and room imagery with targeted laser scans in risers and plant rooms. External façades can be captured by drone or mast‑based photogrammetry depending on access. The right mix depends on what needs proving: geometry validation pushes you towards scans, whereas installation evidence often leans on clear, indexed photos.
# How should we handle data ownership and hosting in contracts?
/> Make it explicit that the client or principal contractor owns the raw data and processed outputs. Allow hosted viewers for day‑to‑day use, but require periodic archive exports into the project CDE so access isn’t tied to ongoing licences. Include a retention period that matches the client’s golden thread policy.
# Who should be responsible for pressing the button on site?
/> Keep overall accountability with the principal contractor, but decide early whether a specialist supplier, digital engineer or trained QA inspector will operate the kit. What matters is consistency: routes, vantage points and metadata must be repeatable and auditable. Trades should be obligated to present areas ready for capture at agreed times.
# Can reality capture replace physical inspections for firestopping and MEP?
/> It can support and evidence inspections, but it rarely replaces competent eyes at the right time. The better approach is to integrate capture into the ITP so visuals are collected immediately after inspection and linked to the record. Building control may still want selective physical checks; good digital evidence can reduce how many.
# How do we manage changes that make previous evidence outdated?
/> Set a clear change control trigger: if a service route, product or detail changes post‑capture, log it and schedule a re‑shoot. In the CDE, mark superseded images as historic and link the new evidence to the updated drawing or model. Price re‑captures in the contract so there’s no wrangle when the programme flexes.
