Frontier incident log vs. daily imagery change log: what's the difference?

A river winding through a desert valley between rocky mountain slopes under a clear sky.

A frontier incident log and a daily imagery-based change log sometimes get filed for the same shift, but they are not recording the same thing. One is built from what patrol units reported on the ground. The other is built from what a sensor caught overhead since the last pass. Mix them up at the watch desk and you either double-count the same crossing or miss one entirely.

What goes in a frontier incident log

A frontier incident log is the written record a patrol unit or duty officer keeps of events tied to a person or a unit: a sensor alarm that got a response, a group apprehended near a mile marker, a vehicle stopped at a checkpoint, a radio call about foot traffic near a wash. Each entry ties to an incident number, a time, a unit, and usually a disposition: apprehended, turned back, lost trail, referred to another agency. It is a narrative record built from testimony and observation on the ground.

That makes it strong at the things ground truth is good at: counts of persons encountered, what got recovered, what charges applied. It is weak at anything nobody on the ground actually saw: a vehicle track that never triggered a response, a section of fence cut overnight in a spot no patrol drove past, a staging area that formed and cleared out before a unit ever rolled through.

What goes in a daily imagery-based change log

A daily imagery-based change log starts from a different place: a pass of overhead imagery compared against yesterday's, with whatever's different flagged. New foot trails. New vehicle tracks. A gap in fencing that wasn't there before. A cluster of vehicles or tents in a stretch of desert with no incident number attached to any of it, because no patrol unit was there to write one.

This log doesn't carry a name, an apprehension count, or a charge. What it carries is a location and a time window: this stretch of the line had new activity between yesterday's pass and today's. A lot of the line between ports of entry gets driven rarely enough that the first sign of a new crossing is the imagery, not a sensor hit or a patrol report.

Why the watch desk needs both

Treat the imagery log as a stand-in for the incident log and you lose the parts that depend on a human witness: who was encountered, what they said, what was seized. Treat the incident log as the full picture and you miss everything that happened in segments nobody patrolled that day. A fence cut at 3 a.m. in a low-traffic sector might not get an incident number for days, if it gets one at all.

The two cross-reference well when both exist. A new vehicle track flagged in the morning's imagery review gives a duty officer a grid reference to route a patrol toward, and that patrol's incident entry closes the loop with a disposition. Without the imagery side, that track sits unflagged until someone happens to drive past it.

For a watch desk running the line at daily cadence, the imagery side of this recordkeeping is where Border Monitoring fits: a standing feed of what's changed along the boundary since the last clean pass, broken out by location, so the morning imagery review isn't an analyst scrubbing archive tiles segment by segment.

If the incident side of your shift log is solid and the imagery side still runs on whoever has time that morning, that's the gap worth looking at first.

Get started

← Back to the blog