-
Per-shop pay rates should come with the export, not be typed in
Shift Roster Builder now reads per-shop pay from a staff CSV or 7shifts. On 40 made-up weeks, imports matched hand-typed rates to the cent.
-
Ten open hours back on a 100-person week, by giving the slower proof less time
On the biggest weeks the roster builder spent 9 s on a proof that never finished. Giving that time to a cheaper LP left 376 open hours instead of 386.
-
Start the second LP where the first one ended: a warm start that cuts the pay floor's pivots up to sixteenfold
The roster builder's pay floor solved its LP from scratch after a sibling LP on the same rows. Starting from that basis: same bound, 107 pivots, not 1,860.
-
The city shop pays more: pricing a higher minimum wage into a two-shop roster
A roster that knows only each person's own wage understated payroll by about 5% on made-up weeks with a Seattle-rate shop. Pricing the floor cut 2.2%.
-
The drive is on the clock: what a two-shop roster costs when the trip is paid
A two-shop roster that ignored paid travel sent people across town 6 to 8 times a week, about 2.5% of payroll it never showed. Pricing it fixed that.
-
The gap was the search: an integer program, a missed roster, and re-solving one day at a time
A 60-person week sat $30.11 above its bound. HiGHS found a valid roster $0.36 above it; re-solving one day at a time closes most of that in 2 s.
-
The last seven dollars: why local moves can't finish a 60-person roster
A 60-person week sits $7 above a proven floor. Pair swaps, cyclic trades and an LP dive failed: the gap is one trade through 52 people on every day.
-
The swap the call-out check forgot, and why fixing it made a café worse
A quick call-out cover check never let the caller take a later shift. Fixing it sharpened the count, then made a short-staffed café's weeks worse.
-
Thirty minutes across town: the trip a two-shop roster never checked
On made-up split-shift weeks, half the days someone worked at both shops left them 30 minutes for the trip. A travel rule fixes it, sometimes at a price.
-
Twenty weeks was not enough: the call-out result that flipped at 200, and a price for the second call-out
A café roster that looked worse over 20 simulated weeks of call-outs was better over 200. A new check prices call-out pairs covered alone but not together.
-
Shift scheduling: the steadier plan's extra churn came from its anchor, not its weeks
Keep-usual-shifts plans moved 4-20% more shifts when solved column generation first. The cause was their anchor week. Fixed: same plans, 1.3-1.8x faster.
-
A scheduling move that never fired, and why we kept it
We taught the shift scheduler to free someone from two shifts to cover a call-out. Over 169 test call-outs it was possible 58 times and worth it zero.
-
Reading a 7shifts schedule without a CSV export
The free roster builder now reads the 7shifts API: UTC times put back on the location's clock, open shifts counted as needed, close shifts ended at closing.
-
Reading When I Work's shifts without a CSV, and why its times are easier than 7shifts'
When I Work publishes its API definition, and its shift times carry their own offset. A second scheduler now feeds the free roster builder.
-
What real Square and Toast exports taught a staffing tool
We had only read Square and Toast exports as made-up rows. Four real public files showed what a guessed header got right, and three places it did not.
-
Equally good weeks that are not equally good months
Which of several equally good weeks a staff planner posts decides what next week can do. A one-week look-ahead kept every hour and cut changes 71%.
-
A week of call-outs at a real roster's rates: keep the posted schedule, tell fewer people
At one firm's real call-out rates, rebuilding a posted week from scratch told 6 people a week of a change; keeping the posted shifts told 2.5.
-
Skipping the rebuilds a call-out doesn't need
Two exact short cuts and early stopping cut the call-out check from 419 rebuilds to 243 with the same schedule picked, so it now runs on the page.
-
Charging a manager for slack the team already had
A quick call-out risk check over-counted badly. Counting hand-over chains raised its precision from 53% to 67% and stopped 21 trades that bought nothing.
-
Five times faster on the sample week, and why the multi-week planner did not get the speed-up
Running the exact method before the search made fresh rosters 3.5x faster, same proven score on 80 of 80 weeks. Tied rosters still differ.
-
When nobody can cover, free someone who could
On a 20-person week where no single shift move helped, freeing a stand-in cut the measured call-out exposure from 113 to 68 hours for $35 of score.
-
Reissuing a posted schedule twice as fast, with the same schedule quality
Exact solver first, local search second: 570 posted-schedule reissues after a call-out ran 2.2x faster with the same score, changes and premiums.
-
The 25-hour gap that was never there
A 60-person week sat unproven at 300 open hours over a 275 h bound. The bound was the problem: a 1.3 s LP with clique rows proves the 300.
-
Three ties, not five: a roster counted twice, and a tie-break that changed nothing
Picking among tied schedules at every reissue of a posted week changed 0 of 983 reissues and took 14 times as long. A tie-counting bug turned up too.
-
Six equally good schedules, and the one a call-out hurts least
Equally good schedules differ by half in what one call-out costs. Picking the least exposed cut open hours 3.5% over 40 seeded weeks, with 16% more changes.
-
Splitting our slowest test file did nothing; remembering the last roster did
A 101 s test file looked like the long pole of a 149 s suite. Splitting it changed nothing: the suite was CPU-bound. Remembering repeat builds cut it to 132 s.
-
The walk that never arrived: half a call-out check spent searching for a roster another stage finds in 20 ms
The rota builder's call-out check now runs 2.3x faster: 570 rebuilds with the same open hours, and retail's wait drops from 10 s to 1.5 s.
-
Two real staff schedules: one store rewrote its week, one firm worked its roster
Our schedule importer had only ever seen made-up files. The first two real exports it met, it refused. Fixing that turned up two very different posted weeks.
-
Two shops in one sales file: planned together, the second shop vanished
Planned as one shop, a two-site sales export came up 12 person-hours a week short and staffed nobody at the second site. Now each site is planned alone.
-
What a rota that survives a call-out costs: $5.82, one shift changing hands
Pricing call-out risk inside the roster search: on one team it removed every open hour a week of sick calls left, for $5.82; on three of five, nothing paid.
-
A proof that froze the page: moving the roster build into a Web Worker
The exact check froze the roster page for 1.9 s, 5.8 s on a slowed CPU. In a Web Worker the longest frame gap is 50 ms, and Stop works.
-
A schedule search that didn't know when to stop
The scheduler kept trying to cover hours after it had already left open the fewest possible. A max-flow floor tells it when to stop; rosters are identical.
-
Clean down before or after you lock the door? It depends on who's closing
On a real bakery's till file, cleaning after close cost 7 staff hours a week against 20 in the last hour. With two people closing, it went the other way.
-
One day off, four people moved: keeping a rota steady
A rebuilt roster moves people who were not off. Scoring each usual shift kept cut week-to-week changes 56-72% on five invented teams, same open hours.
-
Minutes a ticket, minutes a euro: a labour standard from a till export
The roster builder now plans shifts from minutes a ticket, a euro and an item. On a real bakery, ticket-heavy plans were steadier week to week.
-
Seven million questions, one in eight answered yes
A shift roster builder asks 7.7 million times per week whether a person can take one more shift. Asking fewer times cut its build time by about a sixth.
-
Did the backtest cheat? Checking a scheduling win against what the shop could have known
Staffing a closed hour now counts as spare by default, so auto can plan from the last 4 weeks. 77% of the gain survives a hindsight-free check.
-
The proof was faster than the guess, so now it always runs
The roster builder's exact check now runs on every week. On 40 test weeks: never worse, better on 22, proven on 38, faster above 60 shifts.
-
Wiping tables doesn't scale with customers: fixed work in a staffing plan
Fixed minutes every trading hour, at opening and at closing. Added as fixed work, not a slower rate, the same extra work staffed the ends of a bakery's day.
-
Four weeks without a freeze: the roster planner moves off the main thread
Planning four weeks of rosters froze the page for 6.2 seconds. In a Web Worker the longest frame gap is 17 ms, with progress per week and a Stop button.
-
We re-ran our scheduling guides with a proof, and some of their lessons changed
Re-derived with proven-best rosters: a 10-hour rest gap costs a café nothing, two weekend requests are free, and tough shifts even out exactly.
-
Could the call-out rebuild have moved fewer people? An exact answer on 41 weeks
An independent integer program finds the fewest late changes after 41 call-outs. The default rebuild matches it on all 41 once the caller counts too.
-
Someone called out. Rebuild the week, but don't move the people who showed up
After a call-out, a rebuild that keeps the posted shifts made half the late changes of a free rebuild: premiums halved, same hours left open.
-
The roster was right; the proof was 2 hours short
Two call-out weeks the rota builder could not prove came down to arithmetic: with 3, 8 and 10 hour shifts, nothing leaves exactly 2 hours open.
-
Prove first, polish later: a 40-person staff roster checked in 10 seconds
Timing each stage of the roster builder's exact check found two passes the proof made redundant. 40-person weeks: 15-57 s to 6-12 s, all proven.
-
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.
-
Planning a month of shifts: the planner was solving the same week four times
A longer search budget proved no more weeks of a 4-week staff plan. The waste was rebuilding identical weeks; reusing them halves the time, same rotas.
-
The floor was free: proving two staff schedules in 1.7 seconds instead of 19
A staff scheduler took 19 s to prove two call-out weeks. Most of it went on finding a 3-hour floor that a 0.05 s LP plus whole-shift rounding gives.
-
Fifty-one changes where two would do: checking a scheduler against an exact solver
On a 60-person week, one call-out made our rebuild move 51 shifts. An exact solver showed 2 were enough. The missing move: trade up to the longer shift.
-
Three eighths of a shift: why a staff scheduler couldn't prove a roster it had already found
Two call-out weeks stayed bounded because the pay LP left part of an 8-hour shift open instead of a whole 3-hour lunch. One extra LP row proves both.