Skip to content
Orbitify

0204

Progress, quantities and quality from routine capture

Construction

Measure progress against programme, earthworks against design and installation quality against spec, from flights you were already going to fly.

During the build

Progress is reported by the people being measured

The monthly progress claim, the programme update and the quality record are assembled by the contractor, from the contractor's own photographs, and reviewed by somebody who was not on site that week. Nobody is lying. The only evidence available is partial, and by the time a variance is visible in the numbers it is six weeks old and has been built on top of.

One capture

A weekly pass that measures the programme instead of describing it

The same flight produces the progress percentage, the earthworks quantity and the quality exception, because all three are measurements of one model rather than three separate reports.

Steel frame of a building under construction against open sky
O-EYE13 behind

Structure behind programme, zone C

Zone C · levels 3 to 4

programme
74%
measured
61%
since last pass
+8%
captured
12 Mar
O-AGENTWO-0442Notified

Variance flagged before the monthly claim

Raised the week it happened rather than at month end, with the two captures it was measured from attached.

Identifiers, percentages and dates are illustrative.

Construction

What routine capture is worth

One pass a week, and four different questions answered from it.

Progress against programme

Percentage complete per discipline, measured from the model rather than estimated in a meeting. The comparison is against last week's capture, so the trend is real.

Quantities against design

Cut, fill and placed volumes computed from the surface, so an earthworks claim is checked against the ground rather than against a spreadsheet.

Quality exceptions

Installation checked against the design record while it is still accessible. A misaligned row found this week is an adjustment; found at commissioning it is a rework package.

Conditions worth flagging

Missing edge protection, unsafe access, stockpiles where they should not be. Surfaced from imagery you were capturing anyway, for a person to judge.

The measurement

Programme against what is actually there

One capture, read as a comparison. The tick is where your programme says the discipline should be; the bar is what the model measured.

  • Earthworks100%+0
  • Piling94%+2
  • Structure61%-13
  • Mechanical45%-3
  • Electrical12%-13

Percentages are illustrative and show the shape of a weekly read rather than a customer's project. What matters is where the two numbers come from: the bar is measured from the capture, and the tick is your own programme, imported from the schedule you already run.

Who does the work

Three modules, in this phase

Telemetry has little to say about a building that is not energised yet. The work here is capture, the record it is measured against, and the agent that compares them.

O-EYE

Detect

Flies the weekly pass and measures progress, quantities and installation quality against the design record.

Read more
O-OPS

Operations

Holds the programme, the work already raised and the quality record each finding is judged against.

Read more
O-AGENTacts

Decide & act

Compares the capture with the programme and raises the variance in the week it appears, inside the limits you set.

Read more
What you get

What leaves this phase

A weekly progress measurement

Percentage complete per discipline, measured rather than reported, with the capture it came from attached.

Earthworks and placed quantities

Volumes computed from the surface model against the design and against the baseline set before groundbreaking.

A dated visual record

One versioned capture per week, so any date in the build can be looked at again years later.

Exceptions raised in the week they occur

Quality and progress variances with their evidence, in your work system rather than in an email thread.

See, sense, know, then act
  1. 01O-EYEDetectInspection & digital twin
  2. 02O-ARCAnalyseSensors, IoT & telemetry
  3. 03O-OPSOperationsThe system of record
  4. 04actsO-AGENTDecide & actThe agentic layer

Every action writes back to the record, so the model sharpens with every job.

Questions from this phase

How often does a site need capturing?

Weekly is the usual cadence during active construction, because that is roughly the resolution a programme moves at. Sites with fast earthworks often want twice weekly early on and monthly once the structure is up. The planner adjusts rather than holding a fixed calendar.

Will the contractor accept measurements they did not produce?

Generally they prefer it, provided the method is agreed up front and the evidence is visible to both sides. A disputed claim argued from one shared model is a shorter conversation than one argued from two sets of photographs.

Does this work indoors or under structure?

Not from a drone. Aerial capture measures what it can see, and we would rather say so than imply full coverage. Interior progress today comes from your own checklists and photographs held in the same record. Ground and interior capture are on the roadmap and are not offered here as available.

What about airspace and site permissions?

Both are real constraints and usually the slowest part of starting. We plan around restricted airspace, and where flying is not possible the phase still runs on captures your own team takes, at lower fidelity and with that stated.

Bring the whole portfolio under one layer. Start with one site.