Live demos: no login required HIPAA-aligned · BAA on every account Austin, TX · Built for skilled nursing operators
(405) 383-5214

How to Read a Staffing Hours-Per-Resident-Day Dashboard

Hours per resident day is the most common staffing metric, and the easiest to misread. Learn how to build and review it by shift, unit and role.

3 min readBy CarePulse Analytics Team

If you ask five administrators how they track staffing, at least four will mention hours per resident day, often shortened to HPRD. It is a useful measure because it adjusts for census: a building with 90 residents and a building with 60 residents can be compared on the same scale. But a single HPRD number for the whole month is a blunt instrument. This post covers how to build a dashboard that makes the measure genuinely useful for daily decisions.

What HPRD actually measures

HPRD divides the paid hours worked by a group of staff by the number of residents in the building, per day. It can be calculated for nurses, for aides, or for combined nursing. Federal staffing data submitted through the Payroll-Based Journal (PBJ) uses a similar logic, and CMS Care Compare reports staffing information drawn from it, which is why many operators look at their own internal figures before the public ones update.

The strength of the measure is its simplicity. The weakness is that it is an average, and staffing problems are almost never average. They happen on a specific shift, on a specific unit, on a specific weekend.

Build the view in layers

Layer one: the building trend

Start with a weekly line for total nursing HPRD over the last twelve weeks. This tells you whether the building is stable, drifting up, or drifting down. It is the headline, and it should take two seconds to read.

Layer two: by role

Split the line by RN, LPN and nurse aide. A flat total can hide a shift in mix, for example more aide hours offsetting fewer licensed hours. Neither is automatically good or bad, but you should see the shift on purpose rather than discover it later.

Layer three: by day of week and shift

This is where the dashboard starts paying for itself. Show HPRD by day of week, and if your timekeeping data supports it, by shift. Weekends and nights often look very different from weekday days. Your average may be fine while Saturday evening is thin.

Layer four: staffing against census

Plot hours and census together. If census climbs for three weeks and hours stay flat, HPRD is quietly falling. The chart makes the cause obvious where the ratio alone would not.

What to compare it against

A target without context is a guess. Useful comparisons include:

  • Your own trailing average, to catch drift
  • Your internal staffing plan or budget for the building
  • Your acuity and case-mix, since a higher-acuity census may need more hours for the same resident count
  • Hours worked by agency or contract staff versus employees, shown separately so the mix is visible

Be careful with outside benchmarks. Averages published elsewhere may define hours differently or include different roles, so unless you are certain of the definitions, rely on your own history and plan.

Questions to ask in the weekly review

  1. Which day-and-shift combination had the lowest HPRD this week, and was that planned?
  2. Did census change in a way the schedule did not follow?
  3. How much of our coverage relied on overtime or agency hours to reach the number?
  4. Are there positions where open shifts are repeatedly filled at the last minute?

That third question matters. Reaching a target through heavy overtime is not the same as reaching it with a stable schedule. Overtime-supported HPRD can look healthy while burning out the people who produce it.

A hypothetical example

Imagine a hypothetical 80-bed building whose monthly HPRD lines up with plan. When the manager splits the data by day of week, Sundays run noticeably lower than every other day, and census on Sundays is the same as on Mondays. The scheduler had been solving Sunday gaps with call-ins each week. After seeing the pattern, the team adjusts the base schedule and offers a weekend-incentive option for part-time staff. The point is not the specific fix; it is that the pattern was invisible until the data was cut the right way.

Mistakes to avoid

  • Treating the ratio as the goal. HPRD is a signal about coverage, not a measure of care quality on its own.
  • Counting hours that are not at the bedside. Be clear about which roles and which hours are included, and keep the definition consistent over time.
  • Ignoring the denominator. Census accuracy matters. Use the midnight census consistently.
  • Waiting for month-end. A weekly view lets you correct course while it still matters.

Putting it to work

The goal of an HPRD dashboard is to help schedulers and administrators see thin spots early and fix them calmly. If you would like to see how payroll and census data can feed this view automatically, CarePulse can show you a demo built from your own numbers.