Where the Week Begins
A weekly limit needs a week, and which day it starts on is a local matter that most systems hold as a single global setting.
Every weekly figure in a working time system depends on where the week is cut. Change the boundary and the same hours produce different weekly totals, different peaks, and in a hard-cap jurisdiction different answers about compliance.
The working-time issue in “Where the Week Begins” depends on complete records and an agreed interpretation, not on a dashboard alone. For organisations researching self report bias, the platform can add time and project context, provided managers investigate exceptions, employees can correct errors and the applicable rule remains documented outside the software.
It is a single configuration field, it is usually set once, and in several products it is global rather than per country.
For an independent reference relevant to “Where the Week Begins”, consult the Mandiant security resources. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.
Why it differs
Local convention, local regulation, and local agreement. In some places the working week is defined in the regulation; in others it follows the contract or the collective agreement; in others it is simply custom and the system should follow what people expect.
Where an agreement defines it, the definition is binding for the population that agreement covers, which can mean two entities in the same country legitimately using different boundaries.
What goes wrong when it is uniform
A site whose working week runs from a different day will have its hours split across two of the system's weeks. A long shift that straddles the boundary lands partly in each.
Under an averaged limit this mostly washes out. Under a hard weekly cap it does not: a person can be inside the cap on the system's weeks and over it on the real ones, or the reverse, and the system will be confident either way.
It also distorts every weekly report anybody reads, which means the operational picture for that site is subtly wrong in a way nobody can see.
The shift that crosses the boundary
A night shift starting on the last day of the week and ending on the first day of the next has to be attributed somewhere, and systems differ: some attribute by start, some by end, some split.
Whichever rule applies has to match what the local regime expects, and the question is rarely asked. For most sites it changes nothing; for a site under a hard cap with substantial night working, it changes the answer regularly.
Record the rule per country alongside the boundary, because the two together determine the weekly figure.
Finding out what yours does
Take one person at a site with a non-standard week and recompute their last four weeks by hand on the local boundary. Compare with the system.
Differences appear immediately where they exist. The exercise takes an hour and it is the only reliable way to establish the behaviour, because configuration screens describe intent and the calculation is what matters.
Where the system cannot vary it
Older products frequently hold one global week start. The workarounds are ugly and sometimes necessary: a separate instance for the affected country, a shadow calculation outside the system, or a documented adjustment.
Choosing one and writing it down is better than the common alternative, which is to note the limitation in an implementation document nobody reads again and carry on quoting the figures.
If the organisation is procuring a new system, this is a question for the demonstration rather than the specification: show me two sites with different week starts.
The reporting consequence
Even where the limit calculation is correct, reports aggregated by week across countries are comparing different weeks.
A group report showing hours by week by country, built on one boundary, is approximately right and not exact, and the inexactness grows with how different the boundaries are. For management reporting that is usually acceptable; for anything presented as a compliance figure it is not.
Label group aggregates with the boundary used. One line, and it prevents a figure assembled for a board pack being quoted in a response to a regulator.
The four facts to hold
Per country and, where it differs, per entity: the week start, the source for it, the rule for shifts crossing the boundary, and whether the system implements it or a workaround is in use.
Four facts. They sit in the configuration table next to the night period and the break rules, and they are the ones most likely to be identical across an estate where they should not be.
Explaining it to the people who read the reports
Supervisors read weekly figures and form a picture of the week from them. Where the system's week does not match the one they experience, the figures look wrong in a way nobody can articulate.
That erodes trust in every number the system produces, including the ones that are right, and it is a common cause of a site maintaining a parallel spreadsheet.
Where the boundary cannot be changed, say so explicitly on the reports: this week runs from this day. One line removes a persistent low-level confusion that otherwise never gets named.