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 workers

A roster matches workers to shifts. The better each worker's details, the better the match.

What a worker's record holds

  • Where they work, and their groups.
  • Roles and skills, with dates where skills expire.
  • Contract, agreement and hours.
  • Availability, time off and preferences.

Common mistakes

  • Out-of-date skills, so workers get shifts they cannot work.
  • Missing contracts, so hours limits go unchecked.
  • No availability pattern for workers who can only work set times.

How Chrona does it

Auto Schedule, a constraint solver built on Timefold, uses each worker's details to choose who works each shift. A run sends each worker as a placeholder: no names leave your environment.

Each worker has one page, in tabs. A worker counts once a month when Auto Schedule schedules them, and the first five are free.

Step by step in the docs

Key takeaways

  • A worker is someone a roster can give shifts to.
  • Their roles, skills, contract and availability decide which shifts fit.
  • Chrona uses the word worker for everyone it rosters.

Questions

Why does Chrona say worker?

It is one plain word for everyone a roster gives shifts to.

Does a run send workers' names?

No. In Chrona, each worker travels as a placeholder, with no names, notes or contact details.

How are workers billed?

In Chrona, a worker counts once a month when Auto Schedule schedules them. The first five are free.

Can a worker see their shifts on a phone?

Yes, in Chrona Workforce Mobile, once you invite them.

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