The coordination cost of cross-border movement.

A cross-border relocation rarely fails at any single step. Each party performs its part. The advisor advises, the provider provides, the authority decides. And yet the process is slow, fragile, and expensive. The cost is real, but it does not appear on any one invoice, because it does not belong to any one party. It belongs to the spaces between them.

The cost nobody invoices

Coordination cost is the cost of holding a process together across parties that do not share a system. It is paid in time, in rework, in regulatory exposure, and in the management attention spent confirming that handoffs landed. It is structural, and it is mostly invisible, because it is distributed across everyone and owned by no one.

The visible costs of mobility are already substantial. Industry data from Worldwide ERC places the cost of relocating an employee who rents at roughly 24,000 dollars, and an employee who owns a home at roughly 70,000 dollars.¹ Those figures are the line items. The coordination cost sits underneath them, in the effort required to make a dozen separate line items behave as one process.

Where the cost actually sits

It sits in the handoffs. A case moves from an advisor to a provider to a payroll function to a compliance review. At each boundary, context is re-stated, documents are re-sent, and status is re-confirmed. Nothing is technically lost. Everything is simply re-done, because no shared record carries forward.

Mobility teams describe the same problem in operational terms: the burden of managing multiple vendors, each with a separate process and a separate definition of done.² Every additional party is not just another cost line. It is another boundary, and every boundary is a place where the process can stall, drift, or break.

The cost of the case that breaks

When coordination fails outright, the cost stops being hidden. A failed or abandoned assignment carries the expense of the move, the lost productivity, and the cost of replacing the person. Research cited across the mobility industry estimates that replacing a departing employee can cost up to five times their annual salary.³

A process held together by correspondence does not fail loudly. It degrades. A missed deadline, a lapsed document, a salary threshold crossed without anyone noticing. Each is small. Together, across a programme, they are the difference between mobility as a capability and mobility as a recurring risk.

Coordination is a function, not an afterthought

The standard response to coordination cost is more effort: a more diligent case manager, a longer checklist, a tighter set of reminders. This treats coordination as something people do well or badly. It is more useful to treat coordination as a function the system performs, or fails to perform.

COMPASS is that function. It is the execution layer of the platform. A qualified case enters COMPASS as a single record and is carried through the full mobility lifecycle as a governed process. Stage progression is explicit. Handoffs are audited. The definition of completion is the same for every party touching the case, because they are all reading the same system.

This does not remove the work. The advisor still advises, the provider still provides. What it removes is the re-statement, the re-confirmation, and the structural uncertainty about where a case actually stands.

What removes it

Coordination cost is removed by a shared substrate. One record that every party works against. One sequence of stages that every party can see. One definition of state that does not depend on whose inbox the case currently sits in.

That substrate is infrastructure, and it is the difference between a process that is managed and a process that is engineered. The first depends on attention. The second depends on design. For a programme moving people continuously, that difference compounds with every case.