Recruitment Process Outsourcing

How RPO works

An RPO provider takes ownership of recruiting activity that would otherwise sit with an internal TA team or a set of agencies. Its recruiters, sourcers and coordinators work under your employer brand, often with your email domain and inside your applicant tracking system. Candidates usually do not know they are talking to an outsourced recruiter.

Scope is agreed in a contract and statement of work. A full RPO typically covers workforce planning input, sourcing, screening, interview scheduling, offer management and onboarding handoff. A narrower scope might cover only sourcing and screening for one business unit.

The defining feature is that the RPO owns the process and the results, not just the delivery of candidates. It reports on recruiting metrics like time to fill, cost per hire, hiring manager satisfaction and quality of hire, and those metrics are usually tied to service levels in the contract.

The main RPO models

• End-to-end (enterprise) RPO. The provider runs all permanent hiring for the whole company or a large division. Typically a multi-year contract.
• Project RPO. A defined hiring push with a start and end date: opening a new distribution center, staffing a new contact center site, a product launch. For example, 300 hires in 16 weeks.
• Selective or functional RPO. Only certain job families, such as all technology hiring or all hourly hiring in one region.
• On-demand or recruiter-on-demand. Embedded recruiters rented by the month, without full process ownership. Closer to staff augmentation than true RPO.
• Hybrid. The internal TA team keeps executive and specialized roles while the RPO handles high-volume or early-career hiring.

Hybrid is the most common setup at large employers. The in-house team keeps the work where relationships and judgment matter most, and the RPO absorbs the volume.

How RPO pricing works

RPO contracts typically mix two components:

• Management fee: a fixed monthly fee covering the dedicated team, technology and account management.
• Per-hire fee: a fee for each successful hire, often a flat amount by role tier.

Other structures include a pure cost-per-hire model, a pure fixed fee based on recruiter headcount, or a percentage of first-year salary that is far lower than agency fees.

Worked example: a regional health system expects 1,200 hires next year, 900 of them hourly (patient access, environmental services, CNAs) and 300 licensed nurses and allied health. An RPO quotes a $55,000 monthly management fee plus $600 per hourly hire and $2,500 per clinical hire. Annual cost: $660,000 + $540,000 + $750,000 = $1,950,000, or about $1,625 per hire. The health system was spending roughly $3.1 million on agency fees for the nurse roles alone, so the case rests on whether the RPO can actually fill those nurse roles without falling back on agencies.

RPO vs staffing agency

A staffing agency is paid per placement and competes with other agencies to submit candidates. It works under its own brand, keeps its candidate database, and its incentive is to fill the role it is paid for.

An RPO works under your brand, builds your talent pipeline in your systems, and is paid to run the process well across all roles in scope. It has no reason to steer a candidate toward one role over another, and the candidate data belongs to you.

Agencies also supply temporary workers who stay on the agency's payroll. RPO hires go on your payroll. For temporary and contract labor, the comparable outsourced model is a managed service provider, and many large employers run both: an RPO for permanent hiring, an MSP for contingent labor.

RPO vs in-house recruiting

In-house recruitment gives you full control, deep knowledge of the business and recruiters who stay. It is harder to scale up and down. Hiring and laying off recruiters every time demand changes is slow and expensive.

RPO gives flexible capacity, mature processes and technology from day one, and reporting that comes with the contract. You give up some control and pay a margin on top of recruiter costs.

Practitioners usually recommend RPO when hiring volume is high and swings by season or project, when the internal team is stretched across too many job families, or when a company is entering a new market and needs recruiters with local knowledge quickly.

Common mistakes when outsourcing recruitment

• Outsourcing a broken process. If hiring managers take ten days to give feedback, an RPO will not fix that alone. Agree on manager SLAs in the contract.
• Weak service levels. Measure what matters: time to fill, offer acceptance, 90-day retention and hiring manager satisfaction. Volume of resumes submitted is not a quality measure.
• No transition plan. RPO implementations typically take 60 to 120 days. Plan open requisitions, data migration and who owns which roles during the handover.
• Losing the data. Make sure candidate records live in your ATS and stay with you if the contract ends.
• Ignoring culture. RPO recruiters need real access to hiring managers and the business. Treating them as a vendor at arm's length produces generic hiring.

Compliance notes

Because the RPO acts as your agent, its recruiting activity is treated as yours for most legal purposes. Federal contractors need the RPO to keep applicant records and data that support OFCCP obligations. If the provider uses automated screening or AI tools, you remain responsible for adverse impact under federal anti-discrimination law, and in New York City an automated employment decision tool used for hiring needs a bias audit under Local Law 144. Data protection laws such as GDPR apply if you hire in Europe. Requirements vary by state and country.