← Shift roster builder

One person is off on Tuesday. Why did four people's weeks change?

When someone books a day off, the honest fix is small: find cover for their shift and leave everyone else alone. A scheduler that rebuilds the week from scratch does not know what "everyone else alone" means. It finds a roster that is just as good on paper and hands it out, and people who asked for nothing find their closes moved. Do that every time someone is off and the schedule stops being something staff can plan around.

Open the free roster builder

One café, one week with two days off

The roster builder's built-in invented example: a seven-person café, 32 shifts a week. We planned four weeks in a row. In week 3, Ana is off on Tuesday and Ben on Friday. Every week was built with the builder's exact check on, and each roster is the best possible under its settings.

Week 3, compared with the usual weekPlain rebuildKeep people on their usual shifts
Person-shifts changed going into week 3511
Changed again going back in week 4511
Hours left uncovered, whole month6262
Payroll, whole month$14,722$14,722

A "person-shift changed" is one person gaining or losing one shift. Ben's Friday close has to go whatever you do, and nobody free can take it (the week leaves it open). The plain plan now makes only the moves that needs: Ben takes Gus's Wednesday close and Gus takes the Wednesday and Thursday lunches, five changes, and the same five back. Since 13 November 2026 the planner builds each week toward the last week with nobody off and posts that if it is just as good, so it no longer swaps people nobody asked to move (it changed 15 and 15 before). The keep setting starts from its own usual week, where Ana has the Tuesday open, so it moves a chain: Ana's Tuesday open to Dev, Dev's Tuesday close and Gus's Wednesday close to Ben, the Wednesday and Thursday lunches to Gus and Ben's Saturday open to Ana. On this one week the plain plan is the steadier; the month-long runs below are the fairer test.

A month of scattered time off, five teams

One week can be luck, so we ran more. We used the builder's five invented teams (the café example and the café, salon, retail and clinic templates) and planned four weeks for each. Days off were scattered at random at three rates, five different draws each, giving 100 planned weeks per row. "Changes" counts person-shifts that differ from the week before. "Off the usual" counts, over all four weeks, the person-shifts that differ from the week with nobody off. "Forced" counts the shifts whose holder was off that day, which had to move whatever you do.

Days offSettingChangesForcedOff the usualHours uncoveredPayroll
2% of person-daysPlain rebuild36725476785$286,537
Keep usual shifts17026119785$286,423
4%Plain rebuild980651,098952$283,733
Keep usual shifts37864298952$283,542
8%Plain rebuild1,2181061,2711,147$280,042
Keep usual shifts5361074391,147$279,496

At every rate the plain rebuild moved many times more shifts than the time off forced. Keeping the usual shifts cut the week-to-week changes by 54% to 61%, and the distance from the usual week by 65% to 75%. Uncovered hours were the same in every one of the 15 comparisons. Payroll moved by less than 0.2%, and it went down rather than up: among rosters that cover the same hours, the keep setting happened to pick slightly cheaper ones. Every planned week in the run (1,600 across all rates and settings) was proven best under its settings. With nobody off, the setting changes nothing. The cost is time: a plan took 18% to 59% longer in this run, because the usual week is built first and a plan with the setting runs the planner's older, slower search order. (Re-run on 13 November 2026 after the plain planner learned to keep tied weeks steady: its changes fell, most at 2% days off, 617 to 367, and the setting still roughly halves them.) The rates are swept, not taken from real leave records, and the teams are invented.

Plan a month with your own time off

How it works

"Plan several weeks in a row" first builds your usual week, with the dated days off left out. Every planned week then scores a small bonus for each hour someone works one of their usual shifts. The bonus is a tenth of their wage an hour ("Yes, firmly" is a quarter). Leaving a shift open costs far more than any bonus, so the setting never leaves a shift open to keep someone in place. When two rosters cover the same hours for about the same money, it picks the one that looks like the usual week. The week after the time off, the usual week wins again, so people go back to their own shifts.

On a single week, load last week's roster CSV with "Carry over last week" and the same setting keeps people on last week's shifts. On the command line it is --keep-shifts 0.1, with --weeks or --last-week.

Doing it by hand

1. Write down the usual week once

Keep a copy of the rota you would run with nobody off. That is the week you change from and go back to.

2. Move only the shifts the time off touches

Cover the absent person's shifts with someone already free at that time. Only move a second person if nobody free can take it, and stop as soon as the gap is filled.

3. Go back the week after

Don't carry a one-off reshuffle into the next week. Start again from the usual week.

Questions

How do I keep a consistent schedule when someone takes time off?

Start from the usual rota and move only the shifts the person who is off cannot work, then put everyone back on their usual shifts the week after. A scheduler that rebuilds the week from scratch often finds an equally good roster that moves people who were not off. The free roster builder's "Keep people on their usual shifts" setting scores each usual shift kept, so the rebuild moves fewer of them without leaving a shift open.

Does keeping a consistent schedule cost more?

On the invented teams we measured, it left exactly the same hours uncovered and changed the month's payroll by a fraction of a percent. The setting is a small bonus per kept hour, far below the cost of an open shift, so it never leaves a shift open to keep someone in place.

Figures from the builder's own engine on invented teams (12 November 2026), with the exact check on. Your team's availability decides how much a day off has to move. Check the rules where you operate for any notice or premium owed when a posted schedule changes; see changing a posted schedule.