01
The default is to name the employer
A candidate needs the company name to make a basic decision about a recruiting message. It helps them assess the business, the opportunity, and potential conflicts before spending time on a conversation. If the search is not confidential, put the name near the start of your first message, alongside the role and a concrete detail about its scope.
This is a different decision from personalizing outreach. A message can reference someone’s relevant work yet still omit the fact they need most. Naming the company, meanwhile, does not replace a credible reason for contacting that particular person.
- Check with the hiring team or client that the company name and role details are cleared for outreach.
- If the name is public, do not make a call the only way to learn it.
- Do not describe a tactic for generating curiosity as a confidentiality requirement.
02
When is an unnamed employer reasonable?
A genuinely confidential search may involve an unannounced leadership replacement or another hiring plan the employer has not made public. In that case, agree on the disclosure rules before sourcing begins: who can authorize naming the employer, what can be said now, and at what point the name can be shared.
Confidential does not have to mean content-free. Where approved, describe the role’s remit, broad industry, location or work arrangement, and relevant constraints. Check the combination of details, though: individually harmless clues may identify the employer together. If you cannot describe the opportunity well enough for someone to decide whether to continue, reconsider whether outreach should start yet.
- Hypothetical public-search example: “I’m recruiting for Example Works in Chicago. The role leads an operations team and owns a planned expansion into two new markets.”
- Hypothetical confidential-search example: “I’m helping a Midwest manufacturer hire an operations leader. The company has not announced the search, so I can’t name it in an initial message. I can share the approved scope and location in writing, and we would agree on when its identity can be disclosed before any interview with the employer.”
- If the confidentiality terms change, update the outreach instructions rather than relying on an old template.
03
What if the candidate asks, “Which company?”
Answer that question first. If you are permitted to name the employer, do so without a detour. If you are not, say why you cannot, offer the details you can disclose, and identify a meaningful disclosure point. An invitation to “jump on a quick call” is not an answer to a direct question.
Hypothetical response when disclosure is allowed: “Fair question—it’s Example Works. The Chicago role would lead its operations team. I’m happy to send more detail on the scope before we set up a conversation.” Hypothetical confidential response: “I understand why you’d want the company name first. I’m not authorized to share it yet because the search has not been announced. I can send the approved role scope, location, and working arrangements now. If knowing the employer before any further discussion is essential for you, I understand if you’d rather pass.”
- Do not promise the name “soon” unless there is an agreed disclosure step.
- Do not ask for sensitive candidate information in exchange for identifying the employer.
- If the candidate will not proceed without the name, acknowledge that choice instead of repeatedly following up.
04
Make the disclosure decision part of the search brief
Give everyone contacting candidates the same instruction: “May we name the employer in the first message? If not, why not, what details are approved, when can we disclose it, and who approves exceptions?” Review both the initial outreach and a draft reply to “Which company?” against that instruction. This prevents one person’s response from contradicting another’s.
Speiros describes a workflow from role brief through sourcing and candidate conversation, including draft replies for review and a level of supervision set by the hiring team. The disclosure decision should still come from that team. Software cannot determine whether a particular client search is confidential.
- Set the rule before first contact, not after a candidate asks.
- Check that the initial message gives enough approved information to support a decision.
- Revisit the rule when the role becomes public or the employer changes its authorization.