How to verify an encroachment alert before you send a patrol

An alert lands in your inbox with a set of coordinates and a flag for new clearing inside the boundary. Before it goes on the patrol roster, five minutes at the desk can sort a genuine cultivation plot or fresh road from a fire scar left over from last dry season, or a shadow thrown by a ridge at the wrong time of day. Patrol time is the scarcest resource on the whole concession. A flag that turns out to be a cloud shadow still costs you the fuel, the vehicle, and two rangers' morning to find that out.

What actually causes a false positive encroachment alert

A monthly medium-resolution pass tells you where pixel brightness differs between two dates. Explaining why it differs takes someone who knows the ground, which is why these five causes trip an alert without anyone having cut a tree:

• Seasonal water and flooding. A floodplain that goes from green to bare mud between passes can read the same as a cleared plot if the system is only comparing reflectance.
• Cloud shadow. A cloud that happened to sit over your boundary on one pass and not the other leaves a dark patch that looks like new clearing until the next clear-sky image comes through.
• Fire scars. Controlled burns or lightning strikes outside your jurisdiction but near the line can show up as bare ground inside it, especially where the boundary follows a ridge rather than a river.
• Logging roads already on your permit list. If a concession holder has an approved extraction road and nobody updated the boundary layer, every month that road "reappears" as new.
• Agricultural fallow cycles. Smallholder plots just outside the line that get slashed and burned on a rotation can bleed a few pixels across the boundary at medium resolution, especially where the line itself was drawn from an old cadastral survey rather than a GPS walk.

None of these mean the alert is wrong to flag. They mean the flag needs a second look before it turns into fuel, a vehicle, and two rangers' time.

A patrol verification checklist that takes less time than writing the mission order

1. Pull the date and compare it to your fire and weather log. If there was rain or a burn reported in that block in the same window, check that first. It explains most of what looks dramatic and turns out to be nothing.

2. Check the shape against what encroachment actually looks like on the ground. A straight edge or a grid pattern reads as a plot or a road. An irregular blob that follows a drainage line more often reads as flood exposure or a natural die-off.

3. Look at the location relative to your boundary survey points, not just the map line. Boundaries drawn decades ago on paper and later digitized sometimes sit fifty to a hundred meters off from where the pillars actually are. A flag that's "inside" on the digital line might be outside the real one, or the reverse, which matters as much for the patrol as for the paperwork.

4. Cross-check against your permit and concession register. Approved roads, licensed selective logging, and community forest agreements inside your boundary will keep tripping alerts every pass unless you've noted them as known features.

5. Confirm there isn't an obvious access problem before you commit a team. A flag on the far side of a river crossing that's impassable this month needs a different plan than one a ranger can reach on the morning round.

6. Log what you decided, flag or stand down, and why. Six months from now, when the same corner lights up again, you want to know whether that was cultivation last time or a cloud shadow, without re-running the whole check from scratch.

Ground-truthing an alert means spending the two minutes that separate a coordinate worth a patrol from a coordinate worth a note in the log. A monthly pass can't carry your local knowledge: what's permitted, what burned last season, where the real pillar line sits. What it can do is show you, every month, exactly where inside the boundary clearing, a new road, mining or cultivation has shown up, so you're deciding what to verify instead of walking the whole perimeter to find out. That's the gap Encroachment Alerting is built to close.

If your boundary runs long and your patrol roster doesn't, it might be worth seeing what a monthly change flag looks like for your own block.