Who Signs It

Employment obligations attach to the employing entity. A policy approved by a group function is the group's statement of intent; whether it is the employer's policy in a given country depends on whether that entity adopted it.

The workflow in “Who Signs It” becomes more dependable when scheduled work, actual time and later corrections can be distinguished. For teams exploring employment of relatives policy, employment of relatives policy with accountable controls can provide operational context, while policy ownership, employee explanation and consequential decisions remain with accountable people.

In most organisations nobody has asked. The policy was approved somewhere senior, published on an intranet, and is assumed to apply everywhere because it says it does.

For an independent reference relevant to “Who Signs It”, consult the EEOC retaliation guidance. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.

Why adoption matters

In a dispute or an inspection, the question is what this employer's rules were. A document headed with the group's name, approved by a group committee, and never referenced by the local entity is weaker evidence than one the entity formally adopted.

In some jurisdictions there are formal requirements about how workplace rules are introduced, including consultation and in some cases registration, and a document that skipped those steps may not have the status the organisation thinks.

That varies enough that it belongs in the annex as its own line: how was this policy adopted here, and what was required.

The consultation question

Several jurisdictions require consultation with a works council or employee representatives before introducing or changing rules about working time. Some require agreement rather than consultation.

A central policy rolled out without that step may be ineffective locally and, in some places, the rollout itself is a breach. This is the single most common way a well-intentioned harmonisation project creates a problem in one country while solving one elsewhere.

Ask before the rollout rather than after. The timeline for consultation is usually weeks, which is manageable if it is planned and disruptive if it is discovered.

The adoption record

A short record per entity: the policy version adopted, the date, how it was adopted, what consultation took place, and who signed.

Five fields. They are what makes the policy the employer's policy rather than the group's, and they are what somebody will ask for.

Keep them with the annexes. A policy set with adoption records attached is a complete document; one without them is a draft that has been in use for years.

Who signs centrally

Somebody with authority over both the policy and its consequences — usually whoever owns employment compliance, with the operating function represented, because the policy constrains the operation.

A policy signed only by a central HR function and not by anybody who owns a rota tends to be written without reference to whether it can be followed, and the gap shows up as widespread informal non-compliance rather than as an argument.

Who signs locally

The entity's own authorised signatory, not the local HR lead acting on instruction. The point of local adoption is that the entity has taken the document as its own, which requires somebody who can bind it.

Where the entity is small and has no HR function, this will be a director, and the conversation about what they are signing is worth having properly. A director who has read the annex for their country is a considerably better-informed participant in everything that follows.

Changes, which need the same route

A change to the global policy needs re-adoption wherever adoption was required, including any consultation that applied the first time.

The usual failure is a version 3 published centrally while the entities adopted version 1 and nobody re-ran the local step. Two years later the organisation cannot say which version applies anywhere.

Treat a version change as a small rollout rather than as a publication. It is slower and it keeps the set coherent.

The audit that finds the gaps

List the entities, the current policy version, the version each adopted, the adoption date and whether consultation was required and done.

Five columns, one afternoon with the entity list. Most organisations running it for the first time find at least one entity that never adopted anything and at least one operating two versions behind, and both are straightforward to fix once named.

The policy that was never issued locally at all

Beyond adoption, there is the simpler failure: a global policy published on an intranet that employees in several countries have never been pointed at.

Where local law requires workplace rules to be communicated in a particular way, publication is not issuance, and an employee who has not been given the document may not be bound by it.

Record per entity how the policy was communicated and when. It is one more column on the adoption record, and it is the one that answers whether anybody actually received the thing.