Candidates and candidatures are not interchangeable terms, yet many recruiters, HR software vendors, and even political analysts treat them as synonyms. Confusing the two can distort metrics, misalign expectations, and create legal risk in regulated industries.
Understanding the nuance unlocks sharper reporting, cleaner data architecture, and more persuasive stakeholder conversations. The payoff is immediate: a hiring manager who asks for “candidate conversion” will receive a different dashboard than one who requests “candidature completion,” and the difference shapes budget decisions.
Core Definitions with Legal and Operational Precision
Candidate: The Individual Human
A candidate is a natural person who has expressed interest in a role, submitted identifiable data, and can be reached for further assessment. Their existence is binary: either the person is in your talent pool or not.
From a GDPR standpoint, the moment you store a name, email, or phone number, you are processing personal data of a candidate and must justify the lawful basis. If the same person applies to five requisitions, you still have one candidate record, not five.
Candidature: The Container for an Application Journey
Candidature is the legal and procedural envelope that opens when a candidate submits an application for one specific vacancy and closes when the process ends. It carries its own lifecycle states: received, screened, interviewed, offered, hired, rejected, or withdrawn.
One candidate can spawn multiple candidatures across different time periods, departments, or geographies, each with distinct statuses and audit trails. Regulators care about candidatures because equal-opportunity reports are generated per opening, not per person.
Data Architecture: How to Model the Relationship
One-to-Many Schema Design
Build two master tables: Person (candidate) and Application (candidature). Link them through a foreign key so that PersonID can appear many times in Application but each Application row points to exactly one PersonID.
This schema prevents duplicate talent records, simplifies marketing consent, and still allows pipeline analytics to count applications accurately. Include a unique constraint on the pair (PersonID, RequisitionID) if your policy forbids parallel applications to the same job.
Status Tracking at Both Levels
Store candidate-level attributes like sourcing channel, talent-community consent, and GDPR retention clock separately from candidature attributes like stage, interviewer feedback, and offer salary. Separating the two axes lets you query “how many silver-medalist candidates from last year re-applied this year” without contaminating historical funnel metrics.
Recruitment Metrics That Change When You Use the Correct Term
Time to Fill vs Time to Candidate Acceptance
Time to fill is measured from candidature creation (requisition posted) to candidature closure (offer accepted), not from the day the candidate first entered your CRM. Ignoring this inflates the metric by including passive-nurture time.
Conversion Rates That Actually Convert
If 100 candidates enter your CRM and 20 of them submit applications, you have a 20 % candidate-to-candidature conversion rate. Later, if 5 candidatures reach hire, your candidature-to-hire rate is 25 %, but your candidate-to-hire rate is only 5 %—a very different story for cost-per-hire calculations.
Political Context: Ballots and Party Nomination
Nomination Papers Create Candidature, Not Candidate
In electoral law, a person becomes a candidate only after the returning officer accepts their nomination papers, creating a formal candidature for a specific constituency. Rejection of papers means no candidature exists, so the person remains a prospective candidate with no legal standing.
Deposit and Forfeiture Rules Attach to Candidature
The monetary deposit is tied to the candidature; if the same person runs in a by-election later, a fresh deposit is required. Consequently, party treasurers track candidature-level expenses, not candidate-level, to stay within spending caps.
Compliance and Audit Trails
Right to Be Forgotten Requests
When a European candidate invokes GDPR Article 17, you must delete their personal data but retain anonymized candidature statistics for reporting. Store a hashed PersonID that cannot be reversed but still allows linkage for aggregate analysis.
OFCCP Audits in the United States
During a compliance review, the Office of Federal Contract Compliance Programs will request disposition reasons for every candidature, not every candidate. Ensure your applicant-tracking system records a per-candidature code such as “basic qualification unmet” or “interview scored below cutoff.”
Practical Playbook for Recruiters
Job-Board Distribution Settings
Set your multiposter to create a new candidature UUID only when the candidate clicks “apply” on the career site, not when they upload a resume on a job-board microsite. This prevents inflated application counts and keeps sourcing analytics clean.
Silver-Medalist Re-Engagement
Tag candidatures that reached final interview but lost to a margin of less than 10 % score difference. When a similar requisition opens, query for candidates with such historic candidatures and send a personalized “fast-track” email that references their previous finalist status.
Technology Vendor Evaluation Checklist
Data Model Review
Ask the vendor to export a sample schema; look for separate Candidate and Application entities with a clear foreign-key relationship. If the demo environment shows only one combined table, expect deduplication headaches and inflated candidate counts.
Reporting Flexibility
Request a live query: “Show me candidates who applied to two different requisitions in the last 12 months and were hired in the second one.” If the system cannot answer without Excel gymnastics, the underlying model is probably flattening candidatures into candidates.
Common Scenarios and How to Navigate Them
Internal Transfer
When an employee applies for an internal vacancy, create a new candidature linked to their existing candidate record. Do not duplicate the person; instead, mark the candidature type as “internal” so that time-to-fill benchmarks exclude the external pipeline.
Employee Referral with Existing Profile
If a referred candidate already exists in your CRM, append the new candidature to the same person and override the sourcing channel to “employee referral” only for that candidature. This preserves original source data for first-touch attribution while giving the referral program its due credit.
Pitfalls That Even Mature Teams Encounter
Merge Conflicts After Acquisitions
During a corporate acquisition, HRIS migrations often collapse legacy candidate IDs into a new system, creating orphan candidatures. Run a pre-migration script that exports candidature-level custom fields and re-links them post-migration using email plus requisition code as a composite key.
Automated Withdrawal Logic
Some platforms auto-withdraw older candidatures after 90 days, but if the candidate reapplies, the new candidature inherits the old status history, skewing time-in-stage metrics. Disable auto-withdraw or configure it to hard-delete only after explicit candidate consent.
Future-Proofing: AI and Predictive Analytics
Training Data Integrity
Machine-learning models that predict hireability must be trained at the candidature level, not the candidate level, to avoid leakage from parallel applications. Include a feature flag that indicates whether the candidate has other open candidatures to control for competition bias.
Explainability Requirements
If your AI recommends rejecting a candidature, the audit log must show the specific candidature ID and the features tied to that application. Regulators will reject explanations that reference generic candidate attributes like “average past score” because such scores may derive from unrelated roles.