Ask five health system leaders to define RPO scope and you’ll get five different answers. Some think it means handing recruiting entirely to an outside firm. Others think it’s a fancy name for a staffing agency with a longer contract. Neither is quite right, and the confusion around RPO scope for health systems costs time during vendor conversations that should be spent on fit, not definitions.
The stakes for getting this wrong have gone up. Hospital operating margins averaged a median 2.7% in 2025, but swung between 0.3% and 5.0% depending on the month, according to Kaufman Hall data cited in a Staffing Industry Analysts report. Health systems can’t afford recruiting capacity that sits idle in slow months and flounders in busy ones.
At the same time, temporary order fill rates in healthcare staffing sit around 47%, and direct hire fill rates around 22%, reflecting how much clinician capacity remains constrained across the industry. A stretched internal TA team isn’t going to be able to close that gap by working harder. The question is where an outside partner can add the needed capacity.
What typically moves to an RPO partner
Sourcing and pipeline building
This is the bulk of the work and the easiest to hand off. Building candidate pools for hard-to-fill roles, maintaining outreach cadences, and keeping a pipeline warm between openings is labor-intensive and doesn’t require institutional knowledge of the health system.
Initial screening and scheduling
Resume review against role requirements, first-round phone screens, and interview coordination with clinical hiring managers. This is where a lot of internal recruiter time disappears, and it’s work that doesn’t need to happen inside the four walls of the organization.
Candidate communication and experience
Status updates, timeline management, keeping candidates warm through a multi-week interview process. Health systems with inconsistent candidate experience across departments often trace it back to this exact function being under-resourced internally.
Offer logistics
Drafting and extending offers, coordinating start dates, handling the administrative back-and-forth. The decision to make the offer stays internal. The mechanics of extending it don’t have to.
What should stay in-house
Final hiring decisions
No RPO partner should be making the call on who gets hired. They build the shortlist. The hiring manager and department leadership make the decision.
Culture and team fit assessment
A good outside recruiter can spend time with an organization and team and understand what makes them tick. They can screen for qualifications and interest. But they can’t sit in on a department’s Tuesday morning huddle and know whether a candidate will mesh with that specific team’s dynamic.
Compensation approval
Comp bands, exceptions, and sign-on structures are internal decisions tied to budget and equity across the organization. RPO partners can execute on approved terms. They shouldn’t be setting them.
Credentialing sign-off
RPO can coordinate the credentialing process and chase down documentation, but the actual verification and approval needs to stay with the health system’s credentialing office or medical staff services team.
Where things blur
The line gets fuzzy around managed service provider (MSP) and vendor management system (VMS) territory, where RPO functions can start to overlap with broader workforce management. It also shifts depending on role type. Allied health and nursing RPO engagements tend to run higher volume and lean harder on the sourcing and screening side. Physician RPO usually involves more hands-on relationship management earlier in the process, since physician candidates are fielding multiple offers and expect a slower, more personal courtship.
This is exactly why scope needs to be spelled out before a contract is signed, before a department head is frustrated that “the RPO team” made a call they had no authority to make.
Before signing anything
A health system evaluating an RPO partner should get specific answers to a few questions: Who has final say on candidate advancement at each stage? What happens to compensation exceptions? Who owns credentialing coordination versus credentialing approval? How does the partner report pipeline visibility back to internal leadership, and how often?
Vague answers to any of these means that it hasn’t been thought through. That ambiguity can show up later as friction between departments and the outside team. A good RPO partner is an extension of your team, not competition for it.
