Candidate tracking for recruitment agencies: a practical setup guide

Candidate tracking is the process of keeping a person's profile, applications, interview history and next steps connected. For an agency, the useful question is simple: can another recruiter open the record and understand what needs to happen next without searching through chats? This guide gives you a starting structure for that record, whether you use a shared spreadsheet or a recruiting workspace.
Start with one main candidate record
A candidate may have several resume versions and applications, but their contact details should have one main home. Creating a new candidate row for every role makes it harder to tell which details are current. Use a stable candidate ID to connect the profile to applications and interviews.
Before importing a list, review likely duplicates. Two matching names alone do not prove that records belong to the same person. Check the information you already have, review conflicts and keep useful application history when you combine records.
| Field | What to record |
|---|---|
| Candidate ID and name | A stable identifier and the person's preferred name |
| Contact details | Current email, phone and preferred contact method |
| Recruiter owner | One person responsible for the next action |
| Target role and preferences | Role, location, work arrangement and agreed constraints |
| Resume version | The document currently approved for use |
| Last contact and next action | A dated update, task owner and due date |
Keep application status separate from candidate status
A person can be interviewing for one role while waiting for a response to another. A single 'Interview' label on the candidate cannot describe both situations. Create a separate application record for each candidate and role combination.
An application record should include the employer, job title, original posting link, date applied, resume version, stage and next follow-up. Define what each stage means so that two recruiters do not use 'Submitted' differently.
- Saved: the role is worth reviewing, but no application has been sent.
- Applied: the application has been submitted and the submission date recorded.
- Interview: a round is confirmed, with its own date and details.
- Offer: an offer has been received; record the candidate's decision separately.
- Closed: the process ended; note whether the candidate withdrew, was declined or accepted.
Write updates that another recruiter can act on
A note such as 'follow up soon' leaves the next recruiter guessing. Use an action, an owner and a date. Keep the history factual: distinguish a confirmed employer response from an assumption about what might happen.
The example below uses fictional details. Its purpose is to show a record that can survive a handover without a separate explanation.
Use a short daily review and a weekly cleanup
At the start of the day, review overdue follow-ups and interviews coming up next. At the end of the day, update changed stages and add a next action before closing a record. This keeps the tracker useful while the details are still fresh.
Once a week, look for applications with no recent update, missing owners, duplicate profiles and outdated resume references. Ask why a record is blocked before changing its stage. A long wait for employer feedback is different from a recruiter forgetting to follow up.
Know when your spreadsheet needs a different home
A shared spreadsheet can be a reasonable starting point when the team can maintain it consistently. Review the setup when people repeatedly overwrite details, lose application history or need separate copies to work. Those are workflow problems to test in a software demo.
Move a small, representative set of records first. Check that candidate IDs, ownership, application history and resume links survive the move. Agree on a cutover point so your team does not keep two conflicting trackers alive. Decide who needs access to candidate information and how old records will be reviewed.


