Recruitment process outsourcing (RPO)
A model where an external provider takes over part or all of a company's recruitment function, providing people, process, and technology under a service level agreement, typically on a cost-per-hire or retained basis.
Michal Juhas · Last reviewed June 13, 2026
What is recruitment process outsourcing (RPO)?
Recruitment process outsourcing is when a company contracts an external provider to operate some or all of its hiring function. The provider uses the company's brand, ATS, and process, and is paid under a service agreement rather than per-placement. They act as an extension of your talent acquisition team, not as a vendor filling one-off roles.
In practice
- A fintech scale-up growing from 80 to 300 employees in 18 months brings in an RPO provider to own sourcing, screening, and interview coordination across all technical and commercial roles while two internal recruiters focus on executive and culture-sensitive hires.
- A retailer with seasonal hiring spikes uses a selective RPO arrangement to outsource high-volume store associate recruiting between March and August, then ramps the provider back down when the season ends.
- A CPO might say "we are running an RPO motion" to mean the company is using outsourced recruiters under their brand rather than posting roles on job boards or using contingency agencies.
Quick read, then how hiring teams use it
This is for HR leaders, CPOs, and TA leaders evaluating whether to outsource part or all of their recruitment function. Skim the first section for a shared definition. Use the second when evaluating provider options or structuring a contract.
Plain-language summary
- What it means for you: An external team runs your hiring process under your brand and SLA. You pay for capacity and outcomes, not headcount.
- How you would use it: Define which roles or stages to outsource, agree an SLA with measurable output targets, retain ATS ownership and data portability rights, and keep an internal owner for hiring manager relationships.
- How to get started: Calculate your current cost-per-hire and time-to-fill by role type. Request proposals from two or three RPO providers for the same scope. Compare against the all-in cost of the equivalent internal team including benefits, tools, and management overhead.
- When it is a good time: High-volume growth phases, geographic expansion, or a restructure that requires rapid TA scale-up or scale-down.
When you are running live reqs and tools
- What it means for you: RPO affects your ATS configuration, sourcing tool access, interview coordination workflows, and employer brand. The provider needs system access and process documentation to be effective; without those, you pay for a team that spends its first month rebuilding institutional knowledge.
- When it is a good time: After internal process documentation is solid. If your ATS workflow is undocumented and your JDs are inconsistent, RPO onboarding takes longer and produces worse results than if you hand over a clean operating model.
- How to use it: Define who owns each decision point in the hiring process (hiring manager, RPO recruiter, internal TA lead). Agree escalation paths for offers above a certain level or roles with sensitive scope. Run a weekly scorecard review against SLA metrics rather than waiting for monthly reports.
- How to get started: Pilot with one role type or one geography before committing to full RPO. Define your success metrics for the pilot, run it for 90 days, and use the data to decide whether to expand or adjust.
- What to watch for: Provider recruiters who do not know enough about your culture or product to represent the employer brand convincingly. SLAs that focus on activity metrics (CVs submitted) rather than outcome metrics (offers accepted). Contracts with no data portability clause.
Where we talk about this
On AI with Michal sessions, RPO comes up in the AI in recruiting track when discussing how workflow automation and AI tools change what an RPO provider can deliver efficiently, and how to evaluate whether provider-managed sourcing is producing pipeline that feeds your ATS effectively. See /workshops for the next live session.
Around the web (opinions and rabbit holes)
Third-party creators move fast. Treat these as starting points, not endorsements.
YouTube
- Search "recruitment process outsourcing explained" for overview content; the RPOA (Recruitment Process Outsourcing Association) publishes vendor-neutral educational material worth starting with.
- Podcast episodes from HR Leaders and Talent Acquisition Leaders on YouTube cover RPO buyer-side perspectives worth watching before you draft an RFP.
- r/humanresources has honest threads on RPO experiences including failed engagements, which are more useful than vendor case studies.
- r/recruiting includes recruiter perspectives on working for RPO providers, helpful context for understanding provider team dynamics.
Quora
- What is the difference between RPO and a staffing agency? collects practitioner answers worth reading before framing your own evaluation.
RPO model comparison
| Model | Scope | Cost structure | Internal control |
|---|---|---|---|
| Full RPO | End-to-end TA | Retainer or cost-per-hire | Low |
| Selective RPO | One stage or role type | Volume-banded | Medium |
| Staffing agency | Single role | Per-placement fee | High |
| Contract recruiter | Embedded individual | Day rate | High |
Related on this site
- Glossary: Workflow automation, Talent acquisition, Headcount planning, MSP workforce, Quality of hire
- Blog: AI sourcing tools for recruiters
- Guides: Sourcers
- Live cohort: Workshops
- Membership: Become a member
Frequently asked questions
How does RPO differ from using a staffing agency or headhunter?
A staffing agency fills individual roles, charges a placement fee per hire, and operates as a vendor with limited access to your hiring process. An RPO provider embeds inside your organisation, typically using your ATS, your job descriptions, and your employer brand, acting as your talent acquisition team under SLA. They own the process from sourcing to offer. A headhunter or retained search firm works on a specific mandate, usually for senior roles, and is paid regardless of outcome. RPO is distinct from all three because the provider manages the full end-to-end operation, not just individual placements. The commercial model is usually cost-per-hire, monthly retainer, or volume-banded, agreed in a master services agreement.
What does an RPO SLA typically cover?
Time-to-fill by role type, cost-per-hire versus benchmark, hiring manager satisfaction scores, offer acceptance rate, and applicant-to-hire ratio. Some SLAs include diversity targets for shortlist composition or interview slate representation. Quality-of-hire and 90-day retention are increasingly included but require defined measurement methodology agreed upfront. Service credits and exit clauses matter as much as the performance metrics: an RPO contract with no exit path creates dependency risk if the provider underperforms. SLA negotiation is also the right moment to define what data belongs to you, including the ATS records, candidate pipeline, and sourcing lists, when the engagement ends.
What is the difference between full RPO and selective RPO?
Full RPO means the provider owns end-to-end talent acquisition: workforce planning, sourcing, screening, interview coordination, offer management, and onboarding support. Your internal TA team (if one exists) is usually transitioned into or absorbed by the RPO. Selective RPO, sometimes called project or modular RPO, outsources one or more stages of the funnel. A company might outsource sourcing only, keeping internal recruiters for interviews and offers. Or outsource a specific role type (volume hourly) while keeping senior and technical hiring internal. Selective RPO is lower risk and lower commitment than full RPO and is often a better fit for companies with fluctuating hiring volume or a strong internal culture of recruiter ownership.
When does RPO make commercial sense?
When hiring volume is large enough to justify the fixed cost of embedding a provider team, when you lack the internal TA infrastructure to handle a growth phase, or when a restructure means you need to scale down headcount fast. RPO also makes sense when you want to enter a new market or geography without building a local TA team from scratch. The commercial break-even versus maintaining an internal team depends on your cost-per-hire, recruiter-to-hire ratio, and the speed at which volume can change. For companies with fewer than 50 hires per year, selective RPO or contract recruiter arrangements are usually more efficient than full RPO.
What are the risks of RPO and how do you manage them?
Dependency risk is the biggest: if the provider underperforms or the relationship ends, you may not have retained institutional knowledge about your sourcing channels, interview process, or candidate pipeline. Mitigate by keeping ATS ownership, defining data portability rights in the contract, and maintaining a thin internal TA team to own process documentation and hiring manager relationships. Brand dilution is also a risk if recruiters presenting under your employer brand do not know your culture well. Counter this with onboarding investment, brand training, and candidate experience audits. Technology lock-in is a risk if the RPO uses proprietary tools not accessible after the engagement ends. Agree tool and data portability before signing.