How does SeniorCRE forecast payroll for the next two weeks before it is run?
Payroll is a surprise every period. The schedule looks one way, the actuals come in another, and overtime is discovered the week after it was earned.
How it works
- Anchor on a rolling 13-week horizon
- Model the four cost drivers separately
- Layer census + acuity as the demand signal
- Layer merit cycles, market adjustments, and pay-band changes
- Add SNF PPD forecasting aligned to CMS PBJ
- Reconcile forecast vs actual to the GL weekly
- Lock the mid-year reset in May or November
On this page
The best-practice pattern for healthcare payroll forecasting is a rolling 13-week weekly forecast , split into base hours, overtime, agency, and PTO, and fed by both demand signals (census, acuity) and supply signals (schedule, merit cycles). Accuracy is reported as its own KPI, and forecast vs actual is reconciled weekly against the general ledger.
In senior housing & care specifically, PPD alignment to CMS PBJ categories and a mid-year reset in May and November are the two disciplines that separate operators who make budget from operators who don't.
Model each shift in the schedule against a demand curve (acuity-weighted census). Any hours above scheduled coverage go to overtime; hours that can't be filled internally go to agency at contract rate + a fill-time premium. This produces a 14-day open-shift risk and a 13-week agency spend projection you can actually plan against.
Bundling OT and agency into a single “variable labor” line is the most common mistake — it hides which lever to pull. OT is a manager-scheduling problem; agency is a pipeline / retention problem. Different plays, different owners.
Accuracy is a function of pipeline completeness — census, acuity, scheduling, payroll, GL — not of the vendor. SeniorCRE does not publish an accuracy figure; measure it against your own actuals. Accuracy degrades when the forecast is not rebased weekly, when merit cycles are missing, or when acuity is not a demand input. Publish forecast accuracy per community as its own KPI so degradation gets caught early.
For AL and MC portfolios, PPD is optional but useful — most operators forecast in hours per resident day instead, weighted by ADL acuity. For any SNF exposure, PPD aligned to CMS PBJ is mandatory: it is the number surveyors, reimbursement, and the staffing rule are all indexed to.
Key points
- Long enough for a payroll cycle, a holiday, and a meaningful PTO window; short enough that accuracy stays above 85% at the end and above 95% at the front. It also maps cleanly to a quarterly board update and to the May / November mid-year reset.
- Weekly. A rebased forecast plus a published forecast-accuracy KPI is the discipline that keeps the pipeline honest. Monthly rebases lose the front-week accuracy that operators rely on.
- No. SeniorCRE reads payroll of record (ADP, Paycom, Paylocity, UKG, Workday) and scheduling (OnShift, Smartlinx, native) and builds the forecast on top. The system of record stays where it is.
- 30–90 days for a portfolio-wide go-live once payroll, scheduling, and GL feeds are connected. First community can be live inside two weeks.
- A board-ready view of the current 13-week baseline extrapolated to year-end, forecast-accuracy KPIs per community, variance commentary, and a lever-by-lever plan (OT, agency, merit cycles, pay-band). Delivered in May and November.
https://seniorcre.com/workforce-analytics-senior-living/payroll-forecasting/how-to