Assess recruiter capacity before recommending a hiring change

Leaders often describe a recruiting team as overloaded when a delay sits in approval, interview scheduling, or offer review. A talent solutions consultant helps leaders map work from requisition request through accepted offer. Count steps, owners, volume, and waiting time before suggesting a hiring change. A request for more recruiters deserves attention, yet a headcount answer without a process view risks treating a visible symptom instead of a delay creating pressure.

Start by agreeing on the question. “Do we need more recruiters?” invites an early answer. A better question asks where recent requisitions spent time, who owned work during each interval, and what recruiters performed while roles waited. The review does not need a perfect data project. A small sample of recent roles gives enough material for a useful first conversation when date and ownership records exist.

In a fictional situation, consultant Darius meets a manufacturing HR team. Director Elena says, “We need more recruiters. Open roles keep sitting.” Darius asks, “Where do current requisitions wait longest?” Recruiter Noah answers, “We spend Mondays chasing manager approvals and interview times.” Darius replies, “Let us compare approval and interview response waits with sourcing time for ten recent roles. Then we will ask managers what holds replies.” Elena agrees to provide dates and invite two supervisors.

Before a session, Darius requests a limited set of fields for every role. He needs requisition request date, approval date, first sourcing activity, first qualified candidate presented, interview request date, interview confirmation date, decision date, offer approval date, offer sent date, and accepted offer date. He also asks for an owner during every wait. Personal candidate details do not help with this first capacity discussion, so a sample uses role identifiers and job families. Authorized team members retain original records rather than copying unnecessary information into a workshop file.

Draw the current process in ordinary language. One fictional team's map starts when a manager requests a role. HR checks required information. A finance reviewer approves a request. A recruiter begins sourcing. The manager selects interview times. The recruiter confirms candidates. The manager records interview feedback. HR prepares an offer. A final reviewer approves terms. The recruiter communicates a decision. Every step needs one primary owner. When a team says several people own a handoff, ask who carries responsibility when no reply arrives.

Show active work and waiting separately. A recruiter searching, calling, reviewing applications, or preparing a candidate conversation performs active work. A requisition in an approval queue waits. An interview request awaiting a manager reply also waits, even when a recruiter sends reminders. Both categories matter, yet they need different responses. Extra recruiting capacity does not automatically shorten approval response time. A large amount of active sourcing work across roles might lead to a different conversation.

Use dates to calculate each interval with care. For R04 in Darius's fictional sample, a manager requested approval April 2. Finance approved April 5. The recruiter began sourcing April 5. A candidate went to the manager April 12. The manager chose an interview time April 18. The recruiter confirmed an interview April 19. The six day span from April 12 through April 18 deserves a label such as manager interview scheduling wait. Do not place those days in recruiter workload because a recruiter did not own a response.

Ask recruiters about work hidden behind one status label. “Sourcing” sometimes includes an outreach plan, reply review, applicant questions, compensation discussion with HR, or incomplete manager feedback follow up. Darius asks Noah, “For R04 from April 5 through April 12, what work did you complete and what waited on another person?” Noah says he reviewed applicants daily, held four introductory conversations, and sent two profiles. He also waited one day for confirmation of a required shift detail. Darius records active effort and external wait.

Invite managers into a review without framing them as a problem. Darius sends a note saying the group will inspect handoffs across ten roles and identify where response timing creates delays. During a meeting, supervisor Priya sees several interview requests held for five or six days. Darius asks, “What made those requests hard to answer during this period?” Priya explains production planning changed twice, so she lacked an interviewer list. Her answer points toward a scheduling decision, not a claim about her commitment.

Look for patterns after checking individual records. When seven of ten roles waited several days for interview confirmation, ask whether one shared event or handoff appears. When only two roles waited, inspect unique conditions before making a broad rule. Darius finds four roles where managers lacked a current interviewer list. He does not conclude every delay has one cause. He asks whether a weekly availability record would give managers a faster starting point and who would own updates to such a record.

Use equal discipline for recruiter workload. Count active requisitions per recruiter, yet do not stop there. Two recruiters with ten roles often carry different workloads when one group involves early sourcing and another awaits hiring manager decisions. Look at candidate conversations, profile reviews, interviews to coordinate, feedback reminders, offers in review, and role changes needing fresh sourcing. Use a consistent time period, such as four recent weeks, and state limits in a sample. A count grows useful only beside work behind each role.

During the fictional review, Elena says, “I still want a headcount recommendation today.” Darius answers, “I hear urgency. We have evidence of recruiter activity and repeated manager scheduling waits. A recommendation today would mix both into one number. Would you support a two week review of a remaining sample, followed by a decision meeting with managers present?” Elena asks what she receives during those two weeks. Darius offers a current process map, interval notes for every role, and decisions needing an owner.

End every session with a decision log. For each issue, record observed evidence, an owner who investigates or decides, a next review date, and an open question. In Darius's fictional group, Priya owns a proposal for manager interview availability by Friday. Noah owns a five role sample of active sourcing tasks by Thursday. Elena owns a choice about who approves revised requisition information. Darius owns a combined map for a next meeting. Each entry has a distinct purpose, so no one leaves with an abstract request to improve recruiting.

Practice with seven fictional roles. Draw steps from request through accepted offer, then assign a date and owner to every handoff. Ask a colleague playing a director to request more recruiter headcount before you show a map. Respond by asking permission to inspect a sample and naming records needed. Ask another colleague playing a manager to explain one long interview scheduling gap. Write their explanation as a possible factor, not a confirmed cause.

For practice, choose R06 with a four day interview wait. Write a note for a next meeting: “R06 waited from June 10 through June 14 for interview confirmation. Priya will check interviewer availability records before Tuesday's review.” Put this note beside R06 in your process map. During your next client session, ask Priya for an update before moving to another role, then record a new date or leave the issue open.