State vs. Metro Wage Benchmarking: Which Should You Use?

The Problem With Averaging Across an Entire State

A Director of Nursing at a community hospital on the outskirts of a major metropolitan area pulls up the state-level RN wage data. The figure looks reasonable — her pay bands are close. She files the spreadsheet away and moves on.

Three months later, two experienced RNs give notice. Both are moving to hospitals fifteen miles away, inside the metro core, where wages are meaningfully higher than the statewide average suggested.

This is the practical cost of choosing the wrong geographic benchmark. State-level data is accurate — BLS produces it carefully — but it is an average across a geography that may span dense urban labor markets, mid-size cities, and rural counties all at once. When your facility sits near a metro boundary, the state average can mask a competitive gap that your nurses see clearly every time they compare job listings.

This article explains how BLS structures its wage geographies, when state-level data is the right tool, and when you need to narrow to the metro level to see your actual competitive position. By the end, you will know which geography to use for your facility and why the distinction matters for pay-band decisions.

How BLS Structures Wage Geography

The Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) program — the source of the median annual RN wage of $93,600 (BLS May 2024) and the LPN/LVN median of $62,340 (BLS May 2024) — publishes wage estimates at three main geographic levels:

National. A single set of figures for the United States as a whole. Useful for sector-wide context; too broad for any pay-band decision.

State. Fifty states plus the District of Columbia and several territories. This is the level most nurse managers encounter first. It captures variation across states — California's mean annual RN wage of approximately $148,330 (BLS OEWS May 2024) illustrates how far state figures can diverge from the national median — but it does not show variation within a state.

Metropolitan and nonmetropolitan areas. BLS divides each state into Metropolitan Statistical Areas (MSAs) — defined by the Office of Management and Budget as a core urban county or counties plus adjacent counties with strong economic ties to the core — and into Balance of State (BOS) areas, which aggregate the nonmetro counties left over after all MSAs are carved out. This is the most granular level the OEWS program publishes for most occupations.

For state vs. metro wage benchmarking, the MSA/BOS structure is the critical layer. A large state like Texas or Ohio contains dozens of MSAs, each with its own RN and LPN/LVN wage distribution. The statewide figure is the weighted average of all of them.

When State-Level Data Is the Right Benchmark

State-level benchmarking is appropriate — and often sufficient — in two situations.

Genuinely rural or nonmetro facilities. If your hospital or SNF sits in a BLS Balance of State area, the MSA data simply does not apply to you. Your nurses are not commuting to a metro core for competing offers. The relevant peer comparison is other nonmetro facilities in the same state labor market, and the statewide or BOS-area figure captures that reasonably well. For these facilities, the practical question is whether your pay bands track the statewide median and percentile distribution, not whether they match a distant city's wage schedule.

Initial triage and trend tracking. State-level data updates annually on a consistent schedule and is easy to retrieve. For a first pass — checking whether your RN pay band has fallen more than ten points below the state median over several years, or comparing state-to-state variation when evaluating a multi-facility footprint — state-level figures are a fast, defensible starting point. They are also what the Essentials tier of Nursing Workforce Planner uses for BLS wage benchmarking by default, which is appropriate for facilities whose competitive labor market is genuinely statewide or nonmetro.

When You Need Metro-Level Data

Metro-level benchmarking becomes necessary the moment your nurses can realistically commute to a higher-paying competitor. As a practical rule, if a competing hospital or health system is within reasonable commuting distance and operates in a distinct MSA or metro labor market, your benchmark should be that MSA's wage distribution — not the state average.

Three situations make this concrete:

Facilities inside or adjacent to an MSA. A hospital located within an MSA is, by definition, competing in that metro labor market. The statewide figure will understate the local competitive wage if the MSA skews above the state average — common in states where a single large metro (a major city and its suburbs) pulls the state mean upward but the facilities outside that metro drag it back down. Conversely, a small-market hospital in a state dominated by one expensive metro may find the state figure overstates the local rate. Either way, the MSA figure is the right reference.

Facilities near an MSA boundary. County-level commute data frequently shows that nurses at hospitals in adjacent nonmetro counties accept offers from facilities inside the nearby metro. If your turnover exit surveys (or even informal departure conversations) show nurses citing specific metro-area employers, that MSA's wage schedule is your actual competition.

Multi-facility operators comparing across markets. A regional healthcare system with facilities in three cities, each in a different MSA, cannot use a single statewide benchmark to evaluate whether each facility's pay bands are competitive. Each location competes in its own local labor market. Aggregating to the state level obscures which specific facility carries a wage gap — and which one is overpriced relative to its local market.

For a deeper walkthrough of how to locate and read the relevant BLS OEWS tables, see our guide on how to read BLS OES wage data.

The Wage Gap That State Data Can Hide

The practical risk of using state-level data when a metro benchmark applies is not just analytical imprecision — it produces specific, measurable pay-band errors.

Consider a facility near a major metro where the MSA-level median RN wage sits meaningfully above the statewide median. A nurse manager benchmarking to the state figure concludes her pay bands are near-median. Her nurses, applying to positions online, see job postings from metro-area employers and compare those offer letters to their current wages — not to the state average. The gap they perceive is real. The gap the nurse manager's spreadsheet shows is not.

This is the dynamic that underlies the nurse wage gap and flight risk relationship. The pay-band error is not always large, but it is systematic: it causes facilities on the favorable side of an MSA boundary to consistently underestimate their competitive exposure.

Nursing Workforce Planner's Professional tier and above surface BLS metro-level wage data alongside state-level figures, so a Director of Nursing can see both benchmarks side by side for RNs (SOC 29-1141) and LPNs/LVNs (SOC 29-2061) and apply the appropriate one to each facility's pay bands. The product flags an internal pay band that falls more than ten percentage points below the relevant BLS median as a wage-gap alert — a product threshold designed to make the gap visible before it becomes a resignation.

Choosing the Right Geography: A Simple Decision Rule

The decision does not require judgment calls about every edge case. A workable decision rule:

1. Identify whether your facility's county is inside an MSA or in a Balance of State area. The BLS OEWS geography files map every county to its MSA or BOS designation. This is a one-time lookup.

2. If inside an MSA: use the MSA-level wage data as your primary benchmark. Use the statewide figure only for secondary context or multi-market roll-ups.

3. If in a Balance of State area: use the BOS or statewide figure as your primary benchmark. Check whether the nearest MSA is close enough that commute-based competition applies — if departure conversations point to a specific metro employer, treat that MSA as a secondary benchmark.

4. For multi-facility operators: apply the rule facility by facility. A portfolio benchmark that averages across geographies is a portfolio-level management tool, not a pay-band-setting tool for any individual location.

This structure mirrors how BLS intends the OEWS data to be used and is consistent with the nurse wage benchmarking resource hub guidance we publish for nurse leaders.

Putting It to Work

State vs. metro wage benchmarking is ultimately a question of whether the geography of your benchmark matches the geography of your labor market competition. Getting it right does not require sophisticated analytics — it requires looking up one county-to-MSA mapping and then pulling the right BLS table.

What it does require is that the data be current, applied consistently to the right SOC codes (29-1141 for RNs, 29-2061 for LPNs/LVNs), and compared against your actual internal pay bands — not a rounded memory of what the last salary survey showed.

If you are managing pay bands for a facility near a metro boundary, or for multiple facilities across different markets, the features page outlines how Nursing Workforce Planner surfaces both state and metro benchmarks in a single view, with wage-gap alerts flagged automatically. The pricing page covers which tier includes metro-level data. A 14-day free trial requires no contract — and preventing a single RN departure, at an average cost of approximately $60,090 per departure (NSI 2026 National Health Care Retention & RN Staffing Report, via Becker's Hospital Review, 2026), covers multiple years of the Professional tier ($3,490/year).

For facilities in California, where the statewide RN mean of approximately $148,330 (BLS OEWS May 2024) already sits well above the national median, metro-level variation within the state adds another layer — explored in our California nurse turnover landscape article.

The benchmark you use shapes the pay-band decisions you make. Choosing the right geographic level is the first, and simplest, step toward making sure that benchmark reflects the market your nurses actually see.