Gateway 3 hands over more than keys. It hands over legal accountability, a live asset, and the expectation that what’s built matches what was designed—especially for safety‑critical elements. Reality capture is the fastest way to evidence that reality: laser scanning, mobile mapping, 360 imagery and drone outputs stitched into a clear audit trail. Done well, it shortens disputes, de‑risks sign‑off with the building control approver, and anchors the “as‑built” record in something more reliable than redlines and memory.
TL;DR
/>
– Build a capture plan tied to information requirements, tolerances and spaces that matter for safety and maintenance.
– Match tools to tasks: static laser for accuracy, mobile mappers and 360s for coverage, drones for façades and roofs.
– Track metadata and chain‑of‑custody so each dataset is time‑stamped, georeferenced, and linked to zones, trades and packages.
– Close the loop: raise issues from captures, get them resolved, then recapture to prove the fix.
– Deliver accessible outputs: point clouds for coordination, navigable 360 tours for site teams, and concise extracts embedded in the CDE and handover pack.
Reality capture for Gateway 3 in plain English
/> Reality capture means creating a measurable, time‑stamped digital record of site conditions using sensors. The staples are terrestrial laser scanners (high accuracy, tripod‑mounted), mobile SLAM units (fast, good enough for many interiors), 360 photo/video rigs (narrative and context), and drones for externals. For Gateway 3, the focus is not just “nice visuals” but evidence: does the firestopping match locations and types? Are penetrations logged and sealed? Do door sets and risers align to schedules? Can an approver or future maintainer see, measure and trace decisions?
The capture only earns its keep if it connects to your information requirements. Start with a simple matrix: what you need to prove, where, to what tolerance, how often, and in what file format. Tie that to the programme so scanning isn’t an afterthought squeezed into night shifts or after finishes go in. Then decide: self‑perform with in‑house kit and a digital engineer, or procure a specialist who can scale when the programme kicks.
How the workflow runs on real UK projects
/>
– Plan and brief. Define Gateway 3 outputs with the client team, principal designer and building control approver. Put zones, access windows, and safety‑critical items (compartmentation, cavity barriers, fire dampers, structural inserts) on the capture map. Set naming and metadata rules that match ISO 19650 conventions and your CDE.
– Field capture. Lock in survey control early. Use static scans for cores, risers, and plant where millimetres matter; deploy mobile SLAM and 360s for long corridors and flats where speed trumps hyper‑accuracy. For façades and roofs, schedule drone flights around crane lifts and exclusion zones.
– Processing and registration. Register point clouds to control; geotag 360s by level, grid and room. Keep raw data immutable and create publish sets for coordination and review. Automate filename and attribute checks so nothing lands in the CDE without the right metadata.
– Validation and issue creation. Compare point clouds to design models to spot clashes, measure offsets, and verify door swings, soffit heights and service clearances. From 360 tours, pin defects and missing tags. Push non‑conformances into your QA platform with a link back to the exact scan or pano.
– Close‑out and recapture. Once a trade fixes a snag, recapture the specific area at low effort—often a quick 360 set or small SLAM loop—to evidence the change. Update the issue and mark it closed with visual proof.
– Package for handover. Deliver the “long form” data (registered point clouds, orthophotos, 360 tours) and a crisp “short form” for approvers and FM: curated snapshots, dimensioned extracts and a location index. Embed links in PDFs that open the exact view in the CDE.
# Site scenario: mixed‑use tower under programme squeeze
/> A project manager on a 25‑storey residential‑over‑retail scheme is chasing Gateway 3 while façade snagging drifts. The digital engineer has a static scanner booked for risers and the plantroom, but access clashes with a lift install. The fire subcontractor claims all dampers are tagged and accessible; the clerk of works isn’t convinced. A weekend drone slot for the podium roof is pulled due to neighbouring events, and the main contractor has only two night access windows left before retail fit‑out. The team switches to a hybrid: static scans for basement and risers, a mobile mapper for typical floors, and 360 capture for apartments as the cleaning team exits. Issues flagged from the captures push back into the snag list, and quick recaptures verify fixes before ceilings close.
Data that survives Gateway 3 scrutiny
/>
– Make the audit trail boringly clear. Seal raw data; publish derived sets; log who captured what, when, where, and why.
– Keep spatial consistency. Use common coordinates across design models, scans and 360 tours so reviewers can move between them without guesswork.
– Don’t smother approvers in gigabytes. Pair heavy datasets with a one‑page index of links to problem areas, safety‑critical verifications and as‑built dimensions.
– Map captures to packages. Label by trade, zone, and element ID so you can answer “show me level 12 riser R3 post‑firestopping” in seconds.
# Common mistakes
/>
– Leaving capture until finishes are installed, making evidence of concealed works patchy or impossible. Push key captures pre‑cover‑up.
– Treating 360 tours as decoration rather than evidence. Anchor every pano set to zones, dates and package scopes.
– Ignoring tolerances. Not all areas need static‑scan accuracy; equally, some do—choose tools based on purpose, not convenience.
– Dumping unstructured files into the CDE. Without strict naming and metadata, data becomes a haystack at the worst possible moment.
Fixes that actually land on site
/> Lock capture windows into the short‑term lookahead and site access plans. Treat scanning like a delivery or pour—book lifts, clear zones and put it on the whiteboard so trades expect it. Create a “capture before cover” rule for risers, penetrations and fire stopping, visibly signed off by the package lead and clerk of works.
Give supervisors something they can use on a phone or tablet during inspections. A room index linked to 360s, with clickable markers for penetrations and tags, saves arguments and time. For accuracy‑critical checks, pre‑define dimension call‑offs—soffit to finished floor, door set rough opening, plant plinth level—then extract those measurements from the point cloud and place them on a simple annotated sheet.
Where supply chains vary in digital maturity, pair them up. Let the reality capture provider host a toolbox briefing for MEP and firestopping crews: what’s being captured, how fixes will be evidenced, and what “done” looks like. Build in a small contingency pot for recaptures; it’s cheaper than arguing at the gate.
# Checklist: capture‑to‑handover essentials
/>
– Define information requirements by element: what to prove, where, tolerance, and file format.
– Fix survey control early and align all captures and models to it.
– Select the right mix of tools per space: static scan, mobile SLAM, 360, drone.
– Enforce metadata: zone, level, grid, package, date, and capturer on every dataset.
– Push non‑conformances from captures straight into the QA system with live links.
– Recapture only what changed and attach proof to closed issues.
– Deliver a navigable 360 tour plus curated dimensioned extracts alongside point clouds in the CDE.
The market is moving towards lighter mobile scanning, automated compare‑to‑model checks, and CDE integrations that make evidence unavoidable rather than optional. Expect client teams to start asking less “did you scan?” and more “show me the proof, by location and date, in two clicks.”
FAQ
/>
What reality capture tools are acceptable for Gateway 3 evidence?
Acceptability is about fitness for purpose rather than a single mandated tool. Static laser scans are strong where accuracy is critical, while mobile mappers and 360 imagery work well for broader coverage and narrative. Drones help for façades and roofs when scaffold views are limited. The key is to document why each tool was used and how it meets the information requirement.
# Who should own and host the captured data?
/> Ownership is usually set in contracts, but the main contractor typically holds the working set in the CDE during delivery. For handover, clients increasingly expect durable access without specialist software and clear rights to the raw data. Agree up front who pays for long‑term hosting and what formats are guaranteed to remain usable.
# How do we avoid clashes between scanning and live site activities?
/> Treat capture as a planned operation with permits, access windows and a named lead. Coordinate with logistics so hoists, lifts and plant moves don’t block scan lines or flight paths. Short nightly or early‑morning windows often suit corridors and cores, while weekend slots may be best for drone work over public interfaces.
# Can subcontractors contribute their own captures?
/> Yes, and it can speed close‑out, but agree standards and a validation process. Set minimum device specifications, file formats, metadata and how datasets are checked into the CDE. A central coordinator should review and register third‑party captures to maintain a single source of truth.
# How do we link captures to the QA and snag process?
/> Use your QA system or CDE to host issues with deep links to specific panos or point‑cloud views. From compare‑to‑model checks, raise non‑conformances with location, photo/scan evidence and required action. After fixes, attach a targeted recapture so the closure is provable without another site walk.
