-
Ask the cheap question first: 8 seconds a solver spent on a solved week
Our shift roster solver spent 8 s on a lower bound that proved nothing. The next bound, which takes 0.1 s, proved the week. Trying it first saves the 8 s.
-
Berkeley's fair workweek, read from the city's FAQ: a 15-minute cut owes a quarter hour
Shift Roster Builder's team hub now prices Berkeley's predictability pay from the city's own notice and FAQ, which differ from Emeryville's on cuts.
-
In Evanston, an hour cut off a shift the night before can cost four hours of pay
Shift Roster Builder's team hub now prices Evanston's Fair Workweek. Four late changes at $18 an hour: $180 in Evanston, $108 in Berkeley, $63 in Chicago.
-
Fill the payroll service's template, not ours
Shift Roster Builder's team hub now fills the blank hours template your payroll service gives you, matching columns by name, instead of guessing each layout.
-
LA County's Fair Workweek is not the City of LA's: asked cover is exempt and short rests cost less
Shift Roster Builder now prices LA County's Fair Workweek from the ordinance text. Five late changes at $18 an hour: $99 in the county, $172.50 in the city.
-
Reading Deputy rosters when Deputy's API docs won't load
Shift Roster Builder now reads Deputy rosters straight from its API. The field names came from two open-source clients, checked against their own fixtures.
-
Two seconds past the budget: what a scheduler's last search stage buys
Shift Roster Builder's day sweeps run 2 s past a spent 20 s budget. Logged gain by gain on 23 builds, the last 1.5 s covered 2 of 11 open hours. They stay.
-
A floor that lets shifts split made one test search for hours nobody could cover
Our rota builder's open-hours floor let a 16-hour worker hold 10 h of one shift and 6 h of another. Requiring whole shifts halved a 62 s test, same answers.
-
A free time clock with PINs and a geofence that keeps only the distance
Shift Roster Builder's self-hosted time clock adds per-person PINs with a lockout and a site geofence that stores only how far a punch was from the site.
-
A scheduling test that waited 8 seconds a call for a phase it never checked
A shift-roster-builder test took 61 s because each call ran an 8 s exact search it never checked. At 300 ms it takes 13 s and catches the same faults.
-
Fair workweek pay lives in the change log, not the schedule
Shift Roster Builder's self-hosted hub now logs every change to a posted week and prices predictability pay under Seattle, Oregon or Chicago rules.
-
San Francisco and Emeryville pay schedule changes by the hour, not by the hours lost
Shift Roster Builder's team hub now prices schedule changes under San Francisco's and Emeryville's rules, read from the cities' own documents.
-
Two seconds for the repair: a pre-registered test turns a hunch into a default
On 350-400 shift weeks, giving Shift Roster Builder's exact repair 2 s of the budget covered more hours on 22 of 32 fresh builds that differed.
-
Bring your Square schedule across: a reader built from Square's own API definition
Shift Roster Builder now reads Square's scheduled shifts, jobs and locations, from saved JSON on the page or fetched with your own token on the CLI.
-
Every time reserve at once, from two builds a week
Shift Roster Builder's pay bound now gets 6 s past the budget instead of 1.5 s: it finishes 19 of 19 tries on 48 fresh weeks for 0.25 s more on average.
-
New York City counts schedule notice from Monday, not from the shift
Shift Roster Builder's team hub now prices New York City's fast food schedule-change premiums: flat $10 to $75 per change, counted to the week's first day.
-
No formula sizes the warm solve: a time gate replaced by a reserve
A warm-started LP in Shift Roster Builder took 29 ms to 14.5 s on similar weeks, so its size-based time gate went; a fixed reserve proves two more weeks.
-
Reading Oregon's scheduling law itself: two pricing mistakes and a standby list
Checked against ORS 653.455, Shift Roster Builder priced small start changes and short extra shifts wrong in Oregon; it now has the voluntary standby list too.
-
One close-then-open, three prices: Seattle, Los Angeles and Philadelphia
The same 8-hour rest between a close and an open costs $20, $80 or a flat $40 depending on the city. The team hub now prices all three.
-
The same call-out cover costs an hour's pay in Chicago and nothing in Seattle
Shift Roster Builder's team hub now sends a written offer to the whole team after a call-out and prices on-call shifts under Seattle, Oregon and Chicago rules.
-
The proof that came after the deadline: one in five big weeks skipped it
A step skipped once the 20 s budget was spent turned out to hit 1 in 5 big weeks. Two pre-registered tests later, it runs for 4 s more.
-
Less time for the repair, more for the walks: a pre-registered tie
Trimming Shift Roster Builder's repair reserve from 2 s to the 1.2 s it actually uses tied on 48 fresh builds: 7 better, 8 worse, 33 the same.
-
A time reserve with nothing to do, and the second and a half it gave back
Testing whether Shift Roster Builder's repair needs reserved time on 30-60 person weeks found it had nothing to fix, and was spending 1.3 s a build anyway.
-
The walk that ate the pay floor's time: a stage timeline for a 20-second budget
A stage timeline showed one random walk ran Shift Roster Builder's big weeks past their 20 s budget. A clock check inside it cut late builds from 15 to 5 of 48.
-
Twice the reserve, worse rosters: a pre-registered test that said no
Doubling Shift Roster Builder's repair reserve to 4 s left more hours open on 27 of 38 fresh builds that differed, because the repair stops on nodes, not time.
-
Sick leave balances from the punches a small team already makes
Shift Roster Builder's self-hosted hub now earns paid sick leave or PTO per hour worked, at the manager's own rate and caps, and keeps it past the punch trim.
-
The last untimed stage: a 40 ms pay polish and a pre-registered test
Shift Roster Builder's pay polish ran 25-44 ms past the 20 s budget on 8 of 48 builds. A deadline inside it took that to 0, with pay and open hours held.
-
The repair that ran past its deadline: checking the clock inside the search
Shift Roster Builder's cover repair read the clock only between rounds. Reading it inside them took repair overruns from 6 of 48 builds to 0, same rosters.
-
A team schedule page that runs on ten milliseconds
Our staff scheduler's team page needed a $7 server. Now it deploys free to your own Cloudflare account: the roster builds in your browser, the Worker checks it.
-
A time clock for a team page that costs nothing to run
The self-hosted team page now has a time clock: staff punch on their phone, managers see hours against the schedule and get a payroll CSV.
-
Nevada overtime: the workday is not the calendar day
The free team hub's timesheet now reads Nevada's 24-hour workday and the meal-period rules of 13 more states, from the statute and the DOL tables.
-
A cache that was always right and almost never useful
I cached pair searches in Shift Roster Builder. The cache was exact, and it hit 212 times in 283,507 lookups. One number explains why.
-
A scheduling check whose answer depended on the order it searched
Shift Roster Builder's second-call-out check gave different exact answers in different search orders. The definition that fixed it, and why it stays exact.
-
Best moves first didn't pay, and a profile that says why
Trying the most promising moves first in a shift scheduler's search: faster on one week, slower on another, worse on a third. A profile shows why.
-
The bound that also fills shifts: letting an LP steer a local search
On 350-400 shift weeks, Shift Roster Builder's clique LP now steers the cover passes too: fewer open hours on 14 of 30 paired builds, 3 worse.
-
Two of every three repair rounds could never win, and a max flow knew it first
A max-flow floor per neighbourhood let Shift Roster Builder's exact repair skip hopeless rounds. It closed 484 open hours where the old search closed 217.
-
A cleaner count that bought nothing: the order-free call-out check, played
A risk count that doesn't depend on search order made rosters that opened no fewer hours when simulated call-outs hit them, and moved more people.
-
Paying for the second call-out: what it buys on bigger teams
Over hundreds of simulated weeks of sick calls, pricing second call-outs left 2-11% fewer open hours on three of four bigger teams.
-
Stop the walk when the answer is already no
The second-call-out price spent its time proving moves it would refuse. Two exact cuts halved it or better; an exact cache that looked clever lost.
-
The pairs it gave up on: when a search budget counts as a finding
A two-call-out check gave up after 500 steps and called the pair a clash. Run to the end, most were not. The priced pass now checks its moves.
-
The repair that never ran, and the guide that didn't help it
Steering Shift Roster Builder's exact repair with an LP: the repair barely ran on big weeks, and the LP picked people no better than random.
-
A time cap that holds, and why it didn't buy what I wanted
The second-call-out price in Shift Roster Builder now stops at a time limit and keeps the moves it made. On the bigger weeks the moves worth having came last.
-
The 40-hour line is not California overtime: our free time clock now prices the week
The team hub's timesheet flagged hours over 40. It missed California daily overtime, double time, the seventh day and meal premiums. Now it applies them.
-
A 1.7x faster loop, and the flaky test it did not fix
One shift-roster test failed only on a busy machine. The profile pointed at a loop that went 1.7x faster, but the fix was a time budget that was too tight.
-
A time budget checked between rounds is not a budget
The roster builder's column generation overshot its time share by up to 1.2 s because it read the clock between rounds. The fix was easy; the payoff was not.
-
Two shops, one staff list: what pooling people is worth
Shift Roster Builder plans several shops from one staff list. On 40 made-up weeks, letting people work at both shops left 55% fewer hours open.
-
Shift scheduling: a 60-person week's proof gap went from $20,010 to $30
The roster builder proved a 60-person week's open hours but counted the whole pay bill as unproven. Pricing its clique LP cut the gap to 0.16% of payroll.
-
A cheaper map for the roster search: two more shifts filled
When the pricier pay LP no longer fits the time budget, the open-hours LP now steers the scheduler. It filled one or two more shifts on 2 of 10 test weeks.
-
Her own rate downtown: per-person site wages in a two-shop roster
One line on a staff row now gives a person their own rate at one shop. On made-up weeks, ignoring those rates understated payroll by 2 to 4%.
-
Let the lower bound steer: the LP that proves a roster's cost also helps find a cheaper one
Steering a staff schedule search with the LP behind its lower bound halved the remaining pay gap and filled open shifts on 3 of 9 test weeks.