Salary bands: what they are and how to build defensible ones
Salary bands are the pay ranges a company commits to for each role and level, usually anchored to market percentiles such as P25, P50 and P75. A band is defensible when it cites its data source and documents every adjustment applied to it.
This page covers what salary bands are, how they differ from salary ranges and pay grades, why pay transparency law makes them unavoidable in 2026, and how salary benchmarking software like Wagelist builds them from public wage data. Build a band for a real role on the right.
Last updated July 2026
- P25
- $0
- P50 · Median
- $0
- P75
- $0
Suggested posted range
Sample benchmarks derived from public wage data (U.S. BLS OES, May 2024). Early-access customers get live, methodology-documented benchmarks.
Get bands for your whole team
Salary band vs salary range vs pay grade
The three terms overlap in everyday HR speech, but they answer different questions. A salary band is the internal commitment, a salary range is usually the external slice of it you publish, and a pay grade is the ladder the bands hang on.
| Term | What it is | Typical use | Example |
|---|---|---|---|
| Salary band | The internal min-to-max pay range for one role at one level, anchored to market percentiles. | Offers, raises, promotion decisions, pay equity reviews. | $165,478 to $267,059 |
| Salary range | The slice of the band you publish externally, for example in a job posting. | Job ads, compliance with posting laws. | $165,000 to $267,000 |
| Pay grade | A step on a company-wide ladder that groups multiple roles of similar scope into one band. | Larger orgs standardizing pay across departments. | Grade 7: IC senior |
Small companies usually skip formal grades and keep one band per role and level. That is enough for compliant postings and consistent offers, and it is the model Wagelist uses. If the grade side of the table is the part you are unsure about, pay grades vs salary bands works through where one ends and the other begins. What you do still need is a consistent definition of each level, which is what a job leveling framework provides. Once you pass roughly 20 people and want the grades formalized across every department, that is salary structure design, and it has its own math for spread, progression and overlap. If you are still choosing a vendor for this, our comparison of compensation management software covers the ten realistic options and who each fits.
Why salary bands matter in 2026
Pay transparency law has turned salary bands from a nice-to-have into infrastructure. The EU Pay Transparency Directive requires member states to transpose its rules by June 2026: applicants get the pay range before the interview, salary history questions are banned, and gender pay gap reporting phases in for larger employers. In the US, states including Colorado, California, New York, Washington, Illinois, Hawaii and Maryland already require a pay range in job postings, and the list keeps growing.
You cannot post a range you do not have. And once ranges are public, candidates and current employees compare them, so an improvised number creates more problems than it solves. Three practical consequences:
The details of who must post what are covered on our guide to salary ranges in job postings.
Anatomy of a salary band
A market-anchored band has three reference points. P25 means 25 percent of market pay for the role sits below that figure, P50 is the median, and P75 means three quarters of the market pays less. Where you aim inside the band is your compensation philosophy: paying at P50 is matching the market, paying at P75 is leading it.
Senior Software Engineer, Tier-1 metro (sample data)
Two more properties matter. Band width is the spread from bottom to top; for salaried roles a P25-to-P75 band typically spans 40 to 60 percent, wide enough to reward growth without a promotion, narrow enough to stay credible in a posting. We go deeper into the tradeoff in how wide a salary range should be. Band overlap is how much adjacent levels share; some overlap is healthy, because a great mid-level hire can out-earn a new senior hire for a while. Bands with no overlap force premature promotions, and bands with near-total overlap make levels meaningless.
How Wagelist builds a defensible band
Wagelist starts from public U.S. Bureau of Labor Statistics Occupational Employment and Wage Statistics percentiles for the closest matching occupation, then applies a documented multiplier for market (US national, Tier-1 metro, Tier-2 metro, Remote US), seniority and company stage. Every multiplier is published, so you can show a candidate, a board or an auditor exactly how the number was produced. That documentation is what makes the band defensible rather than just plausible.
The step-by-step process, from picking a role to publishing a range, is on how to benchmark salaries. If you want to build the process yourself from scratch, our guide on how to create salary bands walks through it manually.
A worked example with real numbers
Take a Senior Software Engineer in a Tier-1 metro (San Francisco, New York, Seattle) at an established SMB. The sample dataset gives US-national base percentiles of $101,000 / $130,500 / $163,000 for software engineers. Applying the documented Tier-1 market multiplier (1.28) and the senior multiplier (1.28) produces:
The posted range is simply the band's P25 and P75 rounded to the nearest $1,000, which is the format posting laws expect: a good-faith range you actually intend to pay within.
Where your bands become a legal disclosure
In a growing list of states, the range you derive from a band is not an internal note, it is a required line in the job posting. If you hire in any of these states, the band is the compliance input. The builder in the hero above (also on the pay band calculator page) produces a posting-ready range for around 60 roles.
California
Pay scale in postings at 15+ employees, plus the separate pay data reporting duty at 100+.
Colorado
One-employee coverage and five required posting disclosures, the strictest law on breadth.
New York
4-employee threshold, a job description requirement, and a separate NYC rule on top.
Washington
Per-applicant statutory damages and private lawsuits, the riskiest law on exposure.
Illinois
Pay scale and benefits at 15+ employees, plus the 14-day promotion notice.
New Jersey
10 employees counted nationwide, a mandatory benefits description, and internal promotion notices.
Massachusetts
25 in-state employees, a two-year cure period, and the annual EEO wage data filing at 100+.
Maryland
No employee threshold at all, plus benefits, other compensation and a three-year record.
Minnesota
30 in-state employees, a starting salary range, and open-ended ranges banned by statute.
Washington DC
One DC employee is the whole threshold, and the fine ladder runs $1,000 to $20,000.
All states
The pay transparency hub: every US posting law, what defensible means, and the compliance math.
Early access
Get defensible bands for your whole team
Wagelist is in early access. Request your spot and we will email you when it opens. Launch pricing starts at $99 per month, self-serve, no annual contract.