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 time zones
A planner in one city can roster a site in another. The shifts must still start on the site’s own clock.
Where the time zone counts
- The times on each shift.
- Where days and weeks start.
- Rest, nights and weekends.
Daylight saving
A clock change makes one night an hour shorter or longer. Counting on the local clock keeps each shift at its local time.
Common mistakes
- Shifts shown in the planner’s own zone.
- Weekly rules counted on another clock.
- A shift across a clock change counted wrongly.
How Chrona does it
Each site has a time zone. The board shows every time in it, for everyone, and Auto Schedule, a constraint solver built on Timefold, counts periods and rules on the site’s clock.
A view can show another time zone, or each user’s own. A scheduler with no zone shows each user’s Power Apps time zone.
Step by step in the docs
Sites
Set the site’s time zone.
The view row
Show another time zone on one view.
Key takeaways
- A time zone is the local clock of a site.
- Rules count days and weeks on it.
- In Chrona, the board shows every time in the site’s zone.
Questions
Whose time does the board show?
In Chrona, the site’s, for everyone, unless the view sets another.
Where do I set the time zone?
In Chrona, on the site. Its schedulers and shifts take it.
Does a week start in the site’s time?
Yes. In Chrona, on the site’s Week starts on day, on its clock.
What if no time zone is set?
In Chrona Scheduler, each user sees their own Power Apps time zone.
Related terms
The word comes from Timefold, the planning engine Auto Schedule is built on. See the source
