> This is the markdown version of https://www.classet.ai/blog/recruiter-to-req-ratio > Learn more at https://www.classet.ai ![Recruiter to requisition ratio benchmarks for high-volume frontline hiring](/_next/image?url=%2Fimages%2Fblog%2Frecruiter-to-req-ratio.png&w=3840&q=75) # Recruiter-to-Req Ratio: Why the Benchmark Breaks on Frontline Hiring The 1:25 recruiter-to-requisition benchmark comes from corporate professional hiring. Here's why frontline and high-volume teams break it, and what to measure instead. [![Paul Jones](/_next/image?url=https%3A%2F%2Fassets.basehub.com%2Fe0b5701f%2F6599306507912123f90f150a8bfaaf6c%2Fscreenshot-2026-01-28-at-10.53.16-am.png%3Fwidth%3D100%26height%3D100%26quality%3D100&w=96&q=75) Paul JonesHead of Growth at Classet ](/blog/authors/paul-jones) August 31, 2026 Guides & Insights, Hiring Tips Somebody on your leadership team has read that a recruiter should carry about 25 open requisitions. It gets quoted in board decks, headcount requests, and RFPs. It is also the wrong number for most of the people reading this. The benchmark is real. It just came from a different kind of hiring than yours. **TLDR:** - The common 1:20–1:30 benchmark was built on corporate professional hiring, where a req produces a handful of applicants and a long interview loop. - On frontline roles, a single req can pull 200+ applicants. Req count stops predicting workload almost immediately. - Count applicants per recruiter per month, not reqs. That is the number that tracks against burnout and time-to-fill. - Screening is the step that scales worst, and it's the step that gets cut first when the ratio slips. - Adding a recruiter buys you linear capacity. Removing the screening bottleneck changes the slope. ## Where the number came from The requisition-load benchmarks in circulation trace back to corporate talent acquisition, and they assume a shape of hiring that looks like this: a req opens, thirty or forty people apply over several weeks, a recruiter screens maybe fifteen, four go to a hiring manager, one gets an offer. Under that shape, a req is a reasonable unit of work. Twenty-five of them is a busy but survivable desk. Now change one variable. Post a warehouse associate role in a metro with real unemployment and you can clear 200 applicants in seventy-two hours. The req count on the recruiter's dashboard went up by one. The actual work went up by an order of magnitude. This is why two TA teams can report identical ratios and have completely different lives. The ratio is measuring the wrong noun. ## The number that actually predicts strain Applicants per recruiter per month. That's it. It works because it captures the part of the job that does not compress. A recruiter can hold a lot of reqs in their head. What they cannot do is have more conversations than there are hours, and every applicant either gets a conversation, gets a rejection, or gets ignored. Most get ignored, which is a decision your team is making by default rather than on purpose. Run your own math with three numbers you already have: **Applicants per month.** Pull the raw count from your ATS, not the count that survived some filter. The filtered number hides the work. **Recruiters actually screening.** Not TA headcount. The people who do phone screens. If your coordinator does thirty a week, they count. **Minutes per screen, loaded.** A fifteen-minute phone screen is not fifteen minutes. Add the dial, the voicemail, the callback, the reschedule, the notes. Teams that time it honestly land between 35 and 50 minutes of loaded effort per completed screen, and the biggest share of that is spent on people who never pick up. Multiply it out. If one recruiter is nominally covering 600 applicants a month at 40 loaded minutes each, that's 400 hours of screening work sitting on someone with roughly 140 available. The gap doesn't show up as a missed number. It shows up as a queue nobody is working, which is a quieter and more expensive failure. ## What breaks first Screening. Always screening. It breaks first because it's the only step in the funnel with no external forcing function. A hiring manager chases you about interviews. A candidate chases you about an offer. Nobody chases you about the 340 applications from last Tuesday, so that is where the slack gets taken out of the system. The order of collapse repeats across the teams we work with. First, screening moves from "everyone" to "the ones with a good resume," which reintroduces exactly the resume bias frontline hiring is worst suited to. Then response time slides from hours to days, and by day three most of your qualified applicants have accepted something else. Then sourcing spend goes up to compensate for a pipeline that isn't leaking at the top at all. Then somebody asks for another recruiter. That last request is usually granted, and it usually helps for about a quarter. ## Why adding a recruiter is a linear fix to a nonlinear problem Hire a recruiter and you add one person's worth of hours. That is useful and I am not going to pretend otherwise. But applicant volume on frontline roles doesn't grow in step with your headcount plan. It moves with the labor market, your ad spend, seasonality, and whatever a competitor did to their wage last month. Any of those can double your inbound in a month, and none of them care that you just onboarded someone in March. So the ratio drifts back. Then it drifts back again. The alternative is to change what a screen costs. If the first conversation with an applicant happens without a recruiter dialing the phone, the applicants-per-recruiter number stops being a capacity ceiling and becomes a throughput number. [Joy calls applicants](/product) within seconds of the application landing, runs the structured screen, applies your knockouts, and hands the recruiter a summary and a recording instead of a queue. The math changes shape. A recruiter who was spending 400 hours' worth of effort on 600 screens spends it on the 90 people who passed, which is the work you actually hired them to do. ## Ratios worth tracking instead Req count still has a use. It just isn't a capacity metric on its own. These are the numbers that correlate with teams that aren't drowning: **Applicants per recruiter per month.** The headline. Track it monthly, and track the trend rather than the absolute, since your right number depends on your screening model. **Percentage of applicants who get a real first touch.** Not an auto-acknowledgment email. A conversation or a screen. Teams running manual screening at volume are often under 30% and are usually surprised by that. **Median hours from application to first contact.** In our own data, 55% of frontline candidates apply outside standard business hours, so any process that starts the clock at 9am the next weekday has already lost most of a day on most of its applicants. **Screens per hire.** Rising screens-per-hire with flat quality usually means the top of the funnel got worse, not that the team got slower. Worth separating before you fix the wrong thing. **Reqs per recruiter.** Keep it. Just report it next to volume, or it will get quoted back at you in a budget meeting with no context attached. ## Questions we get about this What is a good recruiter-to-requisition ratio? For corporate professional hiring, somewhere in the 1:20 to 1:30 range is a defensible planning assumption. For frontline and high-volume hiring, req count is a poor proxy for workload, because a single req can generate hundreds of applicants. Use applicants per recruiter per month instead, and set your own baseline from your ATS rather than borrowing a published figure. How many applicants can one recruiter screen per month? Working from loaded time of 35 to 50 minutes per completed phone screen, a recruiter with roughly 140 screening hours a month lands somewhere between 170 and 240 completed screens, assuming they do nothing else. Most recruiters do a lot else, so the realistic number is lower. Compare that against your actual monthly applicant count to see the size of the gap. Does adding recruiters fix a bad ratio? It helps, linearly, and it's the right call when the work is the kind only a person can do. It's a poor fix when the bottleneck is first-touch screening, because applicant volume moves with the labor market and your ad spend rather than with your headcount plan. The ratio drifts back within a quarter or two. How do we measure loaded time per phone screen? Time the whole attempt, not the conversation. Include the first dial, the voicemail, the callback window, reschedules, no-shows, and the write-up. The no-shows matter most, because that effort produces no candidate at all and is invisible in any report that only counts completed screens. Should we track reqs per recruiter at all? Yes, but report it alongside applicant volume. On its own it will get compared against a published benchmark from a different kind of hiring, and you'll be asked to justify a difference that has nothing to do with your team's performance. ## Where to start Pull three numbers this week: raw applicants last month, recruiters doing screens, and an honest loaded-minutes figure from timing five screens end to end. If the implied hours exceed the hours you have, you already know what the queue looks like, and the ratio conversation gets much easier when you bring that arithmetic to it. If the gap is large enough that another hire won't close it, [see how instant phone screening changes the math](/demo). ### Related reading - [High-volume hiring: the full guide](/blog/high-volume-hiring-guide) - [The real cost of an open role, with a calculator](/blog/cost-of-vacancy-calculator) - [How AI screening cuts recruiting costs](/blog/ai-screening-recruiting-costs) [![Paul Jones](/_next/image?url=https%3A%2F%2Fassets.basehub.com%2Fe0b5701f%2F6599306507912123f90f150a8bfaaf6c%2Fscreenshot-2026-01-28-at-10.53.16-am.png%3Fwidth%3D100%26height%3D100%26quality%3D100&w=128&q=75) Paul Jones Head of Growth at Classet Paul comes from an operator background running an Alpine-owned company, and brings firsthand experience with the hiring challenges Classet was built to solve. He's driven by a belief that the right technology can make meaningful work more accessible. ](/blog/authors/paul-jones) Follow Classet in Google Add classet.ai as a preferred source and our hiring research is more likely to show up in your Top Stories and AI Overviews. [Add as preferred source →](https://www.google.com/preferences/source?q=classet.ai) ## Explore More ### Use Cases - [RPO / BPO Recruiting](/use-cases/call-centers-bpo) - [Healthcare Recruiting](/use-cases/healthcare) - [Hospitality Recruiting](/use-cases/hospitality) ### Integrations - [Greenhouse](/integrations/greenhouse) - [Bullhorn](/integrations/bullhorn) - [Lever](/integrations/lever)