How to build a nurse staffing grid for your unit

Build a nurse staffing grid from census and HPPD, round each row on purpose, decide when to flex, and check the whole grid against your budget.

The short version

  • A nurse staffing grid is a table that says how many RNs, techs and fixed positions you staff for each census, by shift. It turns your HPPD target into a decision a charge nurse can make in ten seconds.
  • Build every row with the same formula. Census × target HPPD gives the hours for 24 hours, which you split by role and by shift and divide by the shift length.
  • Rounding is where a grid drifts. Work out the HPPD each row actually delivers after rounding, and know which rows sit above or below target.
  • Weight each row by how many days a year your unit sits at that census. That one number tells you whether the grid as written fits the budget.
  • The grid is the starting point for a shift, not the answer. Write down what lets the charge nurse go above or below it, and track every time they do.

A nurse staffing grid is a table with one row for each census your unit runs at and one column for each role and shift, so anyone can look up how many RNs and techs to staff tonight. You build it by multiplying each census by your target hours per patient day, splitting those hours by role and shift, and rounding to whole people. The math takes an afternoon. The hard part is rounding each row on purpose, deciding when the charge nurse can go off the grid, and checking that the grid as a whole still fits the budget.

This guide walks through all of it with a worked grid for a 30 bed unit, the arithmetic behind every cell, and the places grids usually go wrong.

What a staffing grid is, and what it is not

A grid is a lookup table. Rows are census. Columns are roles by shift: RN days, RN nights, tech days, tech nights, and any fixed positions like a charge nurse without an assignment or a unit secretary. Each cell is a number of people.

It is not a ratio. A ratio says one nurse for every four patients, and stops there. A grid says what to do at a census of 21, when four does not divide evenly, and whether the extra nurse goes to days or nights. It is also not the schedule. The schedule is who is coming. The grid is how many you need. The gap between the two is what the charge nurse fixes every shift.

And it is not your budget, although it has to agree with it. Your budget was built from a target HPPD and an expected census. A grid built from the same target, at the census your unit actually runs, is the budget turned into daily decisions. If you have not pinned down your target yet, our guide on how to calculate HPPD covers it first.

What you need before you start

  1. Your target HPPD, and which hours it counts. If your 8.0 is direct care only, the charge nurse without an assignment sits outside the grid math. If it includes the charge nurse, they come out of the same hours.
  2. Your role split: how many of those hours are RN and how many are tech or other assistive staff.
  3. Your shift split: how the 24 hours divide between days and nights. In her staffing plan series in Nursing Management, Pamela Hunt notes that a high acuity unit like a CCU tends to need staff more evenly across shifts, while med surg units need more during the day.
  4. A year of census, ideally the census at the time each shift starts, so you know which rows matter and how often.
  5. Your shift length. Everything below uses 12 hour shifts.

The formula for every row

For each census:

Then, for each role:

Split those shifts between days and nights, and round to whole people. That is the whole grid.

Hunt walks through the same steps for a full staffing plan: census times budgeted HPPD gives the 24 hour need, divided by the productive hours in a shift, then split by shift and by skill mix. Her one strong opinion on census is worth keeping. She plans from the mode, the midnight census a unit sees most often, rather than the average, because in her example the average left the need unmet on most days and the mode left it short on just one.

A worked grid for a 30 bed unit

Take a 30 bed unit on 12 hour shifts with a target of 8.0 HPPD in direct care hours: 6.0 RN and 2.0 tech. All the numbers are invented for the example.

At a census of 24:

  • Total hours: 24 × 8.0 = 192
  • RN hours: 24 × 6.0 = 144, or 144 ÷ 12 = 12 RN shifts, 6 on days and 6 on nights
  • Tech hours: 24 × 2.0 = 48, or 48 ÷ 12 = 4 tech shifts, 2 on days and 2 on nights

That is one RN for every four patients and one tech for every twelve, on both shifts. Add one charge nurse per shift on top, because the target counts direct care only.

Now do every row. The rules used here: round to the nearest whole person, and when a role splits unevenly, the extra goes to days.

CensusRN daysRN nightsTech daysTech nightsHours staffedHPPD delivered
2055211567.80
2165221808.57
2265221808.18
2366221928.35
2466221928.00
2576222048.16
2676222047.85
2777322288.44
2877322288.14
2987322408.28
3087322408.00

Hours staffed is every person in the row × 12. HPPD delivered is hours staffed ÷ census. Check any row yourself: at 21, the RN hours are 21 × 6.0 = 126, which is 10.5 shifts, and rounding to the nearest makes it 11.

Look at the last column. Only two rows land exactly on 8.0. A census of 21 runs at 8.57 because half a nurse and half a tech both rounded up to whole people. A census of 26 runs at 7.85 because the unit is two patients past the point where the seventh day nurse came in, and the next nurse does not arrive until 29. Those are the rows your staff will feel, and the rows finance will ask about.

Check the whole grid against the budget

Each row looks reasonable on its own. The question is what the grid costs across a year. Weight each row by the number of days the unit spent at that census.

Say last year looked like this: 6 days at 20, 10 at 21, 18 at 22, 30 at 23, 52 at 24, 68 at 25, 60 at 26, 48 at 27, 36 at 28, 22 at 29 and 15 at 30. That is 365 days and 9,316 patient days.

  • Hours the grid staffs: each row's hours staffed × its days, added up, is 75,864.
  • Hours the budget allows: 9,316 × 8.0 = 74,528.
  • Grid HPPD: 75,864 ÷ 9,316 = 8.14.

The grid as written runs about 1,336 hours a year over target. Divided by 2,080, that is roughly 0.6 of a productive FTE, and it comes almost entirely from rounding. Nobody overstaffed on purpose.

Now you can choose. You might accept it, because 8.14 is close and the rows that run rich are low census days when admissions come in fast. You might round the RNs at 21 down to 5 and 5, which lands that row on exactly 8.0, because the techs at 21 already rounded up. Or you might keep the grid and flex down harder at 21 and 23. What matters is that you made the call with the number in front of you, instead of finding out from a variance report three months later. Our guide on how to calculate FTEs for a nursing unit shows how these hours turn into positions.

When to go above or below the grid

Hunt puts it plainly: census variability is no friend to the staffing plan. A grid is built for census. It does not know that three of tonight's patients are on drips that need titrating every hour, or that six discharges and five admissions are coming before noon. Census alone also tells you nothing about acuity, and a unit that staffs to a grid without an override is staffing to the wrong number some days.

So write the overrides down, as part of the grid:

  • Up: patients needing one to one care or a sitter, more than a set number of admissions expected in the shift, a fresh post procedure patient who needs a nurse alone, a new grad cohort orienting.
  • Down: a set number of discharges confirmed before a time you choose, or a census that has held below the row for a set number of hours.
  • Who decides: usually the charge nurse, with the house supervisor for anything above a line you set.
  • When: pick the decision times, for example a few hours before each shift starts, so people sent home or called in get fair notice.

Then track every override with a reason. If the charge nurse goes above the grid at a census of 26 most nights, the grid is wrong at 26, not the charge nurse. A short reason list (acuity, admissions, one to one, discharges pending) is enough to see the pattern after a month.

Hunt also asks a question worth answering for your own unit before you settle a borderline row: is it easier to get staff to come in when census goes up, or easier to send them home when it drops? If your unit fills holes easily, round down and call in. If it does not, round up and send home.

Who signs off on the grid

On most units the manager builds the grid and the director and finance agree to it. In some states the law gives frontline nurses a formal role in the staffing plan behind it. Texas, for example, requires a hospital nurse staffing committee in which at least 60 percent of members are registered nurses who spend at least half their time in direct patient care. The committee meets at least quarterly and reviews at least twice a year how actual staffing compared with the plan. Check what your own state requires, and ask your organization which committee owns the plan your grid comes from.

Even where nothing requires it, build it with your charge nurses. They are the ones using it at 0500, and they know exactly which rows are wrong.

Keeping the grid live

Review the grid at least once a year when the budget is set, and any time the target HPPD, the role split or the shift structure changes. A change to the target means every cell moves. A change in which census your unit runs at most means the weighting changes, even if the rows do not.

The other half is comparing the grid with what actually happened. If your unit runs on Adelo Workforce, the manager side shows live coverage by role against the schedule and puts HPPD and overtime in its analytics, so a row that keeps getting overridden shows up while you can still change it. For building the schedule that feeds the grid, see how to build a 6 week nursing schedule.

Questions people ask

What is a staffing grid in nursing?

It is a table that tells a unit how many nurses, techs and other staff to schedule for each census, usually by shift. Each row comes from the census multiplied by the unit's target hours per patient day, split by role and shift and rounded to whole people.

Is a staffing grid the same as a nurse to patient ratio?

No. A ratio sets how many patients one nurse can have. A grid sets the whole staffing for each census, including techs and fixed positions, and decides what to do when the numbers do not divide evenly. A grid can be built to meet a ratio, but it covers more.

Should a staffing grid use average census or the most common census?

Use every census your unit actually runs at as its own row, then weight the rows by how often each happens to check the budget. When you plan positions, Hunt recommends the mode, the census your unit sees most often, because planning to the average leaves you short on more days.

Does the charge nurse count in the staffing grid?

It depends on how your target HPPD was built. If the target counts direct care hours only, a charge nurse without an assignment sits outside the formula as a fixed position. If the target includes them, they come out of the same hours. Ask finance which it is before you defend the grid.

How often should a staffing grid be updated?

At least once a year with the budget, and whenever the target HPPD, the skill mix or the shift structure changes. Also look at it whenever the charge nurses keep overriding the same row, because that row is telling you it is wrong.

Sources

  1. Hunt PS. Developing a staffing plan to meet inpatient unit needs, Nursing Management, May 2018, census × budgeted HPPD as the 24 hour need, the mode midnight census, shift and skill mix splits, and census variability.
  2. Texas Health and Safety Code § 257.004, Nurse Staffing Committee, committee makeup, quarterly meetings and the semiannual review of variations between the plan and actual staffing.
Adam DeLeon, critical care nurse leader and founder of Adelo

Adam DeLeon, MBA, BSN, RN, NE-BC, CCRN-CSC

Adam is a board certified critical care nurse leader who manages a large cardiovascular ICU and built Adelo Workforce from the workflows he uses to run it.

“I built Adelo because my own critical care unit deserved one calm place to run the shift. Every workflow in it started as a problem I lived on the floor.”
Adam DeLeon, critical care nurse leader and founder of AdeloAdam DeLeonFounder and critical care nurse leader

See Adelo on your unit.

Twenty minutes with the nurse leader who built it, starting from the thing you most want to fix.

Free for every nurse, tech and secretary. Start a unit free