The staff scheduler started as one page: give it your shifts, your people, and your coverage requirements, and it hands back a roster. That’s still true. What changed this week is that the one page became thirteen — a nurse scheduler, a firefighter scheduler, a police scheduler, a warehouse scheduler, and nine more — all running the exact same engine underneath. Same solver, same rules, same workbook format. Different pages. Here’s why I did that instead of leaving well enough alone.
The lesson I already learned the hard way
I’ve made this mistake before. The routing tool has a page called /datos — a second theme on the exact same vehicle router, built for one client, that turned out to be a near-duplicate of the homepage in every way Google cares about. It got noindexed as a duplicate, because it was one. Same tool, same copy with the nouns swapped, no reason for two pages to exist instead of one.
So when I sat down to write the copy for a nurse scheduling page and a police scheduling page off the same engine, I gave myself one rule before I wrote a word: if a paragraph would read exactly the same with the nouns swapped, it doesn’t earn its own page. Merge it, or don’t write it. That rule turned out to be a genuinely useful filter, because it forced me to actually go find the thing that’s different about nurse rostering versus warehouse shifts versus a fire station — and it turns out there’s a lot, once you go looking instead of assuming “24/7 coverage” is one problem wearing different hats.
One engine — supply, demand, and a flag called concurrent
None of this changes the model itself, which I wrote about when I generalized it from one client’s rules to any team: demand for coverage, supply of people who can fill it, over buckets of time, with a concurrent flag that says whether a role is a body of its own or just a qualified person already on shift. A charge nurse, a company officer, a night auditor, a forklift-certified picker — structurally the same idea every time, and the reason the engine didn’t need to change at all to cover thirteen industries.
What changes is which rules actually bind, and that’s a genuinely different answer per setting. A few examples, because the differences are the whole point:
- A firefighter’s 24-hour tour plus a 24-hour rest rule means the earliest someone can come back is 48 hours after their last shift started — the roster isn’t rigid because of the headcount, it’s rigid because of that one piece of arithmetic.
- A correctional facility isn’t distributing work across available people at all — it’s proving a fixed set of posts can be manned every hour, and the number that actually matters is the relief factor, not the headcount.
- A distribution center‘s demand isn’t flat like a factory line — inbound and outbound run on different patterns, weekends aren’t the same as weekdays, and peak season can double the requirement for eight weeks. Getting the demand grid right matters more than any parameter on that page.
- A contact center is actually two different problems wearing one name, and the page says so up front: if your call volume rises and falls through the day, you want the slot optimizer, not this one. If your desk runs fixed shifts around the clock, you want this one, not the slot optimizer. Getting that distinction wrong is the single most common way people land on the wrong tool on this site.
None of those are cosmetic differences. Each one changes what the page has to explain before the sample data means anything, which is exactly the test I set myself — nurse rostering and correctional rostering use the identical concurrent flag, but what it’s protecting (a charge nurse present on the floor vs. a compliance-mandated post) is not the same conversation, and treating them as one page would have flattened both.
The other pattern running through all thirteen: saying what it doesn’t do
Writing thirteen pages for one engine is an easy way to oversell it, so I tried to do the opposite — every page names its limits as plainly as its features. The transit driver page opens by admitting it only does the third of three transit scheduling problems (it rosters drivers onto duties you already built — it does not turn a timetable into duties, which is a different piece of software entirely). None of the pages claim to know your labor law: rest hours, consecutive-day caps, and overtime rules are all fields you set from your own regulations, not constants I baked in, because the U.S. has no federal minimum rest requirement and states disagree with each other, and FLSA’s 7(k) exemption for fire and police is its own can of worms I’m not going to pretend to compute for you — check the Department of Labor’s Wage and Hour Division directly for the current rules if that applies to you.
That honesty runs both directions. The correctional officer page tells you it will not schedule mandatory overtime for you — it reports the shortage and leaves the holdover decision where it belongs. The call center page tells you flatly there’s no Erlang C calculation hiding in it; converting call volume and handle time into a headcount happens before you ever open this tool, not inside it. I’d rather a page turn away the wrong use case in the first paragraph than have someone build a roster on a false assumption and find out during a night shift that goes unstaffed.
What I don’t know yet
Here’s the honest part for anyone who’s read this far: I picked these thirteen slugs and titles by guessing at the phrase a nurse manager or a fire captain would actually type, not from keyword data — my Ahrefs account is sitting at zero API units this month, and these pages are five minutes old as far as Google Search Console is concerned. So the ranking potential of every one of these pages is currently a guess, not a plan. I’ll check Search Console in about eight weeks, and whichever pages never earn an impression get cut or merged back into the general one rather than left as dead weight. If you run a 24/7 operation in any of these thirteen categories, I’d genuinely like to hear whether the page for your setting actually matches how the work happens — that feedback is worth more to me right now than any keyword tool.
All thirteen pages, plus the general one, are free and need no signup — paste your data in, or start from the sample loaded on each page. If you don’t see your setting in the list, the general 24/7 shift scheduler is the same engine with nothing industry-specific assumed, and it’s the right place to start if none of the other twelve quite fit.
Things that I use, like, and am affiliated with:
Mint Mobile offers great cell phone service for $15 flat, get $15 off using the link. Get discounted phones with service activation and no contract.
I never spend money before I check Mr Rebates or Rakuten to get cashbacks, rebates, discounts, coupons or cheaper gift cards.