Why your team cannot see the change yet

The essentials

Overview

A week that has already gone out behaves differently from one you are still building. Changing a shift on it does not reach anybody straight away — the change is held against that shift, and your team keeps seeing the version they already have.

That is on purpose. A roster that rewrote itself under somebody mid-thought would make the copy on their phone worth nothing, and half-finished thinking is not something to send out one shift at a time.

Publishing again releases everything you have held, together. Your team gets one updated week rather than a run of small corrections.

Before you start

Have the store, week and specific shift you expected to see ready.

Step by step

1. 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.

2. 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.

3. 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.

4. 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.

What to check

If you need more help

If a confirmed published change is still missing, send support the store, shift date, expected time and the account affected.