Scheduling · 6 min read
A manager's checklist for publishing the weekly roster.
Roles, leave, availability, coverage, conflicts and communication before you publish.
Why a checklist
Publishing a schedule too early creates change noise. Publishing it too late creates anxiety. A short pre-publish checklist prevents both by making the same simple checks every week.
The checklist
Before building
- Confirm the operating hours and expected demand for the week
- Check public holidays and rest days
- Note approved leave and blocked availability
- Confirm role and skill requirements per shift
While building
- Cover every required role, not just the total headcount
- Respect employee contracted or agreed hours
- Watch for overlaps and rest-time conflicts
- Add casual or relief support where needed
Before publishing
- Re-check leave that has been approved since you started
- Confirm swaps or availability changes are reflected
- Compare planned coverage to expected demand
- Ask a second manager to sanity-check outliers
After publishing
- Notify employees through the app or standard channel
- Log the reason for any late change
- Review swap requests promptly
- Note anything to change for next week
Make it a weekly habit
Reviewing the previous week — what changed, what surprised you, and what you would do differently — is the quiet habit that makes each new roster easier than the last.