Run The Region

Cross-Market Labor Arbitrage: What Works, What Backfires

Moving labor between markets looks smart on a wage sheet. It works when the person is a scarce specialist on a finite assignment. It backfires almost every time it is used to cover a scheduling problem you have not fixed.

Kiyong (Eric) Lee·Operations Executive·August 2026·9 min read

The short version

Cross-market labor movement works for traveling trainers, opening teams, catering ops leads, and corporate role fill-ins. Four repeatable use cases.
It backfires when you borrow hourly line staff to cover a schedule hole. The wage math looks clean. The real math almost never is.
Wage rate differences between states are smaller than they look once you add housing, per diem, and travel time.
"Temporary" transfers stick after 8 to 10 weeks. Both units re-form around the new state and pulling the person back costs a second adjustment.
Culture transfers slower than skill. A cook who is excellent in one market can look weak in another for a full week before they land.

Every regional operator who has ever run more than one state has felt the pull. One market is short a line cook on Friday. Another market is over-scheduled on the same shift. The board has taught you to think about labor as a percent of sales, and the arithmetic in your head is that if you just moved the second cook to the first market, both P&Ls would look better. It seems obvious. It is often wrong.

At Hana Group I ran 21 franchise units across 6 states, inside Walmart, Sam's Club, Whole Foods, and Target footprints. On a $36M P&L, cross-market labor movement was a lever I reached for constantly in the first year, and cautiously by the second. This is what I learned about which versions of it actually pay and which versions of it teach the region bad habits.

The four versions that work

There are four cross-market labor moves that repeatedly earned their cost. In each one the person being moved is a scarce specialist, the assignment has a defined end date, and the receiving unit could not build the capability locally in the time available. Those three tests are the whole game.

Traveling trainers for new openings

A new-unit opening is a labor emergency by design. You are hiring 40 to 60 people at once, none of whom have worked together, in a building that has never served a guest. Sending in a two-person or three-person traveling training team for the first six weeks is one of the highest-yield labor moves you can make. In 12-plus new-unit openings across my career, the ones I staffed with a real traveling trainer team hit stable four-wall margin roughly a full quarter earlier than the ones I tried to open with local hires alone.

The math holds because the trainers are teaching the standard, not covering shifts. When the assignment ends, the trainers leave and the local team owns the standard. That transfer of ownership is what makes the cost recoverable.

Opening teams

An opening team is one step bigger than a traveling trainer. It is a group of eight to fifteen people who have opened before, who fly in a week before doors open, and who work the first three weeks on the line while the local team ramps. The opening team is expensive in absolute dollars and cheap in preventable disaster. The alternative is a soft opening that lasts three months and a set of guest reviews you spend a year outrunning.

Cross-market catering ops

Catering is the one line item where wage rates almost do not matter. If you are catering a 400-person Stanford or Google event and you need a captain who has done a 400-person event before, you fly them in. At Zareen's, catering to Stanford, Google, Apple, Meta, LinkedIn, Salesforce, Cisco, Adobe, and Nvidia meant a weekend could produce a $60,000 event with a $180 travel bill for the captain. The delta was noise. The competence was the whole show.

Corporate role fill-ins

When a general manager goes on parental leave, when a director of operations leaves without notice, when a controller is out for a medical stretch, moving a corporate role into the seat for 6 to 12 weeks is usually a good trade. The person already knows the systems. They are not learning the brand. They are covering the seat. The receiving unit gets continuity and the corporate team gets a real look at how the field actually runs.

Fig. 1 · The pattern that separates the good moves from the bad ones.

The three versions that backfire

Borrowing hourly line staff between markets

This is the one that gets tried the most and works the least. The scenario is always the same. Market A is short two line cooks on the weekend. Market B is over-scheduled. Somebody in a Slack channel proposes flying two cooks from B to A on Friday morning, back on Sunday night. The wage sheet looks clean.

The real cost list looks like this: two round-trip flights, two hotel nights, per diem, ground transport, three shifts of learning curve on the receiving line, one demoralized sending team who is now short-staffed for a purpose they do not see the benefit of, and a receiving general manager who spent Friday morning onboarding two people who will be gone by Sunday. Once I actually costed one of these out at Hana, the effective hourly rate of the borrowed cook was $47. The local hire I could have gotten with a week of runway would have cost $18.

Temporary transfers that stick

The phrase "just for a few weeks" is one of the more expensive phrases in multi-unit operations. What actually happens is that at week 8 to 10, both units have re-formed around the new state. The sending unit has shifted responsibilities and is running fine without the person. The receiving unit has come to rely on them. Pulling the person back is now two separate transitions, not one, and both are messy.

The clean version is a bright-line rule: any cross-market assignment longer than six weeks is a real transfer with a real conversation about compensation, family, and housing. Anything under six weeks is actually temporary and comes home on the date it was scheduled to come home. Fuzzy timelines are the failure mode.

Moving hourly staff to fix a scheduling problem

This is the hardest one for operators to catch, because it looks like resourcefulness. A unit is chronically short on Friday nights. Instead of fixing the demand curve, the recruiting plan, or the schedule structure, the region starts sending hourly staff from a neighboring market every Friday. Six months later it is a permanent pattern that everybody has stopped questioning. The receiving unit's real staffing plan has quietly rotted, and the operator does not notice until the neighboring market becomes tight and the crutch disappears.

Every cross-market labor move that becomes a habit is a solved problem you decided not to solve. The transfer becomes the answer, and the underlying question stops being asked.

The wage rate math that does not work

Every operator who has run in California and Texas at the same time has had the same daydream: what if we just staffed the California units with Texas hourly workers on rotation? The wage delta looks huge. The delta is real. It is also not accessible.

Here is the honest arithmetic. Say the California hourly cook is at $20 and the Texas hourly cook is at $15. That is a $5 gap on paper. Now add: $85 a night for a shared apartment ($10.60 per 8-hour shift), $40 a day per diem ($5 per shift), round-trip flight amortized over the assignment ($3 to $6 per shift depending on length), and lost productivity during ramp (add roughly $2 per shift for the first two weeks). The Texas cook working in California costs $35.60 an hour effective in the first two weeks, and about $33.60 an hour after that. The local California cook costs $20.

The arbitrage vanishes. And that is before you count the morale hit on the sending unit and the culture drag on the receiving unit. Wage rate arbitrage across state lines almost never survives its own accounting.

The morale cost the wage sheet cannot see

The line item the spreadsheet always misses is what happens to the sending team. When you pull two cooks out of a market for a two-week rescue at another location, the fifteen people left behind at the sending unit are working a tighter schedule, covering the missing stations, and watching their peers get flown somewhere the company apparently cared about more. That morale drag is real and it lasts longer than the two weeks. General managers at the sending unit will tell you months later that they lost two prep cooks the following quarter because the borrowed pair came back with stories about pay bumps and per diem that the ones who stayed did not get.

The fix is small and non-obvious. When you move someone across markets, tell the sending team publicly, name why the sending unit was chosen, and put a defined end date on the calendar that the sending team can see. Silence is what breeds the resentment, not the move itself. Operators skip this because it feels administrative. It is not administrative. It is the difference between the move being a one-time cost and the move being a recruiting hole six weeks later.

Culture transfers slower than skill

The other thing the wage sheet cannot see is the cultural ramp. A cook who is excellent in a Texas quick-service Sam's Club unit is not automatically excellent in a Bay Area Michelin-recognized concept. The technical skills transfer in a day. The pace, the plating standard, the way guests are spoken to, the amount of prep detail expected: those take a week of real shifts to internalize.

During that ramp, the receiving general manager is watching the transfer person perform below their reputation, and the trust in the whole program erodes. The fix is to brief both sides in advance, give the moving person a written cultural read on the market, and set expectations that week one is a training week, not a productive week. Most operators skip this step. It costs them the program.

What I would tell a regional operator considering the move

Two questions before you approve any cross-market labor move.

Is the person a scarce specialist? If the receiving market has this skill locally and you are moving somebody because the sending market has slack, you are managing a scheduling problem, not a skill problem. Fix the schedule.
Does the assignment have a defined end date? If the end date is "we'll see," the transfer will stick, and it will cost you more than the wage gap it seemed to save. Write the end date on the calendar before the plane ticket is bought.

If both answers are yes, move the person and pay them well. If either answer is no, do not move anyone. Fix the underlying thing instead. It is slower. It is also the work.

The point

Cross-market labor movement is a real tool. It is also the tool operators reach for when they are avoiding a harder conversation about a broken schedule, a weak recruiting funnel, or a market that has been under-staffed for so long it stopped being an emergency. The wage-arbitrage version rarely survives its own math. The scarce-specialist version pays every time.

The regional operator's job is to know which is which, and to have the discipline to fix the thing that is broken instead of flying a body over the top of it. Bodies over problems is not a strategy. It is a habit that costs more every quarter it goes unexamined.

Running labor across multiple states?

I work with multi-unit groups scaling across markets, especially where the labor model is starting to strain. If you are trying to figure out which of your cross-market moves are paying and which are just habit, I am happy to compare notes.

Get in touch

Questions people ask

What is cross-market labor arbitrage in multi-unit operations?

Cross-market labor arbitrage is the practice of moving people, hours, or skills between geographic markets to cover a gap. It shows up in a few forms: traveling trainers, opening teams, catering staff sent across state lines for events, corporate role fill-ins, and, more dangerously, hourly staff borrowed from one unit to cover a scheduling hole at another. The first four often work. The last one usually backfires.

When does moving labor between markets actually work?

It works when the person being moved is bringing a skill the receiving market does not have and cannot build fast enough. Traveling trainers for a new opening, a catering ops lead flown in for a large event, a corporate role covering a general manager on parental leave. In every case the person is a scarce specialist, the assignment is finite, and the relocation cost is small compared to the value delivered. Those three tests matter.

When does cross-market labor movement backfire?

It backfires when you borrow hourly line staff between markets to cover a scheduling problem you have not fixed. The wage rate math looks clean on paper. The real math includes housing, per diem, travel time, morale hit on the sending unit, learning curve at the receiving unit, and the fact that the fix is now a habit instead of a solved problem. In practice, borrowed hourly labor across markets costs 40 to 70 percent more than local hourly labor once you count everything.

How do wage rate differences between states change the math?

The gap looks bigger than it is. A California hourly cook at 20 dollars and a Texas hourly cook at 15 dollars looks like a 25 percent savings, but the moment you add housing, per diem, and travel, the delta closes. On a two-week assignment the effective cost of the Texas cook working in California is often within a dollar of the California local. The arbitrage that seems obvious on a wage sheet usually is not real once the full cost is on the P&L.

What is the risk of a temporary transfer that sticks?

Temporary transfers stick when the sending unit adapts to the person being gone and the receiving unit adapts to them being there. After eight to ten weeks, both units have re-formed around the new state, and pulling the person back requires two adjustments instead of one. If the assignment has to run longer than that, either move the person for real with the compensation and family conversation that requires, or send a different person and let the first one come home.

How do you handle culture differences when moving staff across markets?

The technical skill transfers. The unwritten rules do not. Every market has its own pace, its own guest expectations, its own way of handling the awkward moments. A cook who is excellent in one market can look weak in another for a full week before they adjust, and during that week the receiving general manager is going to lose confidence in the transfer program. Brief the receiving team in advance, give the moving person a written cultural read on the market, and expect a real ramp.

What is the one thing an operator should ask before approving a cross-market transfer?

Ask whether the problem you are solving is a specialist gap or a scheduling gap. If it is a specialist gap, the transfer often pays. If it is a scheduling gap, the transfer is masking a problem in the receiving unit's staffing model, and the real work is to fix the schedule, not to fly in a body. The wrong transfer teaches the region that moving people is the answer, and once that becomes the reflex it is hard to unlearn.