> This is the markdown version of https://www.classet.ai/blog/recruiter-capacity-model > Learn more at https://www.classet.ai # Recruiter Capacity Model: How Many Recruiters You Need Build a recruiter capacity model from applicant volume, not req count. A worked example for 1,000 frontline reqs, and when adding headcount is the wrong fix. [![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) October 20, 2026 Guides & Insights, Hiring Tips ![Low-poly stacks of blocks rising in height, with one stack toppling under its load](/_next/image?url=%2Fimages%2Fblog%2Frecruiter-capacity-model.png&w=3840&q=75) "The ask is for more headcount." We heard some version of that line in more than half of our meetings at an HR conference last week. One health system had over 1,000 open reqs and fewer than 20 recruiters. Another company's recruiters were overwhelmed, and at a manufacturer we met, the whole TA team was one person. Each of them was about to ask finance for recruiters, and most would make the case with a req ratio. That's the weakest version of the argument, because finance can't check a ratio and it doesn't say where the time goes. A capacity model shows finance where every hour goes, in numbers they can check. Quick answer A recruiter capacity model turns your monthly applicant volume into recruiter hours, stage by stage, and divides by the productive hours one recruiter has. The result is how many recruiters the work requires. On frontline hiring, top-of-funnel screening usually takes more than half of those hours. Model it before you request headcount, because removing that work can change the answer by several recruiters. ## Why is req count the wrong input? The usual benchmark of 20 to 30 reqs per recruiter came from corporate hiring, where a req draws a few dozen applicants and a long interview loop. A frontline req for a warehouse selector, a CNA, or a part-time sales associate can draw hundreds of applicants and open again a month later. We covered [why the recruiter-to-req ratio breaks on frontline hiring](/blog/recruiter-to-req-ratio) in detail. Two recruiters with 50 reqs each can have completely different weeks, because hours depend on how many people move through each stage and how long each stage takes per person. A capacity model counts those two things instead of reqs. ## What goes into a recruiter capacity model? A **recruiter capacity model** needs five numbers, most of them already in your ATS: 1. Monthly applicants across the roles your team owns. 2. The share you screen by phone (the rest are knocked out by eligibility questions or resume review). 3. Minutes per screen, including dial attempts, voicemails, and texts to people you never reach. 4. Minutes per advanced candidate for everything after the screen: scheduling, manager follow-up, offers, and onboarding handoff. 5. Productive hours per recruiter per month, after meetings, reporting, and admin. The third number is the one most teams get wrong. They time a 15-minute screen and forget the three unanswered calls that came before it. ## How many recruiters do I need? A worked example This model is for a health system like the one above: 1,000 open reqs, mostly frontline roles, about 12,000 applicants a month. The minutes are typical assumptions. Swap in your own. Stage Volume Minutes each Hours per month Resume and eligibility review 12,000 applicants 1 200 Dial attempts, voicemails, texts 4,200 screen candidates 6 420 Completed phone screens 2,100 reached 15 525 Scheduling interviews 1,000 advanced 20 333 Chasing hiring managers for decisions 1,000 reqs 20 333 Offers and onboarding handoff 400 hires 45 300 **Total** **2,111** For the denominator, a recruiter works about 160 hours a month. After team meetings, reporting, and ATS cleanup, assume 70% of that is available for req work, or 112 hours. 2,111 ÷ 112 = 18.8 recruiters. With 18 recruiters, this team is at 105% of capacity in an average month, with no slack for a hiring surge, a vacation, or a resignation. Look at where the hours sit. Resume review, dial attempts, and screens add up to 1,145 hours, or 54% of the total, all of it spent finding out whether applicants meet the basic requirements. ## Compare three scenarios A capacity model earns its keep when you compare options. Here are three for the same team. Scenario Hours per month Recruiters needed What changes Today 2,111 18.8 Nothing Add headcount 2,111 18.8 Hire about 4 recruiters to get back to 85% load Remove the screening calls 1,271 11.3 Screens happen without a recruiter dialing; recruiters review results The third row assumes an automated phone screen replaces the dial attempts and live screens, and a recruiter spends about 3 minutes reviewing each completed result (2,100 × 3 minutes = 105 hours). That frees about 840 hours a month, or roughly 7.5 recruiters' worth of time. You wouldn't cut 7 people. The team you already have drops below 100% load, and the next hiring surge no longer forces an emergency headcount request. Some of those hours also go back into the work recruiters were hired for, like hard-to-fill clinical roles and getting managers to make decisions. ## Model the peak month separately The average month hides the problem. If your volume doubles for six weeks in spring or before the holidays, model that month separately. A team at 105% in an average month can be well past 150% in the peak. Headcount requests sized on the average tend to get approved months later and filled after the peak has passed. In the meantime teams improvise: one employer we spoke with pulls HR business partners into recruiting every peak season, and another leans on temp labor it would rather not use. ## When is adding a recruiter the right call? Not every capacity problem is a screening problem, and your model will show you when it isn't. Hiring a recruiter is the right move when: - The hours sit in work that depends on relationships: sourcing passive candidates, selling a hard-to-fill role, negotiating offers. - Applicant volume is low and the problem is attraction. Rural plants and markets with a reputation problem need sourcing help more than faster processing of the people who apply. - Hiring managers need a dedicated partner who can push back on unrealistic requirements. If your model shows most hours in sourcing and offers, hire the recruiter. If it shows most hours in screening and scheduling, a recruiter is the most expensive way to fix it. ## Which recruiter productivity metrics should you track? Once the model exists, track these monthly so the next headcount conversation is a five-minute one: Metric What it tells you Applicants per recruiter per month Workload, the input req ratios miss Share of recruiter hours spent on screening Whether the team is doing recruiting or call-center work Time to first contact Whether you reach applicants before competitors do Hires per recruiter per month Output, comparable across teams Days in hiring-manager review How much of time-to-fill sits outside TA's control Slow first contact costs you candidates. In Talent Board research [reported by SHRM](https://www.shrm.org/topics-tools/news/talent-acquisition/candidate-experience-talent-board-research-candes), 36% of US candidates still hadn't heard from an employer one to two months after applying, and poor communication was a top reason candidates withdrew. The last one belongs in the model because chasing managers is real recruiter time. In our example it's 333 hours a month, as much as scheduling. If you own frontline hiring through store or plant managers, our post on [recruiting best practices for hiring managers with no time](/blog/hiring-managers-recruiting-best-practices) covers how to shrink it. ## Building the case for finance Finance wants to see three things: where the hours go today, what each option costs, and what happens if you do nothing. The table above gives you all three. Put the fully loaded cost of a recruiter next to the cost of removing the screening hours, and show the peak-month load for both. Our post on [proving AI recruiting ROI to your CFO](/blog/ai-recruiting-roi) has a template for the cost side. If you use an automated phone screen, model it honestly. Not every invited applicant completes the screen, so base the review hours on completed screens, and keep a recruiter's time in the model for the people who opt out and need a human follow-up. ## Frequently asked questions ### How many recruiters do I need? Divide the recruiter hours your hiring volume requires by the productive hours one recruiter has in a month (about 110 to 120 after meetings and admin). Calculate the required hours stage by stage: applicants reviewed, screens attempted and completed, interviews scheduled, manager follow-up, and offers. For frontline roles, start from applicant volume rather than req count. ### How many reqs should a recruiter carry? For corporate roles, 20 to 30 is a common benchmark. For frontline and hourly roles the number isn't meaningful, because one req can draw 200 or more applicants and reopen monthly. Track applicants per recruiter and the share of hours spent screening instead. ### What are the most useful recruiter productivity metrics? Applicants per recruiter per month, the share of recruiter hours spent on screening, time to first contact, hires per recruiter, and days candidates spend waiting on hiring-manager decisions. Together they show workload, where the time goes, and where time-to-fill is lost. ### Should a capacity model use average or peak volume? Both. Size the steady-state team on an average month, and model the peak month separately so you know how far over capacity a surge puts you. Frontline teams usually fall behind during the surge, so plan for that month on its own. ## Key points - Build the model from applicant volume and minutes per stage, not req count. - Include dial attempts and hiring-manager follow-up. They're the hours teams usually forget. - In a typical frontline model, more than half of recruiter time goes to screening. - Compare scenarios: adding recruiters adds hours at a fixed rate, while removing screening work reduces the hours you need. - Hire a recruiter when the hours are in sourcing, selling, and offers. Fix the process when they're in screening and scheduling. ## See it on your numbers Joy, our AI phone screener, calls applicants, asks your must-have questions, and returns a summary and recording to your ATS, so your recruiters review results instead of dialing. [Book a demo](/demo?ref=blog-recruiter-capacity-model) and we'll run this model on your applicant volume with you. [![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) - [Data Centers Recruiting](/use-cases/data-centers) - [Healthcare Recruiting](/use-cases/healthcare) ### Integrations - [Greenhouse](/integrations/greenhouse) - [Bullhorn](/integrations/bullhorn) - [Lever](/integrations/lever)