How restoration coordinators sequence circuits after a major storm

Every restoration plan starts with the same priority order, and every coordinator who has run a storm desk knows it by heart: transmission comes back first, then substations, then the critical infrastructure tier, hospitals, water treatment plants, 911 centers, shelters, anything on the county's critical facilities list. After that come the big circuits that bring the largest number of customers back fastest, and laterals and individual services come last, worked as crews clear their way down from the feeder.

That order is correct. It's also not the hard part.

The order isn't the problem, the sequencing is

Knowing hospitals and water treatment plants outrank a residential lateral doesn't tell you which of your forty feeders has a broken pole blocking a hospital tie-in, and which just lost a few spans of secondary. The priority tiers are fixed before the storm ever makes landfall. The sequence inside each tier, which circuit gets a crew first, second, third, has to be built after, from whatever damage information is on hand in the first hours.

That's usually trouble tickets. Tickets tell you where customers are calling from, which is useful and also incomplete. A rural circuit with scattered seasonal camps generates fewer calls per mile of line than a dense subdivision with the same amount of damage. A hospital feed that's still energized but one span away from a leaner won't generate a ticket at all, because nobody there has lost power yet. Coordinators who sequence off ticket volume alone end up sending the first wave of crews to the loudest circuits, not necessarily the worst ones.

What changes when you can see the damage before the first truck rolls

The alternative most coordinators fall back on is windshield surveys: bucket trucks and line crews driving circuits to report back what they're looking at, which is accurate and also slow. On a territory-wide event, physically walking or driving every circuit to confirm damage concentration can eat the better part of a day, and that's a day where crews already in the field are working whatever circuit they happened to start on, not necessarily the one with the hospital tie-in down the road.

A pre/post-event imagery comparison closes that gap before the trucks move. Flying or tasking very high resolution imagery, 0.5 m ground sample distance or finer, over the same territory before and after the event and comparing the two flags where tree-down, structure, and span damage is concentrated. The line crew still has to lay eyes on the pole before it's fixed, but the comparison gives the storm desk something closer to a full-territory view than ticket density or scattered field reports can provide on day one, and that's what decides which circuit the crew drives to first.

For the critical infrastructure tier specifically, this matters more than anywhere else in the plan. A hospital or water treatment plant sitting on a circuit with heavy canopy damage two miles upstream isn't going to show up in a ticket queue if the facility itself still has power. An imagery comparison that flags damage along that specific feeder run, before a crew has driven it, is the difference between finding that problem on the first pass and finding it on the third.

Building the sequence, not just the list

A damage concentration map doesn't replace the priority tiers your restoration plan already has. It feeds the sequencing decision inside each tier: which of the critical-infrastructure circuits gets the first crew, which of the high-customer-count feeders gets the second. Storm Grid Damage delivers that comparison across your service territory the same day imagery becomes available after an event, so the sequencing call doesn't have to wait on ticket volume or a circuit-by-circuit drive.

If your storm desk is still building that first-wave sequence off call volume and whoever's closest, it's worth seeing what a day-one damage comparison looks like for your territory.