How fast can satellite imagery reach search-and-rescue teams after a quake
The ground stops moving and the clock starts. For a search-and-rescue coordinator staring at a shakemap with no idea which neighborhoods still have people under them, "how fast can we get a satellite picture of this" is usually the second question, right after "how many are hurt." The honest answer has more moving parts than most people expect, and most of those parts have nothing to do with the satellite itself.
What has to line up before a pass even happens
A very-high-resolution optical satellite does not hover over a city waiting for something to go wrong. It's in a sun-synchronous orbit, crossing the same strip of the planet at roughly the same local time once a day, sometimes twice if a sibling satellite in the constellation is close enough in its own path. For a quake-hit area to get imaged, a few things have to line up on that pass: daylight (optical VHR sensors need sun, not the quake's local midnight), clear sky, and a tasking request that got submitted in time to be queued for that orbit rather than the next one.
Miss the window, and you're not waiting hours. You're waiting until the next pass, which on a bad day with cloud cover over the epicenter can mean 24 to 48 hours, sometimes longer in monsoon season or ash-heavy air from secondary fires.
Tasking a satellite after an earthquake
"Tasking" just means someone with access asks the satellite operator to prioritize a specific footprint on an upcoming orbit instead of running its default collection plan. After a major quake, operators that serve disaster response generally bump the affected area to the front of the queue. That doesn't shrink the orbital mechanics. It just means your request isn't sitting behind a routine agricultural survey when the satellite finally does fly over your coordinates.
The practical effect: tasking priority determines whether you get the first usable pass or the third one. It does not create a pass that wasn't coming anyway.
Revisit cadence isn't the same promise as event-driven delivery
A lot of VHR satellite marketing talks about revisit rate, as in "we can image any point on Earth every X hours." That number describes routine, scheduled collection. A disaster doesn't run on a schedule. What matters for search-and-rescue triage is event-driven cadence: imagery collected specifically because this earthquake happened, on whichever pass is next and clear over the footprint, regardless of the published revisit number.
That distinction matters because it changes what you should be asking a provider. Not "what's your revisit time," but "when this quake hits, how fast does a tasking request turn into a dated pass over my footprint." Those are different questions with different answers, and the second one is the one that decides whether your teams get a read on day one or day three.
Where the time actually gets lost
In practice, the gap between "satellite captures the scene" and "coordinator has something usable" rarely comes from the orbit. It comes from everything after the shutter clicks: downlink, processing, and someone turning raw pixels into a judgment about which blocks are passable and which aren't. A raw image of a collapsed district tells a trained analyst a lot and tells a watch-floor coordinator almost nothing on its own, not fast enough to matter, anyway.
That's the part worth pressing a provider on. A dated pass that arrives already graded, structure by structure, intact through collapsed, is a different deliverable than a satellite photo that still needs interpretation before anyone can point a search team at it. Building Damage Classification handles that second step: turning the first clear pass into a per-structure read, intact through collapsed, that your shelter and search planning can act on directly.
What to do with the time you do have
Get your tasking request in before the first pass, not after. Confirm with your provider which satellite or aerial asset is next over your footprint and when that window closes. And plan your triage workflow assuming the first usable imagery lands within the first one to two days, with the understanding that cloud cover or smoke can push that further out regardless of how fast anyone tasks the request.
If you're setting up that workflow now, before the next event rather than during it, that's the right time to ask what a structure-by-structure damage grade would look like for your area.