Field notes: when a pit timestamp meets an auction photograph

There's a particular kind of quiet satisfaction in this work that almost never makes it into a report. It happens when two things that were never meant to be compared end up side by side on your screen: a dated image of a looting pit from your archive, and a photograph of an object from a sale catalog, a dealer's Instagram, or a seized-shipment inventory. The soil color in the backfill matches. The orientation of the cut matches. Even the cracked flagstone at the edge of the frame matches.
Most weeks in this work aren't dramatic, and this one mostly wasn't either. A tomb chamber gets disturbed sometime between two acquisition dates, and the imagery shows fresh spoil on one pass and nothing on the pass before it. Months later, an object with a plausible find-spot and a vague provenance line turns up somewhere it shouldn't. Nobody knocks anything over connecting the two. You just notice the dates don't contradict each other, and that the hole in the ground is roughly the right size for what's missing.
Provenance researchers have been doing some version of this for years, cross-referencing object photographs against known disturbance at documented sites. What's changed is less the method than the raw material available to feed it. A monitoring officer working a quarterly review used to be the bottleneck. You had the archive, the site list, and a review cycle that assumed you'd sit with a stack of frames and your own memory of what the ground looked like last time. That works fine for three sites. It stops working somewhere around thirty, especially when half of them are in a conflict zone you can't currently fly a drone over.
The part worth writing down from this particular week wasn't the match itself. It was how unglamorous the groundwork was. The disturbance had been sitting flagged in the quarterly comparison for two review cycles before anyone connected it to anything external. Nobody was hunting for a tie-in to a specific object when the flag first came up. It was just a new pit, dated, logged, filed next to the one from the previous quarter at the same tomb cluster.
The date is what made it useful later. Without a dated, before/after record of when the ground changed, there's no anchor point to measure a photograph against. You can say an object looks like it came from somewhere. You can't say when.
That's the unglamorous argument for doing the comparison properly every quarter, even for sites where nothing seems to be happening. A site that's quiet for three reviews and then shows fresh spoil in the fourth is the whole case, or at least the part of the case a monitoring file can actually stand behind. The rest, matching the object to the hole, is somebody else's specialty. Ours is making sure the hole has a date on it and that nobody has to eyeball a raw image dump to find it.
If your own review stack still means scrolling through archived frames site by site looking for backfill nobody flagged last time, that's the exact gap a dated before/after comparison closes, and it's the whole premise behind Looting Monitoring. It won't match a pit to a catalog photo for you, but it will tell you, with a date attached, when the ground changed and where to point the people whose job that matching is.
Keep the file boring. Boring, dated, and defensible is what gets taken seriously later.