Records That Must Be Local

Centralising time and attendance is sensible and it is what most multi-country organisations have done. One system, one archive, one administrator, consistent exports.

The record described in “Records That Must Be Local” should preserve the original entry, the correction and the approval rather than only a final total. When considering a practical route to boss vs leader for boss vs leader, teams should test that complete sequence, limit access by role and confirm that exported records remain understandable outside the live account.

Several frameworks cut across that with a requirement that particular records be available at the place of work. Not retrievable eventually — available, on request, at the site, sometimes in the local language.

For an independent reference relevant to “Records That Must Be Local”, consult the Harvard Business Review security and privacy analysis. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.

Why a central archive may not satisfy it

Because the requirement is about availability at a location, and a system accessible to an administrator in another country does not obviously meet it, particularly if nobody at the site has access or knows how to use it.

Whether it does depends on the local framework and sometimes on how the requirement is interpreted in practice. It is a question with a local answer and it is rarely asked, because centralisation is treated as an improvement rather than as a change in where records live.

The practical test

Could somebody at the site, on a Tuesday morning, with an inspector present, produce the hours and rest records for named people for the last three months, in a readable form, without calling another country.

Most centralised estates fail that test somewhere. The failure is not the archive; it is that nobody local has access, a login, or any idea what to produce.

The cheap fixes

Give somebody at each site read access to their own site's records, with a short note on which report to run.

Or schedule a monthly export, per site, held locally in a readable format. It is a file and a folder, it costs nothing, and it satisfies an availability requirement in a way that an access right dependent on a working network does not.

Either is a morning's work. The common state — no local access and no local copy — is the result of nobody having asked the question rather than of a decision.

Language

Where records must be in the local language, an export with English column headings may not be sufficient.

Most systems can produce localised exports and most installations have never configured them, because the administrator works in one language and the reports were built there.

It is a configuration question with a known answer and it is worth checking per country rather than assuming the system handles it.

What else must be local

Beyond the hours records: the policy and annex, any agreements in force, posted notices where those are required, and in some places specific registers.

Some of these must be displayed rather than merely available, which is a physical requirement nobody central will think of. A notice that must be posted at the workplace is not satisfied by an intranet page.

Ask the local entity what has to be on the wall. The answer is sometimes nothing and sometimes a specific document, and it takes one question.

Data protection, which pulls the other way

Holding employee records locally at every site multiplies the number of places personal data sits, which is its own question.

The resolution is usually scope: a local copy of that site's own records, limited to what the requirement covers, held for the required period and no longer, in a controlled location.

Doing it deliberately with those limits is a better position than either extreme — no local copy at all, or an uncontrolled folder of exports accumulating on a site manager's desktop.

The line in the annex

For each country: which records must be available locally, in what form, in which language, and where the site's copy is held.

Four facts. They are the ones that determine what happens in the first hour of an inspection, and they are the ones a centralised system is least likely to have considered.

The site with nobody to produce anything

Small sites frequently have no administrator, no system access and nobody who has ever run a report.

A requirement to produce records locally cannot be met by access rights nobody holds. For those sites the answer is a scheduled export to a known location, so that producing the records is finding a file rather than operating a system.

Set it up once per small site. It is the sort of thing that looks unnecessary until the morning somebody is standing at the door asking for three months of rest records.

Retention of the local copy

A scheduled export creates a second archive with its own retention question, and left alone it accumulates indefinitely in a folder nobody owns.

Set the retention on the local copy to match the requirement that justified it, and have the export overwrite or prune rather than accumulate.

Otherwise the solution to one compliance question becomes a different one: an uncontrolled store of personal data at every site, which is harder to explain than the original gap.