
When Three Spreadsheets Tell Three Different Stories
The monthly workforce review arrives as three separate email attachments — one from the community hospital, one from the rural critical-access site, one from the outpatient surgery center. Each is formatted differently. Each uses a slightly different definition of "vacancy." One facility counts travelers in the denominator; another does not. By the time the regional HR Director reconciles the numbers into a single slide for the CNO, the data is already two weeks old and the underlying signal — which unit, at which facility, is quietly building toward a cluster of resignations — has been averaged into irrelevance.
This is the structural problem at the center of regional health system workforce planning. It is not a people problem. The nurse managers completing those spreadsheets are doing exactly what they were asked to do. The problem is that facility-by-facility reporting was designed for single-site visibility, and somewhere between the second and third site it stops working.
This guide explains how regional HR Directors and CNOs can build a consolidated, comparable view of turnover, wage positioning, and retention risk across a two-to-five-facility system — and what the data infrastructure needs to look like for that view to be useful rather than ceremonial.
Why Multi-Facility Workforce Data Compounds the Single-Facility Problem
A single 120-bed community hospital tracking nurse turnover in a spreadsheet carries a known set of limitations: manual entry, no rolling calculation, no benchmark comparison, no early-warning signal before a resignation letter arrives. Add a second facility and those limitations do not simply double — they interact.
Turnover rates become incomparable if one facility counts per-FTE departures on a calendar-year basis and another uses trailing 12 months. Vacancy figures mean different things if one site includes funded-but-unfilled positions and another counts only active postings. Wage data from three separate payroll exports, each formatted differently, tells you almost nothing about how your system's collective pay bands sit relative to the regional market.
The practical result: regional health system workforce planning conversations at the system level default to narrative rather than measurement. "Our south campus feels tight right now" is a real signal — it just cannot be acted on with the same precision as "our south campus med-surg unit has a 12-month trailing turnover rate of 28%, placing it in the top quartile of the NSI national range for hospitals in its bed-count tier, and two of its three RNs with tenure under 18 months show elevated risk scores."
The 2026 NSI National Health Care Retention & RN Staffing Report found that national staff RN turnover reached 17.6% in 2025 — and that the range by hospital bed count runs from 5.6% to 40.0% (NSI 2026, via Becker's Hospital Review). That spread is the point. Two facilities in the same regional system can sit at opposite ends of that range for reasons that are entirely visible once the data is structured to show them — unit mix, tenure distribution, pay-band position relative to market — but invisible when the data lives in separate files with separate conventions.
The Four Metrics That Must Be Standardized Across Facilities
Effective regional health system workforce planning depends on agreeing, in advance, on a small number of metrics calculated identically at every site. Without that standardization, consolidation is cosmetic.
1. Rolling 12-month turnover rate. The only comparable turnover figure across facilities is calculated the same way: total RN (or LPN/LVN, or CNA) departures in the trailing 12 calendar months divided by the average FTE headcount over that same period, expressed as a percentage. Calendar-year snapshots taken at different points in the year are not comparable. A consistent rolling window, recalculated monthly, is the baseline for cross-facility comparisons and for tracking whether an intervention at one site is actually moving the number.
For a fuller explanation of how turnover rate is defined and calculated by unit and role, see our guide on turnover rate by unit and role.
2. FTE-weighted vacancy rate. Funded positions minus filled FTEs, divided by funded positions, expressed as a percentage — calculated identically at each facility. The 2026 NSI report found an average 8.6% RN vacancy rate nationally, with 43 unfilled RN FTEs on average per hospital and 33.1% of hospitals reporting vacancy rates at or above 10% (NSI 2026, via Becker's). Knowing where each of your facilities sits relative to those benchmarks — on a consistent definition — is more useful than knowing each site's internally-defined "open requisition count."
3. BLS wage percentile position. The BLS May 2024 national median annual RN wage was $93,600, with the 10th percentile below $66,030 and the 90th percentile above $135,320 (BLS Occupational Outlook Handbook, May 2024). For LPN/LVNs, the May 2024 median was $62,340, ranging from below $47,960 at the 10th percentile to above $80,510 at the 90th (BLS OOH, May 2024). Mapping each facility's internal pay bands against those benchmarks — and flagging any role where the facility's midpoint falls materially below the relevant BLS wage percentile — converts a payroll export into a market-positioning signal. This is not a trivial step in a multi-facility system: the facilities may serve the same labor market or overlapping ones, meaning a pay-band gap at one site creates competitive pressure at adjacent sites.
For a deeper look at how HR Directors can use compensation data in this way, see nurse compensation benchmarking for HR Directors.
4. Retention risk by unit and facility. A retention risk score built on observable inputs — tenure distribution, recent departure rate, wage-gap position, vacancy load — gives the regional HR Director a prioritized view without requiring them to read 15 separate unit-level narratives. The value at the system level is triage: which facility, which unit, needs attention first? Without a consistent scoring method applied across all sites, that question gets answered by whoever sends the most urgent email.
What the Reporting Structure Needs to Look Like
A consolidated regional health system workforce planning view is not simply a sum of site-level reports. It requires two layers of visibility operating simultaneously.
System-level summary. One view, updated on the same cycle at every facility, showing: total nursing FTE headcount by facility and role, rolling 12-month turnover rate by facility, current vacancy rate by facility, and BLS wage percentile position for key roles at each site. This is the view the CNO and regional HR Director need for board reporting, budget conversations, and system-level hiring decisions.
Facility-level drill-down. Below the summary, each facility's view by unit: turnover rate, tenure distribution, vacancy load, retention risk score, and 6-month vacancy forecast. This is the view the facility's Director of Nursing needs for staffing decisions and for the monthly conversation with the regional HR Director.
The two layers need to use the same underlying data and the same calculations. A system-level turnover rate that cannot be decomposed into facility-level and unit-level components is a number without a home — you cannot act on it.
The Cost Case for Getting This Right
The cost of elevated turnover in a multi-facility system is not linear. It compounds.
The 2026 NSI report estimated the average annualized RN-turnover cost per hospital at between $4.2M and $6.2M, with a mean of $5.19M (NSI 2026, via Becker's). Across two or three facilities in the same regional system, even with partial overlap in recruiting and onboarding infrastructure, the total is substantial.
To make the arithmetic concrete: the NSI 2026 estimate for cost per RN departure is $60,090. A 100-bed community hospital with 80 employed RNs and a 20% annual turnover rate experiences approximately 16 departures per year — a modeled cost of roughly $961,000 annually on the NSI per-departure figure. A second facility of similar size running at the same rate adds another roughly $961,000. If one of those facilities is running at 28% turnover and the other at 14% — entirely plausible given the NSI's reported 5.6%–40.0% range by bed count — the difference in modeled annual cost between them is material, and visible, once the data is standardized.
These are worked examples built on NSI 2026 figures. The actual cost at any facility depends on role mix, benefit structure, onboarding investment, and agency/travel coverage patterns — verify against your own numbers.
The cost of travel coverage compounds the picture. The 2026 NSI report cited travel RN rates as high as $160 per hour, with an illustrative example showing that replacing 20 travel nurses with employed staff could save $1.32M (NSI 2026 / Kahuna Workforce, 2026). In a regional system where one facility has been covering chronic vacancies with agency staff while a neighboring facility has excess capacity in the same role, the solution may not require external recruiting at all — it requires visibility into both sites simultaneously.
Each additional percentage point of RN turnover costs the average hospital approximately $295,000 per year — NSI 2026 National Health Care Retention & RN Staffing Report, via Becker's Hospital Review, 2026.
That figure is per facility. For a regional system with three facilities, each percentage point of system-wide turnover elevation represents approximately $885,000 in modeled annual cost. The measurement investment required to track and reduce turnover by even a single point across the system is small relative to that figure.
From Spreadsheet Fragmentation to Consolidated Analytics
The path from three disconnected spreadsheets to one consolidated regional workforce view does not require a multi-year enterprise implementation. The practical steps are:
Standardize definitions before consolidating data. Agree on rolling 12-month turnover calculation, funded-position vacancy definition, and FTE counting conventions across all facilities before building any shared reporting. Consolidation on top of inconsistent definitions produces a tidy-looking number that means different things at each site.
Map internal pay bands to BLS benchmarks by role and geography. For each nursing role at each facility, identify the relevant BLS OES wage data for the state or metro area and position the facility's pay bands against the median and key percentiles. This is a one-time exercise that surfaces pay-band gaps that may have gone unnoticed simply because no one compared them to an external benchmark. Our nursing workforce analytics guide covers the mechanics of this in more detail.
Build a retention risk signal that travels across sites. A unit-level risk score — built on tenure distribution, recent departure rate, and wage-gap position — becomes more valuable in a multi-facility system than in a single site. The regional HR Director using it is not trying to manage every unit's day-to-day staffing; they are trying to identify which two or three units across the system need a focused conversation in the next 30 days.
Establish a shared reporting cadence. System-level reporting is only useful if every facility updates its data on the same cycle. Monthly is the standard; more frequent updates are rarely actionable at the system level. The value of the shared cadence is not the data on any single day — it is the ability to see trends moving in the same direction at the same time, which is the earliest warning a multi-facility system has of a systemic problem.
For community hospitals managing these challenges within a single facility, our guide on community hospital nurse retention covers the single-site foundation that multi-facility planning builds on.
What Purpose-Built Analytics Changes
A regional HR Director managing 150 to 400 nursing FTEs across two to five facilities is, in most cases, doing their workforce planning in tools designed for something else. General-purpose spreadsheets are flexible but break down as FTE counts and facility counts grow — the manual entry burden, the version-control problem, and the absence of benchmark data are structural limits, not user errors.
Purpose-built nursing workforce analytics — with multi-facility support, BLS wage benchmarking by state and metro, rolling turnover calculation by unit and role, retention risk scoring, and 6-month vacancy forecasting — is designed for this specific problem. You can review what the platform covers on our features page and how it's priced for systems at different scales on our pricing page.
The Business tier supports up to three facilities (up to 400 nursing FTEs, 25 seats) with multi-facility consolidation, custom alerts, and a travel-nurse ROI calculator. The Enterprise tier supports unlimited facilities. Annual plans include two months at no cost.
The entry question for a regional health system is straightforward: is the current reporting setup giving the CNO and regional HR Director a consistent, comparable view of turnover, wage position, and retention risk across every facility — or is it giving them three spreadsheets that need to be reconciled before every board meeting?
If the answer is the latter, a 14-day free trial is a low-commitment way to see what consolidation looks like in practice.
Wage data cited from the BLS Occupational Outlook Handbook, May 2024 release (public domain). Turnover and cost figures cited from the 2026 NSI National Health Care Retention & RN Staffing Report, via Becker's Hospital Review, 2026. Cost-of-turnover calculations above are worked examples built on NSI benchmarks — verify against your facility's own data before using in budget or board materials.
Browse our templates: NursingWorkforce.com/store
Run the ROI Calculator: see what turnover is costing you
Join the Waitlist

