Field operations

A field workflow without lost handoffs

From intake and survey to operation and farmer handover.

Sir Airffic Go

Settle what you can before the crew reaches the field.

Updated 2026-10-30 · 5 min read

Agree at intake

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Confirm land access, crop, objective, timing, deliverables, price and contact. Coordinates alone do not describe boundaries, obstacles, access roads, water or neighbors. Keep request acceptance separate from authorization to operate.

Return survey findings to the map

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Update maps with a site survey. Record wires, trees, movement of people and animals, watercourses and sensitive crops. Agree roles for pilot, observer, product handler and farmer, including who decides when someone cannot be reached.

Finish by reconciling records

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Reconcile treated area, quantities, residue, unfinished areas, anomalies and next review date. Link flight records with agricultural work records. Provide a concise handover and retain detail under the same job ID for incidents, complaints or rework.

Separate flight completion from agronomic completion

SOURCE-BASED EXPLANATION

The Philippine TESDA competency standard includes post-operation cleaning, battery storage, waste management and records. A Thai sugarcane study found time savings from reusing flight plans without significant plant-height differences between the tested treatments. These sources inform this guide's proposed separation of flight completion, area treatment, farmer handover and subsequent agronomic evaluation.

Turn a diagnosis into an executable work order

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Record who detected the issue, who makes the agronomic decision and who executes it. For example, a weak-growth image should become a location-specific inspection request with a capture date; the inspector returns observations or sampling results. The farmer and agronomic adviser then choose treatment, monitoring or further investigation. Give the pilot a versioned instruction covering objective, field, exclusions, material, approved conditions of use, timing and the review owner. A coloured map alone is insufficient. If crop stage or material changes, return the instruction for review rather than replacing it through an informal conversation. Agree beforehand when work remains on hold because the decision owner cannot be reached.

Make the farmer's one-page handover actionable

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Lead the handover with familiar field names, date, completed and outstanding areas, next action and a contact. Put technical indices and flight records in a detail view, and label unresolved causes as awaiting inspection. A sentence such as 'The assigned inspector will check the inlet side of the north field and call with the result' connects location, owner and action. Ask the farmer to explain the next step in their own words, then correct misunderstandings. Provide equivalent information through print, phone or audio as needed. Acknowledgement records delivery of the explanation; it does not demonstrate crop-protection efficacy or yield improvement.

HandoffMinimum informationRecipient response
Imagery to inspectionField, location, date and questionObservations and anything unverified
Agronomy to operationVersion, target, purpose and conditionsFeasibility and changes
Operation to farmerCompleted areas, gaps and next ownerUnderstood next action and contact route

Assign ownership for interruptions, revisits and complaints

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

After interruption, preserve the actual treated and untreated areas rather than only a completion percentage. Before returning, review current crop conditions, previous application, weather and neighboring land; do not simply rerun the old route from the beginning. If material quantities do not reconcile with the work record, retain the discrepancy and assign investigation instead of entering a balancing adjustment. Give invoicing, rework decisions and farmer contact separate owners and deadlines. A common job identifier should connect instruction versions, actual work and communications so that complaints can be investigated without searching informally for the pilot. Update preventive measures after resolution.

Check your next steps

Saved in this browser. This checklist does not authorize an operation.
Article data JSON ↓