For Managers
Editing a published week
Changing a week that is already live: where the override editor is, and which scope to give the change.
A published week changes forward, on the live calendar, one block at a time.
Do it
- Open the calendar at the week to change.
- Select the block to open the override editor.
- Add a worker, or remove the one on it.
Choose the scope, then confirm. The worker is notified either way.
| Scope | What it changes | Pick it when |
|---|---|---|
| This week only | Only the week you are viewing. | A one-off: illness, an event, a trade. |
| This week onward | This week, and that weekday and time in every later week. | The pattern itself is wrong. |
What you’ll see
Removing a worker leaves a vacant seat, claimable in Open Shifts and escalated if the desk would be empty.
Rules that apply
- Either scope works on a shift of any age, past or underway, because an override is a correction and not a claim. See How a shift gets covered.
- An override cannot touch a float-committed seat, because the floater was promised it. Decline or void the float first. See Floating: overview.
- The 40-hour hard cap is never bypassable: it refuses the assignment. The 20-hour school-year cap only warns. See Hours, caps, and attribution.
- An SM edits their own house only. HM, BA, RSM, and Administrator override any house, on the authority that lets them publish. See Roles and the duty hierarchy.
If it goes wrong
The editor refuses the worker. The seat is float-committed, or the worker would cross 40 hours.
An onward change hit weeks you did not mean to. Run a second onward override where the old pattern resumes.