What is a disturbance count, and how do monitoring officers use one?

A disturbance count is the number of new ground disturbances at a monitored site between one imagery date and the next. That's it. No interpretation of intent, no legal finding, just a number: this many fresh looting pits, this many new vehicle tracks, counted and dated against the last frame you looked at.
It sounds almost too plain to need defining. But if you've sat with a tell or a necropolis site file for more than one review cycle, you know the term gets used loosely. Some officers mean "anything that looks different." Others mean only pits large enough to read as deliberate excavation. A few fold in natural erosion scarring because it shows up dark on the same band. None of that is wrong exactly, but it means a disturbance count from one officer's desk doesn't always mean the same thing as one from the next province over, or from the same desk a year later when someone else inherits the file.
What gets counted
For a heritage site file, the useful version of a disturbance count is narrow on purpose:
- New looting pits since the last reviewed frame, not the running total since the site was first surveyed
- Fresh vehicle tracks that weren't there last quarter, distinguished from the access road or herding paths that have always crossed the perimeter
- A date range tying the count to the two frames compared, not just "as of today"
Leave out vegetation change, structural collapse unrelated to excavation, and anything that reads as agricultural disturbance on adjacent land. Those belong in the broader condition assessment, not the disturbance count itself. Mixing them in is how a count balloons to a number that looks alarming in a report but doesn't tell the next reader what happened on the ground this quarter.
How the count gets used
In practice, the number does three things for a monitoring officer, and all three depend on it being comparable quarter to quarter.
First, it's the line that goes in the site condition report, the one a heritage body or a field partner reads without opening the imagery themselves. "14 new pits, 3 new vehicle tracks, Q3 to Q4" says more in one line than a paragraph describing the frame.
Second, it's what triggers escalation. A count of two or three new pits near a known access point might sit in the file. A count that jumps from three to thirty, or that shows tracks pushing toward a sector that was previously untouched, is the kind of change that moves a site up the list for the next field visit or for a note to the relevant ministry.
Third, it's the only honest way to compare a site against itself over time. Absolute pit totals for an unexcavated tell can run into the hundreds from historic looting that predates any monitoring program. That cumulative number tells you almost nothing about this quarter. The disturbance count, scoped to what changed since the last review, is the number that actually moves when something happens.
The catch is getting there. Producing a defensible dated pit and track count means pulling the archived frame from last quarter, pulling the current one, and going image by image across every monitored site to spot what's new and what's just the same old crater seen from a slightly different sun angle. Done by hand across a caseload of sites, that's most of a review cycle gone before you've written a word of the report.
That's the comparison work Looting Monitoring carries out: a quarterly before/after pair for each site, with new pits and tracks flagged and dated against the last reviewed frame.
If your next review cycle is coming up and the site list is longer than the hours you've got, it's worth seeing what a dated disturbance count looks like before you start the manual pass.