Talent Acquisition

Recruitment Process Outsourcing (RPO)

Recruitment process outsourcing is an arrangement where an external provider runs part or all of an employer's hiring, working under the employer's brand and process rather than submitting candidates as an agency does. Engagements range from a single project to the whole function, and the commercial model is usually a fee for capacity rather than a fee per hire.

What is recruitment process outsourcing?

Recruitment process outsourcing is an arrangement where a provider takes ownership of part or all of an employer's hiring and runs it as an extension of that employer. The provider's recruiters typically work under the client's brand, follow the client's process and often work inside the client's applicant tracking system, and they are measured on how the function performs rather than on individual placements. That is the line separating RPO from agency work. An agency is paid per hire and competes to supply candidates. An RPO provider is paid for capacity and capability, and is accountable for the process itself. Scope varies enormously: sourcing only, one high-volume project, an entire graduate intake, or the whole function including employer brand and analytics. The commercial model usually reflects that, with a management fee plus a variable element rather than a percentage of salary. The important consequence is that RPO changes who is accountable for hiring outcomes, which makes it a governance decision more than a procurement one.

How does RPO compare with an agency, a contract recruiter and in-house hiring?

Four ways to get recruiting capacity, and they solve different problems. In-house recruiters give you the deepest business context and the strongest employer brand consistency, and they are the slowest to scale up or down. A staffing agency is paid per hire, brings market reach you do not have, and is the right answer for a specific hard role or a market you cannot access. A contract recruiter is a temporary in-house recruiter: your process, your systems, your management, and capacity that ends when the project does. RPO sits between in-house and agency, providing managed capacity plus process ownership across a defined scope and period. Choose by the shape of the problem. One scarce role means an agency. A predictable capacity gap for six months means a contract recruiter. Hiring that is volatile, high-volume or structurally under-served, where the process itself needs work, is where RPO earns its fee. Running more than one of these at once is common and fine, provided the boundaries are written down.

  • In-house: deepest context, strongest brand consistency, slowest to flex
  • Staffing agency: paid per hire, market reach, best for specific hard roles
  • Contract recruiter: your process and systems, capacity that ends with the project
  • RPO: managed capacity plus process ownership across a defined scope

Which RPO engagement model fits which problem?

Three shapes cover most engagements. End-to-end RPO hands the provider a whole hiring function, or a whole business unit's hiring, including sourcing, screening, coordination, reporting and often the technology. It suits organisations with continuous high volume and a genuine capability gap. Project RPO covers a defined burst: a new site opening, a seasonal intake, an acquisition. It is time-boxed with a stated number of hires and a start and end date, which makes it the lowest-risk way to try a provider before committing further. On-demand or selective RPO buys recruiter capacity by the month or by the requisition while the client keeps process ownership, behaving more like flexible staffing for your talent team. Pricing usually follows the model: a management fee plus a cost per hire for end-to-end, a project fee for project work, a monthly rate for on-demand. Read what is excluded as carefully as what is included, particularly advertising spend, assessments, background checks and technology licences, which are frequently passed through.

  • End-to-end: whole function or business unit, provider owns the process
  • Project: time-boxed with a defined hire count, lowest-risk first engagement
  • On-demand: recruiter capacity by month or requisition, you keep process ownership
  • Check the exclusions: advertising, assessments, background checks, technology licences

When does RPO make sense, and when does it not?

RPO makes sense when hiring volume is high or volatile, when the internal team is structurally under-resourced rather than briefly busy, and when the process itself needs rebuilding by someone who has done it before. It works particularly well for expansion into markets where you have no recruiting presence, and for high-volume hiring where coordination rather than judgement is the bottleneck. It does not fix a broken hiring manager culture. If requisitions are approved with no plan, interviews are cancelled routinely and decisions take weeks, an external provider inherits those problems and will miss the same targets your own team missed. It is also a poor fit for a small number of senior or confidential searches, where a retained specialist suits better. Be honest about the motivation. RPO bought to cut headcount cost while keeping the same demands usually disappoints, because the assumed saving is often the capacity that was already missing. Bought to add capability and scale, it tends to hold up.

  • High or volatile volume the internal team cannot absorb
  • Markets where you have no recruiting presence at all
  • A hiring process that genuinely needs rebuilding
  • Not a fix for cancelled interviews and slow decisions
  • Not a fit for a handful of confidential senior searches

What should stay in-house when you use RPO?

Keep whatever determines who you become as an employer. Three things belong in-house in nearly every engagement. The first is the hiring decision itself, including the scorecard and the final call, because outsourcing judgement about who joins the company is a different order of decision from outsourcing coordination. The second is employer brand ownership and the candidate-facing narrative, even when the provider executes it, since that message outlives the contract. The third is your data: candidate records, pipeline history and talent pools must live in a system you own and control. Keeping the talent pool under your own account is the difference between a transition and a rebuild. Executive and confidential hiring usually stays in-house too. Everything else, including sourcing, screening, coordination, scheduling and reporting, is legitimately delegable. Write the split into the contract as a responsibility matrix rather than assuming it, because the boundary nobody documented is the one argued about in month four.

  • The hiring decision, the scorecard and the final call
  • Employer brand and the candidate-facing narrative
  • Candidate records, pipeline history and talent pools
  • Executive and confidential searches
  • A responsibility matrix written into the contract

How do you structure an RPO service level agreement?

An RPO service level agreement should measure things the provider can control and share responsibility for the rest. Good ones set targets on time to submit, shortlist quality measured as submission-to-interview conversion, offer acceptance rate, and hiring manager satisfaction. Time to fill belongs in the agreement too, but as a joint metric, since interview scheduling delays on your side move it and a provider penalised for your slowness will price for that risk. Define every term. Fill rate against what denominator, satisfaction measured how and by whom, and which day the clock starts. Include a governance rhythm: a weekly operational meeting, a monthly performance review, a quarterly business review with named owners. Agree what happens when targets are missed, whether that means a remediation plan, a fee adjustment or termination rights. Agree the data source in advance so both sides read the same recruitment analytics rather than exchanging competing spreadsheets, which is where most of these relationships go wrong.

  • Provider-controlled: time to submit, submission-to-interview, offer acceptance
  • Shared: time to fill, hiring manager satisfaction, candidate experience
  • Define every denominator and when each clock starts
  • Name the governance meetings, owners and the remedy for missed targets

How do you transition into RPO without losing pipeline data?

Treat the transition as an implementation project with a named owner on each side, because this is where pipeline data goes missing. Before anything moves, agree the system of record. If the provider works in your ATS, the data stays yours by default and that is the safer arrangement. If they use theirs, write into the contract how records are exported, in what format, how often, and who owns them at termination. Then run a discovery phase covering current process, live requisitions, hiring manager expectations, existing candidate pools and any in-flight conversations. Migrate live pipelines deliberately, with a handover per requisition rather than a bulk transfer, and tell active candidates what is changing so they do not go silent on you. Expect a dip. Any ATS implementation or process handover costs productivity for weeks while people learn, and a plan assuming day-one parity sets everyone up to declare failure. Keep the old process available until the new one is stable.

  • A named owner on each side, run as a project
  • The system of record agreed before anything moves
  • Discovery covering process, live requisitions and existing pools
  • Requisition-by-requisition handover rather than a bulk transfer
  • Active candidates told what is changing and by whom

How do you exit an RPO cleanly?

Plan the exit before you sign, because the terms are negotiable then and not later. The contract should state notice periods, what happens to in-flight requisitions, how candidate data and pipeline history are returned and in what format, and whether the provider's recruiters can be hired by you and on what terms. That last clause surprises people at the worst moment. Transition out the way you transitioned in: a defined project, a named owner, requisition-by-requisition handover, and a period where both parties run in parallel rather than a hard cutover. The asset you are protecting is the talent pool and the record of every conversation. Without it, an exit resets years of pipeline building. Capture the process knowledge the provider built as well, including question banks, sourcing playbooks and the recruitment metrics baselines, since you paid for all of it. Leaving with better process than you arrived with is a fair test of whether the engagement was worth doing.

  • Notice period and the treatment of in-flight requisitions
  • Data return format, tested during the engagement rather than after
  • Whether you may hire the provider's recruiters, and on what terms
  • A parallel-running period instead of a hard cutover
  • Playbooks, question banks and metric baselines handed back

Hiring while you work through this?

How to put this into practice

  1. 1 Define the problem first Write down what is actually failing: capacity, capability, volatility or process quality. RPO addresses some of those and none of the others, and a provider cannot fix hiring manager behaviour it does not control.
  2. 2 Scope what is in and out List which roles, regions and process stages the provider owns, and which stay with you. A responsibility matrix agreed before signature prevents the boundary argument that otherwise arrives in month four.
  3. 3 Decide the system of record Settle whose ATS holds the data before anything else. If the provider uses theirs, write export format, frequency and ownership at termination into the contract rather than trusting goodwill.
  4. 4 Compare models, not vendors Decide between end-to-end, project and on-demand engagement before shortlisting providers. Project RPO is the lowest-risk way to test a relationship, because it is time-boxed with a defined number of hires.
  5. 5 Write measurable service levels Set targets the provider controls, mark shared metrics as shared, and define every denominator and start date. Agree the data source in advance so nobody argues about whose spreadsheet is correct.
  6. 6 Run the transition as a project Do discovery, migrate live requisitions one at a time, brief active candidates, and expect a productivity dip while people learn. Set the first performance review far enough out to be meaningful.
  7. 7 Negotiate the exit upfront Agree notice, in-flight requisition handling, data return format and recruiter hiring rights before signing. Every one of these is negotiable at the start and expensive at the end.

Mistakes worth avoiding

  • Buying RPO to fix hiring manager behaviour that no external provider can control.
  • Letting the provider hold candidate records in a system you do not own or control.
  • Writing service levels on time to fill alone, which depends on interview scheduling the provider cannot control.
  • Signing with no responsibility matrix, so the boundary gets argued about in month four.
  • Expecting day-one parity and calling the engagement a failure during the normal transition dip.
  • Leaving exit terms, data return and recruiter hiring rights to be negotiated at termination.
FAQ

Recruitment Process Outsourcing (RPO) — FAQs

What is the difference between RPO and a staffing agency? +
A staffing agency is paid per hire, competes to supply candidates, and owns none of your process. An RPO provider is paid for capacity and capability, works under your brand and process, and is accountable for how hiring performs overall. The practical difference is scope and accountability: agencies deliver candidates, RPO delivers a functioning hiring process.
How is RPO priced? +
Commercial models vary by provider and engagement, and there is no standard rate worth quoting. Common shapes are a management fee plus a per-hire element for end-to-end work, a fixed project fee for time-boxed programmes, and a monthly rate per recruiter for on-demand capacity. Read the exclusions carefully, since advertising, assessments and technology licences are frequently passed through.
Is RPO cheaper than in-house recruiting? +
Sometimes, but treating it as a cost-cutting move is where most disappointment comes from. RPO usually competes with agency spend rather than with salaries, and its advantage is flexible capacity you can scale down without redundancies. Model your own total cost, including the internal management time an engagement still requires, before assuming a saving exists.
How long is an RPO contract? +
It depends entirely on the model. Project engagements run for the length of the programme, which may be a few months. End-to-end arrangements are usually multi-year, because the provider is investing in learning your business and the transition costs are real on both sides. Shorter initial terms with extension options lower risk when trying a provider.
Can you use RPO for only part of hiring? +
Yes, and it is often the sensible starting point. Selective or on-demand models cover one region, one business unit, one high-volume role family or a single stage such as sourcing. Scoping narrowly keeps your internal team in control of the rest and gives you a real basis for judging the provider before widening the arrangement.
Whose ATS should an RPO use? +
Yours, where possible. Working in your system keeps candidate records, pipeline history and reporting under your control by default, which matters enormously at exit. If the provider must use theirs, write export format, frequency and data ownership at termination into the contract before signing, and test an actual export early rather than at the end.
What should an RPO SLA include? +
Targets the provider genuinely controls, such as time to submit, shortlist conversion and offer acceptance, plus clearly labelled shared metrics like time to fill. Add definitions for every denominator, a governance rhythm with named owners, an agreed data source, and the consequence of missed targets, whether that is a remediation plan, a fee adjustment or termination rights.
How do you avoid losing candidate data when an RPO ends? +
Agree the exit at the start. Specify the export format, who owns the records, how in-flight requisitions transfer, and the notice period, then test an export during the engagement rather than after notice is served. Also capture the sourcing playbooks, question banks and reporting baselines the provider built, because you paid for that work.
Built for recruiters & hiring teams

Put this into a process that runs itself

See how Pitch N Hire handles the parts of this that eat a recruiter's week — posting, screening, scheduling and keeping every decision in one place.

Prefer to talk? Book a demo · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo