Candidate Data: What It Includes and How Recruiters Use It
What counts as candidate data, six practical ways to use it, and how to collect, update, and protect the records you keep

Every recruiting team builds up candidate data, whether it sits in an applicant tracking system, a CRM, or a set of spreadsheets. Some comes from the candidate, some from recruiters' notes, and some from the hiring process itself.
Candidate data is the information people share with you, the notes and decisions your team adds, and the history your process creates for each person. A clear view of it shapes whom you can find again, how well you match people to roles, and what you must protect.
Key takeaways
- Candidate records include what people share, what your team records, and what your process generates.
- Stage and disposition notes help you find past finalists and see where people leave your process.
- Voluntary self-identification answers belong in a separate store and only in aggregate reports.
- Date every field, review records on a schedule, and ask people to confirm details before you rely on them.
What is candidate data?
Candidate data is any information about a person you're considering for a role, whether they applied, were sourced, or were referred. It ranges from a name and email address to interview feedback, offer details, and the reason someone withdrew.
Most of it lives in the ATS (applicant tracking system), which holds applications and the stages each person moves through. Many teams also use a CRM (candidate relationship management) system to keep in touch with people they want to contact for future roles. On top of those, spreadsheets, shared folders, and email threads hold details that never make it into either system.
When those pieces sit apart, the same person can appear several times with different titles and phone numbers. Pulling the records into one searchable candidate database makes every use described below easier.
Types of candidate data and where each comes from
Candidate records fall into seven broad types, each from a different source and requiring its own caution. The table below shows what each type includes, where it comes from, and what to watch when you record or use it.
| Type | Examples | Where it comes from | Main caution |
|---|---|---|---|
| Contact and identity | Name with email and phone number and location | The candidate or a sourcing search | Confirm details before outreach since they change |
| Profile and experience | Resume with skills and work history | Applications and profiles the person shared | Titles and skills go stale as people move |
| Stated preferences | Role interests and pay expectations plus relocation or work authorization when shared | Conversations and forms the candidate completed | Record only what the person told you and when |
| Process data | Stages and interview feedback plus assessment results and offer details | Your hiring process | Tie feedback to the job requirements |
| Disposition data | Reasons for rejection or withdrawal | Recruiters and hiring managers | Use consistent reason codes so reports make sense |
| Voluntary self-identification | Demographic answers the person chose to give | Optional forms | Store apart from anything used in hiring decisions |
| Consent and communication history | Opt-ins and contact preferences and past messages | Your outreach and the candidate's replies | Respect opt-outs and preferred channels |
The preferences row needs the most care, because the line between what someone told you and what a recruiter assumed is easy to blur. If a candidate once said they'd relocate, that note shows what they wanted then, so ask again before planning around it.
Disposition data is easy to leave blank, yet it records why someone left your process, whether they withdrew, took another offer, or missed a requirement. That reason helps you decide whom to contact first when a similar role opens.
Ways to use candidate data in recruiting
Candidate records help most when they let you find people you already know, match them to openings, and see how your process performs. The graphic shows six uses, each drawing on different parts of those records.
Rediscover past candidates
Rediscovery means searching people who reached late stages in earlier searches before you post a new role. It relies on stage history, interview feedback, and disposition notes, which show who came close and why. Finalists who narrowly missed out, often called silver medalist candidates, are the natural place to begin.
Consider an in-house recruiter opening a role similar to one the team filled last year. Before posting, the recruiter searches last year's finalists, reads their stage and disposition notes, and contacts the ones who asked to hear about future roles. Their circumstances may have changed, so the first message asks whether they're open to a conversation instead of assuming interest.
Match people to new roles
Matching compares the skills, experience, and stated preferences in your records with the job requirements for a new opening. It needs reasonably current profile data and preferences the person gave you, such as location or the kind of work they want.
A skill listed on an old resume may not reflect what someone does today, so treat a match as a reason to reach out and confirm. Weigh nice-to-have skills separately, so a long list of extras doesn't outrank someone who meets every job requirement.
Personalize outreach
Personalized outreach uses what a person shared with you, and when they shared it, to make a message relevant to them. It draws on communication history, stated preferences, and past process notes, such as the role they interviewed for or the team they met.
Mentioning that earlier conversation, and roughly when it happened, tells the person why you're writing now. The same basics of good recruiter outreach still apply: introduce yourself, describe the role, and explain why you're reaching out. Refer only to details the person gave you directly, and leave out anything pieced together from other places.
Find funnel leaks
Funnel analysis uses stage and disposition data to show where candidates leave your process and why. Patterns such as repeated withdrawals after one interview round show up only when stages and reasons are recorded consistently.
A short, shared list of disposition reasons makes those reports readable across recruiters. Standard recruiting funnel metrics then let you compare conversion between stages over time. Small samples can mislead, so look for a pattern across several searches before changing a step in your process.
Check fairness in aggregate
Fairness checks use voluntary self-identification data to see whether people from different groups move through your stages at similar rates. That data stays apart from the records hiring managers and interviewers see, and it appears only in aggregate reports.
The U.S. Equal Employment Opportunity Commission (EEOC) addresses this separation directly. Its guidance on race describes using a mechanism such as tear-off sheets, so race information gathered for affirmative action stays separate from selection information. Tracking pass-through rates with consistent diversity recruiting metrics shows where to look more closely. Never infer anyone's protected characteristics, and never bring self-identification answers into a decision about an individual.
Plan future hiring
Planning uses the skills and experience across your records to show where your pipeline is strong and where it runs thin. It needs consistently tagged profile data, so a skill search finds everyone with that skill, whatever wording their resume used.
Spotting a thin area early gives you time to build relationships before the openings arrive. Ongoing talent pool management keeps those groups of people current between searches. A large pool on paper can include people who have moved on or stopped replying, so base your plans on records someone has confirmed recently.
Ask for what the work needs before you collect more data
Collecting candidate data well means asking only for what the role and your process need, then recording it so you can trust it later.
- Ask for what the work needs: Request information tied to the job requirements and the next step in your process. Extra personal details add privacy risk without helping anyone decide.
- Record it in the person's words: Note what the candidate said, when, and where, such as a screening call or an application form. A dated note in their words is easier to act on than a summary of what they seemed to want.
- Keep self-identification separate: Store voluntary demographic answers apart from the profile and process data your team uses to make decisions.
- Record consent and contact preferences: Note whether the person agreed to hear about future roles and which channel they prefer. Good candidate relationship management depends on those preferences, since they shape every later conversation.
Use opted-in records before you post a new role
Book a demoHow to keep candidate records accurate
Accurate records come from a simple routine: dated fields, regular reviews, merged duplicates, and confirmation from the person. Records age because people change jobs. The BLS tenure release reported a median tenure with a current employer of 4.1 years in January 2026 for U.S. wage and salary workers. A record that's several years old may well name an employer the person has already left.
- Date every field that changes: Store when each contact detail, title, and preference was last confirmed, so readers know how much weight to give it.
- Review on a schedule: Set regular reviews for the records you rely on most, such as recent finalists and people in active talent pools. The right interval depends on your hiring volume and how quickly your market moves.
- Merge duplicates: Combine records for the same person from different recruiters, applications, or imports, keeping the latest confirmed details and the full history.
- Ask the person to confirm: When you reach out, ask whether their details and interests are still accurate, and update the record based on their answer.
Treat candidate data management as a small recurring task, since annual cleanups let errors build up between passes. Shared field standards and deduplication rules, part of basic CRM hygiene, keep the routine consistent when several recruiters edit the same records.
Privacy and retention rules to check
Two sets of rules are worth checking first for U.S. recruiters handling candidate records: state privacy law and federal recordkeeping requirements. Both depend on your business and where your candidates live, so treat this section as a starting point for a conversation with counsel.
California's CCPA (California Consumer Privacy Act) is the clearest example of privacy law that reaches job applicants. The California Privacy Protection Agency's privacy law FAQ says the law covers California residents who are job applicants, and that the employment exemption expired on December 31, 2022. That applies to businesses the CCPA covers, and other states have their own privacy laws worth reviewing.
For retention, EEOC recordkeeping requirements say employers must keep all personnel or employment records for one year, and longer once a charge is filed. The page doesn't name job applications specifically, so ask counsel how the rule applies to your candidate records and how it fits with deletion requests. Agencies have one more step to build in: get the candidate's consent before you share their profile with a client.
How agency and in-house teams use these records differently
Agencies and in-house teams collect similar information but use it differently. An agency may present the same person to many clients over time. Get consent to share a profile with each client, and note in the record which clients have seen it.
In-house teams can reuse past applicants and former employees for their own openings, which makes rediscovery and alumni outreach a sensible first step before posting. On both sides, an accurate communication history helps you improve candidate experience by avoiding repeat questions and messages to people who opted out.
Check what your candidate records hold before the next search
The records you already keep can show who came close last time, what people said they wanted, and where your process loses good applicants. Those uses depend on details that are up to date, kept separate where fairness and the law require, and confirmed with the person. Before your next opening, pick one recent search and read the finalists' stage and disposition notes. Then check whether their details are current enough to contact them this week.
Check opted-in matches before you source from scratch
Book a demoFrequently asked questions
What is a candidate database?
A candidate database is a searchable store of people your team has considered or kept in touch with, along with their profiles, history, and preferences. It can sit inside an ATS, a CRM, or a dedicated system.
How long should you keep candidate records?
Retention depends on the laws that apply to your business, where your candidates live, and your own policy. Federal rules set a minimum for employers, and state privacy laws can add duties around access and deletion, so agree on a written schedule with counsel.
Can you reuse an applicant's details for a different role?
That depends on what the person agreed to when they applied and what your privacy notice says. Asking whether they'd like to be considered before you move them into a new search keeps them informed and confirms their interest.
About the author

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






