The hidden legal risk in your job ads and hiring emails

Recruiting runs on writing: the job ad, the outreach message, the internal note about a candidate, the rejection email. Each one can carry discrimination risk in a single phrase, and the phrases that do it rarely look discriminatory to the person writing them. They read as energy, as culture, as a description of the ideal hire. That is the trap.

Employment law does not require intent to discriminate. A requirement or preference that screens out a protected group, even indirectly, can create exposure on its own. In hiring, the wording is often the act.

The coded phrases that create risk

Most hiring-language risk is indirect. The words do not name a protected characteristic; they stand in for one. These are the common substitutions worth recognizing.

The compliant version is almost always available and stronger: describe the job, not the person. “Digital native” becomes “comfortable with modern tools.” “Native English speaker” becomes “excellent written and spoken English.” “Long hours, no family commitments” becomes the actual requirement, if there is a lawful one. The fix is a phrase, and a phrase is easy to change in a draft.

It is not only the public ad

The ad is the visible risk. The quieter exposure is in the messages around it: an internal note saying a candidate is “probably too senior for the vibe”, an email explaining a rejection in terms that touch a protected ground, a screening message that asks something the law does not allow you to ask. These are written fast, internally, and they are discoverable in exactly the way a discrimination claim needs.

A pre-send check for hiring communication

• The ad and outreach: does any requirement describe the person rather than the job, in a way that maps to age, origin, gender, family status, or disability?
• Internal notes: does any line explain a hiring decision in terms tied to a protected characteristic?
• Screening: does any question ask something a candidate cannot lawfully be required to answer?

Where a pre-send check fits

A pre-send check flags bias-coded language in the compose window, in the job ad, the outreach, and the internal note alike, and offers the job-focused phrasing before the message goes out. It is built for the recruiter writing in good faith who does not realize “young and energetic” is an age signal, not a vibe. It complements the archive that would otherwise preserve the line for a claim. See how this maps to HR and recruitment teams.

The takeaway

In hiring, the wording is the act, and the risk hides in phrases that sound like culture. Describe the job, not the person, and check job ads, outreach, and internal candidate notes before they are sent.