Direct answer
For most skilled nursing facilities, an internal float pool is the better default because it usually produces better continuity, cleaner PBJ documentation, and lower long-run labor leakage than agency staffing. CMS still counts both in PBJ, but ePeople helps operators see where agency use is solving a short-term hole versus masking a recurring scheduling problem.
Key takeaways
- Use agency staff for short, sharp gaps such as call-offs, leave coverage, or census spikes you cannot cover internally in time.
- Use an internal float pool when shortages repeat by building, unit, shift, or weekend pattern; that is where continuity and cost control usually improve.
- CMS PBJ requires facilities to report both employee and agency hours, so the question is not whether agency hours count; it is whether they are becoming chronic.
- Recent research found agency hours became more common after the pandemic, but heavier reliance was associated with lower odds of higher star ratings and higher hourly cost.
- A float pool only wins if it is governed tightly; overtime, reporting-time pay, meal and rest break premiums, and cross-building confusion can erase the savings quickly.
What problem does each staffing model actually solve?
Agency staffing solves a speed problem: you have a hole on tonight’s schedule, next weekend’s med pass, or a leave that opened faster than you could recruit. An internal float pool solves a pattern problem: the same unit, building, shift, or weekend keeps missing coverage. CMS requires both employee and agency hours to be reported in PBJ, so the operational question is not whether the hours count. It is whether you are buying a temporary fix or building a repeatable coverage system.
When does agency staffing make more sense for a skilled nursing operator?
Agency coverage is usually the better tool when the gap is sudden, time-limited, and expensive to leave open: an FMLA leave, same-day call-off, isolation surge, or hard-to-fill licensed shift. That is especially true if your internal bench is thin and pulling regular staff would create overtime elsewhere. The caution is that temporary help has become much less temporary in nursing homes. A Health Affairs study using PBJ data found that the share of facilities using agency nursing staff rose from 23% in 2018 to almost half in 2022, and agency hours rose from about 3% to 11% of all direct care nursing hours over the same period.
When does an internal float pool make more sense than agency use?
A float pool makes more sense when the shortage is predictable enough to schedule in advance. If your Friday PM med-cart gap, weekend CNA holes, or cross-building admit surges recur, a pool of trained employees usually gives better handoff quality and less orientation drag than reintroducing agency staff to the same workflows each week. The labor market still matters: BLS reported 2025 median annual wages of $97,550 for registered nurses, $64,400 for LPN/LVNs, and $42,260 for nursing assistants, which helps explain why operators need a structured internal deployment plan instead of simply adding more core FTEs everywhere.
Which model usually costs less after you count premium leakage and vendor markup?
A float pool usually costs less in the long run, but only if you count labor leakage honestly. The same Health Affairs analysis reported agency nursing staff were 50% to 60% more expensive per hour than directly employed staff in 2018 through 2022. That cost gap is why many operators push work internal first. But float pools can leak savings through overtime, missed meal or rest break premiums, split shifts, and second-reporting problems. In California, those risks sit inside IWC Wage Order 5 and the Labor Commissioner’s reporting time pay guidance, so a cheap-looking internal shift can still become an expensive payroll event.
Agency staffing vs internal float pool for SNFs
| Decision factor | Agency staffing | Internal float pool |
|---|---|---|
| Best use case | Unexpected call-offs, leave coverage, short census spikes, hard-to-fill licensed shifts | Recurring gaps by unit, shift, weekend, building, or acuity pattern |
| Up-front speed | Usually faster if a vendor can fill | Slower to build, faster once the pool is established |
| Hourly cost | Often higher because vendor markup sits on top of wages | Usually lower than agency, but can rise with overtime or premium-pay leakage |
| Continuity with residents and workflows | Lower; orientation resets more often | Higher; staff know residents, call trees, charting, and med workflows |
| PBJ documentation | Counts if reported correctly as agency/contract hours | Counts as employee hours with simpler internal validation |
| Survey and quality risk | Can stabilize dangerous holes, but chronic reliance may signal instability | Better if coverage is consistent and competencies stay current |
| Main management burden | Vendor fill rate, credential verification, shift acceptance timing | Cross-training, fairness rules, break coverage, overtime control, multi-building deployment |
| Best operator question | Is this an emergency gap? | Is this the same gap happening again? |
Which model is easier to prove in PBJ and Care Compare?
An internal float pool is usually easier to prove because the worker, time record, and payroll file live inside one operating system. PBJ still accepts agency and contract hours, and CMS explicitly requires facilities to submit both employee and agency staffing information based on payroll or other auditable records. But the more parties involved, the more chances you have for late files, bad job coding, or reconciliation noise. PBJ submissions are due by the 45th calendar day after each fiscal quarter, and CMS can push a facility to the lowest staffing score when staffing data are missing or significantly erroneous in the Five-Star process.
Which model better protects continuity, turnover, and quality?
Internal float pools generally protect continuity better because the same employees return to the same residents, supervisors, and documentation standards. That matters because CMS now publicizes turnover and uses staffing information throughout Care Compare and related measurement programs. In a 2023 JAMA Internal Medicine study covering 1.06 billion shifts and 7.48 million employment relationships, higher turnover within the same nursing home was associated with worse quality outcomes. Separate 2017-2022 national research found that a 10% increase in agency RN, LPN, or CNA hours was associated with a 4% to 5% lower odds of achieving a higher star rating.
What hidden risks show up when a float pool is built badly?
The biggest mistake is treating a float pool as free labor flexibility. It is not. If the pool is not matched to skill, shift start, break windows, and travel time between buildings, operators can create the same instability they were trying to remove. California adds wage-hour exposure when staff are sent home early, called back, or stretched across long unpaid gaps. ePeople should be used here as a control surface, not as legal advice: it can surface the missed break during the shift, show when a second report may trigger extra pay, and separate a true emergency fill from avoidable scheduling churn.
How should a multi-building SNF operator decide unit by unit?
Start with three months of open-shift data and ask four questions. Is the gap licensed or unlicensed? Is it predictable? Is it building-specific? Does moving an employee internally create overtime or premium-pay exposure elsewhere? If the answer is predictable and repeating, build or expand the float pool there first. If the answer is sudden and sporadic, keep agency as the backstop. CMS staffing data are now updated quarterly in the public PBJ files, with Q1 2026 listed as the latest available file on the CMS catalog page as of July 29, 2026, so operators have more current public proof than they used to.
What should ePeople automate whichever model you choose?
The winning workflow is not “agency” or “float pool” by itself. It is a routing system that escalates coverage in the right order: regular staff, trained float, low-risk overtime, then outside agency when the remaining gap is truly unavoidable. ePeople is designed to make that sequence visible. In the source staffing example, it is designed to return roughly 26 hours a week and produce PPD-compliant, audit-ready output, but those internal figures are design intent, not public proof. The public proof to build around is simpler: fewer recurring holes, cleaner PBJ records, and less labor leakage from avoidable last-minute fixes.
Related resources
- Read Nursing Home Sufficient Nursing Staff Under 42 CFR § 483.35 for the federal survey lens on day-to-day coverage proof.
- Use PPD Compliance for Skilled Nursing Facilities to connect schedule decisions to Care Compare exposure.
- Review How to Reduce Overtime in Skilled Nursing Without Creating New Coverage Gaps before expanding a float pool too aggressively.
- Map recurring shortages back to your facility assessment workflow so staffing decisions match resident needs and building reality.
- See the product page for Staffing Perfection if you want shift-routing logic, escalation rules, and audit-ready staffing proof in one workflow.
Frequently asked questions
Short answers to the most common operator questions are below. Each one is written to stand alone so DONs, schedulers, and regional teams can use the section quickly during staffing decisions.
Sources
Primary sources for the comparisons and statistics in this article are linked inline and listed in full below so operators can validate the rule, method, and year behind each number before changing staffing policy.
