ATS Data Hygiene and Deduplication
Candidates apply more than once — to the same role with a slightly different email, or to several roles over a few years — and most ATS platforms create a fresh record each time rather than recognizing it's the same person. The result is a database full of duplicates that inflate pipeline counts, split a candidate's interview and reference history across records a hiring manager never sees together, and make sourcing tools re-contact someone who already withdrew or was hired elsewhere. Manual cleanup is tedious enough that it rarely happens until reporting numbers look obviously wrong.
STARTING PRICE
From €299
Standard tier · Multi-step workflow with AI extraction/decisioning and 2-3 integrations.
Get a quote →Saves roughly 4-6 hrs/week for recruiting ops maintaining ATS data quality.
How the automation works
We identify likely duplicate candidate records using more than exact name-and-email matching — accounting for name variations, job changes, and multiple email addresses — and route matches for merge review rather than auto-merging anything with legal or compliance history attached. Merged records preserve full interaction history, including GDPR-relevant consent and communication logs, instead of collapsing them into whichever record happened to be created first. Ongoing deduplication runs on new applications as they arrive, catching repeat applicants before they get treated as new sourcing targets, and a data-quality dashboard tracks duplicate rate over time so the underlying cause — usually a broken application form or a sourcing tool creating records outside the normal apply flow — gets fixed instead of just cleaned up repeatedly.
Process flow
- 01
New application or scheduled scan trigger
Every new application runs through a duplicate check on arrival, and a scheduled full-database scan catches older duplicates that predate the automation.
- 02
Identify likely duplicates ai
Matching goes beyond exact name-and-email pairs to account for name changes, multiple email addresses and near-identical work history, surfacing likely matches with a confidence score.
- 03
Route matches for merge review output
Matches above a confidence threshold auto-merge; borderline matches, and any record with legal or compliance-sensitive history, route to a human for review before merging.
- 04
Merge preserving full history ai
Approved merges combine interaction history, consent records and communication logs from both records rather than defaulting to whichever record was created first.
- 05
Track duplicate source and rate output
Duplicate rate is tracked over time by source, surfacing whether a broken application form or a specific sourcing tool is the root cause generating repeat records.
Inputs
- ATS candidate database
- New application stream
- Consent and communication history per record
- Merge confidence threshold and review rules
Outputs
- Merged candidate records with preserved history
- Duplicate match review queue
- Data-quality dashboard by duplicate source
- Reduced pipeline-count inflation in reporting
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Auto-merging records without preserving both sides' communication and consent history can lose the record of when a candidate opted out of future contact, or when a GDPR data-subject request was fulfilled — a merge that drops that history creates a compliance gap, not just a data-cleanliness improvement.
- Matching purely on exact name-and-email pairs misses the most common real-world duplicate pattern — the same person applying years apart with a new email address after a job or name change — while overly loose fuzzy matching on common names risks merging two genuinely different candidates into one record.
- Merging two records that were both active in different, currently-open pipelines can silently drop one of those pipeline associations if the merge logic only keeps one 'active application' field — both active candidacies need to survive the merge, not just the most recent one.
- Deduplication that runs once as a cleanup project rather than continuously on new applications just lets the duplicate rate build back up — the same broken form or sourcing integration that caused the original mess keeps creating new duplicates unless the root cause is tracked and fixed.
Frequently asked questions
Will merging duplicate records ever delete a candidate's interview or reference history?
No — merges are built to preserve full history from both records, including consent and communication logs, rather than keeping only whichever record was created first.
What happens if two records look similar but are actually different candidates?
Matches below a high confidence threshold, and anything involving legal or compliance-sensitive history, route to a human reviewer before any merge happens — nothing merges automatically on a borderline match.
Does this run continuously or only as a one-time cleanup?
Both — an initial scan cleans existing duplicates, and every new application is checked on arrival going forward, so the duplicate rate doesn't quietly rebuild.
Can this tell us why duplicates keep happening in the first place?
Yes, duplicate source is tracked over time, which usually points to a specific broken form or sourcing integration that can be fixed rather than cleaned up repeatedly.