Pay Rationale Tags
Pay Rationale Tags: How the Logic Works
Pay Rationale Tags let you document the legitimate, gender-neutral reasons why an employee's pay differs from their peers — Senior Experience, Shift Work, Part-Time Arrangement, and so on. Evenpay uses these tags to separate the explained part of a pay gap from the unexplained part that still needs attention.
Tags are applied per employee in the Equal Value Cohorts view, on alert pages, and in the employee's Pay Rationale tab. Every tag maps to an objective criterion from Article 4 of the EU Pay Transparency Directive (skills and qualifications, effort, responsibility, working conditions), so your documentation is built on directive-compliant grounds from the start.
The Core Idea
Every employee is compared against their cohort's median salary. The question Evenpay asks is simple:
This employee earns X% more (or less) than the cohort median — how well is that deviation documented?
Each tag you apply earns points, and the points needed to fully explain a deviation scale with its size. A small deviation needs little evidence; a large one needs more. This is the heart of the logic — and the reason a Minor tag is sometimes enough, while other cases need a Strong tag or several tags combined.
Impact Tiers and Points
When you apply a tag, you choose how much it influences this employee's pay:
Impact | Points | Meaning |
|---|---|---|
Minor | 1 | A small but relevant factor |
Moderate | 2 | A meaningful contributor |
Strong | 3 | A primary, well-evidenced driver |
How Many Points Are Enough?
The points needed to reach 100% explained depend on how far the employee deviates from the cohort median. Bigger gaps demand more evidence:
Deviation from median | Points needed |
|---|---|
Up to 5% | 2 |
Up to 10% | 4 |
Up to 20% | 6 |
Over 20% | 8 |
Explanation strength is simply points ÷ points needed:
- A Strong tag (3 pts) on an employee 4% above median (needs 2) → fully explained.
- The same Strong tag on an employee 12% above median (needs 6) → only 50% explained.
- An employee 25% above median (needs 8 pts) → even Strong + Moderate (5 pts) is 62.5% — you'd need more documented factors to fully explain it.
This is why the same tag moves the bar differently for different employees. The tag isn't worth a fixed percentage — it's evidence weighed against the size of the deviation it has to explain. For partners, the rule of thumb to share with customers: small deviation, light documentation; large deviation, strong and multiple documented reasons.
Partial progress still counts. An employee at 50% strength reduces their contribution to the cohort gap by half — you don't have to reach 100% before the numbers move.
Tags Must Point the Right Direction
Every tag has a direction:
- Higher-pay tags (Senior Experience, Shift Work, Rare Skillset…) explain being above the median.
- Lower-pay tags (Early Career Stage, Part-Time Arrangement, New to Organization…) explain being below the median.
A higher-pay tag applied to a below-median employee earns 0 points — it points the wrong way and doesn't justify the deviation you actually observe. Evenpay shows a "Doesn't apply" hint when this happens, so wasted tags are easy to spot.
Who Actually Moves the Cohort Gap
Explaining an employee's deviation only narrows the cohort's gender pay gap when that employee is driving it. For a cohort where men earn more:
Employee | Tagging them… |
|---|---|
High-paid man | Narrows the gap ✅ |
Low-paid woman | Narrows the gap ✅ |
Low-paid man | Doesn't reduce it ⚠️ |
High-paid woman | Doesn't reduce it ⚠️ |
(When women earn more, every direction flips.)
The employee list reflects this: gap-driving employees are sorted on top by impact, and the rest are grouped under a divider ("employees not driving the pay gap"). Tagging below the divider still documents that employee's pay — useful for transparency — but it won't reduce the cohort's unexplained gap. Guide customers to work top-down: the highest-leverage employees are always first.
How the Numbers Move
When an employee's deviation is (partly) explained, Evenpay recalculates the cohort gap as if their salary sat proportionally closer to the median, then recomputes the standard EU mean-based gender gap. The result is shown in the Gap Rationalization bar:
Original gap
− explained by rationales (justified, on current pay)
− closed by pay changes (simulated raises / pay-equity tasks)
= remaining unexplained gap
The two levers are always reported separately: rationale tags explain part of today's gap, while pay changes (from a scenario or pay-equity task) close part of what's left. A simulated raise never reduces the rationale an employee needs — rationales are always evaluated on current pay.
Worked example. A cohort has a 25% gap. One man earns 40% above the median (needs 8 points). You apply a Strong "Shift Work" tag (3 pts) → 37.5% strength → his salary is treated as 37.5% closer to the median → the cohort gap drops from 25% to 20%. The card shows 5.0pp explained.
Good to Know
Smart suggestions — Evenpay reads employee data (experience, tenure, performance ratings, location, working hours…) and suggests tags with a recommended impact tier and a reason, e.g. "12 years experience vs cohort median 5". Suggestions can auto-apply, land as drafts, or stay as suggestions, depending on your settings.
Draft tags don't count — only applied tags earn points. Scenario tags are previews until the scenario is activated.
Cohort changes trigger review — if the Work of Equal Value definition changes after a tag was applied, the tag is flagged for re-confirmation under the new cohort.
Rationalization cap — organizations can cap how many percentage points of an employee's gap rationales may cover. With a cap, reaching the points threshold still counts as "as explained as possible".
Custom tags — beyond the 30+ built-in tags across seven categories (Experience, Performance, Qualifications, Responsibilities, Market, Conditions, Contractual), you can create organization-specific tags with their own direction and EU criteria mapping.
Updated on: 12/06/2026
Thank you!