Mutual Aid Moves Line Crews Overnight. Lodging Is What Slows It Down.

The storm is still two days offshore and the request has already gone out. By Thursday morning, several hundred line workers who were setting poles in another state are staging in a parking lot four hundred miles from home, with bucket trucks, digger derricks, chainsaw crews behind them, and no confirmed answer to the simplest question anyone has asked all day: where are we sleeping tonight?

Mutual aid is one of the most impressive logistics systems in American industry. It can find, commit, and move thousands of skilled restoration workers across state lines in under forty-eight hours. What it cannot do is manufacture hotel rooms in a county that just took a direct hit. The trucks arrive faster than the beds do, and the gap between those two things is where restoration timelines quietly go to die.

The system moves people faster than it moves rooms

The mutual assistance network is a voluntary arrangement among electric utilities: when a storm overwhelms a local workforce, the affected utility borrows crews and specialized equipment from companies in unaffected regions. Requests move through regional mutual assistance groups, of which there are seven across the country, and the requesting utility covers the responding crews’ time, lodging, and meals.

The scale is real. After Hurricane Helene, Eversource sent roughly forty crews and twenty support personnel from Connecticut, Massachusetts, and New Hampshire into southwestern Virginia, working alongside Appalachian Power for more than a week. They were one contingent inside a restoration force that ran into the thousands. Every one of those workers needed a bed within reasonable distance of a work zone, on nights when the local lodging market was already broken.

That is the shape of the problem. The workforce scales elastically. The room inventory does not.

The rooms are gone before the crews get there

In a normal market, a few hundred rooms is a phone call. In a storm zone, the hotel inventory is one of the things the storm hit. Properties lose power. Roofs come off. Water gets in. What is left standing fills immediately with evacuees who left ahead of the wind, with damage assessors, insurance adjusters, tree and debris contractors, telecom and cable crews, and with the utility’s own internal workforce, most of whom booked days earlier.

So the arriving crew gets pushed outward. Sixty minutes out. Then ninety. And a ninety-minute drive is not a minor inconvenience on a restoration job. It is roughly three hours a day of a sixteen-hour clock spent behind the wheel instead of on the line, taken from the same people who are working extended hours in damaged terrain. It slows restoration and it degrades the rest that keeps the work safe, which is the same duty-of-care problem that shows up on every traveling crew, just compressed into the worst possible week.

The utilities that handle this well are not luckier. They started earlier, and they had someone whose entire job was rooms.

Rosters change every single day

Even after the beds are found, storm lodging refuses to sit still. Crews get released early when a circuit comes back faster than expected. Others get extended when a substation turns out to be worse than the first assessment. Crews get reassigned mid-week from one operating district to another, one hundred miles down the road. Foremen swap in and out. A block of ninety rooms that was exactly right on Monday is forty rooms too many and in the wrong town by Wednesday.

Handled by hand, that becomes a coordinator sitting in a hotel lobby at eleven at night with a printed roster and a cell phone, negotiating with a night auditor over rooms that were charged but never slept in. Handled as a program, it becomes a nightly roster update and a desk that reworks the block before the crew ever finds out there was a problem. Add the ordinary realities of the work, bucket truck and trailer parking, four in the morning breakfast, check-ins at odd hours, an occasional laundry run in week three, and the coordination load is constant.

Every room night eventually has to survive a prudence review

Here is the part that outlives the storm by two years.

Major storm costs generally do not sit quietly in an operating budget. They are deferred and later brought before state regulators, who decide whether the spending was prudently incurred before any of it is recovered. That review is document-driven, and lodging is one of the messiest categories in the file: hundreds of separate folios, from dozens of properties, in multiple jurisdictions, tied to crews that moved between districts mid-week. Industry reviews of utility cost recovery have noted that a measurable share of invoices get filed for recovery without adequate supporting documentation, and undocumented cost is the easiest kind for a regulator to disallow.

The same paperwork problem runs sideways, between utilities. The requesting utility reimburses the responding one, and that settlement is only as clean as the underlying records. If lodging arrives as a shoebox of folios and a credit card statement, somebody spends the next quarter rebuilding it.

What makes this survivable is boring and structural: one consolidated record per week instead of hundreds of folios, every room night tied to a named worker, a property, a date, and a cost code for the event and the operating district, and the whole thing audited before it is ever invoiced. Build the file as the storm runs, and the recovery filing is a retrieval exercise. Build it afterward from receipts, and it is an archaeology project.

What “ready” actually looks like

The utilities that do not scramble share a pattern. Lodging is arranged before the season, not during the event.

That means a standing program that costs nothing while it sits idle, with no minimums, no subscription, and no exclusivity, so it can be dormant for eleven months and absorb a thousand room nights in the twelfth. It means known inventory in concentric rings around the service territory, including the second and third rings that matter once the first is gone. It means one point of contact who already has the account, the billing structure, and the cost-coding format, instead of a purchasing department opening credit cards at two in the morning. And it means a desk staffed around the clock, because storm work does not observe business hours and the call about a missing reservation always comes at eleven at night.

Globeo runs that model across a network of more than 30,000 partnered hotels, with same-day bookings typically confirmed in five to ten minutes and 24/7 human support behind every stay. Crews get placed as close to the work as standing inventory allows, roster changes get absorbed as they happen, and the record builds itself while the restoration runs. It is the same operating pattern we bring to disaster relief and restoration and energy services work generally: move fast, stay close to the job, and document everything.

The billing side, in plain terms

Invoicing runs weekly. Every Tuesday, a single invoice covers the previous seven nights of audited qualifying rooms, with statements following on Thursday. It arrives by email as a PDF invoice plus an Excel detail sheet built for reconciliation, so accounting is matching one document against one dataset rather than chasing folios across a dozen properties.

Before any of it goes out, the charges run through our audit process, a proprietary algorithm that compares what was booked against what was billed. Variances beyond a small threshold get pulled for manual review, and a team calls the hotel to resolve them. On extended restorations, which is most of the big ones, stays that cross the thirty-day mark get tracked for state occupancy tax exemption, with the tax either refunded or removed. That is money that otherwise stays lost inside a folio nobody reads.

The result is that the folios from every property consolidate into one weekly invoice, coded the way the utility’s own cost management needs them coded. Which is exactly what a prudence filing wants to see.

The bottom line for storm response

Mutual aid solved the hard problem decades ago. Thousands of skilled workers can be identified, committed, and rolling in a day. The unsolved problem is what happens when they arrive, and it has never really been a sourcing problem so much as a preparation problem. Rooms near the work, absorbed roster changes, one auditable record instead of hundreds of folios: none of it is exotic, and all of it is close to impossible to assemble at two in the morning with the wind still blowing.

Get lodging arranged before the season, and the crews sleep close to the work, the restoration runs on schedule, and the file that goes to the regulator two years later actually holds up.

Frequently Asked Questions

Who pays for lodging on a utility mutual aid deployment?

The requesting utility does. Under standard mutual assistance arrangements, the utility that asked for help reimburses the responding company for its crews’ time, lodging, and meals. That makes lodging a cost the affected utility will eventually have to document and defend, not an expense the visiting company absorbs.

Why is lodging so hard to find during storm restoration?

Because the same event that created the work also damaged the lodging supply. Hotels in the affected area lose power or take structural damage, and whatever remains fills with evacuees, damage assessors, insurance adjusters, debris and tree contractors, telecom crews, and the utility’s own internal workforce. Arriving mutual aid crews are frequently the last group looking, which pushes them sixty to ninety minutes away from the work.

How far from the work should restoration crews be housed?

As close as available inventory allows. On a sixteen-hour storm schedule, a ninety-minute placement can consume roughly three hours a day in drive time, which comes directly out of both productive hours and crew rest. Proximity is the single highest-leverage lodging decision on a restoration, for schedule and for safety alike.

How should utilities document storm lodging costs for cost recovery?

Every room night should tie to a named worker, a property, a date, and a cost code for the event and operating district, and it should be captured while the storm is running rather than reconstructed afterward. Consolidating hundreds of individual hotel folios into a single audited weekly invoice with a line-level detail file is what turns a recovery filing into a retrieval exercise instead of a reconstruction.

Can a lodging program be set up before hurricane season and left idle?

Yes, and that is the point. A managed crew lodging program with no minimums, no subscription, and no exclusivity can sit dormant through a quiet season and scale to thousands of room nights in an active one. The value of setting it up in advance is that the account, billing structure, cost-coding format, and escalation path already exist when the request goes out.

What about roster changes once crews are deployed?

They are constant, and they are the reason ad hoc booking breaks down. Crews get released early, extended, or reassigned across districts mid-week, so a block that fit on Monday is wrong by Wednesday. A managed program absorbs those changes nightly against an updated roster, adjusting rooms and blocks before they turn into charges for rooms nobody slept in.

Schuyler Bagwell, Director of Product, Globeo

Globeo builds crew lodging programs for utilities and restoration contractors: near-site placement across a 30,000-plus property network, 24/7 human support, roster changes absorbed as they happen, and one audited weekly invoice that stands up to review. If your storm plan still ends at “we will find rooms when we get there,” talk to us before the next season.