Construct IQ

Reality Capture Standards for Owners: Writing Requirements That Work Across Every Project

By Kush Agarwal, President and CEO, YelloSKYE. Published 2026-10-27.

Executive Summary

• The Question: How can an owner running many projects make sure every contractor's drone flights, 360° walks and scans are consistent, comparable and still usable after handover?
• The Answer: Write a reality capture standard and issue it with every contract. It should set methods by phase, a minimum cadence plus hold-point captures, coverage, naming, formats, data ownership, access and acceptance, and it should link captures to payment claims and handover so compliance is part of getting paid.
• The YelloSKYE Angle: Construct IQ captures every site in a portfolio with the same drone, 360° and fixed-camera parameters, and DEX gives the owner one record per site that leadership can compare side by side.

A reality capture standard is the owner's rulebook for how its construction sites are recorded: which methods, how often, what must be covered, how files are named, what is delivered, and who owns it. Issued with each contract, it turns site imagery from something every contractor does differently into a consistent record the owner can compare across projects and keep for the life of the asset.

Without one, an owner with ten active projects usually ends up with ten capture habits: monthly drone flights saved to one contractor's cloud drive, phone photos on another site, a third vendor's portal on a fourth. Each may be fine for that project team. None of it adds up to a portfolio view, and most of it leaves with the contractor at completion. This guide sets out what to put in a standard, how to write it into contracts and how to roll it out. It draws on how Construct IQ, our construction monitoring solution, runs uniform capture across multi-site portfolios. For an overview of the capture methods themselves, see our reality capture guide.

Why a requirement to "provide photos" is not enough

Many contracts already include a line asking the contractor to supply progress photographs. That line rarely produces a usable record, because it leaves every important decision to whoever picks up the camera.

• No comparability. Different routes, angles, intervals and naming mean this month's images cannot be lined up with last month's, let alone with another site.
• No coverage guarantee. The areas that matter most, such as services before ceilings close, are the ones most often missed under time pressure.
• No ownership. The files sit in the contractor's systems, and access ends when the contract does.
• No acceptance test. Without a definition of a complete capture, there is no basis for rejecting a poor one.

A standard fixes these by defining outcomes the owner can check.

What a reality capture standard covers

The table below is a working outline. Each row becomes a short clause or schedule in the contract documents.

Methods by phase

Name the methods for each stage, not just in general. A typical building project might use a drone survey for the site baseline and earthworks, drone flights through the structure, 360° interior walks from enclosure onwards, fixed cameras on critical zones, and laser scans where geometry has to be checked against the model. Infrastructure and land-heavy projects lean more on aerial survey.

Cadence and hold points

Set two kinds of trigger. A routine keeps the timeline continuous, so a reviewer can see when something started. Events protect moments that cannot be recreated: before backfill, before each pour, before walls and ceilings are closed, and just before each payment claim. The second list matters more than the first, because a missed routine flight can be recovered next week and a missed pre-concealment capture cannot.

Coverage and routes

Define a complete capture with a route, not a description. For interiors, mark the walking route and the rooms that must appear on each level. For drone flights, fix the boundary, altitude and overlap so each flight covers the same ground. Fixed routes are what make two dates comparable.

Quality and accuracy

Separate visual quality from measurement accuracy. Most captures are for seeing, and the test is whether a reviewer can read what is needed: labels, fixings, sleeves, markings. Where captures are used to measure, for example earthwork volumes or positions against design, require survey control and state the accuracy. On YelloSKYE projects, RTK-GNSS drones combined with ground control points deliver sub-5 cm positional accuracy for survey-grade outputs.

Location and naming

Use one location hierarchy across every project, ideally the same codes the owner will use for the asset register after handover. Our guide to construction handover documentation shows a naming scheme that carries from capture into operations.

Formats and deliverables

Ask for open formats as the master copy so the record does not depend on a single tool, with native files supplied alongside where they help. Whatever platform holds the live record should be able to export it without loss: on DEX that covers CAD files, point clouds, orthomosaic maps and 3D models in standard formats.

Ownership, access and security

Decide before the first flight who holds the account. On most portfolios the owner should: it keeps the record with the asset, lets the owner see every project in one place, and makes contractor changes painless. Contractors receive the rights they need to upload and review, and the owner controls what other parties see and when. Our guide to drone data security covers access control and data residency questions in more depth.

Writing the standard into contracts

A standard only works if it has the same weight as the rest of the specification.

Put it in the contract documents

Attach the standard as a schedule to the employer's requirements or specification, and reference it from the clauses on progress reporting, payment and completion. A standard that sits in a separate guidance note is treated as optional.

Link it to payment

The most reliable lever is to make a current, accepted capture a supporting document for each progress payment claim. Contractors then plan captures into the week rather than assembling them afterwards. In our contractor billing disputes use case, drone captures timed to monthly billing cycles let project managers check claimed progress and reduce verification site visits by up to 80%.

Link it to completion

Make the full capture history, in the agreed formats and structure, part of the handover deliverables and the final account. If it is not complete, the handover is not complete.

Specify outcomes, not devices

State coverage, quality, accuracy, formats and turnaround, and leave the choice of equipment to the contractor or capture provider. Device lists go out of date, and they move responsibility for poor results back to the owner.

Allow for who does the capturing

Some owners appoint one capture provider across all projects; others require each contractor to capture to the standard. Both can work if the standard is the same. YelloSKYE's certified pilots or a project's own site teams can carry out capture, and 360° walks are simple enough for any site worker to run on a fixed route without specialist training.

Rolling the standard out across a portfolio

Pilot on one project first

Run the standard on one live project for a few months before issuing it everywhere. Check which clauses contractors struggle with, which captures reviewers actually open and where the turnaround falls short. Adjust, then issue version one.

Name one owner of the record

Appoint a single person or team on the owner's side to maintain the standard, review compliance across projects and answer contractor questions. Without that role, each project drifts back to its own habits.

Use the record in the owner's own meetings

Contractors take the standard seriously when the owner's project managers open the latest capture in progress meetings, refer to it in requests for information and use it to approve claims. If the owner never looks, the captures stop.

Compare sites on the same footing

The payoff of a standard is portfolio comparison. Our portfolio monitoring use case is a worked example: one set of capture parameters for drones, 360° cameras and fixed cameras was applied on every project, with all of it feeding a single DEX dashboard. A review of the whole portfolio, over ten sites, then took leadership half an hour, and tying contractor bills to that shared baseline cut billing disputes by 90%.

To judge whether the programme is paying for itself, our reality capture ROI guide sets out the cost and benefit lines to track. For owners building their own drone capability rather than buying it in, see our guide to starting a construction drone programme.

Where owner standards usually stall

Checklist: a one-page capture standard

1. State the decisions the record must support.
2. List methods by project phase.
3. Set a minimum routine cadence and a list of hold-point captures before concealment and before each payment claim.
4. Define coverage with fixed routes, boundaries and room lists.
5. Separate visual quality tests from measurement accuracy requirements.
6. Issue one location hierarchy and file naming convention for every project.
7. Name open master formats and the handover export structure.
8. Confirm the owner holds the account and define contractor access rights.
9. Set turnaround times and an acceptance check.
10. Attach the standard to the contract, link it to payment claims and completion, and pilot it on one project before rolling it out.

Explore Construct IQ