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

Most work happens inside a working day. Marking it on the board makes a shift outside it stand out.

Working hours vs availability

  • Working hours: the usual day of the board.
  • Availability: when one worker can work.
  • A shift can be inside one and outside the other.

What to do with a shift outside them

  • Allow it, with the shading as a guide.
  • Warn, so the planner checks it.
  • Block it.

Common mistakes

  • Working hours that do not match a night service.
  • Blocking drops that are needed.
  • Using working hours in place of availability.

How Chrona does it

The view’s Working start and Working end shade the hours outside them. The Working hours policy checks a row dropped outside them: off, warn or block. Off is the default.

A worker’s own times are their availability pattern, which Auto Schedule keeps.

Step by step in the docs

Key takeaways

  • Working hours are the usual hours of the working day.
  • They are not one worker’s availability.
  • In Chrona, a drop outside them can pass, warn or block.

Questions

Are working hours the same as availability?

No. Working hours belong to the view; availability belongs to each worker.

What happens when I drop a row outside them?

In Chrona, nothing by default. Set the policy to warn or block.

What if I set no working hours?

In Chrona, the board shades no hours.

Does Auto Schedule use working hours?

It keeps each worker’s availability pattern. The working hours check your own drops.

The word comes from Microsoft Dynamics 365 Field Service and Universal Resource Scheduling. See the source