Candidate reapplication policy template: waiting periods, several roles at once and old interview notes

A candidate reapplication policy is the written rule for when someone who was rejected, or who withdrew, can be considered again, how many open roles one person can apply to at once, and which records from the earlier process the new reviewers may use. A workable policy sets a waiting period based on the stage the candidate reached, lets people apply to different roles without waiting, and keeps old interview notes away from new interviewers until the new scores are in. As of October 2026, no US federal law sets a waiting period, but federal recordkeeping and anti-retaliation rules, and privacy law if you hire in the EU or UK, limit what you can keep and how you apply it.

Below are the decisions the policy has to make, a copy-ready template, wording for your careers page and rejection emails, and a worked example. The candidate-facing email for someone who applies to several roles at once is in our application acknowledgement email templates, and how to bring back a strong runner-up is covered in what is a silver medalist candidate. This page is the policy that sits behind both.

What should a candidate reapplication policy decide?

Seven decisions, each of which recruiters otherwise make case by case:

1. Waiting periods by the stage the candidate reached and by whether it is the same role or a different one.
2. Exceptions: when the wait is waived (a materially different role, new qualifications, a recruiter or hiring manager invitation).
3. Several applications at once: whether there is a cap, and who owns a candidate who fits more than one opening.
4. Use of prior records: who may see earlier notes and scores, and when.
5. Retention: how far back anyone can look, set by your candidate data retention policy.
6. Communication: what the careers page and rejection emails say about applying again.
7. Consistency and review: who owns the policy, how exceptions are logged, and when it is reviewed.

How long should a rejected candidate wait before reapplying?

Tie the wait to the evidence you already have. A candidate screened out by a knockout question has given you very little information, so a short wait costs nothing. A candidate who completed a final round has given you a lot, and a few months is rarely enough for the reasons behind a no to change. The numbers below are examples to adapt, not a standard.

"Different role" needs a definition, or every reapplication will be argued as different. A practical test: a role counts as different if it has a different job family, a different level, or at least half its scorecard criteria are not on the old role's scorecard.

The candidate reapplication policy template

CANDIDATE REAPPLICATION POLICY
[Company name]   Owner: [Talent acquisition lead]   Effective: [date]
Last reviewed: [date]   Next review: [date]

1. PURPOSE
This policy sets when a candidate who was not hired may be considered
again, how many roles one candidate may apply to at once, and how
records from earlier applications are used.

2. SCOPE
Applies to all external candidates for roles at [Company], including
candidates introduced by agencies. Internal applicants follow
[internal mobility policy].

3. WAITING PERIODS
A candidate who was not selected may reapply for the same role after:
- Screened out on a written requirement: [none once met / X months]
- Recruiter screen: [X] months
- Hiring manager or panel interview: [X] months
- Final round or work sample: [X] months
Candidates may apply to a different role at any time, except after a
final round, when the wait is [X] months.
"Different role" means a different job family, a different level, or
a scorecard where at least half the criteria are new.
Periods run from the date of the rejection message.

4. EXCEPTIONS
The wait is waived when:
- a recruiter or hiring manager invites the candidate to apply;
- the candidate gains a qualification that was the stated reason for
  the earlier decision; or
- the earlier process was closed without a decision.
Every exception is logged on the candidate record with the reason and
the approver's name.

5. SEVERAL APPLICATIONS AT ONCE
A candidate may have up to [3] active applications. When a candidate
fits more than one opening, [the recruiter on the first application]
owns the candidate and agrees with the other recruiters which process
goes first. One screen covers all roles where the criteria overlap.

6. USE OF EARLIER RECORDS
- Recruiters may read earlier notes and scorecards to decide whether
  the reasons for the earlier decision still apply.
- Interviewers do not see earlier scores before they submit their own.
- Evidence from the last [X] months on criteria shared with the new
  role may be reused instead of re-tested, if the hiring manager agrees
  and the same rule is used for every returning candidate.
- Records older than the retention period are not available and are
  not reconstructed from memory.

7. RETENTION
Candidate records are kept and deleted under [Candidate data retention
policy]. A reapplication starts a new retention period for the new
application only.

8. COMMUNICATION
The careers page and rejection messages state the waiting period that
applies, in plain language.

9. CONSISTENCY
Waiting periods and exceptions apply to all candidates in the same way.
No candidate is barred, or given a longer wait, because they raised a
concern about discrimination, harassment or another legal right.

10. QUESTIONS
[Contact name, email]

Can a candidate apply to several open roles at once?

Yes, and the policy should make it work rather than merely allow it. The common failure is three recruiters screening the same person in the same week, or one team rejecting a candidate while another team is about to call. Three rules fix most of it:

• A cap on active applications (three is a common choice) stops scattershot applying without blocking someone who genuinely fits two adjacent roles.
• One owner. The recruiter on the first application owns the candidate and coordinates with the others. The candidate gets one point of contact.
• One screen for overlapping criteria. If two roles share must-haves, screen once and record it so the second recruiter does not repeat it.

Agencies have a version of the same problem across clients: one candidate, several client roles. That is a consent and ownership question as much as a policy one; see how to avoid double submissions for per-role written consent.

Should interviewers see notes from the earlier application?

Recruiters should. Interviewers, mostly not before they score. An earlier "no hire" read just before an interview tends to anchor the new rating, and an earlier "strong yes" does the same in the other direction. The template's approach: the recruiter reads the old record and writes a two-line brief for the new panel ("last time: strong on stakeholder management, gap on SQL depth; please probe SQL"), and the full earlier scorecards are opened after the new scores are submitted.

This only works if the old record is readable. Notes that say "not a fit" are useless a year later; notes written to a structure are not. Our guide to writing candidate notes in your ATS has a section on candidates who resurface for a different role. If your interview notes are produced outside the ATS, for example by a desktop note taker such as Interview Signal that keeps transcripts on the recruiter's own computer, the policy should name the summary that gets pasted into the ATS, because that is all a second recruiter will ever see.

How do retention rules limit what you can look back at?

The reapplication policy cannot promise a longer memory than the retention policy allows. Three rules matter most, as of October 2026:

• US minimum. Employers covered by Title VII must keep "application forms submitted by applicants and other records having to do with hiring" for one year from the date of the record or the personnel action, whichever is later, and keep relevant records until final disposition if a charge is filed (29 CFR 1602.14). Some states and federal contractors have longer minimums, listed in our retention policy template.
• EU and UK maximum. Under the GDPR, personal data must be "kept in a form which permits identification of data subjects for no longer than is necessary" (Regulation (EU) 2016/679, Art. 5(1)(e)). A waiting period longer than your retention period means you will not have the record when the candidate comes back, which is fine as long as the policy says so.
• No retaliation. Title VII makes it unlawful for an employer to discriminate against "applicants for employment" because they opposed an unlawful practice or took part in a charge or investigation (42 U.S.C. 2000e-3(a)). A candidate who complained about the last process must get the same waiting period as everyone else, not a longer one. See what to do about an EEOC charge from a rejected candidate.

This is general information, not legal advice. Check your own obligations with counsel.

Wording for the careers page and rejection emails

Careers page, in the FAQ or application help:

Can I apply again if I was not selected?
Yes. You can apply for a different role at any time. For the same role,
please wait [3] months after a phone screen or [6] months after an
interview. If you have gained a qualification we said was missing, you
can reapply as soon as you have it.

Rejection after an interview:

We will not be moving forward for [Role] this time. You are welcome to
apply for other roles at [Company] whenever one fits, and to apply for
[Role] again from [date].

Reply to a candidate who reapplied before the waiting period ended:

Hi [First name],

Thanks for applying again for [Role]. Because you interviewed for this
role on [date], our policy is to consider a new application from
[date]. We have kept your details [until (date) / under our privacy
notice], and I will look at your application then.

If you are interested in [other open role], you can apply for that now.

[Recruiter name]

A worked example

How to put the policy into use

1. Pick your waiting periods and the definition of "different role", and get the TA lead and two hiring managers to agree them.
2. Check them against your retention schedule so the policy never relies on records you will have deleted.
3. Set up a flag or tag in your ATS for "earliest reapply date" on rejection, if your system supports it, so the check takes seconds.
4. Update the careers page and the rejection templates in the same week.
5. Review the exception log twice a year. Many exceptions for one team usually means the waiting period is wrong for that team, not that the team is ignoring it.

Common mistakes