Writing the Register
One table, seven columns, one row per population. It takes a morning, it will be full of gaps, and the gaps are the useful part.
The register, first draft, four populations
| Manufacturing site | Shared service centre | Field engineers | New sales office | |
|---|---|---|---|---|
| Place of work | One countryreference | One country✓ Same | Four countries△ Differs | Not determined△ Differs |
| Employing entity | Local companyreference | Local company✓ Same | Local company✓ Same | Head office entity△ Differs |
| Governing law | Localreference | Local✓ Same | Local✓ Same | differs△ Differs |
| Sector regime | Nonereference | none△ Differs | Road transport in two△ Differs | not recorded✗ Not recorded |
| Rules determined | Counsel, 2023reference | Counsel, 2023✓ Same | Partly△ Differs | not recorded✗ Not recorded |
Two rows are clean, one is partly done and one is empty. The empty row is nine people who have been working for eighteen months, and writing it down as empty is what makes it somebody's next task rather than nobody's.
The register is one table. It has a row per population and a small number of columns, it fits on a page, and it is the document the rest of this collection assumes exists.
The record described in “Writing the Register” should preserve the original entry, the correction and the approval rather than only a final total. When considering the provider's website for how to calculate idle time, teams should test that complete sequence, limit access by role and confirm that exported records remain understandable outside the live account.
Producing a first version takes a morning. It will have gaps, several rows will say "not determined", and that is the correct output of a first attempt rather than a sign it was done badly.
For an independent reference relevant to “Writing the Register”, consult the Verizon Data Breach Investigations Report. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.
The columns
Population — a named group, described the way the organisation talks about it. Place of work, as a country or countries. Employing entity. Governing law named in the contract. Whether a sector regime applies. Which rule set has been established as applying. And the source for that determination, with a date.
Seven columns. The first five are facts the organisation already holds somewhere. The sixth and seventh are the ones that require somebody qualified, which is precisely why the first five have to be assembled before anybody is asked.
Nothing in the register states what the rules require. It states who is under which set and where that was established, which is a different and much more durable kind of document.
How to define a population
By what makes the answer the same for everybody in it. A site is usually a population. A function spread across several countries usually is not, because the answer differs by country.
Start coarse and split when a row stops being true for everybody in it. Four or five rows on a first pass is normal for a mid-sized organisation; a register with forty rows is usually describing teams rather than populations and will not be maintained.
The test is whether somebody could read a row and know what applies to a named individual. If they would have to ask a follow-up question, the row needs splitting.
Filling it with what you have
Place of work comes from the payroll country reconciled against the directory and access records. Entity comes from finance. Governing law comes from the contract templates, which means opening them rather than remembering.
Sector regime needs an operational judgement about what people actually do, which is a conversation with whoever runs the work rather than a lookup.
Everything in that paragraph is available internally and none of it requires advice. The morning is mostly spent getting four lists into one place.
Marking the gaps honestly
A row where something is unknown says "not determined", not a guess. A row where the determination was somebody's assumption says so, with the name, rather than borrowing authority it does not have.
This feels uncomfortable and it is the entire value of the exercise. A register of five rows with two gaps is a short, specific list of things to find out. A register of five rows with no gaps, where two are guesses, is a document that will be relied on.
The gaps also make the cost of advice predictable. Two questions about two named populations is a quotable piece of work; "please review our working time compliance" is not.
Who confirms each row
The local entity, annually, for its own row. The centre owns the table and does not own the facts in it, because the centre cannot see a new office or a change of contract template.
A confirmation is one email with the row in it and one question: is this still accurate. The replies that say no are the value, and in most organisations there are one or two a year.
Where a row has no local owner — a population spread across countries, or a group employed through a provider — somebody central has to own it explicitly, and that name belongs in the table.
Where it lives
Somewhere dull and durable that survives a system change: a document in whatever the organisation uses for policies, not a page in a tool somebody set up.
Keep dated versions. The question that arises later is not what the register says now but what it said at the time, and a living document with no history cannot answer it.
The first row to fill
Start with the largest population in the organisation's main country, where the facts are known and the rules have probably been established.
Filling a row that is already understood sounds pointless and it is not: it establishes what a complete row looks like, which makes every subsequent row faster and comparable.
It also calibrates the sources. Writing down where the main country's determination came from frequently reveals that it, too, rests on something less solid than everybody assumed.