Nursing home scheduling software: what to look for

A nursing home schedule has to work on the floor and in the records behind it. The right software helps a DON test coverage, overtime, qualifications, and PBJ hours before a schedule reaches payroll or CMS.

What nursing-home scheduling software should calculate

Long-term care facilities must submit direct-care staffing information to CMS through the Payroll-Based Journal, including agency and contract staff.Source: CMS PBJ staffing data submission
PBJ submissions are due by 11:59 PM Eastern on the 45th calendar day after the last day of each federal fiscal quarter.Source: CMS PBJ staffing data submission
CMS reports a full 12-hour shift paid to work as 11.5 hours after deducting the required 30-minute meal break.Source: CMS PBJ Policy Manual, version 2.7
CMS nursing job title code 5 is for a registered nurse director of nursing, code 7 is for a direct-care registered nurse, code 9 is for an LPN or LVN, and code 10 is for a certified nurse aide.Source: CMS PBJ Policy Manual, version 2.7

The buying decision starts with your operating model

For a 60 to 180 bed facility, a full schedule can still be wrong. One overnight shift may be assigned to the wrong reporting date. A nurse can be technically available while already committed to another unit. A replacement can fill the hole while creating overtime or violating a facility policy.

That is why nursing-home scheduling software should be judged as an operating control, not as a nicer calendar. It should understand units, roles, credentials, shift boundaries, paid hours, and the rules your facility has chosen to enforce. If it only fills open boxes, you are buying another place to hide errors.

The schedule is a coverage model, not a grid

Start with the hours your building must cover. One 24/7 post needs 168 coverage hours each week. A four-crew 12-hour rotation divides that into 42 hours per crew on average. That is arithmetic, not a feature choice. A fixed 3 by 12 model keeps a person at 36 hours and needs a separate relief plan.

Use this calculation when comparing patterns. The overtime result depends on the employee's workweek, state requirements, and facility policy.

Pattern	Planning math	Tradeoff to test
Fixed 3 by 12	36 hours each week	Stable day or night assignment, but open shifts need a relief plan.
2-2-3, also called Panama or Pitman	7 shifts in 14 days, 84 hours total, 42 hours average per week	Predictable weekends and no more than 3 consecutive shifts, with day-to-night rotation if the pattern rotates.
4 on, 4 off	48 hours every 8 days, 42 hours average per week	A recovery block, but weekends drift and 4 consecutive 12-hour shifts are demanding.
DuPont	14 shifts in 28 days, 168 hours total, 42 hours average per week	A 7-day break, balanced against 4 consecutive nights and a 72-hour week in the cycle.

Run the same employee through a 40-hour workweek and an 8/80 calculation. In the derived 2-2-3 example, the favorable 40-hour boundary produces 8 overtime hours per 14 days. Under 8/80, the same pattern produces 28 because each 12-hour shift has 4 hours over 8. The 8/80 option is not automatically cheaper for 12s. Confirm the setup with payroll counsel.

PBJ accuracy starts at the shift record

Ask a vendor to show how it turns a schedule into reportable data. CMS measures paid-to-work hours by calendar day, not the label on the schedule. Midnight is the cutoff. In the CMS example, an 11 PM to 7 AM shift places 1 hour on one date and 7 hours on the next. A full 12-hour shift paid to work is reported as 11.5 hours after the 30-minute meal-break deduction, whether the break was taken or not.

The software should keep the source record intact while exposing the fields needed for reconciliation. At minimum, the record needs:

Field	Why it matters
Employee and facility identifiers	Connects the shift to the person and building that reports it.
Job title code	Separates direct-care RN, LPN or LVN, CNA, nurse aide in training, and other roles.
Pay type	Identifies employee or contract status in the reporting workflow.
Start, end, and paid-to-work time	Supports midnight splitting, meal-break deduction, and scheduled-versus-actual review.
Agency or contract flag	Prevents outside coverage from disappearing from the staffing record.

Do not accept a PBJ-ready claim because a vendor can export a CSV. Ask whether the export uses paid-to-work hours, splits night shifts by date, and traces a reported line back to its assignment.

Coverage controls worth paying for

Coverage rules differ by facility. A software demo should show how your rules behave, not how many color choices the calendar has.

Unit demand: set targets by unit, shift, role, and census input. A building may need a different mix on memory care than on a short-stay wing.
Hard constraints: block expired credentials, unavailable employees, overlapping assignments, and a shift that would exceed your configured overtime or rest policy.
Call-out ranking: rank qualified available replacements using the rules you actually use. Include overtime status and keep a record of offers, declines, and acceptance.
Publish review: show unresolved gaps and conflicts before publication. After publication, preserve who changed the assignment, when it changed, and why.

A warning is not the same as a control. If an expired credential appears as a yellow note while the user can still publish the shift, the system has made the scheduler responsible for remembering one more thing. A hard block is appropriate for a true eligibility rule. A visible warning is better for a preference that a supervisor may intentionally override.

The state-law question vendors dodge

Mandatory overtime, staffing ratios, staffing plans, and overtime pay are separate questions. A product that says it handles nursing compliance should tell you which one it means.

The research behind this guide found 17 confirmed state restrictions on mandatory overtime, but coverage varies sharply. Only 4 states clearly reached nursing homes in the facility-type review. Some laws cover hospitals only. Others protect a nurse who refuses extra hours rather than setting a simple hour cap.

Store the state policy, bargaining terms, on-call rules, rest requirements, and emergency workflow as separate inputs. In several reviewed laws, chronic short staffing is expressly not an emergency exception. Have counsel confirm the policy before turning legal language into an automatic block.

Test a vendor with one ugly shift

Do not evaluate a product with a clean Monday morning schedule. Use a scenario that forces the system to reveal its assumptions.

Create a 7 PM to 7 AM RN shift and assign it to a unit with another role due during the same window.
Check the PBJ view. The night shift should split at midnight, with the 11.5-hour treatment after the meal-break deduction.
Add an agency worker, an expired credential, and an employee who would cross your overtime threshold. Try to publish each assignment.
Call out the RN two hours before the shift. Confirm that the replacement list filters eligibility, then records the offers and final decision.
Edit the published assignment. Ask for the audit record and reconciliation export.

Make the vendor show the raw row, not a dashboard screenshot. You are testing whether the system can explain a result when someone audits it later.

Where scheduling systems quietly fail

A vendor exports scheduled hours as PBJ hours without using paid-to-work time or the 30-minute meal-break deduction.
An overnight shift stays on its start date instead of splitting at midnight.
The product markets 8/80 as a shortcut for 12-hour overtime without showing the daily overtime math.
The system applies a hospital rule to a nursing home without checking the facility type and state policy.
An expired credential produces a warning but still allows the assignment to publish.
A call-out workflow forces the person already on duty instead of documenting voluntary coverage efforts.

A practical way to evaluate Shiftd

Shiftd lets facilities configure coverage rules and surface scheduling errors before publication, then keeps an audit record of each change. It computes HPRD against real census and maps shifts to PBJ job codes. It does not replace payroll or timekeeping, and it is not clinical charting.

See Shiftd in action →

Questions worth asking before you buy

What does PBJ-ready scheduling software need to do?

It should map each assignment to the correct job title and pay type, split overnight hours by calendar day, apply the PBJ meal-break treatment, include agency or contract work, and let you reconcile reported rows back to the source shift.

Is 8/80 cheaper for a nursing home using 12-hour shifts?

Not automatically. In the 2-2-3 example, 8/80 creates 28 daily overtime hours per 14 days. A favorable 40-hour workweek boundary produces 8 hours in that example. Confirm the calculation with payroll counsel for your facility.

Can scheduling software enforce mandatory-overtime laws?

It can enforce the policy you configure, such as a rest rule or required replacement workflow. It cannot safely infer the law from a generic nurse setting because coverage and exceptions differ by state and facility type.

Should a nursing-home scheduler track census?

Yes, if your staffing targets change with census or acuity. The tool should show the target it is checking, the source of the input, and the gap before publication instead of presenting a full roster as proof of adequate coverage.

What should I test in a scheduling software demo?

Use an overnight RN shift, a credential that has expired, an agency replacement, an overtime edge case, and a post-publication edit. Ask the vendor to show the PBJ row and audit history produced by that scenario.