Recruitment Tracker Template

In plain language: Records the job title, department, requisition number, hiring manager name, date the role was opened, and the approved headcount it fills.

Common mistake: Omitting the requisition number and treating all candidates as a single undifferentiated pool — this makes it impossible to tie candidate records to a specific approved position during an OFCCP or EEO audit.

In plain language: Captures each candidate's name, contact information, application date, and a unique candidate ID that links all documents in their file.

Common mistake: Recording candidates by name only with no unique identifier — when two candidates share a name or a candidate applies for multiple roles, records become mixed, creating compliance and legal exposure.

In plain language: Documents where each candidate's application originated — job board, referral, agency, direct outreach, or careers page — to support cost-per-hire analysis and channel effectiveness review.

Common mistake: Leaving the source field blank or recording 'online' as a catch-all — granular source data is required to calculate ROI per channel and to demonstrate non-discriminatory sourcing practices.

In plain language: Tracks the candidate's current position in the hiring funnel — applied, phone screened, first interview, second interview, assessment, reference check, offer, hired, or declined — with a date stamp for each transition.

Common mistake: Updating only the current stage and overwriting the prior one — without a complete stage history, you cannot reconstruct the timeline if a candidate files a discrimination complaint months after rejection.

In plain language: Documents each interview round: the date, interviewer names, format (phone, video, panel), questions asked or competencies assessed, and a numerical or categorical score.

Common mistake: Recording only a pass/fail outcome with no supporting notes — a bare 'rejected' entry cannot demonstrate that the decision was based on job-related criteria when challenged in a discrimination claim.

In plain language: Assigns a standardized code to every candidate who exits the pipeline — whether rejected, withdrawn, or declined an offer — with a documented, job-related reason for the decision.

Common mistake: Using vague disposition labels like 'not a fit' or 'cultural mismatch' without tying the decision to specific, measurable job requirements — subjective language is the most common trigger for EEO complaints and litigation.

In plain language: Records the terms of any formal offer extended: base salary, start date, offer date, offer expiry date, and whether the offer was accepted, declined, or rescinded.

Common mistake: Not recording declined or rescinded offers — regulators and courts look at offer outcomes across demographic groups to identify patterns of adverse impact, and missing data prevents you from proving the absence of discrimination.

In plain language: Tracks whether a reference check and background screening were completed, the dates completed, the vendor used, and the pass/fail outcome with any flags noted.

Common mistake: Performing background checks inconsistently — conducting them for some candidates but not others in the same role creates disparate treatment liability, even when the intent was administrative.

In plain language: Records the final hire/no-hire decision, the name and title of the approving authority, the decision date, and any conditions attached to the offer.

Common mistake: Documenting the hire without recording who approved it — in multi-approver environments, an undocumented approval chain makes it impossible to confirm that required sign-offs were obtained during an audit.

In plain language: States the required retention period for the completed tracker, identifies who is responsible for storing it, and notes any data privacy obligations — including GDPR deletion timelines for EU candidates.

Common mistake: Retaining recruitment records indefinitely or discarding them before the statutory minimum — both create compliance exposure. US federal contractors must retain records for at least 2 years; GDPR generally requires deletion once the legitimate purpose has expired.

A recruitment tracker is a structured document — or template — that records every candidate's progress through a hiring pipeline from initial application to final decision. It captures application dates, sourcing channels, interview outcomes, disposition codes, offer details, and the identity of each decision-maker. It serves as both an operational tool for managing hiring and a compliance record demonstrating that selection decisions were made on legitimate, job-related criteria.

US federal contractors are required by OFCCP regulations to retain applicant flow logs and related hiring records for a minimum of 2 years. Non-contractors are not subject to OFCCP, but EEO laws in the US, UK Employment Equality Acts, and EU anti-discrimination directives all create an implicit obligation to be able to demonstrate non-discriminatory hiring if challenged. A recruitment tracker is the most practical way to generate that evidence. In Canada, provincial human rights codes similarly require employers to be able to explain selection decisions.

US federal contractors must retain applicant flow logs and related records for at least 2 years from the date of the personnel action. Non-contractor US employers covered by Title VII should retain records for at least 1 year. In the UK, ACAS guidance recommends at least 6 months after the vacancy is filled. In the EU, GDPR requires that personal data of unsuccessful candidates be deleted once the legitimate retention purpose has expired — typically 6 to 12 months after the recruitment process ends unless consent for longer retention was obtained.

A disposition code is a standardized label assigned to a candidate record when they exit the hiring pipeline, explaining why they were not selected, withdrew, or declined an offer. Codes matter because vague or subjective rejection reasons — such as 'not a fit' — are the most common language cited in EEO complaints and plaintiff discovery requests. A finite, pre-defined set of codes tied to objective, job-related criteria is the single most effective protection against a discrimination claim based on hiring decisions.

An ATS is software — platforms like Greenhouse, Lever, or Workday Recruiting — that automates candidate sourcing, communication, scheduling, and record-keeping at scale. A recruitment tracker template is a document-based alternative that provides the same structural record without a software subscription, making it accessible for small businesses, startups, and any organization managing a limited number of open roles at any given time. The legal compliance obligations are the same regardless of which tool is used.

The tracker itself is typically signed or approved by the hiring manager and an HR representative at the close of the requisition to confirm the accuracy of the record. Offer sections may require additional sign-off. In organizations with formal approval chains, the hiring decision section should bear the signature of the approving authority. While no jurisdiction mandates a signature on a recruitment log specifically, a signed, dated record carries significantly more evidentiary weight than an unsigned one in a dispute or audit.

Under GDPR, personal data collected during recruitment — names, contact details, CVs, interview notes — may only be retained for as long as there is a legitimate purpose. For unsuccessful candidates, this is typically 6 to 12 months after the process ends unless the candidate consented to a longer period. CCPA gives California-based job applicants the right to know what data is collected and to request deletion. Recruitment trackers that include a data privacy notice and a defined destruction date are more easily brought into compliance with both frameworks.

It is generally inadvisable. Using a single document for multiple requisitions makes it difficult to produce the candidate pool for a specific role during an audit and increases the risk of commingled records. The best practice is to maintain a separate tracker instance per requisition, filed under the requisition number, and archived when the role is filled or closed. Summary dashboards can aggregate data across trackers for reporting purposes.

Recruitment trackers should not contain protected characteristic data — race, national origin, religion, disability status, age, or pregnancy — unless the organization operates a formal, separate voluntary self-identification program for EEO reporting purposes. Mixing selection-decision records with demographic data in a single document creates the appearance that protected characteristics influenced the decision. Store any voluntary self-identification data in a segregated file, never in the selection record.

Adverse impact analysis compares selection rates between demographic groups at each stage of the hiring funnel — applications, screens, interviews, and offers. A well-maintained tracker provides the raw data for this analysis: the number of applicants, the number advanced at each stage, and the number ultimately hired. Regulators and courts use the 4/5ths rule as the primary statistical test. Without complete stage-by-stage records, an employer cannot perform the analysis or demonstrate the absence of disparate impact.