Custom Engineering · Scenario Customization

Custom Construction Management Systems

Construction systems succeed when they attach to the schedule the site already follows. A separate UAV reporting cycle is a reporting cycle nobody reads.

3 of 10Method note

Overview

Align the flight cadence to the site's existing reporting rhythm — weekly, milestone-based, or after each stage.
Deliver into the tools already in use: plan sheets, model viewers, issue trackers.
Distinguish measurement products (volumes, levels) from visual records; they have different accuracy claims.
Define who acts on a finding, and what happens if they do not.

Construction work is a repeat-visit problem

Construction and engineering survey is distinctive because the same site is visited repeatedly and the value comes from the comparison between visits rather than from any single one. That single fact drives the entire configuration: consistency of acquisition matters more than the quality of any individual epoch, and a slightly lower-quality dataset acquired identically every time is worth more than an excellent one acquired differently.

The consequence is that the first thing to design is the revisit discipline, not the flight. Fixed geometry, fixed sensor, fixed time of day where the sun matters, fixed ground control or a fixed georeferencing approach, and a documented storage and naming scheme. These are unglamorous and they are what make progress tracking and volume estimation possible at all.

It also means the engagement should be scoped around the comparison the client wants to make. Progress comparison, earthwork volume, stockpile inventory, boundary change and site drainage each require a slightly different acquisition discipline, and specifying them together at the start is cheaper than adding them later.

What usually needs adapting

The first adaptation is the acquisition standard. Sites are obstacle-rich and change continuously, which means flight geometry has to be defined against what is permanent — the site boundary, fixed control, a stable launch point — rather than against features that move. Our custom data acquisition standards work produces that document.

The second is the comparison workflow. What is compared, at what interval, with what tolerance, and who sees the result. Progress comparison typically runs at a fixed interval tied to the programme schedule; volume and stockpile measurement run when a payment or reconciliation event requires it; boundary and drainage checks run on condition. Each has a different cadence and a different output.

The third is integration with the systems the site already runs. Construction programmes use scheduling, quantity and document systems with their own formats, and airborne output that does not reach them gets used once and abandoned. Our GIS platform integration and API integration with business systems work covers connecting them.

Safety and operating discipline on active sites

Aerial work on an active construction site carries a safety discipline that is not optional and not the same as on open ground. Cranes, scaffolding, excavations, moving plant and a workforce not expecting an aircraft overhead all require separation rules, a defined exclusion zone, and a flight authorisation procedure that names who can say no.

Those rules should be written and briefed to site management rather than only to the crew, because the crew cannot control what happens below them. Where a site operates a permit system, aerial work should be inside it rather than alongside it.

The operating discipline also includes honesty about conditions. Sites generate dust, which affects motors and optics; they change layout between visits, which invalidates a flight plan drawn against the previous visit; and they are busiest exactly when the schedule pressure is highest. Our operating environment requirements work covers formalising this into something a crew can be trained against.

Acceptance for construction configurations

Acceptance should be stated against the comparison the client needs, not against the imagery. For volume and stockpile work, the criterion is the accuracy of the measured quantity against an independent check, and it should be stated as a tolerance rather than as a claim. For progress comparison, the criterion is whether the change being looked for is reliably visible at the acquisition interval used.

Consistency deserves its own criterion, because it is what makes the series usable: the same geometry and sensor across epochs, verified rather than assumed. Where a site changes in ways that force a geometry change, that should be recorded as a break in the series rather than silently absorbed.

Automated comparison, where included, needs conservative acceptance — what it flags for human review, and what it deliberately leaves to a person. Our AI performance acceptance note and the progress imagery comparison note together cover how we frame that.

Starting a construction engagement

The path is: identify the comparisons the programme needs; fix the acquisition standard against permanent site features; define the cadence and the output for each; agree the safety and authorisation procedure with site management; then run a pilot pair of epochs and verify that the comparison works before committing to a schedule.

Where the client already flies and needs only the comparison workflow or the integration, we scope that alone.

Send your site type, the comparisons you need, your cadence, your scheduling or quantity systems and your site safety procedures to our engineering team. We will propose the acquisition standard and the comparison workflow, and tell you what we would verify first.