
The budget request that lands in February
The finance office sends the template in the fall, and it looks simple. For each nursing unit, list budgeted FTEs and budgeted labor dollars for the coming fiscal year. The med-surg manager opens last year's file, sees the same number she has defended for three cycles, and realizes she cannot say where it came from. Census has drifted. A new orthopedic service line has changed the mix next door. Two budgeted positions have been vacant so long that nobody counts them anymore.
A budget rolled forward from last year's FTEs is easy to submit and hard to defend. The CFO's first question is "what is this based on," and "what we had" does not survive a second meeting.
The method that does survive is short and entirely arithmetic: project census, set target hours per patient day, and convert those hours into FTEs and then dollars, one unit at a time.
By the end, you will be able to turn one unit's projected census and target HPPD into budgeted FTEs and annual labor cost, with every assumption visible to the reviewer.
By the end of this article, you will be able to take one unit's projected census and target HPPD and produce budgeted FTEs and annual labor cost, with each assumption visible to the person reviewing it.
What a nursing labor budget HPPD calculation measures
Hours per patient day, or HPPD, is the number of nursing care hours a unit budgets for each patient day. Divide total worked nursing hours in a period by total patient days in that period and you have the unit's HPPD. Run the same equation forward and you have a budget: projected patient days times target HPPD equals the nursing hours you need to buy.
A nursing labor budget built on HPPD ties dollars to volume. If census rises, the hours rise with it. If acuity warrants a richer skill mix or a higher target, the change is one visible input rather than a negotiation over a lump sum.
Two clarifications keep the method honest. First, the target is yours. It reflects your unit's acuity, layout, skill mix, and any state ratio floors. We state no outside HPPD benchmark here, because a national figure says little about your 24-bed unit. Set the target from your own history and document the reasoning.
Second, HPPD describes hours, not heads. Hours become heads only after you account for the productive hours one FTE really delivers, which is where many first budgets quietly go wrong.
Step one: project average daily census
Everything downstream scales with census, so spend your effort here. Use average daily census for the budget year, not the number of licensed beds and not last Tuesday's midnight count.
Start with the trailing twelve months of actual average daily census and adjust for known changes: a service line opening or closing, a seasonal pattern in your own history, or a planned bed change. Write each adjustment down with its reason, so a reviewer can see that census moved because of a specific program, not optimism.
Then multiply average daily census by 365 for annual patient days. For a unit averaging 24 patients, that is 8,760 patient days.
Step two: set the target hours per patient day
Now choose the target HPPD for the unit. For this walkthrough, we will use a round example of 8.0 hours per patient day. It is an illustration chosen for easy arithmetic, not a recommendation and not a benchmark. Your own number will differ by unit type, acuity, and skill mix.
In nursing labor budget HPPD terms, annual nursing hours required are patient days times target HPPD. With 8,760 patient days and a target of 8.0, the unit needs 70,080 worked nursing hours for the year.
If you set targets by role, run steps three and four once per role and add the results. If you use a single blended target, keep the blended hourly cost consistent with it.
Where your state sets ratio floors, treat the ratio as a constraint that the HPPD target must satisfy at every shift, not as an average that works out over the day. California's Title 22 CCR §70217, for example, sets ratios that must hold on every shift, including meal breaks. A target that looks adequate on an annual average can still leave a night shift below a legal floor, so confirm current requirements with your state agency.
Step three: convert worked hours into budgeted FTEs
An FTE is paid for 2,080 hours a year, but an FTE does not deliver 2,080 hours of bedside care. Vacation, holidays, sick time, education days, and orientation all come out of the paid total. The hours left over are productive hours, and productive hours are what your HPPD target buys.
For the example, assume the facility's paid-time-off and non-productive time removes 208 hours per FTE, leaving 1,872 productive hours. Again, this is a round example. Use the actual non-productive hours from your own payroll history, ideally by role.
The conversion is then a single division:
Budgeted FTEs = annual worked nursing hours ÷ productive hours per FTE
Working through the example unit, 70,080 hours ÷ 1,872 productive hours per FTE gives about 37.4 budgeted FTEs.
That is the number of full-time equivalents needed to deliver the target hours after known leave and education time. It is not the number of people on the schedule, since part-time and per-diem staff each contribute a fraction. For how headcount translates into FTEs, our guide to FTE-weighted headcount walks through the weighting.
Step four: price the FTEs
Turn FTEs into dollars with your own loaded hourly cost by role: wages, benefits, and the payroll taxes your finance office applies. For a public reference point, the BLS Employer Costs for Employee Compensation release reports a loaded hourly cost for RN occupations in hospitals; look up the current figure and substitute your own payroll rates. Two cautions apply. That rate covers RN occupations only, so nursing assistant hours need their own rate. And ECEC reports cost per hour worked, so adding paid-time-off on top would count leave twice.
To keep the illustration clean, we will use a round $80 per paid hour for the example unit, chosen for arithmetic ease. One FTE then costs 2,080 × $80, or $166,400 a year. Multiply by 37.4 FTEs and the unit's annual labor budget is about $6.2 million.
That excludes overtime, agency and float-pool spend, differentials, and recruitment cost, which each deserve their own line.
Test the budget against census scenarios
A budget that holds only for the base case is fragile. Once the structure is built, run the sensitivity in a few minutes.
Suppose census comes in at 26 instead of 24. That is two additional patients per day, or 730 additional patient days over the year. At 8.0 HPPD, the unit needs 5,840 more worked hours. Divided by 1,872 productive hours, that is about 3.1 additional FTEs. At $166,400 per FTE, the added cost is roughly $519,000.
Run the same arithmetic downward and you see what a census dip does: fewer hours, fewer FTEs, and a decision about holding vacancies or redeploying. The point is to walk into the review with the cost of being wrong already calculated.
Reconcile budgeted FTEs with the vacancies you actually have
Budgeted FTEs and filled FTEs are different columns. The gap between them is your vacancy, and in the first quarter of the year it is the number that decides whether your HPPD is a plan or a hope.
According to the 2026 NSI National Health Care Retention & RN Staffing Report, RN turnover was 17.6% in CY2025, up from 16.4% in CY2024, and the cost to replace one bedside RN was $60,090. The same report puts the average RN time-to-recruit, its Recruitment Difficulty Index, at 78 days. Every departure opens a gap, and every gap takes weeks to close, so a budget that assumes full staffing from day one of the fiscal year will understate contingent labor.
For each unit, record budgeted FTEs, filled FTEs, open requisitions, and expected departures over the next two quarters. The difference is the hours you will cover through overtime, float pool, or agency. For a method to project that gap forward, see our piece on six-month vacancy forecasting.
If your CFO wants the financial case for investing in retention rather than covering gaps with contingent labor, the walkthrough in the CFO retention business case uses the same cost logic.
Put the method into a workbook
A spreadsheet with one row per unit and four formulas will carry a nursing labor budget HPPD calculation through the cycle. The risk is drift: formulas overwritten, assumptions undocumented, a unit tab that no longer matches the summary. To start from a structure that is already built, the Annual Nursing Workforce Budget Planning Workbook takes census and target HPPD in and gives budgeted FTE and labor cost out, so you can build a unit-by-unit annual nursing personnel budget from your own numbers. It holds no patient data. Nothing connects to your EHR, payroll, or scheduling system, and nothing takes over your schedule. You enter the figures you already use and read the result.
Once the base budget is set, the Nursing Vacancy & FTE Forecasting Workbook projects your 6-month FTE gap by unit and the travel-nurse premium cost of leaving it unfilled, which fills in the contingent-labor line the base budget leaves out. For the wider picture of how budget, turnover, and vacancy data fit together, the nursing workforce analytics guide is the place to start.
Whatever tool you use, keep the four drivers on the first page: projected census, target HPPD, productive hours per FTE, and loaded hourly rate. A reviewer who can see them can challenge any of them, and a budget that invites challenge is the one that gets approved.
Browse our templates: NursingWorkforce.com/store
Run the ROI Calculator: see what turnover is costing you
Join the Waitlist

