Public works and construction oversight

Independent satellite oversight of national infrastructure projects: earthworks volume, structural progress and schedule compliance verified from orbit, without asking the contractor.

The dependence this ends: Progress reports written by the contractor being paid

The contractor's incentive is not yours

Every large public infrastructure project generates paperwork: monthly progress certificates, quantity surveyor sign-offs, photographic records supplied by the entity being paid to produce them. Governments have known for decades that this is structurally compromised. What changed after 2022 is the cost of the alternative. Commercial very-high-resolution optical satellites now revisit most locations daily. Synthetic aperture radar penetrates cloud cover and works at night. The data needed to run an independent programme office already exists overhead; the question is whether the government has contracted to receive and interpret it.

The dependence being ended here is specific: the practice of accepting contractor-authored evidence of contractor performance. Road embankments reported as compacted and ready for surfacing can be measured for actual height and volume from orbit. Bridge piers reported as poured can be counted. Earthworks reported as 60 percent complete can be compared against the design drawings the government already holds. None of this requires confrontation on site. It requires imagery, software and an analyst who works for the ministry, not the construction firm.

What the sensors actually see, and what they cannot

Panchromatic optical imagery at 30 to 50 centimetre ground sample distance resolves individual pieces of plant and equipment, stockpile extent and structural elements above a certain scale. It does not reliably resolve rebar spacing or internal concrete quality. Those remain ground-truth problems. What imagery does resolve is presence, absence and approximate volume, which covers the majority of quantity-verification disputes on civil engineering contracts.

InSAR adds a dimension optical cannot: millimetre-scale surface deformation over time. A retaining wall moving laterally, a bridge deck settling unevenly, a dam embankment subsiding at a rate inconsistent with normal consolidation: these show up in interferometric phase stacks before they become visible to the eye or appear in any site report. The practical limit is that InSAR requires coherent surface returns, so heavily vegetated sites or freshly disturbed soil can degrade the signal. A programme office using both sensors in combination gets coverage that neither provides alone.

Video from orbit, short clips of 60 to 90 seconds from a low-Earth-orbit pass, adds activity verification: is the site actually operating at the reported intensity, or is it quiet between inspection visits? This is a supplementary check, not a primary measurement tool. Cadence matters more than any single sensor's resolution. A weekly optical revisit combined with monthly InSAR stacks and occasional video tasking gives a programme office a continuous, timestamped audit trail that is independent of anything the contractor produces.

The pathfinder: what a first programme looks like

A sovereign construction-oversight capability does not require a dedicated satellite at first. The pathfinder level uses commercial data procurement, a ground processing node and exploitation software configured for the specific project portfolio. The government owns the software licences, the processed archive and the analytical workflows. The satellite data is sourced from existing commercial constellations under contracts the government holds directly, so there is no intermediary who can be pressured to withhold or delay delivery.

Small-satellite optical missions of this class, where a government procures or co-procures a dedicated asset rather than relying on commercial tasking, have publicly reported budgets in the range of tens of millions of dollars for the satellite and ground segment combined. A pathfinder that relies on commercial data procurement and a sovereign processing node sits well below that, in the range of programme costs comparable to a modest government IT contract. The honest caveat: commercial data availability over specific sites is not guaranteed on any given day, and tasking priority for a small government customer competes with larger commercial buyers. A dedicated asset removes that dependency entirely, but that is a later decision, made once the programme office has demonstrated it can use the data.

What the government ends up owning

The handover is designed so the ministry's own analysts run the system by the end of the contract. That means trained staff, documented workflows, a processing environment the government controls and an archive that belongs to the government and cannot be withdrawn. Source-access terms for any software are agreed before signature. Hardware audit rights apply to any ground equipment.

The limits are worth stating plainly. The system verifies what can be seen from orbit at the cadences agreed. It does not replace quantity surveyors on the ground for final account settlement; it provides the independent evidence base that makes those negotiations less one-sided. It does not detect subsurface defects. It does not operate usefully through persistent cloud cover without the SAR component, which is why the sensor combination matters. A programme office that understands these limits will use the capability correctly and will not be embarrassed by a failure mode it was not warned about.

The audit trail that changes behaviour

The most significant effect of an independent satellite oversight programme is not the disputes it resolves. It is the disputes that do not arise. Contractors who know that earthworks volumes will be independently measured from orbit before payment certificates are approved tend to report those volumes accurately. This is documented behaviour in analogous contexts: fisheries vessels alter routes when they know satellite tracking is active, and deforestation rates in monitored concessions fall relative to unmonitored neighbours. The same dynamic applies to civil engineering.

A government that can demonstrate to its own auditor-general, its parliament and its development finance partners that infrastructure expenditure is independently verified from orbit is in a materially different position from one that cannot. The audit trail is timestamped, geometrically referenced and produced by a party with no financial interest in the construction contract. That is the asset. The satellite data is how you produce it.

What this mission is built from

High-resolution panchromatic optical imagers: Primary measurement sensor for structural progress, plant activity and approximate earthworks extent at sub-metre resolution.
InSAR mission configurations: Surface deformation monitoring to detect settlement, lateral movement or embankment behaviour inconsistent with design assumptions.
Video-from-orbit payloads: Activity verification at specific sites to confirm operational tempo between scheduled optical passes.
Exploitation and analysis software: Change-detection, volume estimation and timestamped audit-trail generation, configured for the ministry's project portfolio and operated by government analysts.

What you end up owning

Exploitation software licences, with source-access terms agreed before contract signature
Sovereign processing node and data archive, held on government-controlled infrastructure
Direct data-procurement contracts with commercial satellite operators, in the government's name
Trained programme-office analysts capable of independent tasking and product generation
Timestamped, geometrically referenced archive of all processed imagery and deformation products
Documented analytical workflows and quality-assurance procedures transferable to new staff

Handover is staged across the programme: analysts are embedded from month one, workflow documentation is produced in parallel with operations, and the government team holds primary operator status before the Satellize contract closes. Commercial data agreements and any ground hardware remain with the government after handover. Satellize retains no ongoing data access or system dependency.

Programme parameters

Pathfinder configuration	No dedicated satellite required at entry level; commercial data procurement plus sovereign ground processing node
Optical revisit (commercial tasking)	Daily to weekly depending on constellation and site latitude; guaranteed revisit requires dedicated asset
Optical ground sample distance	30 to 50 cm for primary quantity-verification products
InSAR deformation sensitivity	Millimetre-scale line-of-sight displacement per epoch; coherence degrades over freshly disturbed or densely vegetated surfaces
Ground segment	One processing node, ministry-hosted or government-cloud; no dedicated ground station required at pathfinder level
Operator team to sustain	Two to four trained analysts for a portfolio of up to 20 concurrent project sites
Programme timeline to operational capability	12 to 18 months from contract signature to sovereign operational status at pathfinder level
Cloud-cover limitation	Optical products degraded under persistent cloud; SAR component required for reliable coverage in tropical or monsoon climates
Escalation path	Dedicated small optical or SAR satellite procurable as a follow-on; publicly reported small-satellite missions of this class have budgets in the low-to-mid tens of millions of dollars

Sources

One contract, one accountable engineer

Commissioned as one programme, not a stack of contracts: spacecraft, launch, ground segment, mission control, training and handover are priced together. Source-access terms and audit rights are agreed in writing before signature. Request a site-specific data assessment.