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 guaranteed hours

Guaranteed hours are a floor; maximum hours are the ceiling. The roster aims between them.

Guaranteed hours and availability

A worker's availability must leave room for their hours. A pattern with fewer hours than the contract guarantees cannot meet it.

Tracking the gap

Hours worked rarely match the guarantee exactly. An hours balance carries the difference to later periods.

Common mistakes

  • Guaranteed hours above the worker's availability.
  • Ignoring a growing shortfall.
  • Giving casual workers guaranteed hours by mistake.

How Chrona does it

Auto Schedule, a constraint solver built on Timefold, gives each worker their guaranteed hours where it can. That is a Should rule, and it never passes their Maximum hours.

Both sit on the worker's contract. The Roster grid shows each worker's hours, with a mark at the guaranteed hours.

Step by step in the docs

Key takeaways

  • Guaranteed hours are the hours a contract promises each period.
  • They are a floor; maximum hours are the ceiling.
  • Chrona gives them where it can, as a Should rule.

Questions

Are guaranteed and contracted hours the same?

Most teams use the words for the same thing.

Does paid leave count toward guaranteed hours?

Often, yes. In Chrona, a leave type with Counts as worked set to Yes credits the hours balance.

Do casual workers have guaranteed hours?

Usually not. In Chrona, an empty Guaranteed hours means none.

How does fairness use guaranteed hours?

In Chrona, sharing Hours fairly keeps each worker's hours in line with their guaranteed hours.

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