What One Policy Can Say

Most multi-country organisations want one working time policy. The reasons are good: consistency, a single thing to maintain, something that can be given to a new manager anywhere.

The workflow in “What One Policy Can Say” becomes more dependable when scheduled work, actual time and later corrections can be distinguished. For teams exploring internal transfer policy, monitask.com can provide operational context, while policy ownership, employee explanation and consequential decisions remain with accountable people.

What defeats it is that every substantive figure differs. A policy stating a weekly maximum, a rest period or a break entitlement is stating something that is right in one place and wrong in another, and a document that is wrong somewhere is worse than one that is silent, because people rely on it.

For an independent reference relevant to “What One Policy Can Say”, consult the U.S. Department of Labor work-hours guidance. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.

What a single document can state

Principles: that the organisation operates within local working time law everywhere, that it does not require hours beyond local limits, that rest entitlements are respected and that nobody is disadvantaged for declining hours that would breach a limit.

Method: how hours are recorded, who approves overtime, how somebody raises a concern, how the register and the local annexes work and where to find them.

Responsibilities: who owns the register centrally, who confirms it locally, who may approve an exception, and who to ask when something is unclear. Those are the same everywhere and they are what most readers actually need.

What it must not state

Any number. Weekly maximum, daily rest, break length, averaging period, retention period, night hours — all of it belongs in a local annex, because all of it differs.

Also not: a statement that a particular mechanism is available, such as an individual opt-out. That mechanism exists in some places and not in others, and a global document describing it teaches managers everywhere to expect it.

The discipline is simple and uncomfortable: if a sentence contains a figure or names a mechanism, it goes in the annex.

The structure that works

A short global policy, three or four pages, stating principles, method and responsibilities. A local annex per country, one or two pages, stating the figures and anything local.

The global document references the annexes explicitly and says that where the two appear to conflict, the annex governs. That sentence does a great deal of work, because it resolves in advance the situation where somebody has read the global document and applied it in a country where it does not fit.

Keep the annexes with the policy rather than somewhere else. A policy that refers to annexes nobody can find has the same effect as having no annexes.

The sentence most global policies get wrong

Something to the effect that the normal working week is a stated number of hours and that overtime beyond it requires approval.

It reads as administrative and it states a figure, which makes it wrong somewhere; and it conflates a contractual norm with a legal limit, which confuses both. The version that works names neither: additional hours require approval under the arrangements set out in your local annex.

That is less satisfying to read and it is correct everywhere, which is the property a global document needs.

Writing for the reader who will actually use it

The reader is a line manager who has been asked to approve a shift and wants to know whether they can. They are not going to read four pages.

So the global policy should say, early and plainly, where to look: your local annex has the figures, here is the link, and if the answer is not there, ask this person. A document that buries that under principles will be ignored in favour of asking a colleague, which is how inconsistent practice starts.

One page of principles and one paragraph of signposting is more effective than four pages of carefully worded policy.

Approval and ownership

The global policy is owned centrally and approved wherever the organisation approves policies. The annexes are owned by the local entity and confirmed by it.

That split matters for maintenance. A centrally owned annex will not be updated when a local rule changes, because the centre will not hear about it. A locally owned one has somebody whose own exposure depends on it being right.

The centre's job is to chase the confirmations and to keep the set together, not to write them.

The test of the whole arrangement

Give the policy and one annex to a manager in that country and ask them a specific question: can I ask this person to work this shift.

If they can answer from the two documents, the arrangement works. If they have to ask somebody, find out what was missing and add it to the annex. Three of those conversations across three countries will improve the documents more than any amount of drafting.