General information only. This explains a scheduling term. It is not legal advice: the rules that bind you come from the law, your agreements and your contracts.

Understanding roster periods

Rostering happens in steps. Each period is planned, checked and published as one, then the next follows on.

Roster period vs planning horizon

  • A roster period: the time one roster covers.
  • A planning horizon: the coming rosters, side by side.
  • Each roster in the horizon is one roster period.

Choosing a period

  • A week suits work that changes often.
  • A fortnight or a month gives workers more notice.
  • Line the period up with pay and the rules that count by period.

Common mistakes

  • A period that starts on another day than the rules count from.
  • Changing the period length often.
  • Planning past the period that will be published.

How Chrona does it

Set the Period, Week, Fortnight or Month, and the day it starts. Auto Schedule, a constraint solver built on Timefold, plans the period on the board and changes nothing outside it, and no shift that has started.

The Roster grid shows one whole period, Generate fills it, and you publish it as one. Rules can count by Roster period too.

Step by step in the docs

Key takeaways

  • A roster period is the time you plan and publish as one.
  • Timefold calls it the planning window.
  • In Chrona, Auto Schedule changes nothing outside the period.

Questions

Is a roster period the same as a planning window?

Yes. Timefold says planning window; Chrona says roster period.

Which periods can I choose?

In Chrona, Week, Fortnight or Month, from the day you set.

Does Auto Schedule change shifts outside the period?

No. It plans only the period on the board.

What is the planning horizon?

In Chrona, the current roster and the ones after it, as cards above the board.

The word comes from Timefold, the planning engine Auto Schedule is built on. See the source