Defining RPO Scope: Role Intake, Clear Owners and a Useful Weekly Pipeline Review
Recruitment process outsourcing works best when its scope is defined stage by stage, with one clear owner for each stage and a named contact on each side. Start with a role intake that ties requirements to the job's real tasks, agree how candidates and feedback move between you, and use a weekly review to clear decisions and blockers rather than to count CVs.
Nextwo ·
This guide is for HR, talent acquisition and hiring managers at Saudi companies that use or are considering recruitment process outsourcing (RPO).
An RPO engagement can start with nothing more than a job title, a salary range and a request to send candidates. Shortlists arrive, hiring managers reject most of them, feedback slows down, and each side concludes that the other is the bottleneck.
The missing piece in that situation is not effort. It is a shared definition of the scope: which stages the provider owns, what a qualified candidate means for this particular role, and who must decide what, by when.
The short answer: write down who owns each stage before sourcing starts, build every intake from the job's real tasks, and judge the weekly review by the decisions it clears. Keep the final hiring decision inside your organization, and treat any timeline as a plan, not a promise.
Map the stages before you agree the service
“We outsourced recruitment” can mean anything from sourcing alone to almost the whole process. Write down each stage and decide who owns it. The table shows common options; your arrangement should state its own.
| Stage | Provider can own | Your organization usually keeps | Decide and write down |
|---|---|---|---|
| Role intake | Running the intake and recording it | Business need, approved budget, must-haves | Who signs off the intake |
| Sourcing | Searching for and approaching candidates | Approval of channels that represent your brand | Which channels and messages are used |
| Screening | First screening against the intake | Agreement on screening criteria | What a qualified candidate means |
| Technical assessment | Scheduling and administration | Content of the assessment and the assessors | Who designs it and who scores it |
| Interviews | Coordination and candidate preparation | Interview panel and evaluation | Feedback deadlines |
| Hiring decision | Collating the evidence | The decision itself | Who has final authority |
| Offer | Supporting the conversation if agreed | Offer approval and terms | Who can approve exceptions |
| Handover to onboarding | Passing records to your team | Onboarding and employment | What information transfers, and how |
The point is not to maximize what the provider owns. It is to make sure every stage has exactly one owner, and that each owner knows it.
The role intake checklist
The intake is the cheapest place to prevent later problems. The US Office of Personnel Management describes job analysis as examining a job's tasks and the competencies they need, and how the two connect, to set job-related requirements. It is US federal guidance, used here as a general method, not as a Saudi standard. Applied to an intake, it means the requirements should come from the work.
Cover these points before sourcing begins:
- Business reason: what work is not getting done today, and what triggered the hire.
- Main tasks: five to eight tasks the person will spend most time on in the first year, taken from real work such as backlog items, systems and stakeholders.
- Competencies: the knowledge and skills each task needs, at what level, split into must-have and trainable.
- Evidence: how each must-have will be checked, for example a screening question, a work sample or a structured interview question.
- Constraints: work location and arrangement, language needs, the approved salary range and the earliest realistic start window.
- Deal-breakers and preferences: kept in separate lists so preferences do not quietly become filters.
- Interview panel: names and available interview slots for the coming weeks.
- Decision owner: who makes the final call and who can approve exceptions.
- Calibration: an early small batch of profiles reviewed together to test whether the brief and the market agree.
- Feedback turnaround: an internal commitment on how quickly CVs and interviews receive feedback.
If an item cannot be answered, that is useful information in itself. A role without a decision owner or interview slots is not ready for sourcing, however urgent it feels.
Handoff rules that prevent drift
Friction tends to appear where work passes between the two sides. Agree these rules with the provider in writing:
- Qualified candidate: a candidate who meets every must-have with recorded evidence, not just a matching CV.
- Submission format: a short summary against the intake criteria with each profile, so reviewers compare like with like.
- Feedback format: a reason for every rejection, tied to an intake criterion or recorded as new information.
- Brief changes: a change to the must-haves triggers a short re-intake, not a silent shift in screening.
- Candidate communication: who informs candidates at each stage, so no one is left waiting without an answer.
- Candidate data: what you share, where it is stored, who can access it and how long it is kept, checked against your own policies.
Who owns what: a simple owner checklist
| Activity | Provider | Hiring manager | HR or talent team | Finance or procurement |
|---|---|---|---|---|
| Approve the role and budget | Informed | Requests | Coordinates | Approves |
| Keep the intake current | Updates | Owns the content | Reviews | Not involved |
| Source and screen | Owns | Informed weekly | Informed weekly | Not involved |
| Technical assessment | Coordinates | Owns | Supports | Not involved |
| Final hiring decision | Provides evidence | Decides | Advises | Not involved |
| Offer approval | Supports if agreed | Recommends | Prepares | Approves within policy |
| Provider performance review | Reports | Gives feedback | Owns | Reviews cost and terms |
Adjust the columns to your organization. What matters is that each row has one clear owner.
A weekly pipeline review that leads to decisions
A useful weekly review is short, perhaps 30 minutes, and ends with decisions and owners. Counting candidates is part of it, but the purpose is to find where candidates are waiting and why.
A practical agenda:
- Brief changes: anything new from the business since last week.
- Flow by stage: how many candidates sit at each stage compared with last week, read as movement rather than as a target.
- Waiting time: which candidates are waiting for a decision, from whom, and since when.
- Rejection reasons: grouped by intake criterion, to show whether the brief, the screening or the market needs attention.
- Blockers: panel availability, approvals, salary range or assessment logistics, each with an owner.
- Decisions this week: what must be decided, by whom and by what date.
A one-line-per-role tracker keeps the review focused:
| Role | Stage with the longest wait | Waiting on | Since | Decision needed and owner |
|---|---|---|---|---|
| Example: senior data engineer | Interview feedback | Hiring manager | Last Tuesday | Add a second interviewer (hiring manager) |
Read the patterns, not just the numbers. Many rejections for a reason that is not in the intake suggest that the need has changed without the brief being rewritten. Candidates waiting at your feedback stage point to a capacity problem on your side. Offers declined for similar reasons raise a compensation or process question to take back to the business. Track the elapsed time at each stage to find where work waits, not to promise a hiring date.
A worked example (hypothetical)
A hypothetical company asks its RPO provider for a senior data engineer. The intake shows that most of the first year is maintaining existing data pipelines and migrating two of them to a new platform. The must-haves become pipeline design, the migration tooling the team already uses, and working with analysts on data definitions.
After two weekly reviews, most rejections cite a lack of streaming experience, a requirement that was never in the intake. The hiring manager confirms that it matters for one planned project. The team runs a short re-intake, adds streaming as a must-have with a way to check it, and discusses a wider salary range with finance. The review also shows candidates waiting more than a week for second interviews, so the hiring manager adds a second interviewer to the panel.
Nothing in this example depends on sourcing harder. The improvements came from a clearer brief and from decisions that someone owned.
Questions to ask any RPO provider
- How do you run and record the role intake, and who signs it off?
- What does your weekly report contain, and can it show waiting time by stage and rejection reasons?
- Who is our named contact, and who covers when they are away?
- What happens when the brief changes partway through a search?
- Who communicates with candidates at each stage?
- How do you store, share and retain candidate data, and how does that fit our policies?
Next step
Run the intake checklist on your next open role before any sourcing starts, and hold the first weekly review a week later. If you are considering an external recruitment partner, Nextwo's RPO service page describes how its recruitment service is organized. Test it against the questions above, as you would any provider.
Frequently Asked Questions
Does an RPO provider decide who we hire?
It should not. A provider can source, screen and coordinate, and it should present the evidence clearly. The hiring decision stays with the person your organization names as the decision owner.
Should the weekly review include candidate names and CVs?
Share only what the decisions in that meeting need, and follow your own data policies. A review can often work with role-level figures and a short list of the candidates who are waiting for a decision.