Free template · Four teams · Real hours
A 12-hour shift template where a night shift is not always twelve hours
A 12-hour shift schedule rotates staff through day and night shifts in a fixed repeating pattern, so that a unit is covered around the clock by teams working roughly 42 hours a week. This template lays a four-team Pitman rotation onto real dates, and computes each shift's hours as real elapsed time rather than by subtracting one clock reading from another.
Free · No email address · No account
Where can I download a 12-hour shift schedule template?
Here: the two buttons below, and both accept a start date. No email address, no account, and no thank-you page with a sales sequence behind it.
Opens in Excel, Google Sheets, LibreOffice or Numbers. The printable version is laid out landscape for a wall.
What is in it
- Two full 14-day Pitman cycles (28 days) for four teams, on real dates.
- A real-hours column per shift, computed on elapsed time in the timezone you pick.
- A note on every shift that crosses a clocks change, saying what it actually is.
- Per-team totals as formulas, so they stay right when you edit the grid.
At a glance
- A 12-hour shift schedule covers 24 hours with two shifts instead of three, rotating teams through days and nights on a repeating cycle.
- The common patterns are Pitman (2-3-2, 14 days), DuPont (28 days, ending in seven days off) and the fixed 4-on-4-off. All of them average around 42 hours a week.
- This template is a four-team Pitman rotation on real dates: teams A and B on days, C and D on nights, every team getting a full weekend off every other week.
- The hours column is computed on real elapsed time. A 19:00–07:00 night is 12 hours on an ordinary night, 11 the night the clocks go forward, and 13 the night they go back.
- That is not a curiosity. Exporting 12 for a 13-hour night underpays the nurse by an hour, and the clock cannot tell you; only the date can.
What is a 12-hour shift schedule?
A 12-hour shift schedule covers the full day with two shifts rather than three, rotating teams through days and nights on a repeating cycle so the unit is never uncovered and no team works more than about 42 hours a week.
The arithmetic is what makes it popular. Twenty-four hours needs two twelves, so a unit needs two teams on at any moment and four teams to cover the cycle without anyone living there. Each team ends up working roughly half the days in a cycle, seven in fourteen on a Pitman, which is why the pattern buys long stretches off in exchange for long days. Fewer, longer shifts also means fewer handovers, and a handover is the point at which information about a patient is most likely to be lost.
The cost is a real one and it is not evenly shared. Twelve hours is a long time to be upright, three consecutive twelves is longer, and a rotation that keeps four people on nights indefinitely has concentrated a health cost onto four people rather than spreading it across sixteen. Neither answer is obviously right; what is wrong is choosing between them without saying out loud that that is the choice.
What are the common 12-hour rotation patterns?
Three of them account for nearly everything in use: Pitman, DuPont, and the fixed 4-on-4-off. All three average about 42 hours a week, which is not a coincidence.
Forty-two is what falls out of the arithmetic. Four teams covering two 12-hour shifts around the clock is 168 hours a week divided by four, and no amount of rearranging the pattern changes that total; it only changes how the hours feel. That is the useful way to read the differences below: they are not trade-offs between more and less work, they are trade-offs between different arrangements of the same work.
Pitman: 2-3-2, over fourteen days
Two on, two off, three on, two off, two on, three off. Seven working days in fourteen, and the payoff is that every team gets a full Saturday and Sunday off every second week, permanently and without asking. The longest stretch is three shifts. It is the gentlest of the three, and it is what this template generates.
DuPont: twenty-eight days, ending in a week off
Four nights, three off, three days, one off, three nights, three off, four days, then seven consecutive days off. Fourteen working days in twenty-eight. The seven-day break is long enough to actually go somewhere, which no amount of scattered rest days ever adds up to. Four consecutive nights followed by a three-day turnaround onto days is the price. People who love it love it; people who do not tend to leave.
Four on, four off
The simplest thing that works: four twelves, four days off, repeat. Its virtue is that anybody can hold it in their head. Its vice is that an eight-day cycle does not divide into a seven-day week, so your days off walk around the calendar and never land on the same weekend twice, which is fine until someone has a child in a school with a Saturday fixture list.
How many hours is a night shift when the clocks change?
Eleven the night the clocks go forward and thirteen the night they go back, for a shift the roster calls twelve hours, on both occasions.
Subtract 19:00 from 07:00 and you get twelve, every time, on every date, which is exactly the problem: the wall clock is not a measure of elapsed time on the two nights of the year when the wall clock is edited while the nurse is standing under it. In the spring the hour between 02:00 and 03:00 does not occur, and a night shift that spans it is eleven hours long. In the autumn that hour occurs twice, and the same shift is thirteen. Nobody moved; the clock did.
This matters because hours feed a paycheck. Export twelve for a thirteen-hour night and you have shorted the nurse an hour of her life, on the one night of the year she is least inclined to be generous about it. And the error is invisible, because every number in the spreadsheet is internally consistent and wrong. Export twelve for an eleven-hour night and you have paid an hour that was not worked. Both are the same bug: treating a clock reading as a duration.
The figures in the table below are not typed into this page. They are computed by the same code that computes hours for a payroll export: the engine works on instants, in the location's timezone, and asks the operating system's timezone database rather than knowing anything about any government's rules. That is also why the table below is always the NEXT two changes, whichever year you are reading this in.
What this template cannot do about any of that
It can tell you an hour is missing. It cannot stop the missing hour reaching a payslip.
The CSV computes the real hours correctly and writes a note on every shift that crosses a change, which is more than any other free 12-hour template will do for you, and it is still only a document. It cannot re-check itself when you edit a date. It cannot notice that you copied the fortnight forward over a boundary. It cannot enforce the rest gap between a night that ran thirteen hours and the shift somebody is on the next evening, and it cannot tell your payroll provider anything at all; you will re-key it, and the re-keying is where the number gets rounded back to twelve because twelve is what everyone expects.
MedAligna computes every duration on real elapsed time for the same reason this template does, and then does the part a file cannot: the rest rule, the overtime projection and the payroll export all read the same figure, so the thirteen-hour night reaches your payroll system as thirteen without anyone having to remember that November happened.
The next two nights a 12-hour shift is not twelve hours
A 19:00–07:00 night in Eastern time, on the next two dates the clocks change. These numbers are computed by the scheduling engine when this page renders; they are not typed into the page, and they are not a worked example.
| The night of | What happens | The clock says | Actually worked |
|---|---|---|---|
| Any ordinary night | Nothing. 363 nights a year. | 12 | 12 |
| 2026-10-31into 2026-11-01 | Clocks go back. 01:00–02:00 happens twice. | 12 | 13 hours |
| 2027-03-13into 2027-03-14 | Clocks go forward. 02:00–03:00 never happens. | 12 | 11 hours |
Both rows read 19:00–07:00, and subtracting one from the other gives twelve on both. That is the bug: a clock reading is not a duration. The engine computes on epoch milliseconds and asks the operating system's timezone database rather than knowing anything about any government's rules, which is also why this table is correct in Arizona, where it would show twelve on every line.
Questions people actually ask
- What is the Pitman schedule?
- A 2-3-2 rotation over fourteen days: two on, two off, three on, two off, two on, three off. Four teams work 12-hour shifts, two covering days and two covering nights, each averaging 42 hours a week, and each getting a full weekend off every other week.
- Is a 12-hour night shift really not twelve hours?
- Twice a year, no. A 19:00–07:00 night is eleven real hours the night the clocks go forward and thirteen the night they go back, because the hour between 02:00 and 03:00 is either skipped or repeated. On the other 363 nights it is exactly twelve.
- Which hours should I pay for a shift that crosses a clocks change?
- The hours actually worked: eleven or thirteen. We are not your payroll adviser and the treatment of overtime thresholds around it is a question for whoever runs your payroll, but the elapsed time itself is not a matter of opinion: it is what the clock did while your nurse was standing there.
- Can I change the start date or the timezone?
- Yes. Both download links accept a start date and a timezone, and the roster and the hours are recomputed for whatever you ask for. Point it at the week of a clocks change and the notes column will fill in.
- Does this work for Arizona or Hawaii?
- Yes, and the real-hours column will read twelve on every single night, because neither observes daylight saving. That is the correct answer rather than a missing feature; the arithmetic asks the timezone database rather than assuming everyone changes their clocks.
Related
Hours that are right on the two nights
MedAligna computes every duration on real elapsed time, so rest, overtime and the payroll export agree, including the nights everyone else gets wrong. Fourteen days free.