Maintenance issue summary
A short report summarising identified issues across an asset or site, with location references and suggested follow-up. Designed for handover to maintenance and engineering teams.
Deliverables
From aerial capture to decision-ready infrastructure data.
Each project ends with structured outputs your team can actually use — not a folder of photographs. The table below is a quick view of the deliverables we produce, where each one fits, and who tends to use them.
Comparison
Deliverable, application, format, audience.
Most projects produce two or three of these — picked against the decision the data needs to support.
Data quality & scope
Deliverables are scoped outcomes, not defaults.
What you get out of a project depends on a handful of variables agreed at the scoping stage. Being explicit about these up front is the difference between a clean handover and an awkward conversation about expectations.
- Project scope What the data needs to support — planning, inspection, reporting, compliance, or change.
- Site conditions Terrain, vegetation, surface features, and visibility from the air.
- Access restrictions Land access, induction requirements, and operational constraints on the day.
- Weather Wind, rain, low cloud, glare, and conditions that affect both flight and image quality.
- Airspace constraints Controlled airspace, approvals, notifications, and exclusion zones.
- Required resolution Ground sample distance needed for the application — driven by altitude and sensor.
- Accuracy requirements Whether planning-grade or scoped survey-grade accuracy is needed downstream.
- Ground control Whether ground control points and surveyed references are required for accuracy targets.
- Processing workflow Photogrammetry pipeline, QC steps, and the formats expected at the other end.
- Accuracy expectations What the downstream user will treat as fit-for-purpose for their decision.
Reporting examples
Four common report shapes.
Most reporting we produce falls into one of these formats. Each is structured to be readable by the team it is delivered to and traceable back to the source imagery.
Corridor condition report
A continuous corridor review pairing orthomosaic context with geo-tagged inspection imagery and a structured observations log. Useful for pipeline, transmission, and utility corridors.
Construction progress update
A periodic update against a prior baseline — what has changed, where, and how it compares to expected progress. Designed for contractor and stakeholder reporting.
Asset inspection image pack
A structured library of asset-by-asset imagery, geo-tagged, organised, and ready to drop into the asset management system.
Talk to us
Discuss the deliverables your team needs.
The right deliverables are the ones that land in the systems and conversations your team already uses. Tell us about the workflow, and we will scope outputs to fit.