What is an Applicant?

An applicant is a person who has expressed interest in being considered for a specific job or employment opportunity through the application method used by the employer or recruiting firm. The expression of interest may be a completed online application, submitted resume, email, referral response, or another accepted method.

The term usually links a person to a particular vacancy and selection process. A candidate is broader: the person may have applied, been sourced by a recruiter, joined a talent pool, received a referral, or been considered for several roles. In an applicant tracking system, one person can have a single profile and several separate applications, each with its own job, source, stage, dates, and outcome.

Note: Legal and reporting definitions can be narrower than everyday recruiting language. Firms should apply the definitions required by the jurisdiction, client, contract, or reporting program.

Applicants at a glance

• An applicant has expressed interest in a defined employment opportunity.
• The application belongs to a job-specific selection process.
• One person may submit applications for several jobs.
• A sourced or passive candidate may become an applicant after expressing interest through the accepted process.
• Withdrawal, eligibility, consideration, and recordkeeping rules can affect formal applicant counts.
• Clear status definitions improve reporting, communication, and compliance records.

How applicant status works

Applicant status begins when a person expresses interest through a method the organization accepts for the role. The system should capture the person, job, application date, source, submitted materials, consent or notice records where relevant, and current stage.

The recruiting team then reviews the application against documented criteria. Possible stages include new application, review, screen, and interview, as well as client submission, offer, hired, rejected, and withdrawn. Firms can use different labels, yet every stage needs a clear operational meaning.

The applicant record should preserve what happened for that job. A resume update may change the person’s master profile. It should not erase the application date, original answers, stage history, reviewer notes, or disposition reason tied to an earlier role.

Applicant status can end when the person is hired, rejected, withdraws, becomes unavailable, or the vacancy closes. The person’s broader candidate relationship can continue. A past applicant may later enter a talent pool, receive outreach for another role, or apply again.

Example from a recruiting firm workflow

A healthcare staffing firm posts a registered nurse vacancy and receives 180 applications. Each application creates a job-specific record linked to the person’s candidate profile. The firm captures the source, submission time, work authorization response, license details, location, shift preference, and resume.

Duplicate detection finds that 24 applicants already exist in the database. Their new applications attach to the existing profiles, preserving earlier conversations and placement history. Recruiters can review the new role without creating parallel records for the same person.

The firm separates required criteria from preferences. Applicants missing a license number move to a clarification queue rather than receiving an automatic rejection. Recruiters record job-related disposition reasons and send status updates at defined points.

Several qualified applicants do not fit this vacancy’s schedule. With appropriate permission and communication, the firm keeps their candidate relationships active for future roles. Their application outcome remains attached to the original job.

An executive-search firm often starts with sourced prospects rather than applicants. A prospect becomes an applicant or formal candidate under the firm’s process after expressing interest in the mandate. The exact terminology may depend on client reporting and confidentiality practices.

Applicant versus candidate and prospect

The labels can overlap across systems. The useful distinction is whether the person has expressed interest in a defined role and whether a job-specific selection record exists.

Why applicant definitions matter

Applicant counts feed workload planning, source reporting, conversion rates and adverse-impact analysis, client reports, and hiring metrics. An inflated count can make source performance look weak. An overly narrow count can hide people who entered the selection process.

Firms need consistent definitions across jobs and recruiters. If one recruiter creates an application when a resume arrives and another waits until a screening call, funnel metrics will not be comparable.

The distinction matters for candidate experience too. People expect acknowledgment, a clear process, and an outcome after applying. A person stored in a database without a current application may need a different message from someone waiting for a decision on a live role.

How to measure applicant flow

• Application volume: Valid applications received for a job during a defined period.
• Qualified applicant rate: Applicants meeting documented minimum criteria divided by applicants reviewed.
• Source-to-qualified rate: Qualified applicants from a source divided by valid applications from that source.
• Application-to-screen rate: Applicants entering recruiter screening divided by applicants reviewed.
• Application-to-interview rate: Applicants reaching interview divided by valid applications.
• Application-to-hire rate: Hires divided by valid applications.
• Median review time: Elapsed time from application receipt to first completed review.
• Status-update time: Elapsed time between a material decision and candidate communication.
• Withdrawal rate: Applicants who withdraw divided by applicants entering the defined process.
• Disposition completeness: Closed applications with a documented reason divided by closed applications.

Use a stable denominator. Decide how duplicates, incomplete submissions, test records, withdrawals, and clearly ineligible applications enter each measure.

Common mistakes

Treating every database record as an applicant

A sourced profile or old contact is not automatically an applicant for every open job. Create a job relationship when the person enters that role’s process.

Creating a new person record for every application

This fragments history and creates duplicate outreach. Keep one person profile with separate job-specific applications.

Using inconsistent stage definitions

Define what counts as reviewed, screened, submitted, rejected, and withdrawn. Train the team and audit usage.

Closing applications without a reason

Generic rejection statuses weaken reporting and process review. Use concise, job-related disposition reasons and restrict sensitive notes.

Losing applicants after one rejection

A person can be unsuitable for one role and valuable for another role. Preserve the relationship, permission status, skills, and communication history for future consideration.

AI and automation impact

Automation can acknowledge applications, assign owners, identify duplicates, request missing information, schedule approved steps, and send status updates. AI can parse resumes and retrieve evidence, suggest profile updates, and support matching against documented criteria.

Recruiters still need to interpret transferable experience, resolve conflicting information, handle accommodations, assess motivation, manage client tradeoffs, and make or approve consequential decisions. Automated recommendations should retain source evidence and a correction path.

Recruiterflow’s applicant tracking system connects job applications with candidate profiles, stages, communications, collaboration, automation, and reporting.

Editorial note: Product Marketing should confirm any page-level feature statement before publication.

Practical checklist

• Define when a person becomes an applicant.
• Keep one person profile with separate job applications.
• Capture source, date, job, materials, stage, and owner.
• Separate required criteria from client preferences.
• Define each pipeline stage and disposition reason.
• Review duplicates before creating new profiles.
• Set response and status-update expectations.
• Preserve application history after profile updates.
• Track withdrawals and closed-job outcomes.
• Confirm legal and contractual recordkeeping definitions.

Questions recruiters ask

Is every candidate an applicant?

No. A candidate may be sourced, referred, rediscovered, or considered without applying. An applicant has expressed interest in a specific opportunity through the accepted process.

Can one person be an applicant for several jobs?

Yes. The person should have one master profile and a separate application record for each job. Each application keeps its own source, stage, dates, notes, and outcome.

Does submitting a resume always make someone an applicant?

It depends on the organization’s process and the applicable definition. A resume submitted for a specific role often expresses interest. An unsolicited resume added to a general database may not create a job-specific application.

What happens to rejected applicants?

Close the application with a documented, job-related reason and send the appropriate communication. The candidate profile can remain available for future roles under the firm’s permission and retention practices.