How long after a strike until imagery is usable?

Turnaround depends on what's over the target at the time you need the pass: orbit geometry, weather, and how fast the tasking queue moves. Those variables are knowable, and worth understanding before you're staring at a targeting board asking why the imagery still isn't in.

What sets the clock

Three things determine turnaround, in roughly this order of weight:

Satellite revisit interval. A VHR optical constellation isn't parked over your target. It passes on an orbit, and the next usable pass could be twenty minutes away or a day out, depending on the satellite's track and your target's latitude. Tasking priority can pull a collection forward in the queue, but it can't move the satellite's orbit.

Cloud cover at collection time. This is the one that ruins planning officers' days. VHR optical and aerial RGB imagery needs a clear line of sight to the ground. A pass through heavy overcast comes back unusable, and the next opportunity is whatever the next pass happens to be, which could land hours later or the following day. If your target sits under a weather system that isn't moving, you can have a satellite tasked and a clean collection window scheduled and still come away with nothing gradeable.

Processing and delivery. Once the pixels are collected, there's downlink, processing, and delivery to whoever's doing the assessment. This is usually the shortest leg of the three if the tasking was set up right, but it's not zero.

Put together, usable imagery can arrive within the same operational period, or it can take longer if the weather or orbit geometry isn't cooperating. Nobody running an honest BDA program quotes a flat number, because the flat number would be wrong half the time.

Cloud cover and strike imagery delay

This is worth separating out because it's the variable most often underestimated at the planning table. A clear strike package, perfect munition effect, and a fully tasked satellite still produce nothing usable if the target is sitting under a cloud deck when the bird passes. Optical sensors don't see through weather. If your target region runs persistent overcast for a stretch, the imagery delay is a weather problem wearing a satellite-shaped hat.

The practical implication: when you're scoping re-strike timing, check the weather outlook for the target area alongside the next pass schedule. If cloud is forecast to clear in a few hours and the alternative is tasking a pass that will come back obscured, waiting for the clearer window is usually the better bet if your re-strike decision can absorb the delay.

Imagery turnaround time for re-strike decisions

For a re-strike call specifically, the turnaround that matters isn't when imagery exists but when a dated, itemised assessment exists that tells you which aim points still need work. That means before/after imagery, a structure-by-structure grade, and a timestamp you can defend up the chain. Getting raw pixels back fast doesn't help if nobody's turned them into a call you can act on.

That's the gap an event-driven tasking model is built to close. A tasking that fires when the strike happens, instead of waiting on the next scheduled pass in a routine ISR plan, gets into the collection queue as early as the orbit and the weather allow, rather than losing a cycle to administrative lag.

If you're planning the re-strike window around imagery you don't yet have, Battle Damage Assessment turns before/after VHR imagery into a per-structure grading sheet as soon as a usable collection comes in, rather than on a standing schedule. Worth a look if the next tasking decision is still open.