Most scheduling software sees your team as a list of names and your week as a blank grid. Fill the grid, publish, done. That approach produces schedules that are technically complete and practically mediocre. ShiftWiz operates differently. The engine scores every generated schedule across eight distinct dimensions, and it runs thousands of iterations to push that score as high as possible before it hands you anything. Here is what those eight dimensions actually are.
1. Weekend shift fairness across the past six weeks
Not just this week. Six weeks. When the engine builds a new schedule, it looks back at who has worked Saturday opens, Saturday closes, Sunday opens, and Sunday closes over the entire recent window. If one employee has hit three weekend closes in the last six weeks and another has hit zero, the engine skews the new week accordingly. No manual tracking. No spreadsheet. The history is always there and always factored in.
This is the category that most managers think they are handling manually and most are not. The pattern drifts without anyone noticing. ShiftWiz catches the drift before it becomes a problem.
2. Closing-to-opening rest time
A clopening is when someone closes at 10pm and opens at 6am the next morning. It is a documented driver of burnout. ShiftWiz enforces a minimum of 8 hours between any two consecutive shifts for the same employee, and it does this automatically at constraint evaluation time, not as a manual checklist item. The engine will not generate a clopening unless it has no other option and you have explicitly configured it to allow exceptions.
3. Pending time-off requests, not just approved ones
This is a detail that matters more than it sounds. Most scheduling tools block approved time off from being scheduled over. ShiftWiz blocks pending requests too. If an employee submitted a time-off request for Saturday and it has not been reviewed yet, the engine will not assign them to Saturday. You review it, approve or deny, and the schedule reflects reality. You do not generate a schedule and then discover three conflicts when employees start asking questions.
4. Swap history and revealed preferences
Every time an employee successfully swaps off a shift, ShiftWiz notes the pattern. Over time, it builds a picture of which shift types each person consistently tries to avoid. The engine uses that history to stop assigning those shifts to them in future schedules before they even have to ask. Fewer swap requests. Fewer conversations. A schedule that reflects what people actually want to work, not just what is theoretically possible.
5. Skill and certification coverage per shift
Every shift can require specific roles: barista, shift lead, kitchen, front-of-house, certified trainer. ShiftWiz knows which employees hold which certifications and enforces coverage requirements before it finalizes any shift assignment. If your Saturday morning peak requires a certified trainer on the floor, the engine guarantees one is there. It does not leave that to chance or to a last-minute phone call.
6. Individual hour targets and the labor budget ceiling
The engine tracks two numbers for every employee: their target weekly hours and their contract maximum. It tracks one number for the location: the total labor budget for the week. Every shift assignment it makes is evaluated against all three. It tries to get everyone to their target without busting anyone over their max and without pushing the total above budget. When trade-offs are unavoidable, it prioritizes coverage first, then fairness, then budget efficiency. The logic is explicit and consistent, not a manager's judgment call on a Sunday night.
7. Minor labor compliance
For employees flagged as minors, ShiftWiz enforces the applicable caps automatically: 18 hours per week during the school year, 3 hours per school day, no shifts past 10pm on a school night. These are not optional reminders. They are hard constraints built into the constraint evaluation layer. The engine will not assign a minor to a shift that violates them.
8. Demand forecasting from historical sales data
For locations that connect sales data, ShiftWiz forecasts demand by day-of-week and time window and adjusts staffing targets accordingly. A Tuesday that historically runs at 60% of Saturday volume gets scheduled at 60% of Saturday staffing. A Saturday before a holiday that typically spikes 20% above baseline gets the extra coverage. The schedule is not just fair and legally compliant. It is calibrated to actual expected business volume.
These eight dimensions work together simultaneously. The engine is not checking them in sequence and stopping when one fails. It is scoring the entire schedule across all eight at once, running thousands of candidate schedules through simulated annealing, and surfacing the one with the highest combined score. That is not something a human can replicate manually in any reasonable amount of time.
Why this matters
Each of these dimensions in isolation is something a careful manager might track manually some of the time. Tracking all eight, across a full team, every single week, without ever losing track of the six-week history or misreading a pending request, is not realistically possible without software that is actually built to do it.
Most scheduling software is not built to do it. ShiftWiz is.