
When the Average Lies to You
The quarterly board report says your facility's RN turnover is 14.2%. That is below the national staff RN average of 17.6% reported in the 2026 NSI National Health Care Retention & RN Staffing Report. A reasonable CNO might read that number and move on.
But the 14.2% is a weighted average of eight nursing units. Somewhere inside that average — perhaps the ICU, perhaps the overnight med-surg shift — a single unit is running at 31%. Two experienced RNs left in Q1 and a third gave notice last week. The average absorbed those departures quietly. The board report did not surface them.
This is the central problem with facility-wide turnover reporting: aggregation hides variance, and variance is where the real retention risk lives. The NSI 2026 data illustrates just how wide that variance can run — RN turnover by hospital bed count ranges from 5.6% to 40.0% nationally. If the spread across facility sizes is that large, the spread across units inside a single facility is often just as striking.
This article explains how to move from a single facility-wide number to a unit- and role-level breakdown — what to track, how to weight it correctly, and how to read the result so you know which units to address first.
Why Unit-Level Turnover Is a Different Metric
A facility-wide turnover rate answers the question: What fraction of my total nursing workforce separated in the past twelve months? That is a useful governance number. It is not a useful operational number.
A turnover rate by unit answers a sharper question: Which specific care environments are losing staff faster than I can replace them, and how much is that costing me?
The distinction matters because the causes of turnover are largely unit-specific. A step-down unit running at high census pressure carries different retention dynamics than a same-day surgery unit running a predictable daytime schedule. Pooling them into one number does not just obscure the problem — it can actively mislead resource allocation. If your facility-wide rate looks acceptable, a costly intervention budget is unlikely to flow toward the one unit that urgently needs it.
The NSI 2025 data made this structural point clearly: cumulative five-year RN turnover in step-down, telemetry, and emergency services reached 113%–121%, compared with 77.2% in pediatrics and 77.1% in surgical services (NSI 2025, via Becker's Hospital Review, 2025). Units in the same facility, same employer, same wage structure — diverging by 40+ percentage points over five years. The facility average would never surface that.
The Right Denominator: FTE-Weighted Headcount
Before building a unit-level breakdown, the denominator in your turnover calculation needs to be right. For a unit comparison to be meaningful, each unit's rate must be calculated against its own average FTE-weighted headcount — not against a headcount snapshot taken on one day, and not against budgeted FTEs.
The reason is straightforward: a unit that opens three new positions midyear and fills two of them before year-end has a materially different exposure profile than a unit that ran at a stable eight FTEs all year. If you use beginning-of-year headcount as the denominator for both, the opening unit's rate will look artificially high.
FTE-weighted headcount averages the unit's staffed FTE count across the measurement period — typically each month of a rolling 12-month window. A unit that staffed 10.0 FTEs in January and 12.5 FTEs by December had an average closer to 11.2 FTEs. That 11.2 is the denominator that produces a defensible rate.
For a rolling 12-month window, the formula is:
Unit turnover rate = (Voluntary separations in the past 12 months ÷ Average monthly FTE-weighted headcount) × 100
Run this calculation independently for each unit, not as a share of facility-wide FTEs. Units that share FTEs (float pool nurses who cover multiple units) require an allocation decision — the simplest defensible approach is to allocate a float nurse's FTE proportionally to the units they covered during the period.
Disaggregating by Role: RN vs. LPN/LVN vs. CNA
Once you have unit-level rates, the next layer is role. A unit's turnover rate can look moderate in aggregate while concealing a severe RN-specific problem underneath it.
Consider a 20-FTE med-surg unit: 12 RN FTEs, 5 LPN/LVN FTEs, 3 CNA FTEs. If three RNs left in twelve months and no LPNs or CNAs turned over, the unit-level rate is 15% — just inside the national benchmark. But the RN-specific rate on that unit is 25%. Each of those RN departures carries a modeled cost anchored to the NSI 2026 per-departure figure of $60,090. Three departures: approximately $180,270 in a single year on one unit alone.
Separating the rate by role surfaces this. It also allows the right comparison benchmarks:
- RN turnover benchmarks against the NSI national staff RN rate (17.6% in 2025, per NSI 2026 via Becker's Hospital Review, 2026) and the unit-type cumulative data where available.
- LPN/LVN turnover carries its own cost profile and its own market context. The BLS May 2024 data shows LPN/LVN median annual wages at $62,340, with a wide percentile spread ($47,960 at the 10th percentile to $80,510 at the 90th) — wage-band misalignment is a frequent driver of LPN/LVN departures that may not register in RN-focused retention conversations.
- CNA turnover is structurally the most volatile role in many facilities. AHCA's 2024 State of the Sector Report found 94% of nursing homes reporting difficulty recruiting, with CNA average turnover running at 44.2% (Ziegler CFO Hotline survey, via Skilled Nursing News, July 2025). Even if your facility is not a SNF, CNA retention dynamics affect unit staffing ratios and RN workload.
Tracking turnover by nursing role across each unit produces a role × unit matrix. That matrix is the hotspot map.
Reading the Hotspot Map: Which Units Need Attention First
A role × unit turnover matrix will typically show three kinds of units:
Stable units — turnover at or below benchmark across all roles. These units are worth studying for what is working: scheduling practices, charge nurse tenure, patient census predictability, or team cohesion signals.
Role-specific pressure units — acceptable aggregate turnover but one role running well above benchmark. The med-surg RN example above fits here. The intervention is role-specific: review the RN wage band against the BLS May 2024 regional median for SOC 29-1141, assess scheduling load, and examine whether the RN-to-LPN skill mix is placing disproportionate burden on the RN cohort.
High-pressure units — turnover elevated across multiple roles, typically your highest-acuity or most schedule-volatile environments. Emergency, step-down, and telemetry have historically carried this profile; the NSI 2025 data cited above bears that out. These units warrant a retention risk score that integrates turnover rate, vacancy rate, time-to-fill, and wage-gap signals together — because no single metric tells the full story.
The sequencing principle: address the unit where elevated turnover is both above benchmark and concentrated in the highest per-departure-cost role (RN). The NSI 2026 data puts the cost of each percentage point of RN turnover at approximately $295,000 per average hospital per year. A unit running 10 points above its peer benchmark is not an abstraction — it is a modeled cost exposure that merits a specific response.
Building the Tracking Structure: What You Need in Practice
Translating this into a working tracking structure requires the following data elements, maintained monthly:
- Unit identifier — a consistent label (not "4 North" one month and "Unit 4N" the next) that maps correctly to your payroll system.
- Role classification — RN (SOC 29-1141), LPN/LVN (SOC 29-2061), CNA, and any other nursing roles you track.
- Beginning and ending FTE count per month — to compute the average FTE-weighted denominator.
- Voluntary separations — recorded by unit, role, and month. Involuntary separations are tracked separately and typically excluded from the benchmark-comparable turnover rate.
- Hire date and separation date — to determine tenure at departure, which informs whether the problem is onboarding (early departures), mid-tenure dissatisfaction, or retirement/lateral movement.
Even a well-designed spreadsheet structure can hold this data for a small number of units. The structural limitation of the spreadsheet model surfaces above 20–30 tracked FTEs — cross-unit allocation, role-level aggregation, and rolling 12-month recalculation each month become manual error sources that grow faster than the FTE count. For a facility tracking 80–150+ FTEs across four or more units, the time spent on monthly recalculation is substantial, and the risk of a denominator error silently distorting a unit rate is real.
The RN Turnover Tracker template structures this data model in a format you can populate immediately — unit columns, role rows, monthly FTE and separation inputs, and rolling 12-month rates calculated automatically. It is the right starting point for a facility building this discipline from scratch, or for validating an existing spreadsheet structure against a clean reference model.
From Hotspot to Response
Identifying the hotspot is not the outcome — it is the input to a decision. Once a unit and role register as the highest-risk combination on your matrix, the next questions are causal:
- Is the unit's RN or LPN/LVN wage band below the regional BLS median? A pay band that has drifted below the market's 50th percentile for SOC 29-1141 or 29-2061 is an addressable, quantifiable driver.
- Is time-to-fill for that unit running materially longer than the NSI 2026 national average of 78 days for an experienced RN? Extended vacancy compresses the remaining staff and accelerates secondary departures.
- Is the unit's resignation pattern concentrated in a specific tenure band — say, nurses leaving between 18 and 36 months? That pattern suggests onboarding or development gaps rather than compensation.
The nurse turnover resource hub collects the analytical frameworks for each of these follow-on questions. The purpose of unit- and role-level tracking is to make sure the response is calibrated to the actual problem on the actual unit — not to an averaged facility statistic that was never designed to carry that weight.
Start With One Cohort
If your facility does not currently track turnover at the unit and role level, the practical starting point is not a full build-out across every unit simultaneously. Pick the unit where you already have the strongest intuition that something is off — the one where charge nurses mention team fatigue, where you have had two or three unexpected resignations in the past year, where coverage has required more agency or overtime spend than usual.
Calculate the rolling 12-month turnover rate by role for that one unit, using a clean FTE-weighted denominator. Compare it against the NSI national benchmark. Run the cost model: departures × $60,090 (NSI 2026) gives you a defensible annualized estimate to bring into a budget conversation.
That single calculation — done carefully, with a clean denominator and a sourced benchmark — will do more to shift the retention conversation from reactive to analytical than any facility-wide average has.
The RN Turnover Tracker is structured to make that first calculation straightforward. Download it, populate the inputs for your highest-concern unit, and see what the rolling rate actually says.
Browse our templates: NursingWorkforce.com/store
Run the ROI Calculator: see what turnover is costing you
Join the Waitlist

