Operating model

The orchard scouting workflow: survey, decide, verify.

Most orchard tech dies in the same place. The flight happens. The map shows up. Then somebody still has to decide where to walk first, what to check, and whether last week's fix actually helped. This page is about that gap.

Rank the walkWrite the next checkCome back and verify

Why teams actually keep using it

The week gets smaller

The crew gets a shorter walk order instead of a fresh map to interpret from scratch.

The brief is plain enough to use

A useful result should say where to go, what to look for, and what can wait.

The follow-up teaches the system

The second pass matters. Without it, every alert looks equally serious forever.

Decision loop

The workflow should hold up on a busy week.

Nothing here is exotic. That is the point. The work is to keep the loop short enough that an orchard crew will actually keep using it.

Step 1

Survey

Capture on a routine, not on a heroic day

Use a repeatable flight or photo routine so the comparison next week still means something.

Step 2

Analyze

Compare against a baseline

Look for the few places that changed, not a perfect explanation for every pixel.

Step 3

Decide

Rank the walk order

Turn the signal into a short list of blocks or zones worth checking first.

Step 4

Act

Give the crew a real next check

The brief should say what to inspect when they arrive, not just that something looks off.

Step 5

Verify

Come back and see if the fix held

The second pass matters. That is where trust grows and false alarms start to fall away.

One concrete example

A flight should narrow the next walk, not create homework.

Say a 60-acre orchard shows one corner of Block 5 sliding against its own baseline. A weak workflow gives you a heatmap and leaves the rest up to the grower. A better workflow is blunter than that.

Where to start

Block 5, northeast corner

It changed enough to justify the first walk. The rest of the block can wait.

First check

Irrigation uniformity and emitter clogging

The pattern is local and shaped like distribution trouble, so start there before telling a bigger story.

Crew note

Re-scout after the adjustment

Give the team a follow-up window so the result becomes a closed loop, not a one-off hunch.

What that saves

Hours of wandering

The value is not the map by itself. It is the shorter week that follows.

Supporting notes

These two pages answer the objections that usually come next: whether RGB is enough to start, and why imagery by itself still leaves the hard part undone.