To avoid contacting the same candidate twice, keep one record and one message history per person, name one owner for every candidate, and check the record before every message: has anyone written to this person in the last 90 days, on any channel, for any role? The 90 days are an example to adjust. In a spreadsheet this check is manual and fails as soon as LinkedIn and email histories drift apart; a recruiting CRM with one inbox per person makes it automatic.
Why does double outreach happen?
In our conversations with agencies and recruiting teams, double outreach is a real problem wherever several people write to the same market. Three causes repeat:
- Several people, several lists. Each recruiter sources into a personal sheet or a personal licence, so nobody sees the other’s contacts.
- Several channels. A LinkedIn message and an email from a different colleague never meet in one history.
- Several roles. A candidate who fits two vacancies gets two pitches within a week.
What does it cost?
A simple example with assumptions you should replace with your own: a team of five sends 400 first messages a month. If 8 % of them go to someone a colleague already contacted in the last quarter, that is 32 duplicates a month. Each duplicate costs a minute or two of writing time, but the real cost is the reply you lose: a candidate who gets two similar pitches from the same company sees a team that does not talk to itself, and may stop answering. Even at a modest assumption, the risk to your employer or agency brand outweighs the writing time.
Which six rules prevent it?
- One record per person. Match on email, then profile URL, before you create a new entry.
- One owner per person. The owner decides on contact; others ask first.
- One history. Every message on every channel is logged on the record.
- A cooling-off period. After a first message, nobody else writes for a set time (90 days as an example, 14 days after a reply that needs follow-up).
- Check before you send. The status “contacted” is visible at the moment of writing, not in a weekly meeting.
- Check before you import. Match new lists against the pool so you do not re-add people who are already in contact.
Spreadsheet or CRM: where does it hold up?
| Requirement | Shared spreadsheet | Recruiting CRM with one inbox per person |
|---|---|---|
| One record per person | By discipline; duplicates creep in | Duplicate check on import and creation |
| Contact history across channels | Typed in by hand, often late | Messages logged on the record |
| Warning before sending | None, you have to look | Warning when someone was already contacted |
| Cooling-off period | Manual date column | Rule or reminder, depending on the tool |
| Contacts outside the system | Only if someone enters them | Only if imported from mailbox or LinkedIn |
The last row is the honest limit of any tool: it only knows what has been logged or imported.
How long should the cooling-off window be, and for whom?
A single number is too blunt. Define the window per situation and write it on the one-page rule sheet:
| Situation | Who may write | Suggested rule (a team decision, not a legal period) |
|---|---|---|
| First message sent, no reply | Owner only | 60 to 90 days before anyone writes again, then one follow-up by the owner |
| Candidate replied or is in a conversation | Owner only | Everyone else waits until the owner closes the conversation |
| Candidate fits a second role | Owner decides | One combined message instead of a second pitch |
| Candidate declined | Nobody, for now | Set a reminder date the candidate agreed to, or do not write again |
| Candidate asked not to be contacted | Nobody | Block on every channel and list; applies to the whole team |
Tools differ in how they enforce this. Vendor documentation we reviewed in November 2026 shows warning windows from about ten days up to six months, and some of them only warn without blocking. A warning is a hint, not a rule: decide the window as a team first, then check that your tool supports it.
What do you do when it has already happened?
Two candidates got near-identical pitches from two colleagues? Let the owner write one short message: apologise for the overlap, name one contact person, and offer to stop. Do not send a second pitch to “fix” it. Then find the gap: was the person on two lists, or was the contact simply not logged? Fix that cause in the rule sheet and note the case in your two-week review.
Which data protection rules apply?
A contact log is personal data too. Under Art. 5 (1) GDPR it has to be accurate, limited to what you need and deleted when the purpose ends. Keep the date, channel and the owner, not a free-text opinion of the person. Delete the log together with the record when the retention period ends; see talent pools and GDPR. For people you found yourself, the information duty under Art. 14 GDPR applies to the first contact.
How do you introduce it in two weeks?
- Days 1 to 3: merge all personal lists into one pool and deduplicate (see from Excel to a recruiting CRM).
- Days 4 to 7: write down the six rules on one page and name owners per role family.
- Days 8 to 10: switch all outreach to the shared history; no sending from personal lists.
- Days 11 to 14: count duplicates in the first batch and adjust the cooling-off period.
How does Sprad handle it?
In Sprad every talent has one inbox: LinkedIn and email run in one thread, including follow-ups, and the system warns you if someone has already contacted the person, a colleague or for another role. Existing contacts from your mailbox or LinkedIn can be imported so the history does not start empty. The Talent Network is the shared pool behind it and is part of the free core; searches and outreach run on credits (as of 29 Oct 2026, source: sprad.io/pricing). Limit: Sprad only knows contacts that happened in the system or were imported. Details on outreach and search are on the people search page; the bigger picture is in what a talent pool is and how to build one.
FAQ
How do I see who has already been contacted?
Look at the record before you write: the last contact date, channel and owner must be visible there. If they are not, the record is incomplete and the process has to log them first.
How long should I wait before contacting someone again?
There is no legal fixed period. Many teams use 60 to 90 days after a first message without a reply and shorter periods after a conversation. Treat the number as a team rule you adjust with data.
Can two colleagues contact the same person for different roles?
Better not independently. Let the owner of the person decide, and combine both roles in one message.
Does double outreach have a data protection side?
Yes: every contact must have a basis and be documented accurately. Repeated unwanted contact also raises objections under Art. 21 GDPR.
How do I avoid duplicates in a spreadsheet?
Use email as a unique key, sort by it before every import and mark “contacted” with date and owner. It works for very small teams; beyond that a shared CRM is safer.
What if a candidate asks not to be contacted again?
Record it on the person, stop all outreach on every channel and delete the data where required; an opt-out must apply to the whole team, not one list.
Jürgen Ulbrich
Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.
