-
A four-stylist salon week leaves three chairs empty, and the schedule says which
A worked salon week: 13 of 16 chair-shifts covered for $1,466, and the three open ones point to a Saturday hiring decision.
-
Paid rest breaks, staggered so the floor is never empty
The free shift roster builder now suggests paid rest breaks of the length and spacing you enter, placed around meal breaks and staggered so someone stays on.
-
Seven days in a row can hide across the Sunday-Monday line
A seven-day check inside one week misses Thursday to the next Wednesday; the roster builder's --weeks now reports runs across the boundary.
-
Leaving a paid scheduler: staff import for the free roster builder
The roster builder now reads a staff export from another scheduling app, so a switcher skips retyping names, rates and hour limits.
-
Switching schedulers: turn last month's published schedule into the shifts to cover
The shift roster builder now reads a published-schedule CSV and writes the shift-requirement lines, counting people per weekday, time and position.
-
The 14-day scheduling window moves across your week
On an invented cafe the same call-out owes $0 in premium 15 days out, $50 to $88 at 10 days and $68 to $174 at 3 days, because notice is counted per shift.
-
The days-in-a-row limit now crosses Monday
The roster builder started every week at zero days in a row; a new streak cell carries Thursday to Sunday into Monday so the limit holds.
-
What a daily hour cap and a days-in-a-row limit cost a cafe schedule
On the roster builder's invented seven-person cafe, a 9-hour daily cap leaves one more shift open, and a 6-hour cap is a typo that empties 27 of 32.
-
Who should have had that shift? A seniority report for the roster builder
Shift Roster Builder now takes a seniority rank per person and lists every shift a more senior person could have taken without breaking any hard rule.
-
A call-out after you posted the schedule: rebuild the week or change one shift?
On an invented seven-person cafe, rebuilding the whole week after one call-out moved 4 to 10 other people's shifts and often still left the shift open.
-
Your self-hosted team schedule can now ping your own Slack, Discord or phone
The free shift-roster server can post to a webhook you own when staff send a call-out, trade or time-off ask, and when you publish a week.
-
Shift roster builder: one click to cover a call-out
The self-hosted manager page now lists who can cover a called-out shift and gives it to them with one button.
-
Shift roster builder now prices split-shift premiums
The schedule notice flagged split shifts but never said what they cost; with your local minimum wage it now does.
-
When only a third of your crew can close, how fair can a roster be?
We measured the shift roster builder's fairness setting on crews where most people cannot work late: it helps by a third, and availability sets the limit.
-
Why a better cut cannot close this scheduling gap
We tested four linear relaxations of a shift-scheduling problem. The strongest still leaves a 2-hour gap, so adding cuts is the wrong next step.
-
Shift roster builder prices late schedule changes from the command line
node cli.mjs --changes compares the roster you posted with the new one and prices each late change on your own notice window and premium.
-
Covering more hours can leave more shifts open: a roster builder measurement
A repair step cut a sample café's uncovered hours from 19 to 15 but raised open shifts from 3 to 5, so shift-roster-builder keeps it off.
-
Fewer empty hours or fewer empty shifts? Now you choose
Shift Roster Builder can now be told which gap hurts more when it cannot cover everything: on the sample café, 15 hours over 5 shifts or 19 hours over 3.
-
A schedule builder that lets you say what an empty shift costs
The shift-roster-builder's repair step takes an openShiftWeight: at 0 the sample café leaves 15 h open across 5 shifts, at 100 it leaves 19 h across 3.
-
Fewer open hours or fewer open shifts? A scheduler has to pick
Shift roster builder's exact repair covers 4 more hours on the sample cafe but leaves 5 shifts open, not 3. A tiebreak shows the trade-off is real.
-
The shift roster repair search now gives the same roster on every machine
shift-roster-builder's open-hours repair stopped on a 6 second clock, so a slow laptop could print a different week. It now stops on a work budget.
-
Telling the team their shifts, without running a text-message service
The self-hosted shift scheduler now hands the manager a Text and an Email link per person, so a published week reaches staff with no paid messaging.
-
The roster builder now finds the last uncovered hour
A solver check showed the shift roster builder leaving 1 to 2 hours open on half of 12 test weeks. A coverage-only search pass now closes all of them.
-
Proving the fewest open shifts: branching on the price closes 5 of 7 gaps
The shift roster builder now proves its roster leaves the fewest possible hours open on 10 of 12 seeded weeks, up from 5, against an independent solver.
-
Our scheduling guides quoted numbers the engine no longer produced
Every guide page on shift-roster-builder quotes figures from its own engine, and a test re-derives them from the sample cafe. Two of those tests had been...
-
Checking a shift scheduler against an independent solver found a search gap, not a proof gap
Eight seeded 10-person, 28-shift weeks, checked against HiGHS: two weeks left more shifts open than needed, and more search steps fixed one.
-
Closing the last open hour in a staff roster by solving a small piece exactly
The shift roster builder's search now repairs open hours by freeing three people's shifts and solving them exactly, matching the integer-programming optimum.
-
An off-the-shelf solver says our shift scheduler leaves hours on the table
An open-source ILP solver proved optimal rosters on 12 seeded weeks in under a second; our shift scheduler missed the best by 1-2 hours on five.
-
A longer ejection chain did not close the last hour of a staff roster
Adding a three-person ejection chain to the roster engine left 62, 64 and 63 open hours on the hard week, so the move was removed and the benchmark kept.
-
How big a staff schedule can we prove optimal? Measured from 6 to 12 people
A shift-roster solver that proves its answer: 8 of 8 small weeks proven, 0 of 8 at 10 people and up. The table, and what is still open.