The Change Nobody Saw
Rules change in one country, the configuration does not, and the gap between the two dates is the period the organisation was operating on an old rule.
One organisation, five changes across four countries
Two of the five took more than eight months to reach the system, and one never arrived at all. In every case somebody knew: the local HR lead was told by a local adviser and had no route to the person who configures the rota tool.
Working time rules move. Not often, and often enough that any organisation operating in several countries will see several changes a year across its footprint.
The configuration problem in “The Change Nobody Saw” is exactly the kind that should be tested before a system is used for payroll or compliance decisions. A team assessing the platform for mouse jiggler detection should pilot calendars, time zones, rounding, permissions and exports with representative cases from every affected location.
The change itself is rarely the problem. The problem is the distance between the person who hears about it and the person who can act on it, which in a multi-country organisation is measured in months and sometimes in forever.
For an independent reference relevant to “The Change Nobody Saw”, consult the Insider Threat Matrix. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.
The chain, and where it breaks
A rule changes. A local adviser tells the local HR lead. The local HR lead knows it matters and has no idea which system holds the setting, who administers it, or how to ask.
Meanwhile the person who administers the rota tool sits in a different country, receives no feed of legal changes, and would not recognise the significance of one if they did. Between those two people there is usually no process at all — only the hope that somebody will raise it in a meeting.
Measuring the lag makes this visible. For each change in the last two years: when it took effect, when the configuration was altered, and the number of days between. The resulting table is uncomfortable and it is the only honest picture of how the organisation actually responds.
Why the lag is worse than it looks
During the gap, the organisation is operating on the old rule. Every rota built, every average computed and every record kept in that period reflects a requirement that no longer applies.
That is not usually catastrophic and it is cumulative. A rest requirement that rose eight months ago means eight months of patterns that would not now be compliant, and the records for that period say what they say. Correcting forward is straightforward; the past is a matter of record.
The change that never arrives
More common than the slow one. A public holiday added, a definition widened, a new record to keep — things that need a configuration change nobody is responsible for making.
These persist indefinitely because nothing fails visibly. The rota still publishes, payroll still runs, and the only indication is a figure that is quietly wrong in one country. Organisations find them during an audit, usually several at once, which is how a series of small administrative omissions becomes a finding about governance.
What a working route looks like
A named person centrally who receives changes, and a named person locally in each country who sends them. Two names per country, in a list, with the expectation stated: when your adviser tells you something has changed, you tell this person, in writing, that week.
Then a standing item — monthly or quarterly — where the centre reviews what has come in, decides what needs configuring, and records the decision with a date. The record matters as much as the action, because it is what demonstrates the organisation responded rather than happened not to be caught.
Where the changes come from
Local counsel, where the organisation retains any. Local payroll providers, who usually monitor this as part of their service and rarely pass it on unless asked. Employer associations. The entity's own finance or company secretarial function, who frequently receive regulatory updates and do not read them as employment matters.
Asking each of those to send working time changes to one named address costs an email. Most organisations have three or four sources already paying attention and no address to send to.
The annual check as a backstop
Once a year, ask each local source one question: has anything changed in the last twelve months that we should have reflected and have not.
It is a slower instrument than the standing route and it catches what the route missed, which is always something. It also produces the dated record that the question was asked, which is worth having independently of the answer.
Recording the lag as a number
The four dates per change — in force, heard, implemented, confirmed — turn an impression into a series, and the series is what makes the case for fixing the handoff.
A median lag is also the figure most likely to interest whoever approves the small amount of effort this needs, because it is comparable year on year.
Start recording it before fixing anything. A baseline of two hundred days makes a subsequent thirty look like what it is, and without the baseline the improvement is invisible.
The change that arrives through a provider
Payroll providers frequently implement a change in their own processing without telling the client, because from their side it is routine maintenance.
The organisation then has figures computed on a new basis with no record of when it altered, which is visible only as a discontinuity in a series nobody is watching.
Ask providers to notify changes affecting hours or their treatment. It is a reasonable request, it is rarely made, and it closes a route by which rules reach the organisation's numbers without reaching anybody's knowledge.