Source-to-hire vs source-to-deploy, what blue-collar employers should measure

A white-collar recruiter ends the cycle at offer acceptance. A blue-collar cross-border deployment ends the cycle at first day on site, and the gap between the two end gates is where most procurement teams lose track of what they have bought. This guide names the two end gates, walks the operational stages in between, and gives corridor benchmarks for the number that actually matters.

The short version: source-to-hire ends at the candidate's signature on the labour contract. Source-to-deploy ends at the worker's first hour of productive work on the destination site. For a domestic warehouse hire the two numbers can be within five days of each other. For a Nepal-to-Croatia welder deployment they are 60-90 days apart. A buyer that signs against a source-to-hire commitment expecting it to deliver a source-to-deploy outcome will discover the gap in week six.

What "source-to-hire" measures

Source-to-hire is the white-collar SaaS metric. It runs from the first sourcing activity, posting the role, opening the candidate database query, briefing the in-country recruiter, to the candidate's signature on the labour contract.

The scope inside source-to-hire is owned by the recruitment function. Vacancy posting. Database search. Candidate outreach. Phone screening. Skills assessment or trade test. Reference check. Manager interview. Offer. Acceptance. Each stage has a published median in the white-collar literature, and the aggregate median across the SaaS HR benchmarks runs 25-45 days depending on role seniority and market.

The number is useful inside the recruitment function. It is misleading to a buyer that needs the worker on site, not the candidate on a contract.

What "source-to-deploy" measures

Source-to-deploy runs from the first sourcing activity to the worker's first day on site, producing chargeable work. It includes everything in source-to-hire plus the operational stages that move the worker physically to the destination.

The added stages are corridor-specific. For a cross-border blue-collar deployment they typically include:

1. Demand letter preparation and signature
2. Origin-country attestation, DOFE, DMW, e-Migrate or equivalent
3. Visa application at the destination consulate
4. Work permit issuance at the destination regulator, HZZ, NSZ, MOHRE, BAMF
5. Embassy stamping and document collection
6. Pre-departure orientation seminar (PDOS in the Philippines, equivalents in Nepal and India)
7. Flight booking and ticketing
8. Ground transport from airport to site
9. Initial accommodation and induction
10. First day on site, productive work begins

Each stage is governed by a regulator schedule, a clinic appointment, a consular slot, or an airline timetable. None of them are recruitment-team-owned in the white-collar sense. All of them sit inside source-to-deploy.

The benchmark gap, corridor by corridor

The numbers are corridor-specific medians from the deployment book, with the caveat that consular and regulator queues vary by season. The Nepal-to-Croatia gap of 62 days is the structural baseline. The Philippines-to-Adriatic gap of 68 days reflects the DMW Job Order process. The Serbia-to-Slovenia gap of 17 days reflects intra-EU mobility with a tighter document stack.

A buyer that wants the welder cohort on a Hamburg shipyard floor in week 12 from demand letter has to plan against the Bosnia-to-Germany 38-day source-to-deploy, not against a generic 30-day source-to-hire SaaS line.

Why the gap exists, named in five drivers

The gap between source-to-hire and source-to-deploy is not slack. It is structural and each day in it is governed by a third party with its own published schedule.

Permit issuance windows. A destination work permit cannot be filed until the candidate has signed the contract and the origin-country attestation has cleared. The filing window itself is regulator-controlled, MOHRE Tasheel runs faster, HZZ runs slower at certain points in the calendar.

Consular appointment availability. Embassy slots in some destination consulates run two to six weeks out. The candidate cannot fly without a stamped visa.

Document attestation queues. Origin-country attestation queues build during seasonal peaks. DOFE Nepal runs longer in March-May, DMW Philippines runs longer ahead of the EU summer season.

Medical and orientation gates. The pre-deployment medical fit-test, drug and alcohol screening, and trade-test verification require physical clinic appointments. PDOS or equivalent runs on a published seminar schedule.

Travel logistics. Flight availability and routing can add 3-7 days, especially on multi-leg routes like Kathmandu to the Adriatic via the Gulf.

A recruitment partner does not eliminate the gap. A recruitment partner that knows the gap, plans against it, and gives the buyer a confidence-weighted arrival curve is a partner running source-to-deploy as the operating metric.

What this means for the dashboard

A buyer's dashboard should publish both numbers per corridor. The methodology footnote names the end gates explicitly. Source-to-hire ends at "candidate signature on Werklist contract". Source-to-deploy ends at "worker first hour of productive work on site, as logged by destination payroll".

If the dashboard only publishes source-to-hire, the buyer is operating against the white-collar lens. If the dashboard publishes only source-to-deploy, the buyer cannot diagnose where the gap is widening when it widens, sourcing engine, attestation queue, consular slot, or destination logistics.

The two numbers together let the procurement team localise the bottleneck. A source-to-hire that doubles month-over-month is a sourcing engine signal. A source-to-deploy that doubles while source-to-hire holds is a destination-side signal, consular, regulator, or accommodation.

How Werklist quotes the timeline

Werklist quotes both numbers per corridor at the start of a scoping call. The quoted source-to-deploy includes a confidence band, base case, downside case, upside case, against the consular and regulator queue conditions in the trailing 90 days.

The quote is a planning input, not a contractual guarantee on the regulator's schedule. The buyer can hold Werklist to the source-to-hire portion of the timeline, the part owned by the recruitment engine. The source-to-deploy gap depends on third parties whose schedules sit outside any vendor's control.

The procurement question that separates serious vendors from marketing

Two questions on a vendor call separate operators from quote-machines.

First: "What is your median source-to-hire and source-to-deploy in my corridor and trade across the trailing 12 months?" The vendor that answers in two numbers with a methodology footnote and a sample size is operating with the discipline. The vendor that answers in a single "time-to-hire" without distinguishing is operating against the white-collar lens.

Second: "What is the largest variance you have seen in source-to-deploy in the trailing 12 months, and what drove it?" The vendor that names a specific consular delay, a regulator queue, or a seasonal pattern is running the engagement against reality. The vendor that hedges is quoting against the brochure.

Where to go next

For the recruitment KPIs that fold source-to-hire and source-to-deploy into a working dashboard, see Recruitment KPIs for blue-collar workforce. For the cost dimension that pairs with the time dimension, see Cost-per-hire calculation for blue-collar workforce, 2026 benchmarks.

Send the brief. Corridor, trade, target first-day-on-site date, headcount. We come back inside one business day with the source-to-hire and source-to-deploy quote, the confidence band, and the consular slot conditions in your destination. Talk to a corridor lead.