Recruitment process outsourcing (RPO) is a way of buying recruiting capacity: an outside provider takes over some or all of your hiring process and runs it as part of your team, under your brand, against targets you agree up front. For a company that needs to hire fifty or five hundred people this year and has two recruiters, RPO is one of the few ways to add capacity in weeks instead of quarters.
It is also easy to buy badly. An RPO contract signed in a hurry can leave you paying for a process you no longer control, with a hiring bar set by people who will not work alongside the hires. This guide covers what RPO is, how it compares with agencies and an in-house team, the three main models, and a checklist for deciding whether a scaling company should use one.
What is recruitment process outsourcing?
RPO is a contract in which a provider runs recruiting activity on your behalf, as an extension of your talent acquisition team, for a defined scope and period. The provider's recruiters usually work in your applicant tracking system, use your employer brand and email domain, and report against your hiring plan.
The difference from an agency is the unit of work. An agency is paid to fill a role. An RPO is paid to run a process: sourcing, screening, scheduling, candidate communication and offer support, across many roles at once.
How does RPO recruitment work?
Most RPO engagements follow the same shape.
- Scoping. You agree which roles, locations and stages are in scope, the expected volume, and the service levels.
- Onboarding. The provider's recruiters learn your roles, your hiring managers and your systems. This is where most engagements succeed or fail.
- Delivery. The provider sources, screens and moves candidates through your process. Your hiring managers still interview and decide.
- Reporting. Regular reviews against the agreed metrics, usually weekly at the start.
- Exit or renewal. At the end of the term the provider hands back the pipeline, the data and the process documentation.
Scale hiring without outsourcing your hiring bar
Give Cohesyve a job description. It sources, reaches out, tests candidates on simulations of the real work and returns a ranked shortlist before your first interview.
The three RPO models
| Model | What the provider runs | Best fit |
|---|---|---|
| End-to-end | The whole recruiting function for agreed roles or regions | Sustained high volume with no in-house team to speak of |
| Project | A defined hiring push, such as staffing a new office or a product launch | A known surge with an end date |
| On-demand | Extra recruiter capacity, often for sourcing and screening only | An in-house team that is temporarily overloaded |
Some providers sell a fourth option, sometimes called selective or partial RPO, where they take one stage, typically sourcing or screening, across all roles. In practice it behaves like the on-demand model with a narrower scope.
RPO vs agency vs in-house: which should you use?
The short answer: agencies for one-off and specialist roles, RPO for sustained volume you cannot staff yet, in-house for hiring that is core to the business and will continue for years.
| Agency | RPO | In-house team | |
|---|---|---|---|
| Unit of work | A filled role | A recruiting process | Everything |
| Typical commercial model | Fee per hire | Management fee, often with per-hire or per-stage elements | Salaries and tools |
| Speed to start | Fast | Weeks | Months to hire recruiters |
| Control of the process | Low | Shared | Full |
| Knowledge you keep | Little | Some, if the contract requires handover | All of it |
| Best for | Specialist or occasional roles | A volume surge lasting months | Long-term core hiring |
Commercial terms vary widely between providers, so ask each one for their model in writing and compare total cost against your hiring plan. We have a longer comparison of the three routes in recruitment agency vs in-house vs software.
When should a scaling company use RPO?
Use RPO when three things are true: the volume is high, it will last at least six months, and you cannot hire enough recruiters fast enough to meet it. If any of the three is missing, a cheaper option usually works better.
Run through this checklist before you talk to a provider.
- Is the plan real? A board-approved hiring plan with roles and dates. RPO built on a hopeful plan becomes an expensive bench.
- Are the roles repeatable? RPO works best on roles you hire again and again, such as account executives, support agents or mid-level engineers. Unique senior roles are better suited to search firms.
- Do you have scorecards? If you cannot write down what good looks like for each role, the provider will invent its own definition.
- Can hiring managers keep up? RPO increases candidate flow. If managers already take a week to give feedback, more candidates will make that worse.
- What happens after the surge? Decide now whether you will build an in-house team to take over, and write the handover into the contract.
A worked example (illustrative)
The numbers below are invented to show the arithmetic. They are not benchmarks.
A company plans to hire 120 customer success and sales roles over nine months. It has two recruiters, each able to close roughly four hires a month on roles like these. That is about 72 hires over the period, leaving a gap of around 48.
| Option | What it fixes | What it risks |
|---|---|---|
| Hire four more recruiters | The gap, long term | Two to three months before they are productive |
| Agencies for the gap | Speed on the first hires | Cost per hire and inconsistent candidate quality |
| Project RPO for the gap | Capacity within weeks, one process | Control of screening, unless the company keeps the scorecard |
In this example the company might choose project RPO for the nine months, keep its own recruiters on the senior roles, and require the provider to use its scorecards and interview guides.
How to keep the hiring bar when you outsource
The biggest risk in RPO is the hiring bar drifting. The provider's recruiters are measured on throughput. Your team will live with the hires. Close the gap with five rules.
- You own the definition of good. Write a scorecard per role and require the provider to screen against it. Our interview scorecard template is a starting point.
- You own the interviews. Keep structured interviews run by your people, with the same questions for every candidate in a role.
- Test the work early. A short work sample or job simulation before interviews gives you evidence the provider cannot inflate.
- Measure quality as well as speed. Track first-year performance and early attrition by source, and review them with the provider. See quality of hire metrics.
- Audit a sample. Each month, read a random set of rejected applications. If good candidates are being screened out, you will see it.
What to ask an RPO provider
- Which roles like ours have you hired for, and can we speak to a client who did?
- Who will actually work on our account, and how long have they been with you?
- Will your recruiters use our applicant tracking system, our scorecards and our email domain?
- How do you price, and what changes the price?
- What do you hand back at the end: candidate data, pipeline, documentation?
- If you use AI tools to screen or rank candidates, which ones, and what bias audits and candidate notices come with them? Rules on this apply in New York City now and in the EU and Colorado from 2027. Our guide to AI hiring laws has the detail.
- What are the exit terms if the service levels are missed?
RPO metrics to agree before you sign
| Metric | Why it matters |
|---|---|
| Time to shortlist | Shows whether sourcing and screening are keeping pace |
| Shortlist-to-interview rate | Shows whether the shortlist matches what managers want |
| Interview-to-offer rate | The clearest sign of screening quality |
| Offer acceptance rate | Shows candidate experience and offer quality |
| Time to hire | The headline number, but only one of them. See reduce time to hire |
| Quality of hire at six months | The number that tells you whether the bar held |
Where software fits
RPO adds people to a process. Software changes how much work each step needs. Many scaling teams now combine the two, or replace part of an RPO scope with tools that handle sourcing, outreach and first-round screening. Cohesyve is one example: you give it a job description, and it sources candidates, reaches out to them, tests them on AI job simulations of the real work and returns a ranked shortlist before interviews. Whether you use it or not, the principle is the same: whoever runs the top of the funnel, base the shortlist on evidence of the work.
Frequently asked questions
Is RPO the same as a recruitment agency?
No. An agency is paid per role it fills and usually works on a few roles at a time. An RPO provider runs your recruiting process across many roles, in your systems and under your brand, for an agreed term.
How long does an RPO contract usually last?
It depends on the model. Project RPO runs for the length of the hiring push. End-to-end RPO is usually a multi-year arrangement. Ask each provider for its standard terms and exit clauses.
Can a startup use RPO?
Yes, usually the project or on-demand model, for a funded hiring surge. A startup hiring a handful of people a year is normally better served by a founder-led process, a first recruiter or agencies for specialist roles.
Does RPO lower quality of hire?
It can if the provider sets the bar. It does not have to if you own the scorecards, the interviews and the final decision, and measure quality by source.
What should stay in-house with RPO?
The definition of each role, interview design, the hiring decision, offers for senior roles, and your employer brand. Outsource capacity, keep judgement.
