Process
Planned flights. Structured capture. Clear deliverables.
The flight day is the smallest part of a good drone mapping project. Most of the work that determines whether the deliverables are useful happens before — and after — the field team arrives on site.
Six steps from scope to delivery.
The summary view. Detailed step-by-step below.
- Step 01 01 / 06
Discovery and scope
We define the asset, the deliverables, the decision the data supports, and the constraints we need to work within.
Why it matters
Clarity on the decision the data supports prevents the most expensive mistakes downstream.
Output
Documented scope of work and agreed deliverables list.
- Step 02 02 / 06
Site and safety planning
A site risk assessment is prepared, access requirements are confirmed, and the work is aligned to the asset owner's safety system.
Why it matters
Inductions, permits, contractor management, biosecurity, and operational coordination all sit here.
Output
Site risk assessment, access plan, and confirmed safety alignment.
- Step 03 03 / 06
Flight planning and approvals
Flight plans are drafted at the agreed altitude, overlap, and capture parameters. Airspace approvals and notifications are obtained as required.
Why it matters
Controlled airspace, exclusion zones, and time-of-day constraints are confirmed before mobilisation.
Output
Flight plan, airspace approvals, and confirmed flight schedule.
- Step 04 04 / 06
Field capture
The field team mobilises, completes the agreed safety briefings, and executes the flight plan under the documented procedures.
Why it matters
Weather windows, asset operating state, and on-site coordination shape the actual flight day.
Output
Raw imagery, flight logs, and field notes.
- Step 05 05 / 06
Data processing
Captured imagery is processed through the photogrammetry pipeline, paired with thermal data where applicable, and quality-controlled against the agreed accuracy targets.
Why it matters
Processing time scales with data volume, project complexity, and the deliverables list.
Output
Processed orthomosaic, models, paired image sets, and QC notes.
- Step 06 06 / 06
Review and analysis
The processed data is reviewed, observations of interest are identified and annotated, and report drafts are prepared against the asset reference framework.
Why it matters
Findings are screening outputs unless explicitly scoped otherwise — they support, but do not replace, specialist assessment.
Output
Annotated imagery, observations log, and report draft.
What actually happens in each step.
What we do, who is involved, what to look out for, and what comes out the other end.
-
Step 01
Discovery and scope
What happens
We define the asset, the deliverables, the decision the data supports, and the constraints we need to work within.
Client involvement
Asset owner, operations or maintenance lead, GIS or engineering reviewer where applicable.
Key considerations
Clarity on the decision the data supports prevents the most expensive mistakes downstream.
Output
Documented scope of work and agreed deliverables list.
-
Step 02
Site and safety planning
What happens
A site risk assessment is prepared, access requirements are confirmed, and the work is aligned to the asset owner's safety system.
Client involvement
Site contact, safety officer, asset owner, drone operations lead.
Key considerations
Inductions, permits, contractor management, biosecurity, and operational coordination all sit here.
Output
Site risk assessment, access plan, and confirmed safety alignment.
-
Step 03
Flight planning and approvals
What happens
Flight plans are drafted at the agreed altitude, overlap, and capture parameters. Airspace approvals and notifications are obtained as required.
Client involvement
Drone operations lead, asset owner, airspace and regulatory contacts.
Key considerations
Controlled airspace, exclusion zones, and time-of-day constraints are confirmed before mobilisation.
Output
Flight plan, airspace approvals, and confirmed flight schedule.
-
Step 04
Field capture
What happens
The field team mobilises, completes the agreed safety briefings, and executes the flight plan under the documented procedures.
Client involvement
Drone field team, site contact, safety officer on site as required.
Key considerations
Weather windows, asset operating state, and on-site coordination shape the actual flight day.
Output
Raw imagery, flight logs, and field notes.
-
Step 05
Data processing
What happens
Captured imagery is processed through the photogrammetry pipeline, paired with thermal data where applicable, and quality-controlled against the agreed accuracy targets.
Client involvement
Processing team, with QC reference to the scoped accuracy and deliverable requirements.
Key considerations
Processing time scales with data volume, project complexity, and the deliverables list.
Output
Processed orthomosaic, models, paired image sets, and QC notes.
-
Step 06
Review and analysis
What happens
The processed data is reviewed, observations of interest are identified and annotated, and report drafts are prepared against the asset reference framework.
Client involvement
Drone analysis team, with input from the asset owner's technical reviewer where applicable.
Key considerations
Findings are screening outputs unless explicitly scoped otherwise — they support, but do not replace, specialist assessment.
Output
Annotated imagery, observations log, and report draft.
-
Step 07
Delivery and handover
What happens
Final deliverables are packaged in the agreed formats and structure, with a clear handover and an opportunity for follow-up questions.
Client involvement
Project lead, asset owner, downstream users of the deliverables.
Key considerations
Storage location, access permissions, file naming, and retention sit here.
Output
Final deliverables, handover document, and follow-up access.
-
Step 08
Repeat monitoring (if required)
What happens
Where the project is part of a monitoring program, repeat flights are scheduled against the agreed cadence and the baseline flight specification.
Client involvement
Asset owner, drone operations lead, on a recurring schedule.
Key considerations
Consistency between flights is what makes change comparison reliable — equipment, settings, and CRS stay the same.
Output
Repeat orthomosaics, change summaries, and comparative reports.
Plan a project
Plan a drone mapping project.
Tell us about the asset and the access conditions. We will respond with a scope and an indicative plan.