The most common recruitment data quality issues are duplicate candidate profiles, incomplete contact information, inconsistent disposition codes, and missing source-of-hire tracking — and together they make your hiring metrics unreliable, your pipeline reports inaccurate, and your diversity data incomplete.
Recruiting teams make decisions based on their ATS data: time-to-fill metrics, source effectiveness, pipeline diversity, offer acceptance rates. When the underlying data is bad, every metric built on it is wrong — and every improvement initiative based on those metrics targets the wrong problem.
The Most Common Recruitment Data Quality Problems
Duplicate Candidate Profiles
Duplicate candidate records are the most pervasive ATS data quality problem. They're created when:
- The same candidate applies through multiple sources and the ATS doesn't deduplicate
- A recruiter can't find an existing record and creates a new one
- A talent sourcing import doesn't match against existing records
Sohovi automatically finds every duplicate in your dataset — including near-matches — and shows you exactly which rows are affected.
The consequences: a candidate's interview history is split across multiple records. Recruiters see incomplete information. Pipeline metrics double-count candidates. Diversity reports inflate pool sizes.
Incomplete Contact Information
Sourced candidates — those added by recruiters rather than self-applying — often have incomplete records. A LinkedIn profile import might bring in name and title but no email address or phone number. A resume parse might miss contact details that were in a non-standard location.
When contact information is incomplete, follow-up outreach fails, candidates fall through the pipeline, and the recruiting team underestimates how much active sourcing actually required.
Inconsistent Disposition Codes
Disposition codes — Rejected, Withdrawn, Offer Declined, Hired — are the most important categorical fields in an ATS. When they're used inconsistently (different recruiters use different codes for the same outcome, or codes are left blank when a candidate drops off), pipeline reporting and diversity reporting both break.
An ATS with 40% null rates on disposition codes tells you almost nothing reliable about your recruiting funnel.
Missing or Wrong Source of Hire
Source of hire is one of the most valuable fields in an ATS — it tells you where your best hires come from and how to allocate your sourcing budget. When source isn't captured consistently (or at all), you can't calculate which channels produce the best candidates, and sourcing budget is allocated on gut feel rather than data.
Stale Candidate Records
Candidate records that were created during a previous recruiting cycle and never updated accumulate in the ATS — people who have moved, changed roles, or explicitly asked not to be contacted. Sourcing from stale records wastes outreach effort and can damage your employer brand.
Practical Fixes for Recruitment Data Quality
1. Run a quarterly ATS deduplication. Export your candidate list and run a deduplication check by email address. For candidates with no email, check by name and phone combination. Merge duplicate profiles before they compound through another hiring cycle.
2. Enforce disposition codes at every stage. Make disposition codes required for any candidate who progresses past screening. Use a controlled dropdown — not a free-text field — to prevent inconsistent values. Train recruiters on exactly which code applies to which outcome.
3. Require source of hire at record creation. Make source a required field for any candidate added by a recruiter. Use a controlled list of approved source values (LinkedIn, Indeed, Employee Referral, University, Direct Application, etc.) so your source analytics are comparable across time.
4. Build a candidate record completeness check into your onboarding workflow. Before any candidate is moved to interview stage, verify that at minimum their email and phone are populated. This catches sourced candidates with incomplete contact info before the gap causes a missed interview.
Sohovi profiles every column in your dataset for completeness and flags the exact rows where values are missing — free to try.
5. Archive or mark stale candidates. Records that haven't been updated in 24+ months should be flagged as "cold" and excluded from active outreach until the contact information is reconfirmed.
Frequently Asked Questions
Q: What are the most common data quality issues in recruitment? Duplicate candidate profiles, incomplete contact information on sourced candidates, inconsistent disposition code usage, missing source of hire data, and stale candidate records that are never archived are the most common recruiting data quality problems.
Q: How do duplicate candidate profiles affect recruiting? Duplicate profiles split interview history, causing recruiters to make decisions without a complete view of the candidate relationship. They inflate pipeline counts, making the recruiting funnel look larger than it is. They corrupt diversity reporting by counting the same candidate multiple times.
Q: Why are disposition codes important for recruiting data quality? Disposition codes define the outcome of each candidate's journey through your pipeline — they're the basis for funnel conversion rate analysis, diversity reporting, and compliance documentation. When they're inconsistent or missing, you can't reliably measure where candidates drop off, what your offer acceptance rate is, or whether your process is fair.
Q: How does missing source of hire data affect recruiting strategy? Source of hire is the foundational metric for sourcing channel ROI. Without it, recruiting leaders can't calculate which channels produce the most hires, the fastest fills, or the best quality-of-hire outcomes. Sourcing budget decisions made without source data are made on instinct rather than evidence.
Q: How can recruiters prevent duplicate candidate records? Before creating a new candidate record, search the ATS by email address and phone number. If an existing record is found, update it rather than creating a new one. Many ATS platforms support configuring automatic duplicate detection — enabling this catches most duplicates at the point of entry.
Q: What is an acceptable null rate for disposition codes in an ATS? For candidates who have progressed past initial screening, the disposition code should be populated for close to 100% of records. For candidates who applied but were never reviewed, a higher null rate is acceptable. The key threshold is: for any candidate who was actively engaged, the disposition code should be complete.
Q: How do stale candidate records affect recruiting operations? Stale records waste outreach effort (contacting people who have moved on or asked not to be contacted), inflate database counts, and corrupt sourcing analytics by including outdated channel attributions. Archiving or marking candidates inactive after 24 months of no activity keeps the database actionable.
Q: How does recruiting data quality affect diversity, equity, and inclusion efforts? DEI analysis in recruiting depends on accurate demographic data and fair process documentation. Duplicate records inflate pool sizes and distort selection rate calculations. Missing disposition codes prevent fair process documentation. Incomplete demographic data produces unreliable diversity funnel metrics.
Q: What is the most important ATS data quality fix for a small recruiting team? Disposition code enforcement. For a small team, getting consistent use of disposition codes across all active candidates is the single change that most improves recruiting analytics reliability. It's behavioral, not technical — it requires training and accountability, not a system change.
Q: How should recruiting teams handle candidate data from a third-party sourcing tool or LinkedIn import? Every import should include: deduplication check against existing records, email validation (confirm the email field is populated and valid format), source assignment (tag all imported records with the correct source), and a completeness review before any imported candidate is moved into an active pipeline.
Reliable recruiting metrics start with reliable ATS data. A quarterly deduplication, required disposition codes, and source of hire enforcement are the three practices that have the most immediate impact on recruiting data quality.
