Excluding already-contacted candidates in sourcing, and how to avoid duplicate outreach

If you forget to exclude already-contacted candidates, your outreach feels messy

Imagine a candidate gets a LinkedIn message from a recruiter on Monday. Two days later, an almost identical message follows from a colleague at the same agency. That comes across as impersonal, even when both messages were well-intentioned. To the candidate, it feels like nobody actually checked earlier contact moments. That's why preventing duplicate candidate outreach doesn't start with a one-off check afterwards, but right at the beginning of the process.

This kind of experience tends to stick, because recruitment is fundamentally about timing and attention. Candidates sometimes mention it in conversation with colleagues, or share it on LinkedIn as an example of poor coordination. It doesn't need to be a major incident to still cause damage. Anyone who wants to avoid spammy-feeling recruiter messages first needs to get the basics right. Excluding already-contacted candidates then helps keep your outreach calm, logical and credible.

Why excluding already-contacted candidates is a process issue

Duplicate outreach usually doesn't come from one mistake by one recruiter. It happens more often because several people are working the same audience, because there's no shared overview, or because an old list gets reused without checking its current status. This is especially familiar in agency settings. That's why it helps to treat organising candidate contact within a recruitment agency as a fixed team process. That way, ownership, timing and follow-up all stay clear.

Where duplicate outreach actually happens in practice

In practice, things tend to go wrong at a few familiar points. A sourcer opens an old list and doesn't notice someone has already been in contact. A consultant only checks scattered notes, and a colleague relies on memory or old emails. Meanwhile, the LinkedIn conversation history isn't visible anywhere centrally. As a result, the same candidate comes back into view, while nobody immediately sees that a message has already been sent. The problem, then, usually sits in scattered information rather than reluctance.

What you need to record to make excluding already-contacted candidates workable

Keeping a contact history doesn't need to be complicated, but it does need to happen consistently. Without fixed data, excluding people stays guesswork, and the judgement call differs from one colleague to the next. That's why it's smart to record the same core information for every candidate, every time. This way, someone else can pick up the work cleanly, and the odds of duplicate outreach drop considerably.

• Responsible recruiter: this makes clear straight away who owns the contact and the follow-up.
• Date of contact: this shows how recent the approach was.
• Channel: for instance LinkedIn, email or phone, so the context is clear.
• Vacancy or reason for contact: this shows immediately why someone was in view.
• Message type: was it a first approach, a follow-up, or a repeat approach?
• Candidate's reply: no response, interest shown, a rejection, or an agreement to circle back later?
• Next action: this keeps the agreed next step clear at all times.

This foundation works well, because you record enough to make the right calls, without the record-keeping becoming a burden. With already-contacted candidates in the ATS, it's therefore not just about a simple label, but about the explanation behind it. A name with only the status "contacted" says very little if the reason, timing and earlier reply are missing.

One single source for the history prevents confusion

Separate documents only work as long as a single person manages everything. As soon as several recruiters are active in the same market, confusion creeps in fast. That's why you need one central source for statuses, labels, notes and the context of each conversation. We see that managing LinkedIn conversations and contact history becomes far clearer once teams find everything in one and the same place. A colleague can then see immediately what was discussed before, and what the next step should be.

How to build excluding already-contacted candidates into every new search

The best order is actually very simple: check the history first, then search and approach. Excluding candidates from a search should therefore always happen before outreach. Many teams use the term recruitment deduplication for this during sourcing. In plain terms, this simply means the same person doesn't end up unchecked in a new list. This fixed order is exactly what prevents rushed work and delivers a much cleaner shortlist.

A workable process looks like this. You start with the search, check the central history, exclude earlier contacts where it makes sense, review the shortlist, and only then send new messages. After that, you record the outcome and the follow-up neatly. When a team skips this fixed order, duplicate contact often only becomes visible once the second message has already gone out.

Automatic exclusion helps, but agreements are still needed

Automation can save a huge amount of time, as long as everyone works from the same process. Within our software, excluding already-contacted candidates via AI sourcing can help by recognising professionals spoken to before and filtering them out of new search results. This brings real calm right at the start of the sourcing process. Exceptions, of course, remain human work, since a recruiter or team lead always needs to judge whether a renewed approach is genuinely relevant at that specific moment.

Combining sourcing, outreach and follow-up within one and the same working environment helps enormously, because information is far less likely to become scattered as a result. This makes it a lot easier to use excluding already-contacted candidates as a fixed step, rather than an occasional reminder. The real quality, then, isn't hidden in some button, but in how the whole team works together.

Re-approaching without friction: excluding already-contacted candidates isn't a permanent ban

Excluding a candidate obviously doesn't mean they're never relevant again. It simply means you make deliberate choices around timing, reason and content. Approaching a candidate again after an earlier rejection is perfectly fine, as long as something has genuinely changed in the meantime. Think of a different role, a new project, or a previously agreed moment to pick things back up. In that case, don't send an exact repeat of the previous message; instead, briefly explain why this renewed contact makes sense now.

Working agreements for re-approach

Clear timeframes help keep expectations aligned across the team. So treat this timeframe for re-approaching a candidate as a practical working agreement, not a rule carved in stone. The context of the specific candidate always takes priority.

• No response: send at most one personal follow-up after five working days, then wait at least three months.
• Clear rejection for the same role: don't approach that candidate again for around six months.
• Meaningfully different role: a new contact moment can make sense after six to eight weeks, provided you briefly mention and acknowledge the earlier contact.
• Earlier positive reply, but bad timing: follow up on the previously agreed return date, for example after two or three months.

Blindly reactivating old lists without any checks is therefore risky. Always read back first what was sent in the past, what the reply was, and whether a cooling-off period or follow-up action was already planned. This is how a re-approach stays careful, and how you avoid old outreach accidentally going out again.

How excluding already-contacted candidates improves candidate experience in recruitment

Candidates generally respond far better when they notice a team is genuinely aware of earlier contact moments. This builds trust straight away, because the message fits their current situation better and feels far less random. Improving candidate experience in recruitment therefore starts with recognition, good timing, and a clear reason for the contact. For some extra real-world context, take a look at the Vibe Group team case study. It puts seamless collaboration and internal coordination within one organisation front and centre.

Good coordination also helps enormously internally. Recruiters spend less time fixing mistakes, team leads spot exceptions much faster, and new searches start with far more clarity from day one. As a result, the final outreach feels more considered, and the odds of a genuinely relevant reply rise significantly.

Team checklist for checking already-contacted candidates before you start outreach

Feel free to use this checklist for every new sourcing project. This turns the check into a fixed, logical step, rather than something you only do when doubt happens to arise.

• Ownership: is it clear who's responsible for the candidate or the audience?
• History: is the recorded contact history fully up to date and complete?
• Old lists: have all existing lists been carefully checked against the most recent status?
• Earlier messages: have previous messages and the replies that followed been read back carefully?
• Next action: is there already a clear follow-up planned, or is a cooling-off period currently in place?
• Exceptions: are any deviations visible, and have they been consciously assessed by a recruiter or team lead?
• Relevance: is the angle of the new outreach genuinely fresh and appropriate in substance?

Teams who want to redesign their processes, roles and exceptions can talk to us about how to prevent duplicate outreach. From there, we look together at how searching, outreach and follow-up can line up better with each other. This helps the team keep a clearer overview, and means candidates are considerably less likely to be approached twice.

Frequently asked questions

When can you approach a candidate again? That depends entirely on the situation. If you get no reply, one follow-up message after five working days is appropriate, after which you let it rest. After a clear rejection for the same role, it's generally wise to wait around six months. If it's a completely different role, or there was a previous agreement to circle back later, earlier contact can actually be appropriate. In that case, the content of your new message obviously needs to be genuinely fresh.

How do you prevent candidates from being approached twice when several recruiters work the same market? Always work from one central source for contact history, agree clear ownership, and carefully check before every new search who has already been in contact. Make this exclusion a fixed process step, and record any exceptions clearly and visibly. This way, nobody has to rely blindly on scattered notes or a good memory.

What should you record, at a minimum, in a contact history? Record at least who's responsible, when the contact took place, through which specific channel, for which vacancy or reason, what type of message was sent, what the reply was, and what the planned next action is. With this information, a colleague can pick up the process quickly and carefully, without having to start the whole contact from scratch.

When can you put an old candidate list back into use? Only once you've thoroughly checked the current status, read back earlier messages, and verified whether a follow-up action or a cooling-off period had already been agreed. Without that kind of thorough check, the risk of accidental duplicate outreach rises significantly.