Most relocation programs don’t break.
They drift.
From the outside, everything still looks fine:
moves are approved, employees land, costs are tracked, exceptions are explained.
But underneath, something subtler is happening — and it usually goes unmeasured.
The problem isn’t bad decisions. It’s accumulation.
In well-run organizations, relocation decisions are rarely careless.
They’re contextual, empathetic, and defensible at the moment they’re made.
The issue is what happens after.
Over time, individual decisions begin to shape the future decision space — not because anyone intended them to, but because precedent quietly hardens into expectation.
Economists call this a path-dependent system:
once certain choices are made, future options narrow — even when circumstances change.
In relocation, this shows up as:
- exceptions that feel harder to refuse than they once did
- support levels that vary by history rather than policy
- “temporary” arrangements that quietly become the reference point
No single relocation causes the issue.
The pattern only becomes visible when someone is looking across moves — not just at them one by one.
What most programs track — and what they miss
Most mobility reporting focuses on:
- cost per move
- service satisfaction
- timelines and vendors
All important. None sufficient.
What’s rarely tracked are the second-order effects:
- how often exceptions repeat
- whether similar roles are treated differently across time or business units
- when interim arrangements quietly become permanent defaults
These aren’t problems you feel immediately.
They’re problems you feel later, when flexibility erodes and governance gets noisy.
Why low- and mid-volume programs are most exposed
High-volume programs eventually see these patterns through sheer repetition.
Very low-volume programs feel each move as bespoke.
It’s the middle ground — 5, 10, 15 relocations a year — where drift hides best.
There’s enough activity for precedent to form, but not enough friction to force a review.
That’s usually where we’re invited in — not because something has gone wrong, but because someone has started to sense that the program is no longer behaving the way it was designed to.
Watching what others aren’t
Strong mobility programs don’t just execute relocations well.
They monitor the direction the program is moving — not just whether the last move succeeded.
That means paying attention to:
- what each decision makes easier next time
- what it quietly makes harder
- and whether today’s “reasonable exception” is tomorrow’s baseline
Those signals don’t show up in dashboards unless someone is deliberately looking for them.
We are.
