The Four Things

Fifty notes reduce to four actions. In this order, because each depends on the one before.

One: master identity

One system authoritative, everything else referencing it by identifier.

Prevents: people missing from reports, hours on the wrong name, payments to leavers, and access requests that cannot be answered.

Costs: a mapping exercise and a decision about which system is master.

Do this before anything else, because every other fix is unreliable without it.

Two: master reference data

One owner per dimension — site, department, cost centre — with effective dating where the products support it.

Prevents: totals that never reconcile, reports that cannot be compared, and costs landing in the wrong place.

Costs: an afternoon of comparison and an ongoing owner per dimension.

Three: write the rule register

Every pay rule and the single system that applies it.

Prevents: the classic defect of the same calculation in two places, which survives for years and is expensive in both directions.

Costs: an afternoon, and a review after every reconfiguration.

It is also the answer to the audit question — why was this person paid this — which nothing else provides.

Four: reconcile monthly

Four comparisons — headcount, reference data, hours, absence — run before the pay run rather than after.

Prevents: errors being found by employees rather than by the organisation, which is the difference between a correction and a grievance.

Costs: an hour a month, plus the investigations it generates, which fall as the causes are fixed.

What these four do together

They make the chain explainable.

Which means a wrong figure has a sequence to follow rather than three departments to ask, and a disputed payment has an answer rather than an account.

None of them requires buying anything.

And an estate with all four is in better condition than most estates that have just completed a replacement programme, which is the honest summary of this collection.

What the four do not cover

Stated plainly, because the list is short and could read as complete.

They do not build a rota, record attendance, manage absence or run payroll — those are subjects in their own right.

They do not fix understaffing, undecided rules or a product that cannot do the job.

What they do is make the chain explainable, which is the precondition for every other improvement and is where most estates are stuck.

Connect policy and data

The choices in this note can be compared with see this documented scenario. Keep the written purpose in control and enable only the information needed at this boundary.