8 min read
Interior and exterior capture of what is really there, registered into one clean point cloud your architects, engineers and contractors can measure and design against.
Aerial survey flights turned into orthomosaics, elevation and terrain models, and stockpile or earthwork volumes for claims and takeoffs. Roof and facade imagery without a lift.
The point cloud modelled into BIM at an agreed level of detail, with every element checked against the scan before handover. We model what the project needs, not everything the scanner saw.
When drawings are missing or no longer match the building, we capture the space and redraw it as it stands: plans, sections and elevations measured from the scan, with the tolerance stated.
We walk your site with 360 cameras on a recurring schedule and turn every visit into a browsable, dated record. Navigate the site room by room from your desk, at any point in the build.
Scheduled flights and walkthroughs build a dated archive of what was built, when, and by what stage. When a change order, a claim or a warranty question arrives years later, the record is already there.
Reality capture is delivered at a stated level of detail. More is not better. More is slower and more expensive, and a model built for one purpose can be the wrong model for another. So the level is agreed before capture, not discovered afterwards.
Major elements and systems in the right size, shape and location. Enough to route services and check clearances.
Specific assemblies with dimensions a designer can work from, and the interfaces between them where they matter.
What was actually installed, with the geometry checked back against the scan rather than against the old drawings.
Verified geometry plus the asset attributes your maintenance system needs. Attributes are scoped item by item.
LOD numbers describe the model. LOD 500 is the odd one out: it is not more geometry, it is field verification, meaning the element was checked on site rather than assumed. That is worth paying for on the assets you will maintain, and rarely worth paying for on everything else.
Every level of detail has a matching decision on the capture side: how densely the site is scanned and how tightly the scans are registered together. Terrestrial scanning is normally set somewhere between a few millimetres and a couple of centimetres between points at working distances, and drone mapping normally lands in the low centimetres of ground sample distance. Both ranges are wide on purpose. We agree the target with you up front, report what the registration actually achieved, and state it with the deliverable. It is a measured record within a stated tolerance. It is not a legal survey.
Recurring capture is not just insurance. Teams that document systematically measure it in hours saved and rework avoided.
fewer capture hours after moving from manual photos to automated 360 capture, for about 75x more images.
of reality capture users report saving multiple hours every week versus manual documentation.
in rework avoided on a single project by proving what was behind the walls from dated photos.
Published results from other firms’ case studies and customer surveys, not Ventro results. Results vary by project.
Bring the building, the site, or the project, and what you need to do with the result. We will come back with what to capture, at what level of detail, what you receive, and what it costs. If a simpler deliverable answers the question, we will say so.
Existing conditions are usually one mobilisation. Documenting a live build is a rhythm, so that schedule is set per project and per phase, and it changes when your site does.
Fast-moving phases: framing, MEP rough-in, anything that gets covered up.
Steady phases and long builds where a regular rhythm keeps everyone aligned.
Before concrete pours, before drywall, at closeout: capture exactly when it matters.
Coordination, renovation design, an as-built record, a handover, or a progress archive. That decision sets the level of detail, the scan density, and what actually gets modelled.
A technician scans the space, walks it with a 360 camera, and flies the drone where it helps. Active and occupied sites are fine.
Scans are registered and checked, then delivered as point clouds, drawings, models, or a dated walkthrough, with the accuracy we achieved stated in the handover.
It depends on what the capture is for. A registered point cloud, an orthomosaic and terrain model, a BIM model, a drawing set of existing conditions, a dated 360 walkthrough, or several of those together. Formats and file types are agreed at scoping so the output opens in the software your team already runs.
The level the use case justifies, agreed in writing before capture starts. A coordination model, a renovation design basis, an as-built record and a facility handover are four different levels of effort, and modelling everything to the maximum mostly buys delay. We scope the level first, then capture to suit it.
That is a scoping question, not a fixed number. Accuracy depends on the method, the distances, the control, and what the site allows on the day. We agree a target range with you before the first visit, tell you what the registration actually came out at, and state it with the deliverable. Reality capture is a measured record within a stated tolerance. It is not a legal survey and does not replace one.
For progress documentation, on your schedule. Every two weeks, monthly, or tied to project milestones: we set the cadence per project and adjust it as phases change. Fast phases usually justify more frequent visits. A one-off existing-conditions capture is a single mobilisation.
Because walls close. Once drywall is up, the only record of what is behind it is the one you captured. Documentation pays for itself the first time a dispute, a change order, or a warranty question turns on what the site looked like on a specific date.
Capture is the measurement and what comes straight out of it: scans, point clouds, drone mapping, 360 records, models and drawings of existing conditions. Twin is what happens when a building model becomes something you run the building from, connected to your space, asset and maintenance workflows. Most twin work starts with a capture. Plenty of capture work never needs to become a twin.
