No published series tracks work relocation directly. What can be observed is the resulting distribution, and the recurring drivers are labor cost, talent availability, tax and incentive packages, and proximity to customers or infrastructure. Announcements consistently overstate both the size and the speed of moves, because the announcement is made at the point of maximum intention and minimum commitment.
Four reasons work moves, and only one gets announced
Labor cost. The same occupation at a materially lower median somewhere else. This drives back-office, support and shared-service functions more than anything else, and it is the motive least likely to be stated out loud.
Talent availability. The opposite motive, and it moves work toward expensive places rather than away from them. A function that cannot hire enough people goes where the people are, which is why specialist teams end up in the metros with the highest costs.
Tax and incentives. Real, and usually smaller than the headline. Packages are typically staged against hiring commitments, and those commitments are frequently not met in full, which rarely gets reported.
Proximity. To customers, to ports and freight, to a research cluster, or to a regulator. Slower-moving than the others and more durable when it happens.
Why announcements mislead
A relocation is announced when it is decided, and reported as though it has happened. The headcount quoted is almost always a multi-year target, often contingent on conditions, and it is revised quietly when it is revised at all.
Meanwhile the roles that actually move first are the easiest to move, which are rarely the ones described in the announcement. A press release about a thousand engineering jobs frequently begins with sixty people in finance and procurement.
What to watch instead
An employer’s job postings by metro over time. That shows where they are actually hiring rather than where they said they would, and it is public. Watch for a few months rather than a few weeks.
And a metro’s occupational concentration across successive data releases. If a cluster is genuinely forming, that number rises. If it is not, the announcement was the whole event.
Which functions move and which stay
Work whose output is standardized and verifiable moves readily: transactions, processing, first-line support, anything measured by throughput and checked by rule.
Work requiring judgment, relationships or physical presence moves least. So does anything where somebody must be accountable to a regulator in a particular jurisdiction.
That is the same distinction that governs which tasks automate, and for the same underlying reason: both are asking whether the work can be specified precisely enough to hand to somebody who is not in the room.
What it means for you specifically
If your function is the kind that moves, the question is whether you sit in the origin or the destination. The destination is cheaper for the employer, which has implications for your pay trajectory even if your role is perfectly safe.
Being in the origin of a move is not automatically bad either. Origin sites usually retain the judgment-heavy work and shed the process-heavy work, so what matters is which half of your job is which — and that is worth knowing before anybody announces anything.
Checking your own exposure
Compare your metro’s median for your occupation against the national figure. A large premium is exactly the condition that makes a finance director look at a map, and it is published for anybody to see, including them.
Then ask what proportion of your week is standardized and verifiable. High premium plus high proportion is the combination worth acting on, and acting on it usually means moving toward the judgment work rather than moving house.
Remote work changed the shape of this
Moving work used to mean moving a building, which is slow, visible and expensive enough that it only happened for large functions. Distributed hiring lets an employer relocate a function one vacancy at a time, without announcing anything.
That is the version most people will actually experience. Nobody says the team is moving; the next three hires are simply made somewhere cheaper, and two years later the center of gravity has shifted. It shows up in job postings by metro long before it shows up anywhere else.
The pay question this creates
An employer hiring across locations has to decide whether to price a role by the company’s market or the worker’s. Both policies are common and they produce very different numbers for identical work.
Ask which one applies before accepting a distributed role, and ask what happens if you move. A policy that adjusts pay downward when you relocate is a materially different job from one that does not, and it is a normal question that a well-run employer will answer plainly.
Common questions
Is work relocation tracked in official data?
Not directly. Only the resulting distribution is observable, through occupational employment by metro across successive releases.
Why do employers move work?
Labor cost, talent availability, tax and incentive packages, and proximity to customers, freight or research clusters.
Why do announcements mislead?
They are made when a decision is taken, cite multi-year contingent targets, and are revised quietly afterwards.
What should I watch instead?
An employer's postings by metro over time, and whether a metro's concentration in your occupation actually rises across releases.
Which functions move most?
Those whose output is standardized and verifiable. Judgment, relationships and physical presence move least.
Why do employers relocate work?
Labor cost, talent availability, tax incentives, and proximity to customers, freight, research or regulators. The first is the least likely to be stated publicly.
Are relocation announcements reliable?
They are decisions reported as events. The headcount is usually a multi-year contingent target, and the roles that move first are the easiest ones rather than the ones described.