The Annual Confirmation

The standing route handles what arrives. The annual confirmation handles what did not, and on every estate there is something.

The record described in “The Annual Confirmation” should preserve the original entry, the correction and the approval rather than only a final total. When considering this product overview for employee monitoring at tech companies, teams should test that complete sequence, limit access by role and confirm that exported records remain understandable outside the live account.

It is deliberately small: the local owner receives their own row from the register and their own annex, and is asked whether anything in them is now out of date.

For an independent reference relevant to “The Annual Confirmation”, consult the ENISA threat-landscape resources. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.

What gets sent

The register row for their population or site, and the annex for their country. Both as they currently stand, not as a blank form to fill in.

Sending the current version is what makes the exercise fast. Confirming something is a minute; completing a questionnaire is an afternoon and will be deferred.

Add one line of context: this is what we hold for you, it was last confirmed on this date, please tell us what has changed.

The question

One question, phrased so that silence is not an answer: please reply confirming it is accurate, or telling us what to change.

A request that only needs a reply if something is wrong produces a response rate that looks excellent and means nothing. Requiring a positive confirmation produces a lower response rate and a meaningful one, and chasing the non-responders is then a short list.

The deadline

A stated date, early enough that the follow-up work fits before the year end, and the same date every year so it becomes expected.

Attaching it to something the local entity already does — the holiday confirmation covered earlier in this collection, or a year-end process — raises the response rate considerably, because it arrives in a context where this kind of request is normal.

What the replies contain

Mostly confirmations. Then a small number of substantive items: a rule that changed and was never reported, a new site, a collective agreement renewed on different terms, a population that no longer exists.

And, reliably, one or two replies from people who have never seen the register before and did not know it existed. Those are worth following up, because they indicate the local ownership is nominal.

The non-responders

Chase twice, then escalate to whoever the local entity reports to.

A country that does not respond to this request two years running is not maintaining its position, and the register should say so rather than carrying a row with a stale confirmation date as though it were current.

Marking a row as unconfirmed is more useful than quietly leaving the old date in place, because it puts the gap where somebody will see it.

Recording the round

Date sent, date due, who replied, what changed, and what was done about each item.

That record takes no effort to keep — it is the mailbox — and it is the evidence that the organisation maintains its position annually. It also makes the next round faster, because last year's unresolved items are the obvious place to start.

Why the backstop is necessary

The standing route depends on individuals noticing that something matters and acting on it. Most will, most of the time. The annual confirmation exists because most and usually are not enough over a decade.

It also catches the changes that nobody would think to report: a site that quietly grew, a population that changed shape, an agreement that lapsed. Those do not arrive as news and they do change the register.

The version of this that fails

A questionnaire, sent to a distribution list, asking people to describe their local working time position.

It is longer, it asks people to produce rather than to confirm, it goes to a list rather than to a named owner, and the responses will be inconsistent with each other and with last year's. Sending the row back and asking one question is the version that works.

What to do with a confirmation that is wrong

Occasionally a confirmation comes back saying everything is accurate and the centre has reason to believe it is not — a change was reported elsewhere, or a configuration suggests otherwise.

Go back once, specifically, with the item: we understand this changed in March, can you confirm. A general challenge produces defensiveness; a specific one produces an answer.

Record the correction and the fact that it took a second round. Two of those from the same country in successive years is a signal about the local ownership rather than about the country.

Confirming the register and the annex together

They are different documents and they are confirmed by the same person about the same situation, so they go in the same email.

Splitting them doubles the administration and halves the response rate, and it invites a reply that confirms one and ignores the other.

One message, two attachments, one question covering both. The confirmation record then has a single date per country, which is also what makes the read-across possible.