Every recruitment team that works with an Applicant Tracking System for a while sees the same candidates return. Someone who was rejected for a vacancy last year applies again for a new role, sometimes with more experience, sometimes for a completely different position. Without a clear approach one recruiter rejects the candidate automatically because of the old outcome, while a colleague treats the application as if it came from someone new. Both are risky: you lose good candidates, or you repeat a discussion that was already settled. A fixed way of handling returning applicants keeps the assessment fair and the history usable.
The situation differs per segment. Recruitment agencies see candidates return for vacancies at different clients and need to know which client said no and why. Staffing teams work with large flows of applicants who register again after a period away. Secondment organisations regularly reconsider consultants who were not suitable earlier but have since grown. In executive search a candidate who was not chosen for one search assignment can be very relevant for the next. In-house recruitment teams see former applicants return for other departments.
Link the new application to the existing profile
The first step is to recognise that the candidate is already known. When a new application arrives, check for an existing profile by e-mail address, phone number and name, and add the application to that profile instead of creating a second one, as described in merging duplicate candidates. Keep the original candidate source and record the source of the new application separately, so you can later see which channel brought the candidate back.
Look at the earlier rejection reason and date
A previous rejection is information, not a verdict. Check which vacancy it concerned, when it happened and which standardised rejection reason was recorded. A rejection because the candidate lacked a certain level of experience three years ago says little about today. A rejection for another role, at another client or at another location may not be relevant at all. Only a small number of reasons, for example a serious integrity issue that was carefully documented, can justify not proceeding again, and that should be an explicit and agreed decision rather than an individual habit.
Judge the candidate on the new role
Assess the new application against the structured brief and the entry criteria of the current vacancy, not against the old one. Ask the candidate what has changed since the previous application, such as new experience, certificates, availability or preferences, and update the profile accordingly. Use the same screening questions and the same scorecard as for other applicants, so a returning candidate is neither favoured nor disadvantaged.
Agree on a waiting period, if you use one
Some teams agree that a candidate who was rejected after an interview cannot be considered again for the same type of role within a certain period. If you use such a rule, write it down, apply it to everyone and show it on the profile, so that recruiters do not have to search for the earlier outcome. For agencies it also matters whether a client has explicitly asked not to see a candidate again; record that on the client record, next to the off-limits agreement, so it is not forgotten when the candidate returns for another vacancy at the same client.
Respect privacy and retention
You can only use earlier information if you are still allowed to keep it. Check the retention date of the profile and whether the candidate agreed to be kept in the talent pool. If the earlier data should have been removed, do not use it. When a candidate asks what you have recorded about previous applications, the access request process applies. Keep your candidate notes factual and respectful, because they may be read back by the candidate.
Communicate clearly with the candidate
A returning applicant often wonders whether the earlier rejection counts against them. Confirm that the application has been received and explain that it will be assessed on the current vacancy. Keep the candidate informed at every pipeline stage and use shared message templates for the standard steps. You can automate repeated steps such as a task for the vacancy owner when a known candidate applies. Smart suggestions that point out a previous application can be a secondary aid, but the recruiter decides how the candidate is assessed.
A practical start
- Check every new application against existing profiles before creating a record
- Show the earlier vacancy, date and rejection reason on the profile
- Assess returning candidates on the brief and criteria of the current vacancy
- Write down any waiting period or client exclusion and apply it consistently
- Check retention dates and consent before using earlier information
- Review the number of returning applicants and their outcomes in the weekly review
A second chance with context
Candidates who apply again are often motivated and already know your organisation or your clients. With an Applicant Tracking System that links the new application to the existing profile, shows the earlier outcome in context and applies the same criteria to everyone, you give them a fair second chance without losing what you learned the first time. Make returning applicants a regular point in your weekly pipeline review, and when you search your own database first, earlier applicants are often among the strongest matches.