Evaluate RPO around the actual service problem

Recruitment process outsourcing is an operating decision, not a label to apply after a missed hiring target. A stalled search often grows from an unclear intake, slow manager feedback, scattered updates, a crowded approval route, thin sourcing capacity, or several causes together. Those causes require separate review. A talent solutions consultant helps a buyer name each piece of work, test assumptions against a real search, and record which duties stay within the organization before outside support enters a discussion.

Start with one recent requisition. Select a role with enough activity for participants to recall each decision and delay. Ask recruiting for intake notes, candidate status messages, an interview plan, an approval record, and a close or pause decision. Invite a hiring manager, a recruiting operations representative, and procurement where procurement owns part of purchasing. The session is not a judgment of an employee. The group needs a shared view of where work waited, where information changed hands, and where nobody knew a next move.

Use direct questions tied to dates. When did a manager request help? Who turned a broad request into a usable role brief? Which qualifications guided first outreach? Who selected interviewers? How long did feedback wait before recruiting received direction? Where did a budget question go? Who told candidates about a pause? Put each answer beside a process step, owner, input, and expected result. A map based on real events becomes a working record rather than a collection of impressions.

In a fictional review, Grace, a chief people officer, asks, “Would RPO reduce pressure on our recruiter group?” Theo, a talent solutions consultant, replies, “Let us locate each service break first. Managers describe late updates. We need to separate sourcing, feedback, approval, and status ownership.” Grace explains two business units are under a hiring freeze. A third unit expects urgent hiring after an internal product decision. Theo requests one active requisition and one paused requisition. He wants the group to distinguish current work from work dependent on a later decision.

Theo asks who writes an intake brief, who approves a change in role scope, and who receives a manager complaint. Grace says recruiters send status notes, yet managers often respond slowly after interviews. Procurement adds a review before new spending. The group sees two distinct issues. Recruiters need a shared update routine. Hiring managers need a stated feedback expectation and an escalation owner. Neither issue establishes a need for a broad provider transition as a first response.

Separate service measures by purpose. Communication measures show whether a manager receives a usable status note on an agreed rhythm and whether recruiting receives a decision after an interview. Sourcing measures show activity connected to an agreed role profile, such as reviewed prospects, accepted outreach, or qualified screens. Process measures show elapsed time between stages and recorded reasons for a pause. A hiring outcome belongs apart from those measures. An offer decline deserves discussion of role scope, compensation, interview experience, or candidate choice. Calling every result a sourcing failure weakens review quality.

Write every measure so a participant knows what counts. “Better communication” supplies no owner or check. “Recruiting sends a status note each Tuesday with open decisions and next interview dates” supplies a routine. The group still needs agreement on where records live, who checks delivery, and what follows when no decision arrives. A useful measure lets participants inspect performance without arguing over a definition after a problem appears.

Decision rights deserve equal attention. Some decisions involve a role profile, budget, work location, interview panel, offer range, or candidate disposition. Others involve search organization or a status message. During the session, make a simple decision record. For every decision, name a recommender, final approver, people needing notice, and target response time. Do not assign a provider responsibility for a manager or executive decision. Do not leave an internal owner responsible for work without access to needed information.

Data access requires a separate conversation. A possible operating model might need role details, interview feedback, candidate status, approved messages, or reporting definitions. Ask which system holds each record and who grants access under the buyer process. Ask whether names, contact details, or interview comments need a smaller audience. The consultant records the buyer process rather than suggesting an informal shortcut. The aim is a dependable handoff route, not broad information gathering before scope exists.

An escalation route should cover ordinary friction. A manager misses two feedback requests. A requisition receives a new priority after intake. A candidate requests a decision before a review meeting. An approver is absent. For each event, identify a first owner, next owner, and point for leadership notice. Avoid a long chain for routine work. A short route gives recruiting a practical response and gives leaders a view of recurring blockage.

Scope follows evidence from the map. Grace’s group might review a small set of roles in an active business unit. Another option might focus on sourcing support for roles with settled intake briefs, with internal recruiters retaining manager communication and approvals. A further option might delay outside evaluation while a new weekly manager review runs for a month. Each choice requires different information. A consultant earns trust by showing tradeoffs without treating every symptom as evidence for one answer.

Ask procurement early about its own review needs. Procurement often needs a clear service description, named decision owners, reporting expectations, review dates, and scope limits. Recruiting needs to know when procurement enters so a conversation does not halt after participants assume work is ready to begin. The buyer should name a spokesperson for each function. A meeting where five people assume someone else owns approval adds delay before an outside conversation even starts.

At a fictional follow up, Theo places an active analyst requisition on a shared screen. The manager says she interviewed two people last Friday and has not chosen a next step. Grace asks why. The manager says she is waiting for a compensation range review. Procurement confirms an existing range needs no new spending review, yet no one told recruiting. Theo records one open decision, one owner, and Tuesday as a response target. He does not label the delay a supplier issue.

The group then tests a narrower change. For four weeks, recruiting sends Tuesday status notes to each hiring manager. Every note names open decisions, candidate stage, and next interview date. A manager who misses a first feedback request receives a reminder from recruiting. A second missed request goes to Grace’s operations lead. Procurement receives notice only when a role needs a new spending decision. Those choices give the group a baseline before discussion of support scope.

Before closing, read the map aloud from intake through disposition. Invite corrections for missing owners, unclear dates, and assumptions presented as facts. Mark unresolved items as open. Grace assigns her recruiting operations lead to send a draft map by Thursday. Theo schedules a forty five minute review for the following Tuesday with Grace, one hiring manager, and procurement. At 10:15, the operations lead will open the active analyst requisition, record the feedback owner beside both candidates, and send the first Tuesday status note before the meeting ends.