Archival satellite imagery vs. tasking a new pass for heritage site monitoring
A monitoring officer with a dozen sites on a watch list and a quarterly reporting deadline runs into this question constantly: pull what's already sitting in the catalog, or pay for a fresh collect over the AOI. The two paths aren't interchangeable, and picking the wrong one for the situation either wastes budget or leaves you with a gap in the record right when a site needs a closer look.
What archive imagery actually gives you
Archive imagery is whatever the satellite operator already collected and cataloged for that patch of ground, sometimes from a tasking order someone else placed, sometimes from routine wide-area collection. For a standing monitoring program, this is the default. You're not waiting on a tasking window or a weather forecast. You search the catalog for the AOI, filter by date range and cloud cover, and pull the frame closest to your reporting quarter.
The tradeoff is fit. The archive gives you whatever ground conditions existed on the day it happened to be captured. A frame from six weeks before your cutoff date can carry a dust haze over the tell, or a sun angle that throws shadows across exactly the depression you need to measure. For quarter-over-quarter comparison, that's usually workable: you're matching the same ground against itself, so an imperfect pair still shows a fresh pit or a new vehicle track against the prior frame. What the archive won't do is hand you a clean, cloud-free, low-shadow shot for a specific week because looting was reported that week.
When tasking a new pass is worth the cost
Tasking means placing an order for a satellite to collect a fresh pass over a defined AOI, usually within a stated collection window. You'd reach for this when the archive has nothing recent enough, when a site has just been reported as disturbed and you need current ground truth before a field team can get there, or when cloud cover has sat over the region for the last two archive attempts and there's no usable frame at all.
It costs more than an archive pull, and it isn't instant. Depending on the satellite constellation and the collection window you request, you're often looking at days before the pass happens, not hours, and the result still depends on weather cooperating on the day. For a quarterly review cycle where the reporting cadence is already set, tasking is the exception you reach for when the archive comes up empty, not the default you build the whole program around.
Matching the method to the reporting cycle
Most heritage monitoring work on a conflict or post-conflict site runs on a fixed cadence, quarterly being the common one, and the archive fits that rhythm. You know roughly when you'll need a frame, so you can search the catalog ahead of the deadline and pick the best available date rather than scrambling. Tasking earns its keep as the fallback for the sites where the archive genuinely fails you, or for a one-off response to a specific incident report that can't wait for the next scheduled window.
Either way, the raw frame is only the start. A monitoring officer who has pulled two archive frames of the same necropolis or citadel six months apart still has to lay them side by side and count what changed, pit by pit, track by track, across however many sites are on the list that review cycle. Looting Monitoring takes that pair of frames and returns a dated count of fresh disturbance against the prior baseline, so the comparison work on the archive you've already gathered doesn't fall to one person scrolling through a raw image dump.
If archive frames for your monitored sites are already piling up with nobody to compare them, see what a quarter-over-quarter read looks like.