Changing, moving and copying many shifts at once

Next week looks like this week, the crew changed, or the whole Thursday slipped a day. Rather than opening shifts one by one, tick them in the List and change them together.

Ticking shifts

In the Schedule's List, tick the shifts you want. Only shift rows have a tick — routes are edited on their own (see Editing or cancelling a published route). A bar appears above the list:

• {n} selected
• Team, Move and Copy — menus, below.
• Publish {n} drafts — when the ticks include drafts.
• Cancel selected — see Cancelled by mistake? Undo within 15 seconds.
• Export selected — Excel, CSV or PDF sheet of just these shifts.
• Clear — untick everything.

A tick survives a change of filter: changing a filter afterwards never quietly drops a ticked shift out of an edit.

Team

• Set the team… — the same people on every ticked shift. Leaving nobody picked takes everyone off.
• Add people… — adds people to whoever is already on each shift.
• Remove people… — takes named people off. It only offers the people who are actually on the ticked shifts.

Adding and removing work shift by shift, so three shifts with three different crews keep their own people and only the names you pick move. The people picker is searchable, and typing a team name finds everyone in that team. The result line says how many shifts changed and how many were left alone because they already had (or didn't have) those people.

Move

• A day later, A day earlier or A week later.
• Move by… — any number of Days, with Later or Earlier. "Each shift keeps its own start and finish time."
• Set times… — see below.

Set times: one clock for every shift

Set times… puts every ticked shift on the same hours. Each shift keeps its own date. Fill in one or both of Start and Finish:

• Both — every shift runs those hours.
• Start only — each shift slides to the new start and keeps its length.
• Finish only — each shift grows or shrinks where it is.

A finish earlier than the start means the next morning. All-day and ongoing shifts have no clock to set; they are left alone, and the result line says how many.

When the ticked shifts don't all run the same hours, the dialog lists them in a warning — "These shifts do not run the same hours: 07:30–16:00, 08:00–16:30. Setting both times puts them all on one, and the hours they run now are gone." To set both ends you then have to tick "Put all 3 shifts on 07:30–16:00, losing the hours they run now" before Set times is available.

Copy to a later week

• To next week, In 2 weeks or In 4 weeks.
• Copy forward by… — any number of Weeks. "Each copy keeps its day of the week, its hours, its team and its plans, and arrives as a draft."

Copies keep the weekday, hours, team, notes, tasks and files. They always arrive as drafts, so nobody is told about work nobody has checked. Look them over, then tick them and use Publish {n} drafts.

Published shifts ask first

A change to published shifts reaches people's phones, so Maliru asks before sending it: "Change the team on 3 published shifts?" (or the day, or the times) — "Everyone affected is notified straight away." Choose Update & notify or Keep as is. Drafts change without a word, because nobody has been told about them yet.

Moving or re-timing a published shift also asks everyone on it to confirm again.

What the result line says

When the bar finishes, a line at the top of the Schedule says what happened, for example "3 shifts moved a day later · 1 could not be moved — {reason}, and stay ticked · 2 schedule clashes flagged."

• A shift the change wouldn't alter is skipped, not re-sent — a no-op edit to a published shift would still send its crew to check their phones.
• Shifts that fail stay ticked, with the first reason in the server's own words, so pressing the same button again means "the ones that didn't land". None of these actions is safe to repeat on the ones that worked: a second move would move them twice.
• Clashes are flagged, never blocked, and the line names any credential the job requires that someone is missing.

Credentials and bulk changes

Every shift a bulk change touches is checked against what the work requires, the same as saving it by hand — copies included. Shifts that pass are changed straight away. For the rest:

• If you hold Override eligibility and a supervisor may allow them, Maliru asks once, after the pass: Assign anyway?, with the first refusal and a Why box. Give a reason and they go through, each recorded as an override against your name. Cancel, and they stay ticked with the reason.
• Otherwise — or when nobody can allow it — they fail, stay ticked, and the result line gives the reason.

Publish {n} drafts in the bar checks the ticked drafts as at publishing; a draft someone isn't allowed to work stays a draft, and the line says so. See Clashes, leave and who cannot go.