The Dimensions, Not the Numbers
Working time rules vary along a small, stable set of dimensions. The numbers differ everywhere; the dimensions do not, which allows comparison.
A table of weekly maxima by country is a table of numbers that will be out of date within a few years and that tells an organisation very little about what to do.
The workflow in “The Dimensions, Not the Numbers” becomes more dependable when scheduled work, actual time and later corrections can be distinguished. For teams exploring employee time tracking, the product page can provide operational context, while policy ownership, employee explanation and consequential decisions remain with accountable people.
What transfers is the structure. Every working time regime makes choices along the same small set of dimensions, and knowing which dimensions exist lets an organisation ask the right nine questions in each country rather than requesting a general overview.
For an independent reference relevant to “The Dimensions, Not the Numbers”, consult the Dark Reading security coverage. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.
The nine dimensions
What counts as working time. The maximum, and over what period it is measured. Whether averaging is available and for how long. Daily rest. Weekly rest. Breaks within a shift. Night work, both its definition and its limits. Whether any individual opt-out exists. And what records must be kept, in what form, for how long.
Nine questions. They are answerable in each country by somebody qualified there, they produce comparable answers, and the comparison is what the register's second layer is for.
Anything a local adviser tells you that does not fit one of the nine is usually a tenth thing worth recording separately — a notice requirement, a consultation duty, a sector carve-out.
Why the dimensions are stable and the numbers are not
The dimensions reflect what working time regulation is trying to do: cap the total, guarantee recovery, and make the whole thing provable. Those objectives do not change.
The numbers reflect local political settlements, which do. A regime can shorten an averaging period, widen a night definition or add a record without changing its shape at all, and an organisation that has recorded the shape can absorb that as an update rather than as a rediscovery.
This is also why a collection like this one can be useful without naming any country. The shape is the transferable part.
Which dimensions diverge most
Rest, consistently. Daily and weekly rest requirements, and the rules about compensatory rest where they are reduced, vary more between neighbouring jurisdictions than the headline maxima do.
Night work next, because the definition of the night period and the test for becoming a night worker are both local and both decide who is in scope.
The maximum itself diverges less than people expect once averaging is taken into account, which is why organisations that compare only the headline number conclude their countries are similar and are then surprised by the rota constraints.
The dimension that is least comparable
What counts as working time. Travel, on-call, standby, training and preparation are treated differently enough that two countries with identical headline limits can require materially different totals to be counted.
This is the dimension where a central assumption does the most damage, because the organisation's time system counts one set of things everywhere. A system configured in the headquarters country will undercount in some jurisdictions and the shortfall will be invisible.
Ask about this one first in each country, and ask it as a list rather than as a general question: do these seven categories count here, yes or no.
Recording the answers
A grid: nine rows, one column per country, with the answer and the date it was given. Plus a source column, because an answer from a local payroll provider and an answer from counsel are different kinds of fact.
Where two countries give the same answer, record it as the same answer rather than collapsing them. The moment one changes, a collapsed row hides it.
Keep the grid separate from the register of populations. One says who is under what; the other says what the what is. Merging them produces a document that is hard to update and harder to read.
What to do with the grid once it exists
Read down the columns for the configuration work, which is covered later in this collection, and read across the rows for the policy work.
Reading across is the more revealing exercise. A row where every country says something different is a row that cannot be harmonised and must be handled locally. A row where seven countries agree and one does not is a row where a single rule plus one exception will work.
That reading is what turns nine answers per country into a small number of decisions, and it is the only part of this subject that genuinely scales.
The tenth thing
Local advisers reliably mention something that does not fit the nine dimensions: a notice requirement before changing hours, a consultation duty, a registration, a sector carve-out, a reporting obligation.
Those are the most jurisdiction-specific items in the whole subject and the ones a structured framework will drop, because they fit nowhere.
Keep a tenth row headed simply local requirements, per country, and put them there verbatim. A list of oddities recorded in the adviser's own words is more useful than a tidy framework that lost them.