How Many Requisitions Can a Recruiter Handle? Reqs Per Recruiter Benchmarks

How many requisitions can a recruiter handle?

There is no single right answer, but the published benchmarks cluster tightly enough to be useful. The gap that matters is between what recruiters carry and what they can carry without the work degrading, and in 2026 that gap got wider.

Read those rows together and the picture is clear. The number recruiters say they can do well is roughly 15 to 20. The number they are actually given is 25 to 40. The load has been rising, fastest at the biggest employers, and it did not rise because the work got easier.

Why the published numbers disagree so much

Three measurement choices explain almost all the spread, and knowing them stops you from quoting a benchmark that does not describe your team.

What counts as a req. ATS-measured figures like Gem's 14 count requisitions formally assigned to a named recruiter. Survey figures count whatever the respondent thinks they are responsible for, which includes the pipeline they are keeping warm for a role that has not been approved yet. Both are honest; they are not the same quantity.

Who is in the sample. A staffing agency recruiter working contingency, a corporate recruiter at a 400 person company, and an RPO recruiter on a high-volume warehouse account do genuinely different jobs. Averaging them produces a number that describes nobody.

Whether support is counted. A recruiter with a dedicated sourcer and a coordinator can carry roughly double the load of one doing their own sourcing and their own scheduling. Most benchmarks do not say which they measured, which is the single biggest reason two credible sources can differ by a factor of two.

How many requisitions should a recruiter have?

Capacity depends far more on the type of role than on the recruiter. Dr. John Sullivan's long-used framework scales targets by complexity, and it still maps well onto 2026 hiring:

• Corporate professional roles: about 25 reqs, producing roughly eight fills a month.
• High-tech exempt roles: about 45 reqs, where much of the work is pipeline building rather than closing.
• Non-exempt high-volume roles: about 60 reqs, because each individual hire needs far less judgment.
• Executive search: 15 to 20 searches a year, not at a time. A different job with a different unit of measure.

Hire velocity data from Q1 2026 supports the same shape. Recruiters averaged 7.3 hires per quarter overall, but only 3.8 for technical roles against 5.0 for business roles. A technical req consumes close to twice the recruiter time of a business req, so a technical team carrying 25 reqs is under roughly the same strain as a business team carrying 45.

The signs a recruiter is over the line

The useful thing about overload is that it fails in a predictable order, so you can see it before the fill rate drops. The 20 to 30 req band is where quality reliably starts to slip, and it slips like this:

Intake meetings get skipped. The first casualty, because it is the only step with no immediate consequence. The recruiter works from the job description instead of a real conversation with the hiring manager, and three weeks later a shortlist gets rejected wholesale for reasons nobody wrote down.

Active sourcing stops. Outbound is the second casualty. It is slow, it is optional today, and there is a queue of inbound applicants right there. The pipeline quietly becomes whoever happened to apply, which on a competitive role is the wrong people.

Screening goes shallow. Resume review compresses into keyword scanning. Strong candidates with unusual backgrounds get missed because reading them properly takes eight minutes and there are 300 in the queue.

Candidates go cold. Response times stretch, scheduling drifts, and the best people, who have other offers, take one. This is the failure that costs the most and shows up last in any dashboard.

If you are seeing two or more of these, the load is past capacity regardless of what the benchmark says. It is worth being honest about whether the process itself is the problem before assuming the answer is more people, and a structured assessment of where your operating process actually loses time often finds days sitting in approval queues and handoffs rather than in recruiter work at all.

Recruiter headcount or software? Run the actual math

This is the decision the benchmark is usually being looked up for, so here is a way to make it concrete rather than philosophical.

Start with fully loaded cost, not base salary. US recruiter pay in 2026 varies enormously by source and level, from roughly $63,000 for a talent acquisition specialist on ZipRecruiter data up to about $104,000 for an experienced talent acquisition recruiter on Glassdoor data. Add payroll taxes, benefits, equipment and tooling and the fully loaded figure typically lands 25% to 40% above base. Call it $85,000 to $145,000 a year, and remember it takes about a quarter before a new recruiter is productive.

Then work out what that hire actually buys. If your team runs corporate professional roles, one more recruiter is worth roughly 25 reqs of capacity and roughly eight fills a month once they are ramped. If your team runs technical roles, the same hire buys closer to 3.8 hires a quarter. Divide the fully loaded cost by the incremental hires and you get a real cost per unit of capacity.

Now do the same for software, and be honest about which part of the load it removes. Tools that only speed up a step you already do well add very little capacity. Tools that remove a whole leg of the work add a lot. In practice the automatable legs are first-pass screening, sourcing, outreach drafting and interview coordination, which together account for most of the hours that disappear when a recruiter is overloaded. Our breakdown of AI agents for recruiting covers what each of those legs looks like when it is automated, and the wider AI recruiting software buyer map sets the categories side by side with US price ranges.

The comparison that usually decides it is not cost against cost, it is cost against elasticity. A recruiter is a fixed 25 reqs whether you have 12 open or 60. Software absorbs a spike without a hiring cycle and without you having to lay anyone off when the spike ends. For teams whose req count swings hard by quarter, that flexibility is often worth more than the raw price difference.

How to raise capacity without lowering the bar

Write the criteria down before the search starts. Most rework in recruiting comes from a brief that was never made explicit. A structured brief costs 30 minutes and prevents the shortlist rejection that costs three weeks.

Take coordination off the recruiter entirely. Interview scheduling is pure overhead with no judgment in it, and it fragments a recruiter's day worse than almost anything else. It is also the easiest leg to automate. Automated interview scheduling tends to pay for itself faster than anything else on this list.

Automate the first pass, not the decision. Screening 300 applicants against written criteria is the biggest single time sink on any high-applicant role, and it is the part where a tired human is genuinely worse than a consistent system. Keep the hiring decision human and hand back a ranked shortlist with the evidence attached. That is what candidate screening software is for, and what high-volume recruiting software is built around when the applicant counts get large.

Rebalance by complexity, not by count. Giving every recruiter 25 reqs is fair only if the reqs are equivalent, and they never are. Weight technical and executive reqs at roughly double a business req when you distribute the load.

Close reqs that are not real. A meaningful share of any req list is roles that are on hold, unfunded, or waiting on a decision nobody is chasing. They consume attention without producing hires. Audit the list quarterly and the number often drops by a fifth before you spend anything.

What is the average number of requisitions per recruiter?

The 2026 median is 25 requisitions per recruiter according to SHRM's benchmarking, up from 20 in 2025. ATS-measured data puts the figure lower at around 14, because it counts only formally assigned reqs. Cross-industry averages of 30 to 40 are widely reported, and at extra-large employers the median now sits between 60 and 100.

Is 30 requisitions too many for one recruiter?

For corporate professional hiring, yes in most cases. Thirty sits above the 15 to 20 that recruiters describe as sustainable and above the 20 to 30 band where intake meetings, active sourcing and screening depth start getting dropped. For high-volume non-exempt hiring, 30 is comfortably manageable and the practical ceiling is closer to 80 to 100. The role type matters more than the number.

How many hires should a recruiter make per year?

Q1 2026 data puts average velocity at 7.3 hires per recruiter per quarter, so roughly 29 a year, with technical recruiters closer to 15 and business-role recruiters closer to 20. Sullivan's framework implies about eight fills a month, or close to 96 a year, for a corporate recruiter carrying 25 reqs, which is a stretch target rather than a median. Use your own historical fill rate before adopting either.

The number is a symptom, not the problem

Req load is worth tracking, but on its own it tells you very little. Two recruiters carrying 25 reqs each can be in completely different situations depending on role complexity, whether they have sourcing support, how much of the coordination they do themselves, and how many of those reqs are actually live. Before you use a benchmark to justify a headcount request or a software purchase, work out which of those four things is actually the constraint on your team. Then fix that one. If you want to attach a dollar figure to the answer, our guide to the cost per hire formula and benchmarks gives you the arithmetic, and reducing time to hire covers where the days usually go.