Solutions · Recruitment process outsourcing
AI sourcing for recruitment process outsourcing (RPO) providers
Recruitment process outsourcing (RPO) means an employer hands all or part of its recruitment to an external provider. For RPO providers, AIcruiters runs sourcing inside each client programme: vacancy analysis, market search, evidence-based ranking and outreach in the client's voice. Recruiters take over interested candidates, and the reasoning behind each shortlist stays visible for client reviews.
What is recruitment process outsourcing, and where does sourcing fit?
In recruitment process outsourcing, a provider takes over some or all of an employer's recruitment function. Unlike an agency that fills individual vacancies, the provider runs the process itself, often with recruiters working under the client's name. Programmes range from end-to-end recruitment for a whole organisation to a project for one business unit, location or hiring wave.
Sourcing sits at the start of every programme and determines most of what follows. If the shortlist is late, the service level is at risk; if it is weak, hiring managers lose confidence in the programme. And because the provider has committed to results for a contract period, every hour spent searching manually comes out of the programme's margin.
The term is sometimes shortened to RPO, which also stands for unrelated things such as Recovery Point Objective in IT. On this page it always means recruitment process outsourcing. The glossary lists the related recruitment terms.
How do you scale a programme when a client's hiring volume jumps?
A client announces a hiring wave for the next quarter. Two ways to respond.
Recruiters remain essential for intake, candidate conversations and hiring manager relationships. The question is who does the searching.
How do you run sourcing for several clients without mixing them up?
Each client programme becomes its own set of workflows, with its own criteria, employer voice and approval rules. Candidate data access, use and retention are limited per workflow. A candidate approached for a bank is approached in the bank's tone; a candidate for a hospital programme hears about the hospital.
- Separate workflows and rules per client programme
- Outreach in the voice each client has agreed
- Approval per action; how rules differ per client is agreed per implementation
- Search strategyNeeds approval
- Candidate selectionRecruiter reviews shortlist
- OutreachNeeds approval
- Follow-upAutomatic
- Low confidenceAlways to a recruiter
How does it help you meet service levels?
Most programme service levels depend on time: time to shortlist, time to fill, response time to hiring managers. Sourcing can start as soon as a vacancy enters the programme and runs for all open roles in parallel, so a busy week does not push the shortlist back. The guide to time to hire and cost per hire explains how to measure these steps.
Quality commitments matter as much. Vacancy intelligence makes requirements explicit before the search, and every ranked candidate shows matching experience, missing requirements and risk factors. When a hiring manager disputes a shortlist, the discussion is about the criteria, not about the recruiter.
What the record gives you for reporting
The search strategy, the reasons behind each ranking and the conversation history at handover are visible, which is useful material for client reports and quarterly reviews. What reporting and exports are possible for your programmes is agreed per implementation.
What AIcruiters does not take over
Programme management, client governance, interviews, assessments and offers. It does not decide who is hired, and uncertain cases go to a recruiter.
Which programmes are the best place to start?
High-volume professional hiring
Recurring roles in IT and tech or finance where candidates have a visible profile.
Scarce roles under a tight service level
Programmes in markets such as healthcare where shortlists arrive late.
New clients in ramp-up
Where the first months decide whether the client extends the contract.
Questions from RPO providers
Can outreach go out under our client's employer brand?
Messages are written in the tone and rules you set per programme. How sender identity is handled on LinkedIn is part of the setup we agree per client.
How is candidate data kept separate between clients?
Access, use and retention are limited per workflow. Hosting, privacy and contract requirements are covered in the technical review; see our security page.
Does it work with the ATS each client uses?
RPO providers often work in the client's ATS, and that differs per programme. For each system we assess whether a direct integration, a structured handover or another setup fits, so one programme's choice does not dictate the next.
How does it compare with giving recruiters LinkedIn Recruiter seats?
Seats work well for recruiters who know a client's market. In a programme that grows and shrinks with hiring waves, the question is whether search capacity should follow recruiter headcount. See AIcruiters vs LinkedIn Recruiter.
Is it also relevant for in-house teams?
Yes, with a different setup. See AI sourcing for in-house talent acquisition.
Test it on a role from a live programme
Bring a vacancy from a client programme. We run the sourcing workflow on it and calculate what it means for recruiter capacity and seats across the programme.