Per-patient-day (PPD) budgeting is how long-term care runs its numbers, because it is the only basis that survives contact with a fluctuating census. A flat monthly supply budget looks fine at 92% occupancy and falls apart at 78%. PPD normalizes for the one variable you cannot control.
But most operators inherit their PPD targets rather than build them. The numbers came from a previous administrator, an old corporate template, or last year's actuals plus 3% — and nobody can say what they should be. This guide covers how to build PPD budgets from the ground up, and how to run them so a variance gets caught in week two instead of at month-end close.
We already covered the real-time tracking technology in How to Track Spending Against PPD Budgets in Real-Time. This is the companion piece: how to build the budget itself.
Step 1: Establish Your Baseline From Actuals
Pull twelve months of spend by department — food, medical supplies, housekeeping, laundry, office, maintenance — and divide each by your actual patient days for the same period. Not budgeted days, not licensed-bed days: actual census days.
Twelve months matters because LTC spend is seasonal. Flu season inflates medical supplies. Summer changes food costs. A quarter of data will mislead you; a year averages the cycle out.
The result is your true baseline PPD by department. For most operators doing this the first time, at least one department comes out meaningfully higher than anyone expected — that department is your first project.
Step 2: Set Department-Level Targets
A single house-wide PPD number hides everything useful. Food can be over while medical supplies are under, and the total looks fine until both go over together. Budget each department separately, and hold department heads to their own number — the dietary manager can act on a food PPD variance; nobody can act on a blended one.
One honest caveat: published benchmarks for what LTC operators should spend per patient day are remarkably scarce. There is no authoritative industry table to check yourself against — which is why baseline-from-actuals is step one, and why we are running the LTC Spend Benchmark survey to build that missing reference from real operator data. If you want the report when it publishes, contribute your (anonymized) numbers.
Step 3: Get the Denominator Right
The census number you divide by matters as much as the spend you divide. Three rules:
- Use actual midnight census, not occupancy assumptions. If your EHR (PointClickCare, MatrixCare, or otherwise) is the census system of record, your budget math should pull from it — not from a spreadsheet someone updates weekly.
- Decide how you count bed-holds and leave days, and apply it consistently across facilities. Inconsistent denominators are the most common reason multi-facility PPD comparisons mislead.
- Recalculate as census moves. A budget built at 90% occupancy is wrong at 80% — not because spending changed, but because the denominator did. This is where static spreadsheets quietly fail.
Step 4: Run a Weekly Cadence, Not a Monthly Autopsy
If PPD variance is reviewed at month-end close, every number you see describes money already spent. The review meeting becomes an autopsy.
The practical rhythm that works:
- Weekly: each department head sees month-to-date PPD against target. Ten minutes, standing agenda.
- Mid-month checkpoint: anything tracking over target gets a corrective action *this month* — substitute products, hold non-urgent orders, tighten approvals.
- Monthly: close the loop; feed what you learned into next month's target.
Alerts make the weekly rhythm automatic rather than heroic. A threshold like "80% of PPD budget consumed by day 20" notifying the department head and administrator directly means nobody has to remember to check a dashboard — the warning comes to them.
Step 5: Connect the Budget to Purchasing
A PPD budget that lives in finance while orders happen in a separate system is a scoreboard, not a control. The connection that changes behavior is at the point of order: the person placing the order sees where the department stands against its PPD target before the order goes in, and orders within budget flow through while orders that break the budget route for approval.
That single mechanic — budget visibility at the moment of purchase — is the difference between tracking overspend and preventing it.
The Bottom Line
Build the baseline from twelve months of actuals. Budget by department, not house-wide. Pull the census denominator from your system of record. Review weekly, act mid-month. And put the budget in front of the person placing the order.
And if the lack of industry PPD benchmarks frustrates you as much as it does us: take the LTC Spend Benchmark survey — every response makes the eventual reference table better.
Book a 15-minute demo to see census-synced PPD budgets with order-time visibility, live across all your facilities in weeks.