Candidate Outreach Templates for Active Sourcing

What's Included in These Candidate Outreach Templates

Outreach works when the message is short, specific and honest. This Word file gives you 15 templates for every step of active sourcing, grouped by the type of role you are filling:

• Specialists (5): connection request, network message, email, follow-up 1 and follow-up 2.
• Leaders (4): discreet connection request, network message, email and a follow-up with a referral question.
• Frontline roles (2): a short first message and a follow-up written for easy replies.
• All roles (4): a rejection after an interview, a rejection when the role does not fit, a talent pool invitation and a reply to “not now”.

Each template names the channel, the best timing and the length. A rules section at the start covers legal basis, channel, character limits, equal treatment and objections.

Key Features That Save You Time

• Placeholders instead of invented facts. Hook, role, pay and sender are marked in curly braces, so you only write what is true.
• A privacy line in every first contact. If you did not collect the data from the person, Art. 14 GDPR requires information at the latest at first contact.
• Consent text for the talent pool. The invitation states what you store, why, how long and how to withdraw.
• Formal and informal German. The German file offers both address forms for each template.
• Length-checked requests. Both connection requests stay under 200 characters.

How to Use These Candidate Outreach Templates

1. Pick the role type and copy the first template.
2. Write one sentence about the person that they would recognise as accurate (the {Hook}). Use only public, professional facts.
3. Replace every placeholder and delete what does not apply, such as a pay range you cannot share.
4. Send the follow-ups on the suggested rhythm and stop after two.
5. Use the rejection and talent pool texts to keep people who fit later, with their consent.

Why These Candidate Outreach Templates Work

They ask for one small step, tell the person who is writing and why, and make saying no easy. That last point matters for trust and for compliance: anyone who objects or declines is not contacted again. For the legal side of the approach, see our guide to active sourcing under the GDPR.

In our conversations with recruitment agencies and recruiting teams, double outreach is a real problem when several people write to the same candidate. Keep contact status in one place, whatever tool you use.

Who Should Use This

• Recruiters and sourcers who write many first messages.
• Recruitment agency partners who need a discreet tone for leadership searches.
• HR teams who hire frontline roles and need very short texts.
• Anyone building a first talent pool who wants a consent text that holds up.

If you want to see how outreach and sourcing can run in one place, read about active sourcing with AI.

A Worked Example: From Hook to Follow-Up

Take a specialist role, for example a backend developer. The weakest first message says "We have an exciting opportunity" and nothing else. A message built from the templates has four parts: who you are and why you write, one true sentence about the person (the {Hook}), one small next step, and a privacy line. The hook is the part you cannot template. It might be a public talk, an open-source project or a role change the person announced themselves. If you cannot find a true hook in two minutes, do not send the message.

The follow-ups then add something instead of repeating. The first follow-up gives one new fact about the role, for example the team size or the stack. The second makes saying no easy: "If this is not for you, a short answer is enough and I will not write again." That sentence costs you little and protects the relationship.

Common Mistakes in Candidate Outreach

• Copying the same text to everyone. Candidates recognise mass messages within a line. Change the hook every time.
• Hiding the pay or the employer. If you can share a range, share it. If you cannot name the employer yet, say why.
• Writing five follow-ups. More than two is pressure, not interest. After the second one, stop and log the contact status.
• Using sensitive data as a hook. Age, family, health, origin or religion never belong in a first message. Stick to professional facts.
• Forgetting who already wrote. When several colleagues approach the same person, trust drops fast. Keep one status per candidate in one place.

Channel and Legal Basics in Short

Which channel you use changes the rules. A message in a professional network is a private message to a person who has made their profile visible for professional contact. Email and phone are stricter: in Germany, Section 7 of the UWG limits unsolicited advertising by these channels, and whether a job approach counts depends on the case. On top of that, the GDPR applies whenever you process personal data: you need a legal basis (usually legitimate interest under Art. 6(1)(f), with a written balancing test), you must inform the person under Art. 14, and you must respect an objection under Art. 21 at once. The rules section in the file lists these points as a checklist. It does not replace advice from your data protection officer.

Sources

• Regulation (EU) 2016/679 (GDPR), Art. 6, 14 and 21
• Section 7 UWG, unreasonable harassment
• Section 26 BDSG, data processing for employment purposes

FAQs

Can I copy the templates one to one?

Use them as a draft. Replace the placeholders, add a real hook and check the text against your channel rules and your privacy notice. The templates are not legal advice.

How many follow-ups should I send?

Two. A common rhythm is three to four working days after the first message and another five to seven days after that. After the second follow-up, stop.

Is cold email to candidates allowed?

It depends on country and channel. In Germany, email and phone outreach need a separate check under Section 7 of the UWG on top of the GDPR. A message in a professional network is usually simpler. Check your rules before you send.

Do the templates work in other languages?

The file comes in English and German. The English and German texts are written separately, not translated word for word.

What should I do when someone objects?

Stop contacting the person, record the objection and delete the data you no longer need. Under Art. 21 GDPR an objection to processing based on legitimate interest has to be respected. Do not ask the person to explain.

How long may I keep the contact data of someone who did not answer?

Only as long as you need it for the stated purpose. Set a delete-on date when you first note the contact, for example after the last follow-up plus a short buffer, and write it into your record. If the person agrees to join your talent pool, the consent text defines the new period.

Which channel works best for frontline roles?

Short messages that fit on a phone screen and can be answered with one word. The file's frontline templates are built for that. Test one channel at a time so you know what worked.