Skip to content
Back to guides

Rostering

How rosters work

One store, one week, and what publishing actually does.

The essentials

Overview

A roster covers one store for one week. You build it in the grid — people down the side, days across the top — and nobody on your team can see any of it until you publish.

After a week is out, shifts become timesheets as people clock in and out. Changing a published roster is allowed, and the people affected are told.

Before you start

Choose the store and week you are planning. Make sure the people and areas you need are available in the builder.

Step by step

  1. The week is the unit

    A roster covers one week at one store. People run down the side, days across the top, and a shift is a block of time on that grid.

  2. Add a shift

    Drag across the grid to draw a shift, or tap a day to type the times. The block you draw is the shift.

  3. Send the week to your team

    Nobody sees a roster until this moment. What happens when you press it depends on how your business has chosen to work.

    Review the choices available for your organisation in Orbit.

  4. What happens next

    Once the week is out, shifts turn into timesheets as people clock in and out. That is where hours are checked before anybody is paid.

What to check

If you need more help

If a person cannot see a shift, check their store, selected week and whether the change has been published. If publishing needs approval, follow your organisation’s approval process.

Contact the Orbit team

Open in Learn Orbit for guidance suited to your access and business settings. Sign-in may be required.