---
name: compensation-benchmarking
description: Use when asked to compare an organization's pay against the external market — setting pay ranges, checking if an offer or raise is competitive, building a pay philosophy — distinct from [[job-description-with-uk-gdad-pcf-and-agenda-for-change]], a specific UK public-sector job-evaluation scheme rather than the general market-benchmarking practice covered here.
---

# Compensation Benchmarking

Compensation benchmarking is the practice of comparing what an
organization pays against what the external market pays for comparable
work, so that pay stays competitive enough to hire and retain people
and equitable enough to defend internally. It produces the pay ranges
and reference points that individual offers, raises, and promotions get
checked against — not a one-off comparison done for a single hire.

## Key components

- **Comparable market data** — compensation survey or aggregator data
  matched on role, level, location, and industry together, not on job
  title alone (see below for why this matters).
- **A defined pay philosophy** — a stated target, such as paying at the
  50th percentile of market, or the 75th percentile for a small set of
  hard-to-fill roles, so individual pay decisions have a shared
  reference point instead of being negotiated ad hoc.
- **A regular refresh cadence** — market data reviewed and pay ranges
  updated on a set schedule (commonly annually, more often in fast-
  moving markets or roles), since market rates move and a benchmark
  gathered once goes stale.
- **A defined role-matching method** — a documented way of mapping
  internal roles to external survey benchmarks, so the match is
  repeatable rather than reinvented each time someone asks.
- **Internal equity check** — comparing the resulting ranges against
  what peers in the same role and level are currently paid, so external
  benchmarking doesn't quietly create internal pay gaps.

## Why matching on role, level, location, and industry matters

The same job title can describe very different scope at different
companies — a "Senior Engineer" at one company may carry the scope of a
staff-level role at another, and a title alone says nothing about
whether the company is in the same industry, competing for the same
labor pool, or operating in the same cost-of-living market. Benchmarking
against title alone routinely over- or under-shoots the real market
rate. Matching on role, level, location, and industry together — using
the actual scope of the work, not just what it's called — is what makes
the comparison meaningful. A benchmark built on title alone isn't a
weaker version of a real benchmark; it isn't measuring the same thing.

## Common pitfalls

- **Benchmarked against a job title alone** — matching survey data by
  title without checking that scope and level actually correspond
  produces a pay range for a different job than the one being paid.
- **Stale data never refreshed** — a benchmark gathered once, years
  earlier, gets treated as current even as the market moves, quietly
  drifting the organization out of competitive range without anyone
  noticing until attrition or failed offers make it visible.
- **No consistent pay philosophy** — without a stated target (e.g.
  median, or a specific percentile), individual offers and raises get
  negotiated ad hoc against no shared reference point, producing
  inconsistent and hard-to-defend pay across similar roles.
- **Benchmarking done once at a hiring event** — treating benchmarking
  as a one-time project for a single hire rather than an ongoing
  practice means every subsequent decision reuses an outdated number.
- **Ignoring location or industry differences** — applying one national
  or cross-industry number to roles that actually sit in different
  labor markets misprices some of them in both directions.

## Learn more

- [[job-description]] for the role definition that benchmarking has to
  be matched against — level and scope come from here, not the title.
- [[job-description-with-uk-gdad-pcf-and-agenda-for-change]] for a
  specific UK public-sector job-evaluation scheme, distinct from the
  general market-benchmarking practice described here.
- [[total-rewards-statement]] for communicating the resulting pay
  decision to an employee alongside the rest of their package.
- [[succession-planning]] for another people-management practice that,
  like benchmarking, depends on an honest, current view of roles rather
  than a stale one.