Cross-border recruitment is an operations problem, not a sourcing one

There's a particular kind of recruitment agency that doesn't compete on who sources fastest. They place welders, mechanics, electricians and HGV drivers from countries with a surplus into countries with a shortage, and the candidate, more often than not, is the easy part.

I spent years building the operations system behind a Norwegian automotive and industrial staffing firm that does exactly this, moving skilled tradespeople across NO, UK, PL, HU and ES. It's the same kind of system that runs behind Vorentis. The lesson from both is the same: cross-border recruitment is an operations problem wearing a sourcing costume.

The shortage is structural, and the supply is one border away

This isn't a niche play. Across Europe, the most widespread shortage occupations include welders, electricians, building trades and drivers (EURES Report on Labour Shortages and Surpluses 2024). The striking part of that report: of the 430 occupations flagged as in shortage in at least one country, 422 (98%) are in surplus in at least one other. The whole economic logic of cross-border recruitment sits in that sentence. The worker exists; they're just on the wrong side of a border.

And EURES names the two things standing in the way of matching them up: recognition of qualifications and language. Neither is a sourcing problem. Both are operations.

Automotive makes it concrete. In the UK alone, the aftermarket carried roughly 23,000 vacancies in early 2024, and the sector needs to fill an estimated 111,400 roles over the next decade as the workforce retires and traditional migrant labour thins (Autovista24). When the domestic pipeline can't cover that, agencies reach across borders, and inherit the operational load that comes with it.

Sourcing is the easy 20%

Place a domestic permanent role and the job is essentially done at "offer accepted." Place a cross-border technician and "offer accepted" is the starting line.

What follows is a managed project: qualification recognition, a work-and-residence permit, a chain of documents that each expire, a medical, a police check, relocation, onboarding, and the small matter of keeping a real human being engaged through months of waiting. Drop any one of those and the placement, already sold, quietly dies.

A single placement is a three-to-six-month project

The numbers are real. General-system recognition of a foreign qualification can take up to three months from complete documents (Make it in Germany). German skilled-worker permits commonly run six to twelve weeks, and three to six months end-to-end depending on the case (Skilled Immigration Act).

These timelines are improving. Germany's new digital visa portal has cut some permits to around 27 days, down from 66 a year earlier. But "improving" still means a multi-month, document-heavy journey you have to manage, not a transaction you close.

The part that kills deals: documents that expire

A passport with under six months' validity. A police certificate that's only good for three months and was pulled too early. A qualification recognition that lapses while the permit is still pending. Each of these is invisible until it isn't, and then it restarts a clock you'd already half-run.

On a desk moving dozens of people at once, "which document expires next, and for whom" is the single most expensive question nobody has time to answer by hand. Miss it once and you don't just lose admin time; you lose the candidate, and the fee.

Why a generic recruitment CRM wasn't built for this

Bullhorn, JobAdder, Vincere and the rest are good at what they were built for: fast contingency and permanent recruitment, with requirement, shortlist, submit, place, invoice. They model a placement as an event.

A migration desk needs to model it as a six-month compliance journey, with stages those tools simply don't have: recognition status, permit stage, a document register, country-to-country handoffs, expiry alerts. So the real work ends up in spreadsheets, shared inboxes and one coordinator's memory, which is exactly where, on a long enough timeline, things slip. That isn't a knock on those tools. It's a mismatch between what they model and what a migration desk actually does.

What a migration-fit system actually tracks

You don't need a different ATS. You need a layer that models your journey:

• a status pipeline that mirrors the real stages (recognition → permit → documents → relocation → onboarding), not generic "submitted / placed";
• a document register per candidate, with expiry dates and 30/60/90-day alerts, so nothing lapses silently;
• recognition and permit status visible at a glance, across every entity in the group;
• a way to surface candidates who've gone quiet mid-journey, because people go cold during a four-month wait, and a re-engagement nudge at the right moment is the difference between a placement and a restart.

I build this on the firm's own Microsoft 365, so the data, including passports, certificates and personal details, never leaves the company's own tenant. Where it helps, AI assists: flagging an expiring document, ranking who needs a call this week. A person always decides.

When you don't need this

The honest counter-cases, because not every desk should build operations like this:

• You place mostly domestic, fast perm or contingency. A generic CRM is the right tool. This would be overkill.
• You move a handful of people across borders a year. A disciplined spreadsheet and a good coordinator genuinely cover it; build the system when the volume hurts, not before.
• A partner handles the compliance steps. If visas and recognition aren't your responsibility, you don't need to track them in depth; track the handoff instead.

Build the operations only where the volume and the responsibility actually sit with you.

The bottom line

The shortage that drives cross-border recruitment is structural, and the surplus on the other side of the border is real, so this work is growing, not shrinking. The agencies that win it aren't the ones who source best; sourcing is the easy 20%. They're the ones whose operations don't drop a sold candidate somewhere in the three-to-six-month gap between "yes" and "on site."

That's not a talent problem. It's a systems problem, and unlike the shortage, it's one you can actually fix.