Pay transparency job ad checklist for 2026

A pay transparency job ad checklist comes down to seven things: state a real pay range from objective criteria, strip out every salary-history question, use gender-neutral wording in the title and body, name the currency and period, and pick a house standard for cross-border roles by defaulting to the strictest market. These obligations flow from Article 5 of Directive (EU) 2023/970, with national rules applying from 7 June 2026.

This article is practitioner guidance, not legal advice. National implementations differ; confirm specifics for your market with counsel.

What does the directive actually require in a job ad?

Article 5 of Directive (EU) 2023/970, titled “Pay transparency prior to employment,” sets three concrete duties at the hiring stage. First, applicants have the right to information about the initial pay or its range for the position, based on objective, gender-neutral criteria (Article 5(1)(a)). Second, an employer must not ask applicants about their pay history in current or previous employment (Article 5(2)). Third, job vacancy notices and job titles must be gender-neutral, and recruitment must be conducted in a non-discriminatory manner (Article 5(3)).

The directive lets member states decide exactly how pay is communicated, for example in the published advertisement or before the first interview. But the most defensible and least error-prone approach is to put the range in the ad itself. For a country-by-country view of where in-ad disclosure is mandatory versus where pre-interview disclosure suffices, see do job ads need a salary by country in 2026.

The 7-step compliant job ad checklist

Run every vacancy through these steps before it goes live:

1. State the pay range, not a placeholder. Include the initial level or a genuine band, for example EUR 48,000 to EUR 58,000 per year. Name the currency and the period (annual, monthly, or hourly).
2. Build the range from objective criteria. Anchor it to a job-evaluation grade, market data, or an internal pay band, not to what you hope a candidate will accept. Keep a one-line note of how you set it, in case you are asked.
3. Remove every salary-history question. Delete it from the ad, the application form, the screening script, and any recruiter intake template. Article 5(2) makes the question unlawful once your market’s rules are in force.
4. Make the job title gender-neutral. Use “Salesperson” not “Salesman,” “Chef” not “Chef de cuisine (m),” and avoid masculine or feminine inflections where the local language allows a neutral form.
5. Audit the body copy for coded language. Replace “competitive salary,” “aggressive,” “rockstar,” “young and dynamic,” and similar terms. They fail the gender-neutral and non-discriminatory test and read as evasive on pay.
6. List what the range does and does not include. Note whether bonus, commission, allowances, or equity sit on top of the base band, so candidates can have an informed pay discussion.
7. Set the cross-border default. For roles open to multiple countries, apply your strictest-market standard to every version (more on this below).

For the line-by-line copy mechanics behind step 5, including the phrasing recruiters reach for and what to write instead, see competitive salary in job ads under pay transparency.

How do I write a pay range that holds up?

A defensible range is narrow enough to be useful and grounded in something objective. The directive does not fix a maximum width, but a band that spans EUR 30,000 to EUR 90,000 signals you have not done the work and invites challenge. As a practical norm, keep the spread to roughly 15 to 25 percent of the midpoint, and tie the band to a documented basis.

Range basis	Example	Holds up under Article 5?
Job-evaluation grade or internal band	“Grade 4: EUR 52,000 to EUR 60,000”	Yes, this is the strongest basis
External market benchmark	“EUR 50,000 to EUR 58,000, benchmarked to market data”	Yes, if you can show the source
“Competitive” or “market rate”	“Competitive salary”	No, fails the in-ad disclosure duty
“Depending on experience,” no figure	“DOE”	No, gives the applicant no actual information

Two practical points. Tie the band to the role, not the candidate, because pegging pay to who applies is exactly the practice the directive targets. And resist publishing a band wider than you would defend in writing, since the same objective criteria must later justify where in the band a given hire lands.

What exactly counts as a salary-history question?

It is broader than the obvious “What do you earn now?” Article 5(2) bans asking applicants about their pay history in current or previous employment, so the prohibition reaches every wording that backs into the same answer. Treat all of the following as off-limits once your market’s rules apply:

• “What is your current salary?”
• “What were you earning in your last role?”
• A mandatory “current compensation” field on the application form.
• “What are your salary expectations, and what are you on now?”

Asking about a candidate’s salary expectation for the role you are filling is a different question and is generally still acceptable, but keep it cleanly separated from any reference to current or past pay. Before the rules bite, sweep your ATS templates, careers-site forms, and recruiter call scripts, because a banned field buried in an old application form is the most common way teams trip up.

Before and after: a non-compliant ad fixed

Here is a typical opening rewritten to pass the checklist.

Before (non-compliant):

Senior Account Manager (m). Competitive salary, depending on experience. We are looking for a young, hungry sales rockstar to smash targets. Please state your current salary in your application.

This fails on four counts: a gendered title, no pay figure, coded age and gender language, and a salary-history request.

After (compliant):

Senior Account Manager. EUR 55,000 to EUR 65,000 base salary per year, plus uncapped commission, set against our Grade 5 pay band. We are looking for an experienced account manager to grow our enterprise client base. We do not ask for your current or previous pay.

The rewrite states a real range with a documented basis, names what sits on top of base, uses a neutral title and inclusive body copy, and signals the salary-history position explicitly. For the full ad anatomy this draws on, see how the EU pay transparency directive changes job ads.

How should we handle cross-border and remote roles?

Default to the strictest market you are hiring into and apply that single standard to every version of the ad. As of June 2026 only four of the 27 member states (Slovakia, Italy, Lithuania, and Malta) met the 7 June 2026 transposition deadline, the Netherlands has confirmed an implementation date of 1 January 2027, and several others are running late. That patchwork is precisely why a per-country approach is a maintenance trap.

Three reasons to standardise upward rather than tailor down:

1. One template, fewer mistakes. A single compliant format removes the risk of the wrong country variant going live.
2. Direct effect already binds public-sector roles. Even where a state has not transposed, Article 5 can have vertical direct effect against the state and public bodies from 7 June 2026, so public-sector and state-adjacent employers should treat the rules as live now regardless of local law.
3. The trend only tightens. Late-transposing states are catching up, not rolling back, so building to the looser standard means rewriting again within months.

For a vacancy advertised in, say, both Italy (in force) and Germany (no draft published as of June 2026), publishing the range in both is the lower-risk path. Agencies posting on behalf of multiple clients face a sharper version of this; for that angle see the pay transparency directive for recruitment agencies.

How Recruitifly helps

Recruitifly runs posting compliance checks on a vacancy before it goes out: the checker flags a missing or absent pay range, catches vague phrasing such as “competitive salary,” spots gendered titles and coded language, and warns when an application form still carries a salary-history field. The Fly assistant can rewrite a non-compliant draft into a passing version against your internal pay bands, and the Agency Hub lets recruitment agencies apply one house standard across every client posting. You can see the wider toolset on the features page.

Recruitifly is in private beta. If you want a compliant job ad workflow built in rather than bolted on, talk to us and join the beta.