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 demand-based scheduling

The need rises and falls through the day and the week. Shifts follow it, so cover matches the work.

Demand vs fixed coverage

  • Fixed coverage: the same shifts each weekday.
  • Demand: a minimum and maximum headcount for each time span.
  • Many teams use coverage for the floor and demand for the peaks.

How demand-based scheduling works

  1. Set the need: role, time span and headcount.
  2. Make shifts that meet it.
  3. Fill them within the rules.
  4. Check again when the need changes.

Common mistakes

  • Demand set too finely to staff.
  • Not removing shifts when demand drops.
  • Forgetting the minimum headcount at quiet times.

How Chrona does it

Auto Schedule, a constraint solver built on Timefold, makes the shifts your demand needs. It fills them in the same run. A shift nobody can work is saved as an open shift.

Each demand row sets a role, a time span and a minimum and maximum headcount. The Coverage strip shows each half hour as met, under or over.

Step by step in the docs

Key takeaways

  • Demand-based scheduling makes shifts from the number of workers needed.
  • Demand sets a role, a time span and a headcount range.
  • Chrona's Auto Schedule makes and fills demand shifts in one run.

Questions

What is the difference between demand and coverage?

Demand is the need over time. Coverage is a fixed number per shift type and weekday.

Where does demand come from?

From a forecast or a count, such as residents, guests or orders.

What happens when demand drops?

The roster may have more shifts than it needs. In Chrona, a new run removes open shifts that are now covered.

Does demand-based scheduling work for fixed posts?

Yes. A fixed post is demand that never changes.

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