Recruiter req load: measure it as a daily average, weight it by difficulty and stage, and rebalance desks

Recruiter req load is the number of open requisitions a recruiter is responsible for. Measure it as an average daily count, the total req-days in a period divided by the days in it, which is how Gem defines job openings per recruiter in its 2025 benchmark report. Then weight each req by difficulty and by stage, so a fresh executive search and a req waiting on a signed offer do not count the same. Compare each recruiter's weighted load with a ceiling taken from their own history, and rebalance when the ratio stays high.

Published averages and the reasons they do not fit every team are in how many reqs per recruiter, and headcount planning is in the recruiting capacity planning template. This page is the measurement itself: the formula, the weights, a worked month and the rules for rebalancing.

What does req load measure, and what do the benchmarks count?

Gem's 2025 Recruiting Benchmarks Report defines job openings per recruiter as "the average number of job reqs a given recruiter is working on simultaneously on any given day in a given year." Its 2026 report takeaways put the figure at 13.4 open roles per recruiter, from data on over 165 million applications (as of November 2026). Two things follow. First, the benchmark is a daily average, so a count you take on one Monday is not comparable to it. Second, it counts reqs, not work: one req for thirty warehouse associates and one for a finance director both count as one.

Why does a one-day count mislead?

Reqs open and close through the month. A recruiter can start June with 7 open reqs and end it with 9, having closed one and opened three in between. Either snapshot is true and neither describes the month. The average daily count does, and it is no harder to calculate if your ATS records when each req was opened, assigned, put on hold and closed.

How do you calculate average daily req load?

Req-days       = days each req was open AND assigned to the recruiter
                 within the period
Average load   = sum of req-days ÷ days in the period
Weighted load  = sum of (req-days × difficulty weight × stage factor)
                 ÷ days in the period

Use calendar days for both the req-days and the period, so weekends cancel out. A req reassigned mid-month counts for each recruiter only for the days they held it.

Worked example: one recruiter, one month

Invented data for June (30 days). Difficulty weights are the example tiers from how many reqs per recruiter: repeatable 0.5, standard 1, hard 2, executive 3. Stage factors are our example convention for how much active work a stage needs: sourcing 1.0, interviewing 0.75, offer 0.5, on hold 0.

• One-day counts: 7 open on June 1, 9 open on June 30.
• Average load: 241 ÷ 30 = 8.0 reqs.
• Weighted load: 224.75 ÷ 30 = 7.5.

Now compare a second recruiter who held 12 repeatable reqs, all interviewing, all month: an average load of 12.0 but a weighted load of 12 × 0.5 × 0.75 = 4.5. On raw counts the second desk looks half again as busy; weighted, it carries about 60% of the first desk's work. If your ATS can export each req's stage every day, sum the daily weights instead of using the main stage; the main-stage shortcut is close enough for most monthly reviews.

How should you set the weights?

• Difficulty from hours, not opinion. Ask recruiters to log hours on a sample of reqs for two weeks, then set tiers so that a hard req's weight roughly matches the hours it took compared with a standard one.
• Multi-opening reqs. A req with ten openings is more work than one with a single opening but not ten times more, because the ad, the screen and the interview kit are shared. A simple convention, as an example: count the first opening at the req's weight and each extra opening at a quarter of it. Check it against logged hours.
• Stage factors. Work is front-loaded in sourcing and screening. If your recruiters also coordinate interviews, raise the interviewing factor.
• Keep the weights the same for everyone and change them at most once a quarter, or the comparison between desks stops meaning anything.

The same weights should drive output measures, so load and results sit on one scale; see recruiter productivity metrics.

How do you set a ceiling for each recruiter?

Look back two or three quarters and find the weighted load at which each recruiter's work held up: time to first submittal or slate on new reqs, candidate reply times and hiring manager feedback. That is their ceiling. Then track a load index:

Load index = current weighted load ÷ the recruiter's ceiling × 100

Continuing the example, if the first recruiter's ceiling is 9.0, a weighted load of 7.5 is an index of 83%. A new executive search in sourcing adds 3 × 1.0 = 3.0, taking the index to (7.5 + 3.0) ÷ 9.0 = 117%. The second recruiter, with a ceiling of 8.0 and a load of 4.5, sits at 56%, but may not have run an executive search. The index tells you who has room; it does not tell you who has the skills, which is a separate check.

When should you rebalance a desk?

• The index stays above 110% for two weeks. One busy week is normal; two is a pattern.
• Early-warning signs appear, such as reqs with no activity for a week or time to first submittal rising on new reqs. How many reqs per recruiter lists the signs; any two together are stronger evidence than the index alone.
• A new req arrives. Assign it to the qualified recruiter with the lowest index, and record why when you do not.

When you move work, move whole reqs at the sourcing stage. A req at offer stage should stay with the recruiter who holds the candidate relationship. If nobody has room, the decision is which reqs wait, and that belongs with hiring leaders; see how to prioritize open requisitions.

How do you report req load?

REQ LOAD, JUNE (average daily, weighted)
Weights: repeatable 0.5 / standard 1 / hard 2 / executive 3
Stage factors: sourcing 1.0 / interviewing 0.75 / offer 0.5 / hold 0

Recruiter   Avg reqs   Weighted   Ceiling   Index   On hold   No activity 7d+
Recruiter 1    8.0       7.5        9.0      83%       1           0
Recruiter 2   12.0       4.5        8.0      56%       0           0
Recruiter 3   10.6      11.9       10.0     119%       2           3

Action: two sourcing-stage reqs move from Recruiter 3 to Recruiter 2
from July 1; Recruiter 3's holds reconfirmed with hiring managers.

A desk-level version belongs on the recruiter KPI dashboard, next to time to fill and pipeline numbers.

Does this work for agency desks?

Yes, with one change: count job orders that are actually being worked, not every order a client has sent. Agencies often hold contingent orders that are competed with other suppliers and rarely touched. Count an order in the load only while it has had activity in the last seven days, list the rest separately, and give exclusive and retained searches a higher weight than contingent ones. Rising time to first submittal on new orders is the clearest sign a desk is over its ceiling; time to submit covers measuring it, and recruiting agency metrics defines the rest.

Common mistakes