Fixing a call-out without reshuffling 60 people

Rebuilding after one call-out moved 1,623 shifts over 24 call-outs on 60-person weeks. Keeping posted shifts and starting from them cut it to 76.

Someone calls out for tomorrow. You mark them off and build the week again. The scheduler finds a good roster, but it isn't trying to find one close to the roster you already posted. So it moves other people around, and under a predictive-scheduling rule each of those moves can owe a premium.

Earlier today Shift Roster Builder learned to reissue a posted week: shifts that have already started stay put, and every posted shift someone keeps counts in the score. On two invented cafés that halved the changes to other people. This run checked whether the gain holds on bigger teams.

Bigger teams, bigger reshuffles

Here are changes to people other than the caller, summed over the call-outs (Wednesday onward, with the change made at 5pm the evening before):

TeamFree rebuildKeeping posted shiftsPlus the new kept start
4 built-in templates (56 call-outs)1627373
20 people (24)2532626
30 people (24)5075050
40 people (24)60312440
60 people (24)1,62397376

Every column leaves the same number of hours open. Keeping the posted shifts never cost coverage.

A free rebuild gets worse as the team grows: at 40 people, one call-out moves about 25 other shifts on average. Up to 30 people, keeping the posted shifts brought that down to one or two. At 40 and 60 people it didn't work as well. Two Wednesday call-outs on one 40-person week still moved 37 and 39 shifts, while their neighbours moved 7 or 8.

Why, and the fix

The search builds every roster from scratch. On a small week the exact check then proves the best roster, and the best roster is the one close to what you posted. On a big week the exact check runs out of time, so what you get is whatever the quick search found, and it started nowhere near your posted roster.

So now, when there's a roster to keep, the builder also starts from that roster. It gives each shift back to whoever had it if the rules still allow that, fills the gaps as cheaply as it can, then polishes. It keeps whichever start scores better. On those four 40-person Wednesday reissues the changes fell from 91 to 7, with the same open hours and $136 less pay. At 60 people the total fell from 973 to 76, about three shifts per call-out, and payroll fell too. Below 40 people nothing changed, because those weeks were already proven.

What we can't tell you

These teams and weeks are invented, and the seeded weeks sample four call-outs a day. Whether a premium applies to you, and what it is, depends on your local rules. You enter those yourself, and the tool doesn't check any ordinance. On the biggest weeks the exact check still runs out of time on half the reissues, so those rosters are good, not proven best.

The code, tests and full output are in the repository (eval/reissue-scale.mjs). The tool is free, runs in your browser and needs no sign-up. Its numbers are estimates from your own team and rules, not legal or staffing advice.

All writing · More in Tools and projects · More on Shift Roster Builder · All tools and research