National vs. State vs. Metro Wage Data: Which Should You Benchmark Against?
The benchmark geography you pick quietly sets every salary decision you'll make
Picture this: you're an HR generalist at a 90-person professional-services firm headquartered in Denver. You're building a pay band for a Senior Financial Analyst role and you pull BLS OEWS national data. The all-occupation annual mean wage for the entire U.S. sits at $69,770 — a useful orientation point, but the Denver–Aurora–Lakewood metro market for that specific occupation tells a materially different story. Set your band midpoint on the national figure and you may be offering a range that looks reasonable in a spreadsheet and consistently loses candidates at offer stage.
The reverse trap is just as real. A small manufacturer in rural Ohio that anchors every band to the Columbus metro median will build pay ranges it cannot sustain for roles that don't actually compete in that market.
Geographic salary benchmarking is not about picking the highest number. It is about picking the number that reflects the actual labor market your roles compete in — which varies by role, by hire location, and sometimes by whether candidates can work remotely. This article walks you through how the BLS geographic tiers work, when to use each one, and how to apply a simple decision rule so you stop second-guessing the geography call every time you open a band.
How BLS OEWS geographic tiers are structured
The Occupational Employment and Wage Statistics program — the most widely used free source of US wage benchmarks — publishes estimates at three distinct geographic levels.
National. A single estimate covering all US employment in an occupation, regardless of where workers are located. Because it aggregates millions of survey responses across every cost-of-living environment in the country, the national figure smooths out the extremes. It is the most statistically stable estimate (largest sample, smallest margin of error) and the right starting point when you have no other anchor.
State. Estimates broken out by all 50 states plus DC and several territories. State figures sit between the national average and metro-level precision. They are particularly useful when a role is distributed across a state but not concentrated in one metro, or when you are comparing your pay program to a state-level pay-equity standard.
Metro and nonmetro area. OEWS produces wage estimates for approximately 530 areas — a mix of metropolitan statistical areas (MSAs), metropolitan divisions within large metros, and nonmetropolitan "balance of state" areas that cover the rural portions of each state not captured by an MSA. This is where you get true local-market precision for competitive roles in defined geographies.
Across all three tiers, the program covers roughly 830 occupations. For a full walkthrough of how to navigate OEWS tables and read the underlying percentile columns, see the BLS OEWS benchmarking guide and how to read wage percentiles.
When national wage data is the right call
National data earns its place in three specific situations.
1. The role is fully remote with a dispersed candidate pool. If you are hiring a software engineer who can sit anywhere in the country, the relevant labor market is national. No single metro or state defines your competition. Using national data is not a compromise — it is accurate. (For a deeper treatment of how remote work reshapes geographic benchmarking, see remote work pay bands.)
2. Sample sizes at lower geographies are too thin to trust. OEWS flags estimates when the sample is not statistically reliable. For uncommon occupations in small states or rural areas, the metro or state estimate may carry a suppression flag — meaning BLS did not release it at all, or the confidence interval is too wide to be actionable. In those cases, stepping up to the national figure is not a defeat; it is the statistically appropriate move.
3. You need a cross-geography anchor for internal equity. When you have employees in five states doing the same job, you need a single reference point for internal comparisons before you layer in geographic differentials. National data provides that anchor. You can then apply location adjustments on top, rather than managing five independent band structures.
A practical caution: the national all-occupation mean wage of $69,770 (May 2025 OEWS release) tells you very little on its own. You need the national median (the 50th percentile) for the specific occupation code — not the all-occupation average — as your actual midpoint anchor. The all-occupation figure is a useful orientation, not a benchmark.
When state wage data bridges the gap
State data is underused. Most HR generalists jump straight from national to metro, but state-level estimates are the right tier in several common situations.
Roles hired across a whole state, outside a single metro. A regional logistics coordinator who might work from any of a dozen mid-sized cities in Texas is not a Dallas metro hire or a Houston metro hire — they are a Texas hire. State data reflects that dispersed competitive reality more accurately than any single metro.
Pay-equity and transparency compliance. Several pay-transparency laws reference compensation relative to the role's location without specifying metro precision. If you are documenting your good-faith pay range methodology for a California or Colorado compliance audit, state-level OEWS data is a defensible and commonly cited reference — especially for roles that are not location-specific within that state. (Review your specific obligations with employment counsel before finalizing your methodology.)
A cross-check on metro estimates. When a metro estimate looks surprisingly high or low relative to the national figure, comparing it to the state estimate helps you determine whether the divergence reflects a genuine local market premium or a thin-sample artifact. If the state figure sits closer to the national figure than the metro figure does, flag the metro estimate for a closer look before using it.
When metro area wage data is the right call
Metro data is the right default for any role where the hire location is fixed and the metro has a large enough workforce to produce a reliable OEWS estimate.
The intuition is straightforward: if a candidate must commute to your Chicago office five days a week, they are comparing your offer to other Chicago employers — not to employers in Peoria or in Baton Rouge. Using national data for a fixed-location role in a high-cost metro means you are systematically underpricing relative to the relevant competition.
The practical test is simple. Open the OEWS metro-area tables for your target occupation and location. If the estimate is available and not flagged as unreliable, use it as your primary geographic benchmark. If it is suppressed or unreliable, step up to state data; if state data is also unreliable, step up to national. This cascading approach — metro first, then state, then national — is the standard practice for location-based pay benchmarking.
One nuance worth tracking: OEWS metro definitions follow the Office of Management and Budget's Metropolitan Statistical Area boundaries, which are periodically revised. A boundary change can shift which counties fall inside your metro's estimate. If your wage data looks meaningfully different from one survey year to the next, check whether the OMB definition changed before concluding that the market moved.
A decision rule for choosing your geographic tier
Rather than making a case-by-case judgment under pressure every time you build a band, you can codify a simple rule in your compensation framework:
- Identify the hire location type for the role. Is it fixed-site (office or facility), hybrid with a defined home metro, or fully remote with no location constraint?
- Fixed-site or hybrid: Use metro data if a reliable estimate exists. Step up to state if it does not. Step up to national if state is also unreliable.
- Fully remote, US-wide: Use national data. If the role is remote but limited to a specific state, use state data.
- Multi-location or distributed across a state: Use state data as the primary reference; flag roles in high-cost metros for a metro premium review.
Document this rule in your job band structure so that every future band-builder — including whoever takes over the HR function after you — applies the same logic. An undocumented geographic methodology is a liability the moment you face a pay-equity review or a transparency compliance audit.
For a complete treatment of how geographic decisions fit into your broader compensation architecture, see the job band structure complete guide.
A note on Canadian benchmarking geography
Canadian employers have an equivalent tiered structure through Statistics Canada's NOC-based wage data (Table 14-10-0417-01), which provides wage percentiles broken out by province and by Census Metropolitan Area. The logic mirrors OEWS: province is the equivalent of the US state tier; CMA is the equivalent of the US metro tier. As with OEWS, smaller CMAs and less common NOC codes may produce less reliable estimates, and stepping up to the provincial figure is the appropriate fallback.
For a full walkthrough of the Statistics Canada source, see Statistics Canada NOC benchmarking.
Stop letting geography be an afterthought
The geography call is made — consciously or not — the moment you open a wage table. Making it consciously, with a documented rule, changes the quality of every band you build. National data is not lazy; it is correct for remote roles and thin-sample occupations. Metro data is not extravagant; it is accurate for fixed-site roles in major labor markets. State data is the underrated middle tier that fits more roles than most HR practitioners use it for.
The most common geographic benchmarking error is not choosing the wrong tier — it is applying a single tier uniformly to every role in the company, regardless of where or how each role competes for talent.
If you are building or rebuilding your compensation bands and want to apply this tiered approach without maintaining a tangle of OEWS downloads, Job Band Builder structures BLS OEWS and Statistics Canada data by occupation and geography so you can pull the right benchmark at the right tier for each role. Start a free trial at app.jobbands.com/signup and build your first geographically accurate band in under an hour. ```
Ready to go beyond the guide?
Build a defensible, BLS-benchmarked band structure in under 30 minutes.