Bulk Changes

Most scheduling changes aren't one chip at a time — the start time moves for the whole day, a role needs two more people, or a worker goes on leave and has to come off every shift for the next month. The board has two families of bulk action: day-level edits (change a day) and fleet actions (change one resource across many days).

None of them touch past days, and the ones that span many shifts preview what they will do and report what they skipped.

Day-level edits — the ⋮ menu

Each order × day cell has a ⋮ menu (also available on cards in Card layout):

Edit all start/end times. Set the shift window for the day's requirements in one go. By default it covers every row on that day; select specific roles first and the dialog scopes to just those, saying "for 3 of 7 rows". Rows already at the target time are left alone, and the dialog tells you what it excluded. This retimes the day as an exception — the order's usual pattern is unchanged, and the day is badged Retimed on the board.

Edit all role quantities. Set how many of each role you need on that day. A role can be turned off for the day entirely. Reducing below what's already allocated is flagged as over-allocated rather than silently unallocating people.

Add role. Add a role to that day only. The picker offers the roles already on the order first, then any labour role, plant class or operator pairing. If the order already carries the role but it doesn't run on that day, adding it turns the day on as a one-day exception rather than creating a second card — you can still choose to add it as a separate card if that's what you meant.

The menu is disabled on past days and on days outside the order's date range, and says which it is.

Fleet actions — one resource, many shifts

From a placed chip (or the resource's sweep menu) you can act across a scope:

Replace across a scope. Swap one resource for another everywhere in scope — the leave/handover action. The dialog previews the shifts affected (expandable to the full list) and reports anything skipped, such as a day where the replacement is already booked.

Remove across a scope. Stand a resource down across the scope. Same preview, same skip reporting, and the summary is confirmed before anything is written.

Operator pairs sweep together. When the resource is paired on any of the shifts in scope, the dialog offers to take their partner too — on by default, since the chip you clicked shows both halves. The partner is worked out per shift, not per resource: the same operator can be on a different machine tomorrow, and that machine can belong to someone else on the days this resource isn't working. Each half keeps its own dates, so sweeping a worker booked Mon–Fri paired with a machine booked Mon–Wed removes the worker Mon–Fri and the machine Mon–Wed. A pair leaves together or not at all — if either half is in the past or holds a filed timesheet, both are withheld and reported once.

Undoing a sweep. A fleet remove can be undone from its toast, which stays up long enough to review a change spread across days and orders you can't all see. Undo re-books only what the sweep actually deleted, and puts operator halves back together as a pair. It isn't offered where it couldn't be faithful — an untimed shift can't be recreated, and a shift whose filed timesheet you confirmed detaching can't be re-linked to it.

Both actions stop at today: upcoming means today forward, and worked days are never rewritten. A scope covering an unusually large number of shifts is offered but not selectable — split the work rather than writing thousands of rows in one go. Where a shift in scope already has a filed timesheet, you're warned about the consequence for that timesheet before you confirm — see Forward-Only Planning.

Order-level changes

Changing an order's own resourcing — its pattern, dates, quantities and times — happens in the order's resource editor, not on the board, and follows the same forward-only rule. See Forward-Only Planning.