End-to-end vs partial-service recruitment, which model fits which employer

Some employers want one partner to run the deployment from candidate sourcing to the worker's first day on site. Others want to keep the internal recruitment team in the driver's seat and bring in a partner only for the cross-border filings and the mobilisation. Both engagement models are valid. The decision is mostly a question of internal capacity, corridor familiarity, and where the buyer wants the failure modes to land.

The short version: end to end fits buyers without in-country sourcing infrastructure or with limited HR bandwidth for the regulator-facing scope. Partial-service fits buyers with an established internal sourcing function who need help only with the cross-border filings, the trade test, or the mobilisation logistics. The model split matters less for the headline cost than for who is on the phone when something breaks at week six.

What "end to end" actually covers

End to end in cross-border blue-collar recruitment is an eight-stage workflow adopted across the operator-grade corpus: requirement analysis → sourcing from origin countries → pre-screening and trade tests → medical fitness → visa and documentation → deployment → onboarding and HR support → 30-day on-site survey.

Each stage has a real deliverable. Requirement analysis produces a written corridor fit and a rough mobilisation window. Sourcing produces a shortlist of pre-screened candidates. Trade tests produce a pass/fail record against the buyer's specification. Medical fitness produces a clinic-issued report against the destination-country standard. Visa and documentation produces a stamped passport and a permit. Deployment produces a flight manifest and an arrival confirmation. Onboarding produces a site induction record and a first-paycheck confirmation. The 30-day survey produces a worker-side report independent of the employer.

An end to end engagement runs all eight stages under one contract, with one corridor lead, one set of escalation paths, and one combined invoice. The buyer's HR team participates at the gates, sign-off on the shortlist, sign-off on the trade test, sign-off on the demand letter, but does not run the operational scope between gates.

What "partial-service" covers, in practice

Partial-service is the same workflow split across two or more vendors, with the buyer's internal team holding part of the scope. Three common splits.

Source plus mobilise. The buyer's internal team does requirement analysis and shortlist review. The partner runs sourcing through 30-day survey. Common when the buyer has clear specifications and a strong internal HR function but no destination-country licence or cross-border filing capability.

Trade test plus mobilise. The buyer brings its own shortlist from existing labour-hire relationships or internal channels. The partner runs trade test, medical, visa, and mobilisation. Common when the buyer has long-standing relationships with origin-country contractors and needs help only with the regulator-facing scope.

Mobilise only. The buyer or its destination-country labour-hire partner has signed contracts with named candidates. The partner runs visa, work permit, flight, ground transport, and arrival induction. Pure logistics scope, no recruitment involvement.

Each split changes the cost-per-hire stack, the failure-mode distribution, and the speed at which the deployment can be turned around. None of them is wrong. The wrong choice is matching the model to the buyer's internal capacity.

When end to end wins

Four conditions point to end to end.

First, the buyer has no in-country sourcing infrastructure in the origin country and no relationship with one of the labour-export regulators (DMW Philippines, DOFE Nepal, the Protector of Emigrants in India, NSZ Serbia, HZZ Croatia). Standing one up for a single deployment is a six-month exercise.

Second, the headcount is in the 10-200 range. Below 10, the cost of running a full end-to-end engagement is high per worker. Above 200, the buyer typically wants to split sourcing across multiple partners under an MSP layer rather than concentrate it with one vendor.

Third, the buyer is unwilling to absorb operational scope between the gates. Their internal HR team can review shortlists and sign demand letters but cannot run trade test logistics or chase consulate appointments.

Fourth, the buyer's CSR audit framework requires a single chain of custody on the recruitment process. End to end produces a single audit trail. Partial-service produces multiple, joined under the buyer's coordination.

When partial-service wins

Three conditions point to partial-service.

First, the buyer already runs sourcing in the origin country through long-standing channels, a sister company, a regional procurement office, a labour-hire relationship that predates the cross-border engagement. Bringing in an end to end vendor over the existing channel duplicates cost without adding signal.

Second, the buyer has high internal capacity for one segment of the workflow but a hard gap in another. A construction principal with a strong site-induction function and a well-staffed HR team has internal capacity for onboarding but a gap for visa filings in a new destination country. Partial-service buys exactly the gap.

Third, the deployment is recurring and the buyer has already absorbed the corridor learning curve. Year one of the deployment may have been end to end. Year three is partial-service because the buyer's internal team can now do most of the scope.

The decision matrix

The matrix is a starting point, not a substitute for a scoping call.

The cost trade-off

Partial-service is not automatically cheaper than end to end on a fully-loaded basis. The headline invoice is lower because the partner is doing less, but the internal cost the buyer absorbs to run the missing scope often offsets the saving. A buyer that splits sourcing from mobilisation needs internal capacity to coordinate the handoff, the candidate that the source-side partner produced has to land cleanly in the mobilise-side partner's process, with the same name on the documents and the same wages on the contract.

The hand-off is where contract substitution risk concentrates. A worker signed a contract with the source-side vendor for one wage. The mobilise-side vendor sees a different wage on the demand letter. The worker arrives in destination and discovers the on-site contract is different again. Each splice in the workflow is a potential substitution point and the buyer's CSR audit will catch all of them.

The disclaimer pattern applies: in a partial-service engagement, each vendor's scope is explicit, the boundaries are named, and the buyer's coordination is the single source of truth on the worker's contract. Without that coordination, partial-service is a cost-saving line on the proposal and a CSR risk in operation.

How Werklist runs both models

Werklist runs end to end as the default and partial-service on request. For partial-service engagements, the contract names exactly which stages of the eight-stage workflow are in scope, exactly which artefacts the buyer is responsible for, and exactly which handoff documents are shared between partners.

The four payment gates, shortlist delivered, demand letter signed, permit issued, worker landed and inducted, still apply, but in partial-service the gates may be split across vendors. The buyer holds the integration view.

Where to go next

For the model decision that pairs with this one, see EOR vs recruitment agency, what blue-collar employers should choose. For the cost dimension, see Cost-per-hire calculation for blue-collar workforce. For the time dimension, see Time-to-fill benchmarks, blue-collar 2026. For the partner-selection checklist, see Cross-border recruitment agency, selection guide for employers.

Send the brief, corridor, trade, headcount, internal capacity for source-side vs mobilise-side scope. We come back inside one business day with the scope split that fits and an honest read on whether end to end or partial-service is the better engagement. Talk to a corridor lead.