RPO advice: how to get the most from a Recruitment Process Outsourcing partnership
Updated May 2026
Most of what's written about RPO is about choosing a provider. Less is written about what happens next, which is odd, because that's where partnerships succeed or quietly fail. We've run enough of them to know the difference isn't usually the provider's recruiters. It's seven things the client does, or doesn't, in the first few months. Here they are.
1. Know what you want before you sign
The partnerships that work start with a specific objective: cut time-to-hire for operations roles from nine weeks to five, stop paying agency fees on customer service hiring, get a graduate intake of forty recruited by August. "Improve our recruitment" isn't an objective; it's a hope. If you can't say what the provider should have changed by month six, agree it before the contract, not after. What is Recruitment Process Outsourcing (RPO) and why does your business need it? covers the decision; this post assumes you've made it.
2. Choose for fit, then get out of the way
Sector experience, a track record in your kind of roles, a working style your hiring managers can live with: how to find a reputable RPO provider sets out the test. Once chosen, treat them as your team, because that's what they are. Providers who are managed like an agency perform like one.
3. Give them the data and the systems on day one
The single biggest cause of a slow start is access: no ATS login, no email address, no view of the hiring plan, no baseline numbers. A provider can't improve a process it can't see or report on results it can't measure. Systems access and a baseline (current time-to-hire, cost per hire, offer acceptance, source of hire) in the first two weeks is the difference between a partnership that shows results in month three and one that's still explaining itself in month six.
4. Bring the hiring managers with you
An RPO changes how hiring managers work: how they brief, how quickly they give feedback, who schedules the interviews. If they hear about it from the provider rather than from you, they'll treat it as an agency to be ignored. Tell them what's changing and why, name what you expect of them (a brief within two days, interview feedback within one), and back the provider when the first manager tries to route around the process.
5. Agree the numbers and look at them
Time-to-hire, cost per hire, offer acceptance, quality of hire at ninety days and twelve months, candidate experience. Agree them at the start, against the baseline, and look at them every month with the provider in the room. Reporting that nobody reads is a cost; reporting that drives a conversation is the point. Recruitment as an operating model sets out what that reporting should contain.
6. Say yes to the changes you hired them for
A good provider will propose things: a shorter interview process, a different sourcing channel, structured scorecards, a change to the ATS workflow. Some will feel uncomfortable, because they're changes to how the business has always done it. That's the value. A client that hires a provider for its expertise and then declines every recommendation has bought recruiters, not RPO.
7. Run the relationship, not just the contract
Weekly on the operational numbers, monthly on the KPIs, quarterly on the relationship: is the scope still right, has the hiring plan changed, what should stop and what should start. Name an owner on your side who has the authority to decide. And plan the exit from the start: who owns the data, the pipeline and the process if it ends, because a partnership with a clear exit is one both sides work harder to keep. How to run the RPO reviews themselves, and which measures to put in the contract, is in how to review your RPO partner.
Where Vermelo comes in
We build all seven into how an engagement starts, because we'd rather have the conversation about objectives, access and hiring managers in week one than the conversation about why the numbers haven't moved in month six. The RPO solution page sets out how we run it.
Need some help, whether you're choosing a provider or trying to get more from the one you have?
Making RPO work, answered
Typically three phases (to be discussed with the RPO provider). For example, Weeks one to four: discovery and set-up. The provider maps your current process, roles, hiring managers, systems and data, agrees the scope and the KPIs, and gets access to the ATS, email and calendars. Weeks four to eight: the provider takes over live roles while the baseline is measured, so the first numbers you see are yours, not theirs. Weeks eight to twelve: the process changes start, the reporting settles into a rhythm and the first review happens against the baseline. If nobody has agreed what good looks like by week four, or the provider is still waiting for systems access in week six, the partnership is already behind.
Rarely because the provider cannot recruit. Usually one of four things. Scope that was never clear, so the client thinks employer brand is included and the provider thinks it is extra. Hiring managers who were never told, and treat the provider as an agency to be ignored. Data the provider cannot get at, so the reporting is guesswork and the improvements never land. And a governance gap: no regular review, no named owner on the client side, and problems that fester for a quarter before anyone says them out loud. All four are fixable in the first month and expensive by the sixth.
Weekly on the operational numbers (open roles, pipeline, time in stage, offers), monthly on the KPIs against the baseline (time-to-hire, cost per hire, offer acceptance, candidate experience), and quarterly on the relationship itself: is the scope still right, has the hiring plan changed, what should the provider stop doing and start doing. Then an annual review against the original business case. The weekly one is the one that keeps the partnership honest; the quarterly one is the one that keeps it relevant.