Guided walkthrough

Change a published week

How a change to a week your team already has reaches them.

Step 1 of 4

Changes to a published week wait

Changing a week that is already out holds the change aside instead of pushing it through. Your team keeps seeing the current version until you publish again.

Open in Orbit

This walkthrough explains the steps. Moving through it does not change your business or mark work as completed. Links to Orbit open in a new tab and may require sign-in.

All steps

Changes to a published week wait
Changing a week that is already out holds the change aside instead of pushing it through. Your team keeps seeing the current version until you publish again.
Open in Orbit
Change a shift
Move a shift, retime it, or hand it to somebody else — any change on a published week will do. Nothing you do here is visible to your team yet.
Open in Orbit
Publish the changes
Send the held changes out. They go together in one go, so your team sees one updated week rather than a run of small corrections.
Open in Orbit
What your team sees
The new times quietly replace the old ones. Nobody is pinged for an edit, because a shift moving by half an hour is not news at eleven at night.

Read the related guide

Guide · Rostering

Why your team cannot see the change yet

Changes to a week that is already out are held until you send them.

Read guide