How to Handle Duplicate Job Applications and Reapplicants

Handle duplicate applications by matching on email, phone and name, merging them into one candidate record, keeping the most recent CV and the full history, and replying once. For reapplicants and people who apply to many jobs, review the earlier outcome first, then apply a written policy on waiting periods and what has changed.

Three situations that look similar but are not

A duplicate is the same person applying to the same job more than once, often by mistake, from two devices or after an error message. A multi-job applicant is one person applying to several of your open jobs at once, which can be a sign of interest or of a broad search. A reapplicant is someone who applied before, was rejected or withdrew, and applies again later, to the same or a different job. Each needs a different response. Mixing them up causes problems: you might reject a good candidate twice, send two contradictory replies, or interview someone you rejected last month without noticing. Start by deciding which of the three you are looking at, and make sure your records can tell you. There is a fourth case worth naming: the candidate who has been referred or sourced by you and then also applies through the advert. Here the application should join the existing record, and the source should be noted accurately, because it affects reporting and, for agencies, fees. A fifth case is the internal applicant, who may need a different process and a conversation with their manager. Clear definitions let you handle each case with a short, consistent routine rather than a new debate each time.

How to detect duplicates

Match on several fields, not one. Email address is the strongest single signal, but people use more than one. Phone number, full name, and a link to a profile also help. Normalise the data before comparing: ignore capital letters, spaces and punctuation, compare the last digits of phone numbers, and watch for common name variants and typing errors. Look at the CV text and employment history for strong overlap. Treat a possible match as something to confirm, not as proof, since two people can share a name, and family members can share an email address or phone. Agree who confirms a match and what evidence is enough, and record the decision in the candidate record. Build a simple routine for the times you cannot rely on software. Sort or search your list by email domain and surname, scan for near matches, and check any pair that looks similar. Compare dates, because two applications minutes apart for the same job usually mean an accident. Compare CV text length and the first lines. Keep a list of known shared inboxes and family addresses to avoid false matches. If you handle high volumes, schedule a clean-up before each report so counts are accurate.

How to merge without losing information

When you confirm a duplicate, keep one record. Retain the most recent CV, but do not delete the older one if it contains different information, because the changes can be useful. Keep the dates of each application, the source, any notes and any scores. If the duplicates came in with different answers to screening questions, keep both sets and note which is current. Send one acknowledgement, not two. Check that no one else on the team is working the second record, to avoid separate emails and interviews. If candidates applied through different channels, such as an agency and directly, check your agreements about who holds the relationship, and ask for advice if there is any dispute. Write a short merge rule so that anyone on the team does it the same way: keep the earliest created date as the first application date; keep the most recent CV as the current one; store older CVs as attachments; combine notes in date order and mark them with their source; and record who merged and why. If your tool lets you undo a merge, use that for any case you are not sure about. Never merge records where you are only guessing at identity, and tell the candidate if you are unsure which application they wish you to consider.

Multi-job applicants: choose the best fit, tell the candidate

If a candidate applies to several of your jobs, look at all applications together. Decide which role fits best against the must-haves, and make sure only one recruiter owns the conversation. Tell the candidate you have seen their other applications, and which one you want to discuss. If they might fit more than one, say so. Avoid running separate processes that make contradictory offers or interview the same person three times in a week. Equally, do not assume that applying widely means a lack of interest: some applicants simply read the list of openings and applied to the ones that match. Treat each application against its own must-haves, and record the outcomes for each. If a candidate is a strong fit for two roles, tell both hiring managers and agree who interviews first, so the person has one clear path and one contact. Record the decision in the shared record so nobody repeats the conversation.

Reapplicants: a written policy

Decide a policy before the question arises. A common approach has four parts. First, always look at the earlier record: why were they rejected and what stage did they reach? Second, set a waiting period for the same role, for example a few months, or no waiting period if the candidate can show something relevant has changed, such as new experience or qualification. Third, allow applications for a different job at any time, assessed on its own must-haves. Fourth, treat past silver medalists differently from earlier rejections for conduct. Apply the policy equally to everyone. Do not let a past rejection by one person become a permanent bar without a reason, and do not bar people on grounds connected to protected characteristics. Add a short template for the reply to a reapplicant who is not yet eligible: Thank you for applying again. We last reviewed your application for this role on [date], and our policy is to wait [period] before reconsidering. If your experience has changed in a way that is relevant to the must-haves, please reply with details and we will take another look. We would also welcome an application for a different role that matches your skills. Keep it kind and specific, and make the waiting period reflect a real reason, such as the time it takes for experience to change.

A worked example

An invented case. Priya applies for Accounts Assistant on Monday, then again on Tuesday after her browser crashed. The system flags a match on email and phone. The recruiter confirms, merges the records, keeps the Tuesday CV because it adds a certification, and sends one acknowledgement. Three months later Priya applies for Finance Analyst. The record shows she reached the second interview for the earlier role and scored well, but another candidate had more systems experience. The recruiter reviews her scores against the new must-haves and invites her to a phone screen, mentioning that her earlier application was a close one. Another applicant, Tom, applies for the same role he was rejected for last month. Under the written policy, he is asked what has changed, and since nothing has, he receives a polite reply suggesting he reapply after the waiting period. A last situation arises when two recruiters in the same team both reply to a multi-job applicant on the same day. To avoid it, assign one owner as soon as a link between applications is found, and make the owner responsible for the single message to the candidate. The other recruiter adds their notes to the shared record and steps back. This small rule prevents the common experience of a candidate receiving two conflicting emails and wondering whether the company is organised.

Replying fairly and keeping data rules

Reply to every applicant once, and do not send automated rejections to a duplicate that you have merged into an active application. Use the same tone for reapplicants as for first-timers, and give a reason where you can. Personal data rules matter here: how long you may keep a rejected candidate's data, whether you need consent to keep it for future roles, and whether candidates can ask to see or delete it differ by country. Check local rules and your retention policy, and tell candidates how you use their data. Do not use a past application to make decisions based on information you no longer have a lawful basis to keep. When a reapplicant asks why they were not progressed last time, share the reason you can support from the record, in neutral terms, and what would strengthen a future application. Avoid giving detailed comparisons with other candidates. If you hold interview notes, remember that candidates may have rights to request their personal data in some places, so keep notes factual and professional. Delete data on schedule, and record when you did it.

Common mistakes

Merging two different people because they share a name or an address. Deleting the older record and losing its history. Replying twice with different messages. Rejecting a good reapplicant because the previous recruiter did not like them, with no reason recorded. Having no policy, so decisions depend on who handles the application. Failing to spot a candidate who applies to many jobs and then interviewing them separately for each. Spending hours on manual checks when your records could flag matches. Counting duplicates in your funnel numbers, which inflates applications and lowers your apparent conversion rates. Clean the data before you report. Also watch for the opposite problem: treating every duplicate as a spam signal and blocking people who may be applying from a different device or after correcting a mistake. Another error is to let different hiring managers interview the same person for different jobs without knowing, which wastes the candidate's time and may produce inconsistent feedback. Share a single candidate record, keep notes visible to authorised colleagues, and use one point of contact for the person across all applications.

Checklist

Have you matched on email, phone and name? Have you confirmed before merging? Do you keep the history, dates and notes? Is there one owner and one reply for each person? Have you looked at all open applications from the same candidate? Does a written reapplicant policy exist, with waiting periods and a way to show what has changed? Have you checked local data retention rules? Have you cleaned duplicates before you report numbers? Finally, review the routine twice a year. Count how many duplicates you merged, how many reapplicants you invited back and whether the waiting period still makes sense, and adjust the policy where the evidence suggests it. A short note of the changes keeps everyone aligned.

In Rezumz

In Rezumz, duplicate detection works across jobs, so when the same person applies to more than one of your jobs, you can see it and review the applications together. The candidate record keeps the history, notes, scores and emails. CVs are ranked against the must-haves for each job in the job workspace. Rezumz does not decide your reapplicant policy or merge people without you, and people make each decision.