A monthly healthcare staff schedule template that holds up

What the month should show

• A 2-2-3 12-hour rotation puts 7 shifts, or 84 scheduled hours, into 14 days. That averages 42 hours per week before any pickup shift.
• CMS PBJ reporting uses hours paid to work by calendar day, not the schedule's planned shift total.Source: CMS PBJ Policy Manual v2.7
• CMS requires a 30-minute meal-break deduction from each full shift paid to work, so a 12-hour shift is reported as 11.5 hours.Source: CMS PBJ Policy Manual v2.7
• The FLSA 8/80 option requires a prior agreement and calculates overtime after 8 hours in a workday and after 80 hours in a fixed 14-day period.Source: U.S. Department of Labor FLSA Overtime Advisor

Use the month for balance, not proof of coverage

Use the month to see patterns that disappear in a weekly view. Is the same RN taking every weekend? Does a 2-2-3 rotation create 42 scheduled hours every week? Is approved leave concentrated on the same night shift? Those are planning questions.

Do not use the month grid as proof that every day is covered. A full-looking month can still contain one thin Tuesday or one call-out that changes the actual hours. Keep a daily coverage check beside the monthly view.

Build the grid around decisions, not names

Start each row with a date and a shift. Then separate the role from the person's name. A cell such as 'Jordan, 7a-7p' hides the role and makes a replacement hard to record.

Use one line for the planned assignment and one for what actually happened.

A blank monthly layout you can copy

Keep the month view compact. Put the detail in rows below each date rather than squeezing four roles into one text cell.

Repeat the date block through the month. Add a running-hours column for each employee in the underlying sheet. The visible month can stay readable while the calculation layer answers whether a proposed pickup crosses your overtime policy.

Test the rotation before you publish the month

The pattern belongs in the template, but the pattern is not the coverage plan. A 2-2-3 schedule looks balanced at a glance and creates a predictable math problem.

Under a 40-hour workweek, the 42-hour average usually creates overtime in weeks with four shifts. The total depends on where the fixed seven-day workweek begins. Federal rules allow a fixed workweek to begin on any day, but changing it to evade overtime is not permitted under 29 CFR 778.105. Have payroll or counsel confirm the setup before using the number as a cost-saving tactic.

A fixed 3 x 12 model schedules 36 hours each week, but it does not solve weekend balance or open coverage. The month template still needs a replacement path.

Keep scheduled hours separate from PBJ hours

A monthly template can plan a shift. It cannot turn the plan into the PBJ record by copying the shift length into one date. PBJ counts hours paid to work by calendar day. It excludes paid leave and meal breaks, and a shift crossing midnight is split across both dates.

The HPRD example is arithmetic, not a legal target. Keep a correction column for a late arrival or replacement. Do not overwrite the original assignment.

Put the legal check beside the schedule

Federal overtime pay and mandatory overtime are different questions. The FLSA does not itself place an absolute limit on hours when the required premium is paid. State law, a collective bargaining agreement, or facility policy may restrict whether someone can be required to stay.

Give the template a policy field, not a generic warning that every hour over 40 is illegal. Record the applicable state or agreement, the exception path, and who authorized a holdover. Chronic short staffing is not a safe assumption for an emergency exception in the state laws covered by the research. If the plan depends on repeated holdovers, it is showing a vacancy problem.

The same 12-hour rotation can create different payroll results under a 40-hour workweek or an 8/80 arrangement. The 8/80 arrangement requires prior agreement and pays overtime over 8 hours in a workday plus over 80 hours in 14 days. Have payroll review the setup before encoding it in a spreadsheet.

Run this check before the month goes live

1. Scan each date for the required role coverage on both shifts.
2. Compare planned hours with each person's running hours at the fixed workweek boundary.
3. Mark approved leave before assigning the replacement.
4. Test the highest-census dates again after every open shift is filled.
5. Keep the original assignment beside the actual replacement and paid hours.

Repeat the daily check after a call-out. A monthly template that never changes after publishing is a calendar, not a staffing tool.

Where the spreadsheet lies

• A name in a date cell does not prove that the assigned role is covered.
• A 12-hour scheduled shift becomes 11.5 PBJ hours after the required meal-break deduction.
• A night shift crossing midnight must be split between two PBJ dates.
• A 2-2-3 rotation averages 42 scheduled hours per week, so the pattern does not avoid overtime under a 40-hour workweek.
• Leaving approved PTO in a note without a replacement assignment makes the month look fuller than the actual roster.
• Overwriting the original assignment after a call-out destroys the record of what changed.