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 historic shifts

A roster does not start from nothing. A worker who ended last week with a late shift or six days in a row still needs their rest.

What they are used for

  • Rest before the first shift of the period.
  • Days in a row that run across the period start.
  • Periods and windows that began before the roster.

How historic shifts work

  1. Read the shifts worked before the period.
  2. Go back as far as the longest rule needs.
  3. Count them in the rules, but never move them.

Common mistakes

  • Planning each roster as if the last one did not exist.
  • Going back too little for a long rolling window.
  • Changing past shifts to fit the new roster.

How Chrona does it

Auto Schedule, a constraint solver built on Timefold, counts the shifts before the roster period, as far back as the longest rule needs: its rest, its run of days, the start of its period or its window.

Their breaks are not read, so a night shift before the period is judged from its start to its end. A run never changes them.

Step by step in the docs

Key takeaways

  • Historic shifts are the shifts worked before the period.
  • Rules that look back count them.
  • Chrona sends them as far back as the rules need.

Questions

Does Auto Schedule change past shifts?

No. It counts them in the rules and plans only the period.

How far back does a run look?

In Chrona, as far as the longest rule needs: its rest, its run of days, its period or its window.

Are breaks of past shifts counted?

No. In Chrona, a shift before the period is judged from its start to its end.

Why does a worker get no shift on the first day?

Often a rest or days-in-a-row rule from the shifts they worked just before.

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