Workforce & Labor
Why don't our payroll forecasts match actual labor cost?
Last reviewed
Direct answer
Payroll forecasts usually miss because they are built on scheduled hours and base rates, while actual cost includes overtime, agency hours, differentials, paid leave, benefits and census changes the forecast did not assume. Forecasts and actuals also often use different definitions and period cutoffs. Reconcile scheduling and payroll on shared definitions first, then measure the variance by cause.
Why this happens
Scheduling systems record planned shifts; payroll records what was paid, including gap-fill overtime, agency invoices and leave. Those are different events on different clocks.
When variance is measured only as one total, nobody can tell whether the forecast method, the census assumption or an operational change caused it.
Example: labor hours per resident day
Payroll hours ÷ EHR census
3.9
Uses the clinical census, which includes a bed hold.
Payroll hours ÷ billed days
4.1
Uses accounting’s billable days.
Scheduled hours ÷ budget census
3.6
Uses planned hours against a budget assumption.
- Evidence
- Disagreement
- Authority
- Governing Record
- Intelligence
- Execution
Illustrative figures. Governance first. Intelligence second. Execution last.
All three ratios are arithmetically correct. They answer different questions, and a portfolio comparison is only meaningful if every community uses the same governed definition.
The governance question
Staffing decisions should read from a census the operator has approved for staffing, and labor KPIs should declare which hours and which census they use. Agency, overtime and pickups need explicit treatment rather than being absorbed silently.
Evidence → Disagreement → Authority → Governing Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- An approved staffing census and labor definitions.
- Reconciliation between scheduled, worked and paid hours.
- Explicit treatment of agency, overtime and premium pay.
- Comparable labor KPIs across communities.
- Timely updates when census changes quickly.
SeniorCRE perspective
SeniorCRE is designed to tie labor measures to a governed census so staffing, finance and leadership read the same denominator. Workforce systems stay authoritative for hours and pay; the operator governs how they combine with census into a decision. Status: the governed operating record is designed and not yet implemented in any community. What is built, validated and deployed is published on the evidence page, and nothing here should be read as a production result.