Applicant Pool: What It Is, How to Build One, and What Happens After You Pick a Hire
What an applicant pool is, how it differs from a candidate pool and talent pool, realistic benchmarks, and how to manage one without HR or an ATS.
Applicant Pool
What it is, how it differs from a candidate pool and talent pool, realistic size benchmarks, and how to manage one without an ATS
An applicant pool is not a complicated concept, but it is a frequently confused one. If you search "applicant pool" right now, you will find 10 articles that give you 10 slightly different definitions, mix up "applicant pool" with "candidate pool" and "talent pool," and assume you have an applicant tracking system with automated screening. If you have 15 employees and the "ATS" is your email inbox, those articles are not helpful.
This guide defines what an applicant pool actually is, how it differs from a candidate pool and a talent pool (they are not the same thing), realistic size benchmarks for small businesses, how to build and manage one without an ATS, and what happens after you pick someone from the pool. That last part is where most guides stop and where most small businesses lose money.
What Is an Applicant Pool?
An applicant pool is the complete set of individuals who have submitted an application for a specific open position at your company. Everyone who clicks "apply" and submits their resume or application is part of the applicant pool, regardless of whether they are qualified for the role. The pool exists for the duration of the hiring process and closes when the position is filled.
This definition matters because it has legal implications. The SHRM and EEOC use a specific definition of "applicant" for anti-discrimination recordkeeping purposes. If you have 15 or more employees, you are required to retain records of everyone in your applicant pool for at least one year. This includes people you rejected immediately.
Applicant Pool vs Candidate Pool vs Talent Pool
These three terms are used interchangeably in casual conversation, but they mean different things. Confusing them creates problems when you are trying to build a structured hiring process.
| Term | Definition | When They Enter | Example |
|---|---|---|---|
| Applicant pool | Everyone who applied for a specific open role | When they submit an application | 50 people applied for your operations manager posting. All 50 are your applicant pool. |
| Candidate pool | Applicants who passed initial screening and are being considered | After you screen resumes and conduct phone screens | Out of 50 applicants, 8 meet your qualifications. Those 8 are your candidate pool. |
| Talent pool | People who might be right for future roles but have not applied to a specific position | Before any role is open (proactive) | A list of 20 people you met at events, interviewed previously, or received referrals for, maintained for future openings. |
The relationship is a recruiting funnel: talent pool (passive, ongoing) feeds applicant pool (active, per-role), which narrows to candidate pool (screened, per-role), which narrows to your hire. For small businesses, the talent pool is often informal (a mental list of "people I should call when I have an opening").
How Big Should Your Applicant Pool Be?
Industry data shows the average job posting receives approximately 250 applications. That number is misleading for small businesses. It is driven by large companies posting on multiple platforms with established employer brands. According to BLS JOLTS data, millions of job openings exist at any given time across the US economy, but the applicant volume per posting varies dramatically by company size, location, and role type. For a small business posting on Indeed and LinkedIn, realistic applicant pool sizes look different.
| Role Type | Typical Applicant Pool Size (SMB) | What Drives the Number |
|---|---|---|
| Entry-level (admin, retail, customer service) | 50-150 applicants | High supply of candidates, broad job boards, low barrier to apply |
| Mid-level (operations, marketing, bookkeeping) | 20-60 applicants | Moderate supply, more specific qualifications filter out casual applicants |
| Senior / specialized (developer, controller, project manager) | 10-30 applicants | Limited supply, candidates are selective about where they apply |
| Executive / niche (CTO, licensed trades, specialized technical) | 5-15 applicants | Very limited supply, often requires direct outreach or referrals |
The target is not "as many applicants as possible." It is "enough qualified applicants to give you 3-5 candidates to interview." If you post a role and get 5 applicants, 4 of whom are unqualified, your applicant pool is too small. If you get 200 applicants and spend 30 hours screening, your job post is too broad.
When the Pool Is Too Small: Diagnosing a Quiet Posting
A posting that produces four applications in ten days is not bad luck, and reposting the identical text rarely fixes it. Application volume is front-loaded, so a quiet first week is a signal to change something rather than to wait. The diagnosis depends on where the drop-off happens, and every major job board reports enough to tell you: views, clicks to the application, and completed applications.
| What the numbers show | What is actually wrong | The fix |
|---|---|---|
| Few views | Nobody is finding the post. Almost always the job title or the channel. | Rename the role to the term candidates search for. Search your own title on Indeed and see whether comparable jobs use it; if the results are unrelated roles, your title is internal jargon. 'Office Manager' gets found, 'Administrative Operations Coordinator' does not. |
| Many views, few clicks to apply | The preview is not selling. Usually a missing salary range or a location that reads as ambiguous. | Put the pay range in the first three lines and state the arrangement plainly: onsite in a named city, hybrid with days specified, or remote with the eligible states listed. |
| Many clicks, few completed applications | The application form is the problem. | Count the screens. Requiring an account, a cover letter, and re-keying a resume that was already uploaded are the three biggest killers. One page, resume upload, two or three screening questions. |
| Plenty of applications, almost none qualified | The post describes a broader job than the one you are filling. | Move the three genuine must-haves into the first section under a 'you need to have' heading and cut the wish list. Vague postings attract volume and repel fit. |
| Good numbers, but candidates drop out after the first call | Pay, schedule, or a requirement you did not disclose. | Ask the ones who withdraw. Two honest answers will tell you more than another week of applications. |
Compensation deserves its own check, because it is the variable that quietly caps every other fix. In the growing number of states and cities with pay transparency laws, competitors have to publish ranges in their own postings, which means the market rate for your title in your metro is sitting in public for free. If your range starts below where theirs end, no amount of rewriting will help.
Types of Applicant Pools
| Type | Source | When to Use | Quality Signal |
|---|---|---|---|
| Internal applicant pool | Current employees applying for a new role | Always post internally first for senior or desirable roles. Shows employees there is a growth path. | High: you already know their performance, culture fit, and reliability |
| External applicant pool (active) | Job board postings (Indeed, LinkedIn, industry boards) | Most common for all role types. Required when no internal candidates exist. | Moderate: candidates actively seeking work, but qualifications vary widely |
| External applicant pool (referral) | Employee or personal network referrals | Use for every role. Ask before posting publicly. | High: referred candidates are pre-vetted by someone who knows your company |
| External applicant pool (passive) | Direct outreach to people not actively job-seeking | Senior, specialized, or hard-to-fill roles where qualified people are employed elsewhere | Variable: high quality if targeted, but low response rates (10-20%) |
For most small businesses, the applicant pool is a mix of job board applicants (60-70%) and employee referrals (20-30%), with occasional direct outreach for specialized roles. Running the opening through internal recruitment first costs nothing and occasionally ends the search before it starts.
Building and Managing an Applicant Pool Without an ATS
If you hire 3 to 10 people per year, you do not need an applicant tracking system. You need a Google Sheet with 5 columns and a process for reviewing applications within 48 hours of receipt.
| Column | What to Track | Why |
|---|---|---|
| Name | Applicant's full name | Basic identification |
| Date applied | When the application was received | Response time tracking (respond within 48 hours) |
| Source | Where they applied from (Indeed, LinkedIn, referral, direct) | Track which channels produce qualified applicants |
| Qualified? | Yes / No / Maybe (based on 3-5 must-have skills from the JD) | Separates applicant pool from candidate pool |
| Notes | Resume highlights, phone screen verdict, interview score | Context for comparison after multiple interviews |
The process: check for new applications daily during an active posting (set a 5-minute calendar reminder). Mark each applicant as qualified, not qualified, or maybe based on the 3 to 5 must-have skills from the job description. Phone screen the qualified ones within a week. Interview the top 3 to 5 within the following week. Decide within 48 hours of the last interview. Total time investment: 1 to 2 hours per week during the active hiring period.
An applicant tracking system becomes worthwhile when you hire 15+ people per year or when you have multiple hiring managers who need to share applicant data. Below that volume, the spreadsheet is faster to set up, easier to use, and costs nothing.
Screening 50 Applicants Down to 8
This is the step every guide summarizes as "review applications" and nobody explains. The work is to turn a job description into a scorecard before the first resume arrives, then apply it the same way to every person in the pool. Building the scorecard afterward, once you have already read a few resumes, means the criteria get shaped by the applicants instead of by the job.
Split your requirements into two lists. Must-haves are three to five binary facts: holds the license, has closed a month-end, writes production SQL, can work Saturdays. They are pass or fail, never partially credited. Nice-to-haves are three or four qualities you score from 1 to 5 and weight. If a must-have has more than five entries, it is not a must-have list, it is a fantasy, and it will empty your pool before you have read anything.
Then run two passes. The first pass is knockouts only: 60 to 90 seconds per resume, checking whether each must-have is evidenced somewhere on the page, marking yes or no in the spreadsheet, and ranking nothing. Fifty applications take about an hour. The second pass scores only the survivors on the weighted nice-to-haves and ranks them, which is where you decide who gets a phone screen. Keeping the passes separate stops the common failure where an impressive resume in an unrelated field survives because it was read early and everything after it got graded against it.
| Stage | Time per person | What you are deciding | Typical survivors from 50 |
|---|---|---|---|
| Pass 1: must-have knockouts | 60-90 seconds | Does the resume evidence every must-have? Pass or fail, no ranking. | 12-18 |
| Pass 2: weighted scoring | 3-5 minutes | How well does each survivor match the nice-to-haves? Score and rank. | 8-10 |
| Phone screen | 15-20 minutes | Pay expectations, availability, and two role-specific questions. Same questions, same order, every time. | 4-6 |
| Interview | 45-60 minutes | Depth on the must-haves, plus a work sample if the role allows one. | 3-4 |
| Reference and offer | 30 minutes | Verify the two claims that most affect the decision. | 1 |
Work backward from that table when you are deciding whether your pool is big enough. If a role needs three finalists and roughly one in six applicants survives to the interview stage, you need somewhere near twenty applications of the right type. Run the arithmetic on your own numbers after your next two hires rather than borrowing anyone's benchmarks, because the ratio that matters is yours: the share of your applicants who clear your must-haves, which depends almost entirely on how specific your posting was.
Consistency is not bureaucracy here, it is the whole legal defense. If a rejected applicant later claims the decision was discriminatory, what you have is a scorecard applied identically to everyone or you have nothing. Two habits carry most of that weight: ask every phone-screened applicant the same questions in the same order, and write the notes the same day, in job-related language only. "Could not describe a reconciliation she had run" is a record. "Not a culture fit" is an exhibit for the other side.
Applicant Records: What to Keep, for How Long, and Why
Everyone in the applicant pool generates records, including the people you rejected in the first ninety seconds. The retention rules are short but they are specific, and the common small-business practice of letting applications live in an email inbox until the inbox gets cleaned out satisfies none of them.
| Rule | Who it covers | How long |
|---|---|---|
| Title VII and ADA recordkeeping (29 CFR 1602) | Employers with 15 or more employees | All personnel and employment records, including applications and resumes from people you did not hire, for 1 year from the date the record was made or the personnel action was taken, whichever is later |
| ADEA recordkeeping (29 CFR 1627) | Employers with 20 or more employees | Applications and other pre-employment records for 1 year, and job advertisements and postings for 1 year |
| Charge or lawsuit filed | Any covered employer | Preserve everything related to the position and the charging party until final disposition. The 1-year clock stops mattering the moment a charge arrives. |
| Federal contractors (41 CFR 60-1.12) | Covered contractors and subcontractors | 2 years, reduced to 1 year for contractors with fewer than 150 employees and no contract of $150,000 or more |
One point of confusion worth clearing up: the detailed "Internet Applicant" test that circulates in hiring guides is an OFCCP rule written for federal contractors, not a general Title VII definition. If you hold federal contracts it tells you precisely who counts and what you must keep. If you do not, it is still a sound working definition, but your actual obligation is the simpler one above: keep the records for a year and be able to produce them.
Three practical consequences. If you invite applicants to voluntarily self-identify race, sex, or ethnicity, collect it on a form separate from the application and keep it away from whoever is making the screening decisions, so the data exists for reporting without touching the selection. If you run background checks, the FCRA sequence is not optional: written disclosure and authorization first, then a pre-adverse action notice with a copy of the report and the summary of rights, then a reasonable wait so the applicant can dispute an error, then the final adverse action notice. Many employers treat five business days as that reasonable period; the statute says only "reasonable." And if you use any automated tool that scores or ranks applicants, check your local rules before you turn it on: New York City requires an annual bias audit and advance notice to candidates for automated employment decision tools, Illinois regulates AI analysis of video interviews, and more jurisdictions are adding requirements.
The unglamorous version of all this is a single folder per opening containing the job posting as published, the scorecard, every resume received, the screening notes, and the offer. It takes minutes to maintain during an active search and is close to impossible to reconstruct a year later, which is exactly when someone asks for it.
Building a Diverse Applicant Pool
Diversity in the applicant pool does not require a DEI software platform or a dedicated diversity recruiter. It requires removing the filters that unintentionally exclude qualified candidates from underrepresented groups.
| Action | Why It Works | Effort |
|---|---|---|
| Remove degree requirements for roles that do not legally require one | Degree requirements disproportionately exclude candidates from underrepresented backgrounds. Expands the pool by up to 10x. | 5 minutes (edit the JD) |
| Post salary range in the job description | Salary transparency attracts candidates who would otherwise self-select out, especially women and minorities who are less likely to negotiate from an unlisted salary. | 0 minutes (add one line) |
| Post on at least one community-specific job board | Diversejobs.com, Remote.co, Jopwell, or industry-specific boards that reach candidates not found on Indeed. | $0-$200 per posting |
| Use skills-based screening instead of resume-based screening | Resumes reward privilege (school name, internship access, employment gaps). Skills tests reward ability. | 15 minutes to create a simple task |
| Ask every employee for referrals from different networks | Referral programs naturally reproduce the demographics of the existing team. Explicitly ask for referrals from 'people you know who are different from the current team.' | 5 minutes per conversation |
According to SHRM, inclusive hiring practices produce better business outcomes because they increase the diversity of perspectives on the team, not because of compliance requirements. For small businesses, diverse hiring is practical: in a tight labor market, excluding candidates based on unnecessary degree requirements or invisible barriers means competing for talent with one hand tied behind your back.
What Happens After You Pick a Hire From the Applicant Pool
Every applicant pool guide ends at "screen, interview, hire." None of them cover what happens to the person you selected: the transition from "applicant" to "employee." For small businesses, this transition is where the investment in building an applicant pool either pays off or is wasted.
The applicant pool funnel looks like this: 50 people apply, 8 are qualified, 3 get interviews, 1 gets the offer letter. That 1 person represents the entire ROI of your hiring effort. Protecting that investment requires the same structure after the hire as before it.
I built FirstHR for the moment the applicant pool closes and the new hire begins. The AI onboarding wizard generates a 30-60-90 day plan from the job description. Compliance paperwork (I-9, W-4, handbook acknowledgment) goes out for e-signature before Day 1. Task workflows ensure nothing falls through the cracks between offer acceptance and full productivity.
Frequently Asked Questions
What is an applicant pool?
An applicant pool is the total group of people who have submitted an application for a specific open position at your company. It includes everyone who applied, regardless of qualifications. This is different from a candidate pool (applicants who passed initial screening) and a talent pool (a database of potential future hires who have not applied to a specific role). At a small business, the applicant pool for a typical role ranges from 20 to 100 people depending on the channel, location, and role type.
What is the difference between an applicant pool and a candidate pool?
An applicant pool includes everyone who applied for a job. A candidate pool is the subset of applicants who passed your initial screening criteria and are being actively considered. Think of it as a funnel: 50 people apply (applicant pool), you screen out 40 who do not meet basic requirements, and the remaining 10 become your candidate pool. Some companies also use 'candidate pool' to mean a database of people interested in future roles, but technically that is a talent pool.
What is a good applicant pool size?
Research shows the average job posting receives approximately 250 applications. For small businesses posting on one or two job boards, a more realistic range is 20 to 100 applicants. The right number depends on the role: entry-level positions attract more applicants, specialized roles attract fewer. A good rule of thumb is that you need at least 10-15 applicants to have 3-5 qualified candidates to interview. If you are getting fewer than 10 applicants, your job post is either too specific, the salary is below market, or the channel does not reach your target candidates.
How do you build an applicant pool without an ATS?
For small businesses hiring 3-10 people per year, you do not need an ATS. Post the job on 2-3 channels (Indeed, LinkedIn, and employee referrals). Create a simple spreadsheet to track applicants: name, date applied, source, qualification status (yes/no/maybe), and notes. Review applications within 48 hours of receipt. Move qualified applicants to a 'candidates' tab. This takes 5 minutes per applicant and replaces the core function of an ATS for low-volume hiring.
Who legally counts as an applicant?
It depends on which rule you are under. Federal anti-discrimination recordkeeping applies at 15 or more employees and simply requires you to preserve application records for everyone who applied. The detailed four-part 'Internet Applicant' test often quoted in hiring guides (submitted an expression of interest through the employer's online process, is being considered for a specific position, meets the basic qualifications, and has not voluntarily withdrawn) comes from OFCCP's rules for federal contractors, not from Title VII generally. If you hold federal contracts, that test defines exactly who you must track. If you do not, treat it as a useful working definition and focus on the underlying obligation: keep records of everyone who applied for at least a year, do not delete applications, and apply the same screening criteria to everyone.
How long should you keep applicant records?
Federal law requires employers with 15+ employees to retain all hiring records (applications, resumes, interview notes) for at least one year from the date of the hiring decision. If you are a federal contractor, the requirement extends to two years. Even if you are below the EEOC threshold, keeping records for at least one year is good practice because it protects you if a rejected applicant files a discrimination claim. Store records in a consistent place (folder, spreadsheet, or HRIS), not scattered across email inboxes.
What is the difference between an internal and external applicant pool?
An internal applicant pool consists of current employees who apply for an open role (promotion or lateral move). An external applicant pool consists of outside candidates. For small businesses with 5-50 employees, internal applicant pools are often one or two people at most. The advantage of internal applicants: they are already onboarded, culturally integrated, and have a track record you can verify directly. The disadvantage: promoting internally creates a new vacancy downstream that still needs to be filled externally.
How do I increase the size of my applicant pool?
Five practical tactics: (1) Add salary range to the job post (increases applications by 30%+). (2) Remove unnecessary degree requirements (expands the pool by up to 10x). (3) Post on one industry-specific board in addition to Indeed or LinkedIn. (4) Ask every employee for 2 referrals before posting publicly. (5) Rewrite the job title to match what candidates actually search for (use 'Office Manager' not 'Administrative Operations Coordinator'). The biggest mistake: posting on 8 job boards and monitoring none of them. Two channels managed well outperform eight channels managed poorly.