Publish and republish
Publishing is the moment a week stops being yours and becomes the answer to when do I work. Two questions come with it, and they are different questions.
- Who this is for
- A manager or the chief manager, on the website.
Step by step
Publish the schedule
Publish schedule asks who can see it: each person only their own shifts, everybody the whole schedule, or the whole schedule for anyone holding a qualification you name, which is useful for shift managers. Everybody always sees their own shifts.
Everybody is told
Publishing tells your staff the week is out and how many shifts they have on it, in their own language, through whichever channels they have left switched on.
Change something afterwards
Edit the week as usual. Publish changes then asks who should hear about it again: only the people whose shifts changed, or everybody.
When there is nobody to target
If nothing has changed since the last publish there is nobody to tell about a change, so publishing again updates everyone. Weeksort says so rather than offering a choice it cannot honour.
Taking a week back
Unpublish takes the schedule back from staff and tells them the shifts they were shown are no longer final. Every week published together with it is taken back too, and preferences stay closed — unpublishing never reopens ranking.
What your staff actually hear
A message that names the week and says what moved. A change to a draft nobody has seen notifies nobody, which is why the question is only ever asked about a week that is already out.