Shift Scheduler — Build a Rotating Shift Calendar You Can Print
Pick a rotation, a crew and a start date. The calendar fills in for the whole year, counts the overtime week by week, and prints or exports without an account.
The shift calendar
First ten days — Crew A, Panama 2-2-3
- Mon 4DAY12 h
- Tue 5DAY12 h
- Wed 6OFF—
- Thu 7OFF—
- Fri 8DAY12 h
- Sat 9DAY12 h
- Sun 10DAY12 h
- Mon 11OFF—
- Tue 12OFF—
- Wed 13DAY12 h
Crew A · Panama 2-2-3 · overtime after 40 h
FLSA default: overtime after 40 h in each 7-day workweek; over 28 days that is 160 h.
- 42.0average hours a week168 h per 28-day cycle
- 2,184hours a year1,976 regular + 208 overtime
- 4.0overtime h a week26 of 52 weeks carry overtime
- $91,520gross a year$40/h · OT ×1.5
- 25full weekends off624 weekend hours a year
- 3longest break, days12 h shortest rest · 0 night→day
| Week of | Hours | Regular | Overtime |
|---|---|---|---|
| 2027-01-03 | 48.0 | 40.0 | 8.0 |
| 2027-01-10 | 36.0 | 36.0 | — |
| 2027-01-17 | 48.0 | 40.0 | 8.0 |
| 2027-01-24 | 36.0 | 36.0 | — |
| 2027-01-31 | 48.0 | 40.0 | 8.0 |
| 2027-02-07 | 36.0 | 36.0 | — |
| 2027-02-14 | 48.0 | 40.0 | 8.0 |
| 2027-02-21 | 36.0 | 36.0 | — |
Crew A · Panama 2-2-3 · 42.0 h a week · 208 h overtime a year at 40 h · 3-day longest break
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1OFF | 2OFF | |||||
| 3OFF | 4DAY | 5DAY | 6OFF | 7OFF | 8DAY | 9DAY |
| 10DAY | 11OFF | 12OFF | 13DAY | 14DAY | 15OFF | 16OFF |
| 17OFF | 18NIGHT | 19NIGHT | 20OFF | 21OFF | 22NIGHT | 23NIGHT |
| 24NIGHT | 25OFF | 26OFF | 27NIGHT | 28NIGHT | 29OFF | 30OFF |
| 31OFF |
- DAY Day 07:00–19:00
- NIGHT Night 19:00–07:00
- OFF Off
Compare with another rotation
Both columns use the same 52 workweeks, the same 40-hour threshold, and the same $40/h at OT ×1.5.
| Measure | Panama 2-2-3 | DuPont |
|---|---|---|
| Cycle length | 28 days | 28 days |
| Hours per cycle | 168 h | 168 h |
| Average week | 42.0 h | 42.0 h |
| Overtime a year | 208 h | 468 h |
| Full weekends off | 25 | 25 |
| Longest break | 3 days | 7 days |
| Shortest rest | 12 h | 12 h |
| Night → day turns | 0 | 0 |
| Weekend hours a year | 624 h | 624 h |
| Gross at this rate | $91,520 | $96,720 |
The cycle, block by block
Checked day by day across all 28 days of the cycle: exactly 1 crew on days, 1 on nights, and 2 off.
| Block | Days | Length | Shift | Hours so far |
|---|---|---|---|---|
| 2D | 1–2 | 2 | Day 07:00–19:00 | 24 h |
| 2O | 3–4 | 2 | Off | 24 h |
| 3D | 5–7 | 3 | Day 07:00–19:00 | 60 h |
| 2O | 8–9 | 2 | Off | 60 h |
| 2D | 10–11 | 2 | Day 07:00–19:00 | 84 h |
| 3O | 12–14 | 3 | Off | 84 h |
| 2N | 15–16 | 2 | Night 19:00–07:00 | 108 h |
| 2O | 17–18 | 2 | Off | 108 h |
| 3N | 19–21 | 3 | Night 19:00–07:00 | 144 h |
| 2O | 22–23 | 2 | Off | 144 h |
| 2N | 24–25 | 2 | Night 19:00–07:00 | 168 h |
| 3O | 26–28 | 3 | Off | 168 h |
| 28-day cycle | 1–28 | 28 | 2D-2O-3D-2O-2D-3O-2N-2O-3N-2O-2N-3O | 168 h |
| Crew | Block shorthand | Shifts | Hours / cycle | Avg h / week |
|---|---|---|---|---|
| Crew A | 2D-2O-3D-2O-2D-3O-2N-2O-3N-2O-2N-3O | 14 | 168 h | 42.0 h |
| Crew B | 2O-2D-3O-2D-2O-3D-2O-2N-3O-2N-2O-3N | 14 | 168 h | 42.0 h |
| Crew C | 2N-2O-3N-2O-2N-3O-2D-2O-3D-2O-2D-3O | 14 | 168 h | 42.0 h |
| Crew D | 2O-2N-3O-2N-2O-3N-2O-2D-3O-2D-2O-3D | 14 | 168 h | 42.0 h |
Shorthand reads as count then code: 4N is four nights, 3O three off,
7O a seven-day break. Hours are counted from the first block of the cycle.
A shift scheduler that opens on a calendar, not a form
Most pages that rank for a shift scheduler hand you a formula, a picture of somebody else's rota, and a blank spreadsheet to retype it into. This one opens on a filled month: a pattern, a crew and a start date are already chosen, and every day of the year is already coloured Day, Night or Off.
The defaults are a real rotation rather than a demo: Panama 2-2-3, four crews, twelve-hour shifts, cycle starting on a Monday. There is nothing to configure before you can judge whether the pattern suits your life, which is the only question the page is trying to answer.
Every day has a crew on it, and the page shows its work
A rotation with an uncovered day is not a rotation, it is a rota with a hole in it, and the hole usually shows up on a holiday. For each round-the-clock preset the engine walks every single day of the cycle and checks the staffing: exactly one crew on days, exactly one on nights, the other two off. On a 28-day DuPont cycle that is 28 checks, not a vibe.
The cycle table further down prints the block shorthand shift workers actually use — 4N-3O-3D-1O-3N-3O-4D-7O — with the running hour count after each block and the average week it works out to. If a pattern you built yourself cannot be covered, the page says so instead of drawing a calendar that looks fine.
Overtime is a workweek question, not a monthly one
Forty-two hours a week does not mean two hours of overtime a week. On a 2-2-3 rotation the weeks are 48 and 36 hours, so the 48-hour week carries 8 overtime hours and the 36-hour week carries none. Divide the month by four and both facts disappear into an average that nobody is ever paid on.
So the tool splits the year into workweeks first and applies the threshold week by week: 40 hours normally, or 53 with the FLSA § 207(k) fire-protection toggle, which is 212 hours per 28-day period under 29 CFR 553.230. The workweek start is a control of its own, because moving the boundary between Sunday and Monday genuinely changes the answer.
That last point is worth sitting with, because it is a policy lever rather than a scheduling detail. A 2-2-3 crew measured Sunday to Saturday can see 48 and 36 hour weeks; the same crew measured Monday to Sunday can see 60 and 24. Same shifts, same year, a very different overtime bill, and the only thing that changed is the day the workweek begins.
The numbers that actually choose between two rotations
Pay is rarely the deciding factor. People choose rotations on how often they get a whole weekend, how long the longest break is, and how badly the switch from nights to days wrecks the following week. All three are countable, so this page counts them over 52 workweeks instead of describing them.
What the cards measure
- Average hours a week, and the hours in one full cycle behind it.
- Regular and overtime hours a year, at the threshold you chose.
- Full weekends off: a Saturday and a Sunday with no shift on either.
- Longest break in days, and the shortest rest in hours between two shifts.
- Weekend hours a year, so a pattern that "gives you weekends back" has to prove it.
- Night-to-day turns, the ones with no day off in between.
Exports that do not need an account
The calendar prints as a clean sheet with the controls and the prose dropped, one month per screen or all twelve on a wall-planner layout. The .ics file has one timed event per worked shift, so a crew member can import their own year into any calendar app and see the nights as nights rather than as a note they have to decode.
The CSV is one row per day and one column per crew, with the same D, N and O letters the calendar uses, so a spreadsheet can count anything: shifts per crew, weekend days, or the number of times a particular pair of people are on nights together. The share link carries the pattern, the start date, the crew and the workweek — nothing anybody typed, and no pay rate.
Questions this page gets asked
Is this shift scheduler free, and does it need an account?
It is free and there is no account, no email field and no payment anywhere on the site. The calendar is computed in your browser from the pattern and the start date; nothing is uploaded and there is no server-side copy of your schedule to lose.
Why do the default shifts start at 07:00 and 19:00?
Because a twelve-hour shift has to start somewhere and 07:00/19:00 is the convention most 2-2-3 and DuPont sites use. The .ics export uses those clock times, so a night shift appears as 19:00 to 07:00 the next morning. If your plant runs 06:00/18:00 the shift arithmetic, hours and overtime are all identical — only the calendar file times differ.
How do I know the rotation is actually covered every day?
The page checks it rather than claiming it. For each round-the-clock pattern the engine counts, for every day of the cycle, how many crews are on days and how many are on nights, and prints the result under the calendar. The unit tests assert the same thing for each preset so a future edit cannot quietly break coverage.
Can I model a 28-day FLSA work period instead of a 7-day workweek?
The overtime cards work in 7-day workweeks because that is the unit most payroll systems and most people actually get paid in. The § 207(k) toggle switches the threshold to 53 hours, which is the 7-day equivalent of the fire-protection 212-hour standard for a 28-day period, and the panel prints that 28-day figure next to it so the conversion is visible.
Does it handle 8-hour shifts or only 12s and 24s?
The eight built-in patterns are 12-hour and 24-hour rotations because those are the ones with named, published cycles. The custom builder takes any block sequence, and a sequence like 5D,2O with 8-hour shifts is a five-on, two-off week — the hours, overtime and weekend counts all work, only the shift labels stay on the twelve-hour clock.
What happens to my schedule if I close the tab?
It is gone from the tab, but the link in the address bar brings it back exactly: the pattern, the start date, the crew, the workweek start and the calendar view are all in the query string. That is also why the pay rate is deliberately not in the link — a URL people paste into a group chat should never carry a salary.
Every number on this page is computed from the pattern and the start date in your browser. The calendar is a model of the rotation, not a payroll record: check your own contract, workweek definition and any § 207(k) election with whoever runs payroll before relying on a figure.