Skip to main content

How Pay Gap Analysis Works in Evenpay

Learn how Evenpay calculates unadjusted and adjusted pay gaps, what pay factors are used, how comparison levels work, and how to read your analysis results.

Evenpay calculates two pay gap metrics: the unadjusted (raw) gap and the adjusted gap. Understanding the difference between them — and knowing what drives each one — is the foundation of effective pay equity work. This article explains how the analysis works, what the numbers mean, and what to pay attention to when reading your results.

Two Types of Pay Gap

Every pay equity analysis in Evenpay produces two numbers. They tell you different things, and both matter.

Unadjusted (raw) pay gap — the straightforward difference in average pay between men and women. No explanation of why the gap exists — just the number. This is the figure required for EU Pay Transparency Directive reporting.

Adjusted pay gap — the portion of the gap that remains after controlling for legitimate pay factors like job grade, experience, and education. This is the number that tells you what actually needs investigating.

Metric

What it tells you

Example

Unadjusted gap

Overall average pay difference between genders

"Women earn 12% less than men"

Adjusted gap

Unexplained difference after controlling for legitimate factors

"After accounting for job grade, experience, and tenure, women earn 4% less"

A raw gap of 12% might sound alarming — but if 8 percentage points are explained by differences in job grade, experience, and tenure, the unexplained gap is 4%. That 4% is what requires action. The adjusted gap separates the signal from the noise.

How the Unadjusted Gap Is Calculated

Evenpay uses both mean-based and median-based calculations depending on the context. The right formula depends on what you're comparing:

Comparison level

Formula used

Why

Overall organization gap

Mean-based

Standard EU directive formula

Grade-based gaps

Median-based

Less sensitive to extreme salary outliers

Job level, org unit, job family, position

Mean-based

Standard comparison

Historical / regulatory reporting

Both

Full picture across time

A statistical significance test (t-test) is run for all gaps to confirm whether the observed difference is real or could be due to chance.

Comparison Levels

Evenpay calculates unadjusted pay gaps at five levels. Each serves a different purpose — use them together for a complete picture.

Level

What it compares

Best used for

Grade-based (primary)

Employees in the same grade — work of equal value

EU directive reporting and headline gap figures

Job level

Employees at the same job level

Diagnostics within a grade

Organization unit

Employees in the same department

Finding where gaps are concentrated

Job family

Employees in the same function

Gaps by function, e.g. Engineering vs. Sales

Position

Employees in the same specific role

Most granular, role-level view

Grade-based gaps are the most important for compliance purposes. Job levels are mapped to grades to define what "work of equal value" means in your organization — for example, IC3, M2, and P2 might all map to the same grade.

How the Adjusted Gap Is Calculated

The adjusted gap uses the Blinder-Oaxaca decomposition — an internationally recognized standard for pay equity analysis. It works in three steps.

Step 1: Salary transformation

Salaries are log-transformed before analysis. This is standard practice in labor economics because salary differences are proportional (percentage-based), not absolute. It also means the model's outputs can be read directly as approximate percentage effects.

Step 2: Regression model

Evenpay runs a multiple regression using your enabled pay factors — job grade, experience, tenure, and so on — to model how salaries are distributed across the organization. Gender is deliberately not included in the model. It's only used afterwards to compare outcomes between groups.

Step 3: Decomposition

The total pay gap is split into two parts:

  • Explained portion — differences accounted for by your pay factors (e.g., men are on average in higher job grades)

  • Unexplained portion — the remaining difference that can't be attributed to legitimate factors. This is the adjusted gap, and it's what requires action.

The decomposition trains three separate models — one on men, one on women, and a pooled reference on all employees — to calculate explained and unexplained portions fairly.

Good to know: Factor contributions can be negative. If women in your organization have more experience on average than men, experience actually counteracts the gap rather than contributing to it.

What's Driving the Gap: Factor Contributions

Beyond the overall split between explained and unexplained, Evenpay uses Shapley values to show exactly how much each individual factor contributes to the difference between the raw and adjusted gap.

Think of it this way: if your raw gap is 12% and your adjusted gap is 4%, something accounts for that 8 percentage point difference. The factor contribution breakdown tells you how much of that 8pp comes from job grade, how much from experience, how much from education, and so on. The values always sum to the total adjustment, giving you a complete and consistent breakdown.

This is where the analysis becomes actionable — you can see exactly which structural differences in your workforce are explaining pay differences, and decide whether each one is a genuine business reason or something worth addressing.

The Factor Statistics panel shows each pay factor's coefficient, p-value, impact on the gap, and data quality rating:

Pay Factors

Organizations choose which factors count as legitimate pay determinants through the Pay Philosophy settings in Evenpay. Each factor can be independently enabled or disabled. Only enable factors that genuinely drive pay decisions in your organization.

Factor

Type

What it captures

Example values

Job Grade

Ordinal

Level in the job structure — usually the strongest predictor of pay

IC1, IC2, Senior, Lead, Principal

Experience

Continuous

Years of total professional experience

3, 7, 12 (years)

Tenure

Continuous

Time with the organization

1, 4, 8 (years)

Skills

Continuous

Skill count or aggregated skill score

5, 12, 20 (skills)

Skill Fit

Continuous

Match between employee skills and position requirements

60%, 85%, 100%

Education

Ordinal

Highest education level achieved

Bachelor's, Master's, PhD

Certifications

Continuous

Number of professional certifications

0, 2, 5

Certification Fit

Continuous

Match between certifications and position requirements

50%, 75%, 100%

Work Location

Categorical

Employee's work arrangement

Remote, Hybrid, On-site

Organization Unit

Categorical

Department or division (opt-in)

Engineering, Sales, Finance

Job Family

Categorical

Functional role grouping (opt-in)

Software Engineering, Customer Success

Performance

Continuous

Weighted average of recent performance reviews

1–5 scale, e.g. 3.2, 4.8

You can also add custom factors based on your organization's own fields if your compensation philosophy includes criteria beyond the defaults.

Categorical factors (like organization unit and job family) are encoded as separate comparison groups in the model. Small categories are automatically merged to keep the model stable. Continuous and ordinal factors go directly into the regression. If a factor has too much missing data, it's automatically disabled for that analysis run — you'll see which factors were excluded and why.

Salary Configuration

You control exactly what goes into the salary figure used for analysis:

  • Salary components — choose which parts of compensation to include (base salary, bonuses, allowances, etc.)

  • Session overrides — adjust component selection for a specific analysis without changing your org-wide defaults

  • Normalization — all salaries are converted to a common monthly basis. Annual salaries are divided by 12; hourly rates are converted using contracted hours

  • FTE adjustment — salaries are adjusted for full-time equivalence before analysis so part-time and full-time employees are compared fairly

Employees with zero or invalid salary data are automatically excluded. Evenpay supports two salary modes: Agreed salary (current contractual salary — the default for standard reporting) and Historical salary (for tracking how gaps evolve over time using stored snapshots).

Analysis Modes

Evenpay offers two modes depending on how much context you want to bring into the analysis.

Statistical Mode (default) — Pure Blinder-Oaxaca regression based on your data and enabled pay factors only. No manual adjustments. This is the right mode for standard compliance reporting — it gives you a clean, objective baseline.

Justification-Aware Mode — This mode incorporates documented justifications: approved business reasons for individual pay differences recorded by managers or HR. The system adjusts salaries by justified amounts before running the regression, then shows what gap remains after both statistical factors and documented reasons are accounted for. It tracks documentation coverage, addressed vs. unaddressed gaps, and overall compliance readiness.

Here's how that looks in practice. Say you have an employee whose salary sits above the expected range for their level, contributing to the pay gap. Once you document a justified business reason — for example, a specialized certification — that amount shifts from unexplained to explained:

Before justification

After documenting a certification

Raw gap

−12.5%

−12.5% (unchanged)

Explained by factors

7.8%

7.8%

Explained by justifications

2.1%

Unexplained gap

−4.7%

−2.6%

The raw gap never changes — it's always the real number. What changes is how much of it is accounted for.

At the grade level, Evenpay also calculates a justification-adjusted gap: the raw gap minus documented justifications, floored at zero. This gives you a combined operational view that's useful for tracking remediation progress over time.

Alert Thresholds

Evenpay flags gaps automatically at configurable severity levels: low, medium, high, and critical. You set the percentage thresholds for each level and define the minimum group sizes required for a comparison to be flagged. This means you're always aware of the most pressing issues without having to check the analysis manually.

Understanding Your Model Quality

Every analysis includes quality indicators so you can assess how reliable the results are. You don't need to be a statistician to use these — the key question is simply: does this model explain pay well enough to trust the adjusted gap?

The model quality panel is accessible by expanding Show model transparency at the bottom of your analysis results:

This opens the full Model Performance breakdown:

Metric

What it tells you

What to look for

R² (R-squared)

How much of salary variation the model explains

≥ 0.70 is strong. ≥ 0.50 is acceptable. Below 0.50 means important factors may be missing from your pay philosophy.

Adjusted R²

R² corrected for the number of factors used

Prevents inflated scores when many factors are enabled with a small employee population

p-value

Whether the model's fit is statistically significant

Below 0.05 means the results are unlikely to be due to chance

F-statistic

Overall explanatory power of the model

Higher is better. Read together with the p-value for the full picture.

Max VIF

Whether factors overlap too much with each other

Above 5 is a moderate concern. Above 10 means some factors may be redundant and could be removed.

Obs / PIF Ratio

Whether you have enough data for the number of factors enabled

At least 10 employees per factor is recommended for reliable results

Each individual factor also reports its own coefficient, significance level, and confidence interval — so you can see exactly which factors are carrying weight in the model and which are not.

If your R² is low, the most common cause is a missing factor. Job grade is almost always the biggest driver of pay — if it's not included or not assigned consistently, the model won't explain much.

Data Requirements

For the analysis to run, you need:

  • A minimum number of employees with valid salary data

  • At least one employee of each gender

  • For the full Blinder-Oaxaca decomposition: each gender group needs more employees than the number of enabled pay-influencing factors plus one

If you don't have enough data for the full decomposition, Evenpay will tell you why and continue with the prediction model alone. Factors with too much missing data are automatically disabled for that run — you'll always see which factors were excluded and how many employees were omitted from the analysis.

Compliance and Certification

Evenpay's methodology is designed to meet and exceed the requirements of the FPI Universal Fair Pay Check, which requires an adjusted gender pay gap calculation based on multiple regression using the Oaxaca-Blinder method. FPI does not prescribe a specific formula, transformation, or variable set — Evenpay's approach is fully compatible.

For the EU Pay Transparency Directive, Evenpay supports the required reporting on gender pay gaps and comparison of pay between workers doing the same work or work of equal value. The adjusted analysis is an additional method that supports deeper investigation of underlying drivers.

Features like factor contribution attribution, cost-to-fix estimation, model diagnostics, and justification-aware analysis are Evenpay's own analytical enhancements that go beyond what any standard or directive requires.

Next Steps

Now that you understand how the analysis works, here's where to go next:

  • Configure your pay factors — go to Settings → Pay Philosophy and enable the factors that reflect how pay is determined in your organization

  • Check data completeness — make sure all employees have a job level assigned and valid salary data. These two gaps account for most analysis exclusions.

  • Run your first analysis — navigate to Pay Equity Analysis and start a new session

  • Investigate flagged gaps — use the factor contribution view to understand what's driving them, and decide whether each driver is justified or needs to be addressed

Frequently Asked Questions

Which number should I focus on — the unadjusted or adjusted gap?

Both, but for different purposes. The unadjusted gap is required for EU Pay Transparency Directive reporting and gives you the headline number. The adjusted gap tells you what actually needs to be addressed — it's the part of the gap that your legitimate pay factors can't explain. If your adjusted gap is close to zero, your pay structure is working equitably. If it's significant, that's where to focus.

What if my adjusted gap is higher than my unadjusted gap?

This can happen. It means that your pay factors are actually masking a larger underlying gap — for example, if women in your organization tend to be in higher job grades on average than men at similar pay levels. It's unusual but not impossible, and it's important information worth investigating.

My R² is below 0.50. What should I do?

A low R² usually means the model is missing an important factor. The first thing to check is whether job grade is enabled and whether all employees have a job level assigned — it's almost always the strongest predictor. After that, consider whether experience, performance, or another factor is genuinely driving pay in your organization and isn't yet reflected in the model.

When should I use Justification-Aware Mode vs. Statistical Mode?

Use Statistical Mode for compliance reporting — it gives you a clean, objective baseline with no manual inputs. Use Justification-Aware Mode when you've already documented business reasons for specific pay differences and want to see what gap remains after those justifications are accounted for. It's particularly useful for tracking progress as you document and address gaps over time.

How do I reduce my adjusted gap?

There are two levers. The first is to address actual pay inequities — reviewing and correcting salaries where the gap is unjustified. The second is to improve data completeness: if key factors like job grade, experience, or performance are missing for many employees, the model can't explain pay differences that are actually justified, which inflates the adjusted gap. Start by checking factor coverage and fixing data gaps before making pay adjustments.

Why are some employees excluded from my analysis?

Employees are excluded when they're missing data the analysis requires: no salary on record, no gender assigned, or no job level. You'll always see a count of excluded employees and the specific reason for each. The two most common gaps are missing job levels and missing salary data — fixing those will maximize your analysis coverage.

Did this answer your question?