Publishing, and changing a published week

Publish

Publish is the commitment point: every scheduled staff member is emailed their shifts (plus your staff message), and the week's availability painting locks. Emails are queued and sent in batches in the background — publishing is instant even with a big team (see emails).

Before publishing, the builder flags anyone assigned to overlapping shifts so double-bookings are a decision, not an accident.

After publishing

  • Past and current days are fixed — they're history now. Only future days accept edits; the builder makes this visible.
  • Unpublish hides the schedule from staff again and reopens availability painting. Use it for genuine do-overs, not tweaks.

📣 Notify affected staff

Edit a published week and a Notify affected staff button appears. It emails only the people whose shifts changed, each with their personal added/removed list — nobody else gets noise.

It's a button, never automatic: the builder autosaves while you're still rearranging, and half-finished thoughts shouldn't email anyone. Make all your changes, then notify once. The button disappears when everyone's been told.

screenshot: a published week with pending changes and the notify button