Salary Range Midpoint Explained: Why It Anchors Your Pay Band
Your salary band's midpoint is its anchor to the market median — and the reference point for compa-ratio. Here's how to set it correctly.
Rovaryn Digital · May 12, 2026
The Question Your Employment Attorney Will Ask First
Picture this: you have a Software Developer posting due by end of week, your state requires a salary range in the listing, and your manager just asked you to copy the range from a job board you found via Google. You pause — because you remember that your employment attorney, during last year's handbook review, asked one pointed question: "What methodology did you use to set the midpoint?"
You didn't have a great answer then. You'd prefer to have one now.
The salary range midpoint is the single number that connects your internal pay band to the external labor market. Get it right, and every other number in your band — the minimum, the maximum, and every employee's position within it — has a defensible, documented rationale. Get it wrong, and you have a band that looks reasonable until someone checks it against real wage data.
By the end of this article, you'll know what a salary range midpoint is, how to derive it from Bureau of Labor Statistics data, why it drives your compa-ratio calculation, and what to watch for when one midpoint has to serve a multi-state posting.
What the Salary Range Midpoint Actually Represents
The salary range midpoint is the value at the center of a pay band — arithmetically, it is the average of the band's minimum and maximum. In a well-constructed band, it is also set to equal (or closely approximate) the market median for the role: the wage below which 50% of workers in that occupation and geography earn, as reported by a benchmarking dataset.
Those two things — arithmetic center and market anchor — should be the same number by design. If they are not, your band is either systematically above or below the market, and you need to make that a deliberate, documented choice rather than an accidental one.
A few related terms you'll encounter:
- Market median (50th percentile): the wage below which half the workers in a given occupation and geography earn. The Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) program publishes this figure annually for more than 800 occupations at the national, state, and metropolitan-area level. It is the most widely cited, publicly available, legally defensible anchor for a pay-band midpoint.
- Range spread: how wide the band is, expressed as a percentage of the midpoint (or sometimes the minimum). A 20% spread above and below the midpoint produces a band whose minimum is 80% of the midpoint and whose maximum is 120%. (For a deeper treatment, see our guide to what is range spread.)
- Compa-ratio: an employee's actual salary expressed as a percentage of the band midpoint. A compa-ratio of 1.00 (or 100%) means the employee is paid exactly at the midpoint. Below 1.00 signals below-market positioning; above 1.00 signals above-market.
Understanding these three terms together is what makes the midpoint useful as a management tool rather than just a compliance checkbox.
Why the Midpoint Is the Most Important Number in Your Band
Every other structural element of a pay band is derived from, or measured against, the midpoint.
The minimum and maximum follow from it. Once you decide your midpoint and your target spread, the band's edges are arithmetic. A ±20% spread around a $133,080 midpoint produces a minimum of $106,464 and a maximum of $159,696. Change the midpoint, and both edges shift in lockstep.
Compa-ratio is meaningless without it. The compa-ratio — calculated as an employee's salary divided by the band midpoint — tells you at a glance whether someone is below market (compa-ratio below 1.00), at market (1.00), or above market (above 1.00). That ratio is what HR Directors use to prioritize merit-increase budgets, identify compression risk, and answer the employment-attorney question about pay equity. It cannot exist without a defined, market-anchored midpoint.
Range penetration depends on it. Range penetration measures where an employee sits within the full width of the band — calculated as (salary − minimum) ÷ (maximum − minimum). A tenured senior employee near the top of a band has high range penetration; a newly hired employee near the minimum has low penetration. Both metrics require a correctly set midpoint to be interpreted in context.
Pay-transparency postings reference it, even when they don't name it. When a state pay-transparency law requires you to post a salary range, the range you post is (or should be) your band's minimum-to-maximum. The midpoint is the internal anchor that makes that posted range defensible — not a guess, not a number pulled from a job board, but a documented alignment to a published wage dataset.
For the full picture of how bands are constructed from the ground up, see how to build a salary range.
How to Set a Salary Range Midpoint from BLS OEWS Data
The Bureau of Labor Statistics OEWS program is the standard publicly available source for occupation wage benchmarks. It is free, updated annually, and produced from a sample of approximately 1.1 million establishments covering more than 800 occupations (BLS, May 2025). Here is a straightforward process for using it.
Step 1: Identify the correct SOC code and geography
Every occupation in the OEWS is assigned a Standard Occupational Classification (SOC) code — a six-digit identifier the BLS uses to organize wage data consistently across industries and geographies. Misclassifying a role (using the SOC for a Marketing Manager when you're actually benchmarking a Marketing Coordinator) will anchor your midpoint to the wrong population. For guidance on reading the OEWS percentile table and selecting the right SOC code, see percentile wages explained.
Choose the most specific geography available for your role. National figures are the broadest and most stable; state and metropolitan-area figures are more precise if your workforce is concentrated in one location. For remote roles that draw from a national candidate pool, the national median is a reasonable anchor — document that choice.
Step 2: Pull the median (50th percentile) wage
The OEWS publishes five wage percentiles for each occupation: the 10th, 25th, 50th, 75th, and 90th. The 50th percentile — the median — is the figure you set as your midpoint.
Worked example. For Software Developers (SOC 15-1252), the BLS OOH reports a national median annual wage of $133,080 (BLS OOH, May 2024). Set that as your midpoint.
Always record the dataset name (BLS OEWS or OOH), the SOC code, the geography, and the reference year in your documentation. A midpoint without a data vintage is not auditable.
Step 3: Apply your spread to derive minimum and maximum
Once you have a midpoint, apply your organization's chosen range spread to calculate the band edges.
Worked example (continued). Using a ±20% spread:
- Minimum = $133,080 × 0.80 = $106,464
- Maximum = $133,080 × 1.20 = $159,696
This is arithmetic applied to a sourced anchor — it is a worked example of the method, not a separate BLS statistic. Your actual spread choice will depend on the role's seniority range, your organization's pay philosophy, and any jurisdiction-specific constraints on how wide a posted range may be. (The New Jersey Pay and Benefit Transparency Act, for instance, includes proposed regulations that would limit the spread between minimum and maximum to no more than 60% of the minimum — confirm the current rule with the New Jersey DOL or legal counsel before relying on any spread for a NJ posting.)
Step 4: Document everything
Your methodology file should contain, at minimum: the SOC code and title, the BLS dataset and reference year, the geography selected and the rationale, the median figure used as the midpoint, the spread applied and why, and the date the range was set. That file is what you hand to your employment attorney.
The Midpoint-to-Market Median Relationship Over Time
One important discipline: midpoints require maintenance. The BLS publishes updated OEWS figures annually (the May 2025 reference data was released May 15, 2026 — BLS, 2026); wages in high-demand occupations can shift materially from one release to the next. A midpoint anchored to May 2022 data that has never been updated may now be significantly below the current market median, which means your posted range could be misrepresenting the market to candidates — and your incumbents may be paid below market without your realizing it.
Best practice: schedule a band-review cycle that coincides with the annual OEWS release. When you refresh the midpoint, recalculate the band edges from it, and recheck every employee's compa-ratio against the updated figure. For a visual framework for tracking how bands and employee positions relate, see our pay band visualization guide.
When One Midpoint Is Not Enough: Multi-Location and Remote Roles
A single national median midpoint is straightforward for a single-location role. For remote roles or multi-state organizations, it gets more complicated.
The OEWS publishes state- and metro-level wage figures. A Software Developer median in one metro area may differ materially from another. If you post the same role for candidates in two locations, you have a few documented options:
- Use the national median as the midpoint and document the rationale (national talent pool, location-agnostic pay).
- Post location-specific ranges anchored to the relevant state or metro median, and document each separately.
- Use the higher of the relevant geographic medians as the midpoint, and document the conservative-anchor rationale.
None of these is universally required — but whichever you choose must be documented and applied consistently. For a walk-through of how a single band connects to multiple state posting requirements, the salary range resource hub collects the relevant guides in one place.
Putting It Together: From Midpoint to Defensible Posting
Here is the full chain of reasoning in one place:
- Select the SOC code that most accurately describes the role.
- Pull the 50th-percentile median from BLS OEWS for the relevant geography and reference year (verify the current figure at bls.gov/oes).
- Set that median as your salary range midpoint.
- Apply your organization's chosen range spread to derive the band minimum and maximum.
- Document the SOC code, dataset, reference year, geography, spread, and date.
- Post the resulting minimum-to-maximum as your public salary range.
- Calculate compa-ratio for each incumbent against the midpoint to identify equity and compression issues.
- Schedule a refresh for the next annual OEWS release.
That eight-step chain is the difference between a range you can defend and a range you hope no one challenges.
If you want a structured template for this process — including SOC-code lookup, percentile entry, spread calculation, and a compa-ratio table — the Salary Range Builder Workbook walks through each step in Excel with built-in formulas and a methodology documentation section you can share with counsel.
Stay Current: Get Methodology Updates in Your Inbox
Wage data changes every year. Pay-transparency requirements change faster than that. If you want to know when the next OEWS release updates the figures that anchor your bands — and when a new state law affects how you post them — subscribe to the Salary Range Builder newsletter. We send practical, sourced compensation methodology guidance to HR Managers and People Ops leads who need to stay current without wading through regulatory text on their own.
No spam. Unsubscribe any time. Just the methodology context you need, when it matters.
Get new guides in your inbox
One email when a new article goes live. Unsubscribe with one click.
