Where to Start Reading
Four common situations and the route through these notes that suits each, plus the three to read if you only have time for three.
Reference · Reference
Fifty notes is more than anyone needs at once. These are the paths that fit the common situations.
The rota is late and constantly changing
Publishing in advance, and the achieved-notice measure.
Changing a published schedule.
How long the rota takes to build, which is usually the cause.
Forecasting demand, for the buffer.
Where to start, for the first quarter.
Coverage is fine and people are unhappy
Who gets the awkward shifts.
Who gets the hours.
Closing then opening.
Shift length.
Scheduling and turnover, for the number that funds fixing it.
You operate in a covered jurisdiction
Fair workweek rules, for the shape and the exceptions.
Predictability pay.
The estimate given at hire.
Records to keep, which is where enforcement cases are decided.
Outside the United States, if you also operate elsewhere.
A purchase has been proposed
The question to ask first.
Choosing scheduling software.
When the rota is generated.
Reading a vendor claim.
What scheduling cannot fix, which shortens most specifications.
If you read only three
What a schedule is actually for, because the tension between cost and stability is the whole subject.
Publishing in advance, because it is the largest improvement for the least money.
The question to ask first, because it makes explicit who is carrying the uncertainty.
A closing note
Nothing here is legal advice, and the notes say so where it matters. Scheduling rules vary substantially by jurisdiction and this area has moved considerably in recent years.
No industry savings figures are quoted, deliberately. Every number worth having is one you produce from your own records, and the notes say how to produce each of the six that matter.
If you have ten minutes
The shortest useful route.
Measure your achieved notice period, which takes one query.
Count employer-initiated changes per published shift, which takes another.
Those two numbers tell you whether you have a scheduling problem, how large it is, and which direction to start in — which is more than most operations discussing this subject have established.
Reproduce the workflow
For another way to make this requirement testable, review browse the integration directory. Treat it as a starting point, then reproduce the case with real roles, sites and exceptions.
More in this section