TL;DR

Project RPO is a fixed-scope, time-limited recruitment process outsourcing engagement where a provider takes ownership of a defined hiring programme -- a product team build-out, geographic expansion, technology migration, or graduate intake -- and returns full control to the client on completion. Unlike enterprise RPO (a long-term outsourcing of the entire TA function) or hybrid RPO (a permanent division of responsibilities), project RPO has a defined end state. The provider delivers a specified number of hires by a specified date under a fixed or per-hire commercial model.

When Project RPO Makes Sense

Project RPO is the right model when the client has a real, time-bounded hiring need that exceeds the in-house team's capacity and that will not recur at the same volume once the project is done. The signal is a defined hiring list with a completion date -- not an ongoing staffing need, but a surge.

Typical triggers include: a new office or site opening requiring 80-150 hires over four months; a technology platform migration requiring 30-50 specialist engineers over six months; a merger integration creating immediate backfill needs across two combined entities; or a seasonal programme requiring 200 temporary workers for a three-month peak period.

The alternative comparison is always between project RPO and contingency recruitment agency. Contingency agencies charge 15-25% of first-year salary per hire. For a 50-hire programme averaging £45,000 salaries, contingency fees run to £337,500-562,500. A project RPO arrangement on the same scope, priced per hire at £4,000-6,000, comes to £200,000-300,000 -- plus the provider manages process, quality, and candidate experience, rather than racing against competing agencies to fill from the same limited pool.

The comparison shifts at low volume. For two or three specialist hires where the agency's market access and speed justify the fee, contingency beats project RPO on unit economics. The crossover point typically sits around 15-20 hires, depending on role type and salary level.

How Project RPO Works

A project RPO engagement runs in three phases.

Mobilisation (weeks 1-3). The provider embeds a team -- typically a project lead, sourcing specialists, and a coordinator -- into the client's environment, physically or virtually. They audit the existing process: ATS access, job brief quality, hiring manager availability, preferred channels, and any existing agency relationships to be managed around. They agree on the hiring plan: role-by-role breakdown, target start dates, sourcing channels for each category, and milestone checkpoints.

Delivery (project duration). The provider sources, screens, and coordinates candidate pipelines for each role according to the agreed process. Progress is reported against the hiring plan weekly -- roles opened, candidates at each stage, offers extended, offers accepted, start date confirmed. Red flags (manager availability problems, pipeline shortfalls, compensation misalignment) are raised in weekly reviews rather than discovered at the end.

Transition (final 4-6 weeks). As the project nears completion, the provider documents processes, sources, and lessons learned, and transfers the final hired cohort into the client's standard onboarding workflow. Any incomplete requisitions are handed back to the client's in-house team or to a retained agency, with warm introductions to candidates in earlier pipeline stages.

Project RPO Pricing Models

| Model | How it works | Best for | |-------|-------------|----------| | Per hire | Fixed fee per successful hire, regardless of time spent | Clear hire count, milestone-driven projects | | Management fee | Fixed monthly fee for provider team and process | Large programmes where hire count may flex | | Hybrid | Management fee plus reduced per-hire fee | Programmes with both fixed overhead and variable volume |

Per-hire pricing aligns incentives well: the provider only earns if they fill the role. The risk is cherry-picking -- providers on per-hire models are motivated to focus on easier-to-fill roles and deprioritise difficult specialist searches. Management fee models carry more delivery risk for the client if volume falls short of the plan, but give the provider margin certainty and incentive to deliver process quality across all roles.

What Separates Good from Bad Project RPO Execution

The most common project RPO failure mode is mobilisation delay. Providers who take two or three weeks to set up ATS access, brief the sourcing team, and produce first pipeline instead of using week one for substantive sourcing lose the time buffer that separates an on-time delivery from a missed deadline. Contracts should specify that sourcing activity begins no later than day five of the engagement, with first candidate profiles presented by day ten.

Hiring manager engagement is the second frequent failure point. A project RPO team produces 40 CVs in two weeks; the hiring manager reviews them across three weeks. The provider cannot shorten time-to-fill if the client-side bottleneck is feedback latency. SLAs for hiring manager feedback turnaround (24 hours for first-round CVs, 48 hours for interview feedback) should be agreed in the contract, with escalation pathways when the client misses them.

Employer brand consistency is the third. Project RPO teams sourcing on behalf of a client need access to current employer brand messaging, benefits copy, and any competitive salary data to pitch the opportunity accurately. Candidates who receive inconsistent information about the role, culture, or compensation between the RPO sourcer and the hiring manager drop out at high rates.

Project RPO in Practice

A scale-up logistics operator wins a major retail client requiring a new regional hub to be operational in four months. The hub needs 110 hires: warehouse operatives, team leaders, health and safety coordinators, and a site general manager. The in-house TA team of three cannot run a programme of this size alongside steady-state hiring without dropping quality across the board.

The company engages a project RPO provider on a 16-week engagement. The provider deploys a four-person team: a project lead, two volume sourcers for operative and team leader roles, and a specialist sourcer for the H&S and GM positions. Week-one mobilisation includes ATS setup, job brief calibration with site leadership, and agreed SLAs for hiring manager feedback. First operative candidates reach hiring managers by day eight.

By week 12, 91 of 110 roles are filled and confirmed for start. The remaining 19 -- including the GM and both H&S roles -- complete by week 16. Total project cost: £298,000 on a per-hire model. Comparable contingency agency cost for the same hires: £520,000-£680,000. The project RPO team closes the engagement with a documented sourcing playbook for any future hub openings, which the in-house team retains.