Create rotating shift schedules for teams with day, swing, and night shift patterns.
A shift roster is a coverage puzzle. Every day needs day, swing, and night staffing, and the teams filling those shifts should carry the burden evenly over time. This tool takes your crew sizes, shift times, and a rotation cadence, then returns a week-by-week schedule that cycles each crew through the ladder: day to swing, swing to night, and back around. The thing most people miss is arithmetic: three 8-hour crews covering 24/7 means every crew works all seven days, about 56 hours a week. The tool shares the night shift fairly, but it cannot manufacture days off. A fourth crew or longer shifts does that.
A concrete input and expected output from the current implementation.
Input
18 people split into 3 crews of 6. Shifts: Day 07:00-15:00, Swing 15:00-23:00, Night 23:00-07:00. Rotate forward each Monday, starting June 1, 2026. Week 1: Crew A on days, Crew B on swing, Crew C on nights.
Expected output
Week 1 (Jun 1-7): Crew A = Day, Crew B = Swing, Crew C = Night. Week 2 (Jun 8-14): Crew A = Swing, Crew B = Night, Crew C = Day. Week 3 (Jun 15-21): Crew A = Night, Crew B = Day, Crew C = Swing. Week 4 (Jun 22-28): the cycle repeats Week 1.
Forward rotation moves each crew one step later in the ladder each week, so every week still has exactly one crew per shift and the pattern repeats after 3 weeks. Each crew gets one week on each shift per cycle; June 1, 2026 falls on a Monday, so the week boundaries line up cleanly.
The tool assigns shifts to crews, not to individuals, and each period rotates every crew one step forward in the ladder: day to swing, swing to night, night back to day. With 3 crews and 3 shifts, every period has exactly one crew on each shift, so coverage never gaps, and a full cycle takes 3 periods.
Shift times carry through the rotation, so the output shows concrete clock hours, not just shift labels, and weekly totals follow directly: an 8-hour shift staffed 7 days is a 56-hour week per crew member. That is why 24/7 coverage with 3 crews leaves no full days off; adding a relief crew is what breaks the week up.
Because 8 weeks is not a multiple of the 3-week cycle, the printed window ends mid-rotation: one crew logs 3 night weeks while another logs only 2, even though the underlying rotation is even. Extend the schedule to a multiple of the cycle, such as 9 weeks, and every crew lands on nights exactly 3 times.
Only if coverage does not run seven days. The rotation staffs every day it is given, so 24/7 coverage means each 8-hour crew works all 7 days, about 56 hours, and no rotation fixes that on its own. If weekends off matter, plan a fourth crew, 12-hour shifts, or reduced Saturday-Sunday coverage and enter that as the pattern.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Create customizable checklists with groups, due dates, and priorities for any project.
Design a printable daily planner with time blocks, goals, and priority sections.
Measure your typing speed in WPM and accuracy with real-time feedback and stats.
Pomodoro timer with built-in ambient noise (rain, cafe, forest) generated via Web Audio API oscillators.
Stay focused with a customizable Pomodoro timer featuring work and break intervals.
A precise stopwatch with lap tracking, split times, and exportable results.