Adding many shifts at once

Planning a week for a dozen people one New shift at a time is slow. Add multiple shifts is a grid: one row per shift, all saved in one go.

Open it from the Schedule: Add multiple › Multiple shifts ("Add multiple shifts at once").

Filling in the rows

The chips at the top — All workstreams or one workstream — narrow every row's job list. Each row has:

• When — opens the same Date & time window as a single shift, with All day and Ongoing.
• Job — Select job opens Choose a job. A row without a job isn't saved.
• Team — Add team opens Choose the team; the row then shows how many people are on it.
• Site — Choose a site, or Use a one-off address at the foot of the list for somewhere that isn't a saved site. A long address shows in full when you hover over it.
• Notes — Add notes (optional).
• Claim, Spots and Approval — open the shift for staff to claim, how many spots, and whether each claim needs your approval.

At the end of each row: Tasks and Files (each with a count — files come from the job's own attachments), Duplicate row and Remove row. Add shift adds a new row at the bottom. The header counts the rows that have a job, and the foot adds up shifts and people.

When a row's job has a client, the site list offers only that client's sites. When it hasn't, every site is offered.

Overlaps between rows

If two rows put the same person in two places at once, the foot shows {n} worker overlaps with Review. Review lists them — "These rows put the same person in two places at once." — as Shift 1 and shift 3 with the names. It's a warning: fix the rows or save anyway.

This checks the rows against each other. Clashes with shifts already on the schedule, and with approved leave, are counted when you save — see Clashes, leave and who cannot go.

Saving

• Save as drafts — every row becomes a draft. Nobody is told.
• Save & publish shifts — the rows are saved and then published together, and everyone on them is notified.

When it's done, the Schedule says so: "Created 6 shifts as drafts." or "Created 6 shifts and published."

If some rows can't be saved, the grid stays open: "2 rows could not be saved. Successful rows are saved as drafts. Check the rows and retry; saved shifts will be updated." Fix the rows and save again — rows that already saved are updated, not duplicated. Publishing only happens once every row has saved.

Each row is checked against what its job requires, the same as a single shift. If rows are refused and you hold Override eligibility, Maliru asks once — "2 rows were refused. The first: …" — with Assign anyway and a Why box; give a reason and those rows save as recorded overrides. Otherwise they count as rows that couldn't be saved.

With Save & publish shifts, the saved shifts are then checked as at publishing. Any someone isn't allowed to work stay drafts — "1 shift is saved as a draft, not published: …" — unless you choose Publish anyway. See Clashes, leave and who cannot go.

Tip: build one row, then Duplicate row and change only the date or the team. To repeat a whole week, create it once and use Copy › To next week on the ticked shifts — see Changing, moving and copying many shifts at once.