ATS data enrichment: how to update candidate records without losing good data

Which candidate fields to enrich, how to write results back without overwriting good records, and the retention and privacy rules to check first

person looking at ats data on laptop

Recruiting teams use ATS data enrichment to bring older candidate records in an applicant tracking system (ATS) back into use. Past applicants keep changing emails, titles, and employers after they leave your pipeline. Refreshing their records lets you search for people your team already knows before sourcing a role from scratch.

ATS data enrichment means adding or updating information on existing candidate records from outside sources, such as a current work email, phone number, title, employer, or location. Done well, it fills gaps without overwriting what candidates told you, and it records where each new value came from.

Key takeaways

  • Enrich contact details, employer and location, but keep resumes, application answers, consent and notes as the candidate gave them.
  • Write enriched values to their own fields with a source and a date.
  • Deduplicate and test on a small sample before enriching a whole talent pool.
  • Check your retention policy and deletion requests before a cleanup removes or restores data.

What ATS data enrichment includes

Candidate enrichment, as it's also called, works on records you already hold. A provider matches identifiers such as a personal email or profile URL against its own data, then returns fields like a current title, employer, or work email. How confident that match is matters as much as the fields themselves.

Enrichment differs from two related jobs. Resume parsing pulls fields from a document the candidate sent, while enrichment brings in information from elsewhere, so it needs more validation. Customer relationship management (CRM) enrichment does similar work on client and prospect records, but it uses different fields.

Why candidate records in an ATS go out of date

Candidate records age because people keep changing jobs, numbers, and cities after they apply. In January 2026, federal tenure data showed median employer tenure at 4.1 years for wage and salary workers, with 20.6 percent having a year or less. The U.S. Bureau of Labor Statistics (BLS) figures measure time with an employer, not how fast records go stale. Still, they suggest a record collected a year or more ago may list a former employer for a meaningful share of people.

Contact details drift too, as people switch phone numbers and emails, move, and pick up skills their old resume never mentioned. Duplicates add confusion when someone applies twice with different email addresses.

Which fields to enrich and which to leave alone

The useful line runs between fields that describe where someone is now and fields that record what the candidate told you. A resume shows what the candidate submitted, while a provider's match is a best guess about the present. Recruiters need to see which is which.

  • Work email and phone: Enrich these, then verify them before outreach and carry over opt-out status, so a new number doesn't reset someone's choice not to be contacted.
  • Current title and employer: Write them to their own fields and confirm them in conversation, because a provider can lag behind a job change or match the wrong person.
  • Location: Enrich it, then ask about relocation rather than assume, since a new city doesn't tell you where someone would work.
  • Skills and work history: Add provider data alongside the resume and never overwrite it.
  • Resume and application answers: Keep these exactly as the candidate submitted them.
  • Consent, opt-outs and notes: Enrichment never changes these, because a provider can't know what a candidate agreed to or what came up on a call.
  • Protected characteristics: Leave age, race, religion, disability and similar traits out of every run, and don't infer them from other fields.

Ways to run ATS data enrichment

You can run ATS data enrichment inside the ATS, through a connected provider, through your own scripts, by file, or by hand. The right route depends on volume and how much control you need over which fields change.

ApproachHow it worksBest forMain limitation
Built-in ATS featureThe ATS enriches records through a partner providerTeams that want little setupOverwrite rules may be hard to adjust
Marketplace integrationA provider connects through the ATS marketplace and writes to mapped fieldsOngoing enrichment at moderate volumeMapping options vary
Enrichment APIYour scripts or middleware call a provider and write results backTeams with technical supportNeeds development time and upkeep
Batch file export and re-importYou export records and enrich the file before importing itOne-off cleanups of a segmentImports can overwrite good fields
Manual updates during outreachRecruiters correct records as they contact peopleSmall pools and priority candidatesSlow and uneven across a team

Integration and application programming interface (API) routes need the most planning because you decide where provider fields land. Check what your system supports and how ATS integrations work. If you're building your own pipeline, look at what a person data API returns and how it reports match confidence.

A batch run cleans an entire segment on a schedule or before a search, which suits a talent pool you're about to reactivate. Enrichment on create fills in new records as they're added. On-demand enrichment updates one record when a recruiter opens it, which ties cost to active work.

Check matches and field mapping before you write back

Run a careful test on a defined segment and sample before anything touches live records.

  • Start with a defined segment: Pick one role family or a talent pool you plan to search soon, rather than the whole database.
  • Deduplicate first: Two copies of one person double the cost and can end up with conflicting values, and the steps for merging duplicate records apply in an ATS too.
  • Match on strong keys: A personal email or profile URL makes a reliable match, while name plus employer can point to the wrong person, so route those to a recruiter.
  • Map fields and keep the originals: Write enriched values to separate fields, not over candidate-supplied ones.
  • Record the source and date: Store which provider supplied each value and when — the same habit behind good CRM hygiene — so recruiters know when to refresh it.
  • Test on a small sample: Include records you know are correct, and review the mismatches before approving the full run.
  • Verify emails before outreach: Enriched addresses can bounce or belong to someone else, so check each lookup before sending.

Consider an agency recruiter who enriches a talent pool and finds that a strong candidate now works at one of the agency's clients. Before reaching out, the recruiter checks the client's off-limits terms, then confirms the new job in conversation. In-house recruiters don't face that conflict, though they may want to know when someone has rejoined the company.

Start with candidates who shared their own details

Book a demo

Retention, deletion and privacy rules for applicant records

Enrichment projects often turn into cleanups, where recordkeeping and privacy rules come into play.

Federal recordkeeping rules from the U.S. Equal Employment Opportunity Commission (EEOC) require employers to keep all personnel or employment records for one year. Once a charge is filed, employers must keep those records until the charge or any related lawsuit is finally resolved. Confirm your retention policy before a cleanup removes old records, and at an agency, check client requirements too.

In a July 2023 announcement, California's Attorney General said covered businesses have had to apply California Consumer Privacy Act (CCPA) protections to employee data since January 1, 2023. The inquiry covered employees' and job applicants' personal information. It noted that businesses must handle requests to access, delete, and opt out of the sale and sharing of personal information.

Recording which provider supplied each field helps you respond to access or deletion requests. It also lets the next run skip anyone who asked you to delete their data. What the CCPA requires of your business specifically is a question for counsel.

How to choose an enrichment tool or integration

When comparing enrichment tools, how each writes data back into your ATS matters as much as how many matches it finds.

  • Supported integration: It writes into your ATS through a supported connection rather than a manual re-import.
  • Field-mapping control: You choose which provider field lands in which ATS field, including custom fields.
  • Overwrite rules: You can pick never overwrite, overwrite blanks only, or overwrite all, and start with the most cautious setting.
  • Source and date: Each enriched value carries the provider's name and the date it was supplied.
  • Matching keys: It shows which keys it matched on and flags uncertain matches.
  • Email verification: It verifies the emails it returns rather than only finding them.
  • Deletion and opt-out handling: It respects your opt-out and deletion lists, so removed data stays removed.
  • Audit log: A change log lets you undo a bad batch.
  • Pricing model: Compare per-record pricing, credits, and seats against how many records you'll enrich and how often.

Test a shortlisted tool on records you know are correct to measure its match accuracy. Then weigh the results against your enrichment buying criteria.

How to tell whether an enrichment run worked

Compare a sample of records before and after the run, then track outreach results.

  • Bounce rate: Compare bounces on enriched addresses with the addresses they replaced.
  • Confirmed current employer: Track the share of sampled records where a recruiter confirmed the employer in conversation.
  • Reactivation replies: Watch whether candidates respond to messages about new roles.
  • Duplicates created: New duplicates suggest weak matching.
  • Complaints and opt-outs: Note anyone who asks where you got their details.

If replies stay low even when contact details check out, review the message and timing before paying for another run. Updating records during outreach, as part of steady talent pool management, can reduce how often you need a large batch job.

Check your field rules before a batch run

Enrichment changes records your whole team relies on, so field, matching, and retention decisions matter as much as the provider. Before your next batch run, write down which fields a provider may update and how each value will be labeled. A test on one small segment shows where those rules need adjusting.

Check whether you need to enrich at all

Book a demo

Frequently asked questions

Can you enrich candidates who applied years ago?

You can, though older records carry a higher chance of a wrong match or of contacting someone who no longer expects to hear from you. Check consent, opt-out status and your retention policy first.

Does ATS data enrichment replace asking candidates to update their profiles?

No. Enrichment gives you a provider's best match, while a candidate's own update gives you details you can rely on. The first conversation after enrichment is a natural point to ask them to confirm what's on file.

About the author

Mihailo Bozic
Mihailo Bozic

Founder & CEO @ Rotto

Founder & CEO of Rotto, building tools that help tech recruiters source better candidates, faster.

Related articles

Rotto

Built for recruiters who work from a brief, not a boolean.

rotto.com