Local Annexes
One page per country, holding every figure the global policy cannot state. It is the only part of the documentation that has to be locally owned.
The local annex is where the numbers live. The global policy states principles and method; the annex states what the weekly maximum is here, what rest is required, what records are kept and for how long.
The workflow in “Local Annexes” becomes more dependable when scheduled work, actual time and later corrections can be distinguished. For teams exploring gdpr employee monitoring, this workforce tool can provide operational context, while policy ownership, employee explanation and consequential decisions remain with accountable people.
It exists because a global document stating any figure is wrong somewhere, and because the alternative — a policy per country — duplicates the ninety per cent that is genuinely common and guarantees the versions will diverge.
For an independent reference relevant to “Local Annexes”, consult the ICO employment-practices guidance. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.
What goes in it
The nine dimensions with their local values. Whether any sector regime applies to populations at this site. The local public holidays or a reference to where they are published. Any collective or works council agreement in force and what it adds.
Plus two local facts the global policy cannot hold: who to ask here, and who confirms this annex.
One or two pages. Anything longer is usually the global policy being restated, which is the most common way annexes rot.
What stays out
Principles, which are in the global policy. Process, which is in the global policy. Anything that is the same everywhere, because repeating it in eight annexes creates eight things to update.
The discipline is that the annex contains only what differs. A reader holding both documents sees the full picture; a reader holding only the annex should be in no doubt that there is a global policy too, which is why the annex should open by naming it.
Who writes it
The local entity, from its own advice, with a template from the centre.
A template matters more than it sounds: nine headings in a fixed order means the annexes are comparable, which means somebody can read down a column across countries and spot where one is empty. Free-form annexes are each reasonable and collectively unusable.
The centre supplies the template and the deadline. It does not supply the content, because it does not have it.
The source column
Every value in the annex should carry a source: the regulation, the agreement, or advice with a date and a reference.
That column is what distinguishes an annex from a summary somebody wrote. It also makes updating possible: when a rule changes, the person updating knows which values came from where and which need rechecking.
Values with no source are the ones that will be wrong in three years, and marking them as unsourced is better than letting them look authoritative.
Keeping them current
An annual confirmation, with a date, from the local owner. One email, one question: is anything in this annex now out of date.
Plus an event-driven route for changes between confirmations, which is the subject of a later section of this collection. The annual confirmation catches what the route missed, and it produces a dated record that the question was asked.
An annex with a confirmation date from two years ago is a document nobody is relying on, and the date is what makes that visible.
Versions, which matter more than usual
Keep dated copies. A question about how somebody's hours should have been treated in 2024 is answered by the 2024 annex, not by the current one.
This is the same discipline as for the global policy and it is more important here, because the annexes change more often. An annex system that overwrites is an annex system that cannot answer a historical question, and historical questions are most of what gets asked.
The test
Hand the global policy and one annex to a manager in that country, and ask: how many hours can this person work next week, and how much rest must they have between shifts.
If they can answer, the pair works. If they cannot, the gap is in the annex, and it is worth finding out which of the nine headings they looked under. That tells you how to label it so the next person finds it.
The annex for a country with one person
A single remote hire in a new country still needs an annex, and producing a full one is disproportionate.
A short form works: the nine headings with values where they are known, a note saying the determination rests on the payroll provider's confirmation, and a date.
Half a page and it is honest about its own basis, which is better than either a full annex built on guesswork or no annex at all. It also makes the row easy to upgrade if the population grows.