Skip to main content
Several shifts selected on the schedule grid, with the bulk actions bar below them Several shifts selected on the schedule grid, with the bulk actions bar below them A change that belongs on twenty shifts should cost one action, not twenty. Select the shifts, pick what to change, and Begin applies it to every one of them.

​
Select what you want to change

Hold Shift and click a shift to add it to the selection; click it again to drop it. To sweep a run of them, press on empty row background and drag a box across them. Either Cmd / Ctrl + A or the count on the bar that appears selects everything matching the and filters you have on, not only what has loaded on screen. Esc clears the selection.
A week of the schedule with five night shifts selected, four of Kadri Tamm's and one of Mārīte Ozola's, each ringed in blue, and the bulk bar at the foot of the window reading 5 selected beside ActionsA week of the schedule with five night shifts selected, four of Kadri Tamm's and one of Mārīte Ozola's, each ringed in blue, and the bulk bar at the foot of the window reading 5 selected beside Actions

Five shifts selected, and the one bar that acts on all of them

​
Change the same field on many shifts

The bar’s Actions button opens the list, and the command palette carries the same one. Assignee, position, location, type, status and colour each put the one value you pick on the whole selection. Publish all, Unpublish all, Duplicate all and Delete all act on it as it stands. What is offered depends on what you selected: no location choice unless every block in it is a shift, no status unless your role can set one, and no Time off until your workspace has a time-off policy to book against. Switching a selection to Time off books each absence against the policy the time-off form would open on. A block already booked against one keeps it, so a mixed selection changes no balance you had already spent. A large selection runs in the background. Its progress row offers Cancel while it works and Revert once it has finished, and it counts anything it skipped because that shift had changed since you started. Or ask Begin AI (Cmd / Ctrl + J):

Move all of Jonas Petrauskas's shifts next week one day later.

It moves every one of them in a single change, after a card you confirm unless your approval mode applies changes automatically.

​
Repeat a week you have already built

Copy with Cmd / Ctrl + C, hover the person and day you want it on, and paste with Cmd / Ctrl + V. A paste lands on the row under the pointer, so the copy is what decides who ends up working it: Copied open shifts always land on the row you paste onto. Dragging does the same job for one shift: drag it to another day, or onto another person’s row to reassign it. Or ask Begin AI:

Copy this week's shifts to next week.

It copies every block in the week, time off and availability included, not only the shifts.

​
Put it back

Cmd / Ctrl + Z undoes the last change and Cmd / Ctrl + Shift + Z redoes it. Both survive stepping between periods with the arrows, so a copy made in one month can be undone from the next. Reloading the page clears the history, and the clipboard with it.
Deleting or moving shifts the team has already seen reaches them at once. The confirmation says how many of your selection are published, and a delete can still be undone.
Yes, if they are in your selection. Each one is copied as the same type. A copied shift is a draft, like any new shift. A copied absence is not: it goes back through approval, so it lands as Needs review where a workflow reviews that policy, and as Approved where none does.
Copy to next month keeps the date, not the weekday: the 15th goes to the 15th, whatever day that falls on. A date the next month does not have, such as the 31st, lands on its last day.

​
Next

Publishing

How a draft week reaches the team.

Templates and rotas

The answer when you copy the same week every week.

​
Still need help?

Contact support

Email the Begin team and we’ll get back to you.

Ask Begin AI

Open the AI assistant and get instant answers based on these docs.