The Requisition Count Trap: Why Two Recruiters With 15 Jobs Have Different Workloads
Build a recruiter capacity model from active work hours, stage effort, role complexity and reserve time rather than raw requisition count.
Fifteen open jobs is not a workload. Fifteen urgent jobs with interviews, offers and two hiring managers who never respond is a workload.
A practical, evidence-led field guide. All case figures are illustrative; the procedures below are editorial synthesis, not validated prediction rules or jurisdiction-independent legal advice.
Why “requisitions per recruiter” is a seductive bad target
One recruiter has 15 evergreen retail vacancies with shared assessments and predictable hiring-manager availability. Another has 15 executive and niche technical searches across time zones, each with custom stakeholder meetings. A dashboard that calls them equally loaded is not measuring work; it is counting labels.
SHRM publishes recruiting benchmarks, including requisitions per recruiter, but a benchmark describes a population and depends on how organizations count work. It does not tell you how many complex roles one specific recruiter can safely manage this week. The missing unit is time and decision friction per requisition stage.
Build a work inventory before setting a capacity target
Break recruiting time into observable activities: intake and calibration, sourcing/search, screening, candidate communication, scheduling, interview coordination, offers, client or hiring-manager follow-up, data hygiene and exception handling. Sample one representative week from the calendar and ATS activity—not just self-reported “busy hours.”
Label each activity direct role work, shared operations, or unplanned exception. Do not double-count a 30-minute intake meeting against five requisitions. Shared work belongs in a separate fixed bucket, or must be allocated by a declared rule. The inventory should reveal process waste as well as workload.
A capacity equation that makes assumptions visible
A simple weekly planning model is:
Planned demand = fixed coordination hours + active requisitions × average direct hours per requisition.
Usable capacity = recruiting hours available × (1 − exception buffer).
For example, 32 available hours, 7 fixed hours, 15 roles at 1.8 direct hours each, and a 15% buffer produce 34 hours of demand against 27.2 usable hours. The gap is 6.8 hours. This is a scenario, not proof of overtime: role effort varies and the inputs must be checked against real work. Use the result to renegotiate priorities, not to grade an employee.
Use a stage-weighted queue instead of treating all jobs as active
A requisition waiting for a hiring-manager approval may consume less direct sourcing time but create repeated follow-up and candidate risk. A role in offer negotiation can be more time-sensitive than a newly opened search. Classify each role into its current dominant stage, then estimate weekly effort from observed examples of that stage.
A practical starting table:
| Stage | Primary effort driver | Typical surprise |
|---|---|---|
| Intake | stakeholder alignment | role scope changes |
| Search | scarce skills and channels | low response quality |
| Interview | scheduling and feedback | reschedules and panel availability |
| Offer | approvals and candidate questions | exception negotiations |
| Hold | follow-up and candidate updates | hidden reactivation work |
Do not publish generic hour norms as industry standards. Calibrate with your own time samples and update when the mix changes.
The hidden work of “on hold” requisitions
A requisition may be paused in the ATS yet still generate candidate updates, sourcing follow-ups, client status meetings and compliance tasks. If the dashboard removes paused roles from the denominator but leaves their workload with the recruiter, capacity looks better while experience gets worse.
Track paused-but-serviced roles separately. For each, specify the owner of candidate communication, the next decision date and the amount of work allowed before reapproval. A role with no decision owner should not quietly consume the same priority as an authorized urgent search.
Why more automation can initially increase recruiter load
Automation that finds more possible matches may increase downstream review, outreach replies, interviews and exception handling. The recruiter gets “more productivity” upstream but more work in the human stages. Measure end-to-end work: minutes of review saved, additional candidates needing response, and decision latency at the next handoff.
If a sourcing tool doubles outreach but the interview team cannot add slots, the bottleneck has moved rather than disappeared. A strong capacity model includes downstream absorption, not just how many profiles a tool can surface.
A two-tier priority contract with hiring managers
For a team operating above its usable capacity, ask leaders to classify roles as committed now or queued with a review date. Document the business consequence of delay, candidate commitments already made, and the next action owner. Make a visible trade-off: adding an urgent role means pausing or resourcing another.
Avoid the false compromise of promising equal attention to every requisition. Recruiters should not need to negotiate priorities in private Slack threads. The manager-facing contract can be as small as a weekly table with owner, stage, next decision, and escalation deadline.
The 14-day calibration experiment
During week one, estimate direct hours by stage for ten active roles and track actual effort in broad categories; do not surveil every keystroke. In week two, compare the estimates with reality, identify the two biggest exception causes and change one workflow. Recalculate capacity using the observed mix.
Measure quality guardrails alongside throughput: unanswered candidate messages, overdue feedback, incomplete evidence notes and unreviewed accommodations. A capacity model that improves throughput by silently reducing care is not an improvement. The counterintuitive success criterion is sometimes fewer active requisitions with more completed, defensible decisions.
Try the operational check
This interactive check runs locally in your browser. It requires only hypothetical or aggregate inputs and does not transmit candidate data.
Weekly recruiter capacity stress test
A transparent time-budget estimate. Enter planning assumptions, not employee productivity judgments.
This descriptive tool is not a legal opinion, a selection decision or a validated prediction model. Inputs remain in this browser.
Implementation standard and limitations
Pilot the workflow on a small anonymized sample, write down the decision owner and the data definitions, and monitor adverse or unintended effects. Examples are synthetic. The named framework is an original editorial synthesis of the cited public guidance, not a proprietary scientific finding. Seek local legal and professional review where needed.
Research basis and further reading
Selected directly relevant primary, professional and clearly attributed industry sources. The operational checklists are our synthesis; no source is represented as validating a calculator or a universal threshold.
The decision worth changing this week
Choose one real workflow, record the baseline and test one reversible change. Publish what improved and what did not. Good hiring operations protect the quality of decisions and the candidate experience, not just the speed of a dashboard.
Make evidence usable, not just searchable.
RoleRise supports evidence-led recruiting workflows and recruiter review.
Explore RoleRise