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. The HR rules and regulations guide covers the full EEOC framework.
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 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"). The talent pool guide covers how to formalize this into a simple, maintainable system.
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. The job description guide covers how to write a JD that attracts the right applicants and filters out the wrong ones.
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 referrals (20-30%), with occasional direct outreach for specialized roles. The sourcing ideas guide covers 25 channels for building each type of pool.
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. The prescreen interview guide covers the 15-minute phone screen that separates qualified candidates from unqualified applicants.
An ATS 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. The recruitment metrics guide covers how to track hiring efficiency with or without an ATS.
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. The skills-based hiring guide covers how to evaluate ability instead of credentials.
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. That 1 person represents the entire ROI of your hiring effort. Protecting that investment requires the same structure after the hire as before it. The full cycle recruiting guide covers all 6 stages, including the onboarding stage that most hiring guides skip.
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. The onboarding checklist covers the full 50+ task list. The 30-60-90 day plan guide covers the milestone framework.
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.
Does the EEOC definition of applicant matter for small businesses?
Yes, if you have 15 or more employees (the EEOC threshold for most federal anti-discrimination laws). The EEOC defines an internet applicant as someone who: (1) submitted an expression of interest through the employer's online process, (2) is being considered for a specific position, (3) has basic qualifications, and (4) has not voluntarily withdrawn. For practical purposes: keep records of all applicants for at least 1-2 years, 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.