It sounds straightforward: an applicant is someone who applies for a job. In practice, the word carries real legal weight, and employers that use the term loosely create compliance problems. The EEOC and OFCCP care about applicants because recordkeeping, diversity reporting, and non-discrimination analysis all rely on a defined pool. The Internet Applicant rule, issued in 2005 and still in force, sets out four criteria that have to be met before someone counts. Recruiting systems, LinkedIn outreach, referrals, and talent pools all raise the question of who made it across the line.
The Internet Applicant Definition Under OFCCP's Internet Applicant rule (41 CFR 60-1.3), a person is considered an applicant for federal contractor recordkeeping purposes when all four of the following are true: (1) the individual submits an expression of interest through the Internet or related electronic data technologies, (2) the employer considers the individual for employment in a particular position, (3) the individual's expression of interest indicates they possess the basic qualifications for the position, and (4) the individual does not remove themselves from consideration or otherwise indicate they are no longer interested.
All four criteria matter. Someone who submits a resume but isn't considered for the specific role doesn't count. Someone who meets qualifications but withdraws before the screening is complete doesn't count either.
Why the Definition Matters for Compliance The applicant definition determines who gets tracked for demographic data, who counts in adverse impact analysis, and which candidates factor into disparate impact calculations. Federal contractors subject to Section 503 and VEVRAA also use the applicant pool to calculate hiring benchmark performance.
Applicants do not include passive LinkedIn contacts, referrals who never submitted an application, or people who attended a job fair without formally applying. The line is drawn at the formal expression of interest tied to a specific position.
What About Candidates Sourced Through Recruiters? The same criteria apply. If a recruiter's sourced candidate submits an application for a specific posting and meets the basic qualifications, they count. If the recruiter identifies someone who never formally applies, they don't count.
Common Employer Mistakes in Applicant Tracking Three patterns cause trouble in audits. First, inconsistent application of "basic qualifications": counting some candidates as applicants and others not, when they submitted similar information. Second, failing to track withdrawals: employers that don't record when a candidate removes themselves end up with inflated applicant counts and skewed demographic data. Third, treating passive sourcing and formal applications as equivalent, which inflates numerators or denominators depending on the context.
The cleanest practice is to define basic qualifications in the job posting itself, apply them consistently at intake, and document every withdrawal or failure-to-respond moment in the applicant tracking system. EEOC and OFCCP auditors look for consistency more than perfection.
Running a Clean Applicant Data Process in 2026 The underlying point of applicant tracking is to enable non-discrimination analysis and equal opportunity practice. For HR teams, the practical steps are: maintain a single definition of applicant that aligns with the Internet Applicant rule, document basic qualifications in every job posting, record every expression of interest and every withdrawal, and audit the resulting data quarterly for anomalies.
The applicant pool is also the starting point for broader workforce planning conversations: the onboarding forecast, the diversity analysis, and the early-career pipeline. Accurate applicant data makes all of those conversations sharper, and it makes the performance review and promotion discussions downstream more defensible because the entry point to the organization is well documented.
.svg)
.svg)
