One Person, Four Records

Every workforce system holds a record of the same human being, and in most organisations none of those records agrees on how to name them.

What goes wrong

Payroll has an employee number. Scheduling has a login. Time capture has a badge. HR has an email address.

None is the same string, and the mapping between them exists in a spreadsheet somebody maintains.

A person changes name, and three systems update at different times.

Someone is rehired and gets a second record, so their history splits.

An agency worker exists in one system and not another, and their hours land nowhere.

Why it produces confusing errors

A broken identity mapping does not fail loudly.

It produces a person missing from a report, a shift attributed to the wrong name, a payment to a leaver, or hours that vanish.

Each of those gets investigated as its own incident by whoever noticed it, and the common cause is never found because the incidents look unrelated.

The rule

One system is the master for identity, and everything else references it.

Almost always HR or payroll, because that is where joining and leaving are recorded.

Every other system holds the master identifier as a field, and matches on it rather than on name, email or badge.

Names are for humans. Identifiers are for systems. Matching on a name works until two people share one, which in a workforce of any size is immediately.

The joiner, mover, leaver path

Joiner: the master record is created first, then downstream systems, in a stated order. A person scheduled before they exist in payroll is the commonest cause of an unpaid first week.

Mover: a change of team, site or contract has to propagate, and the systems that do not receive it produce the reference data mismatch in its own note.

Leaver: access removed everywhere, record retained per policy, and the scheduling system in particular checked — a leaver still on a rota is a coverage gap nobody sees until the day.

The check worth running

Count records in each system and compare.

Then reconcile: who exists in payroll but not scheduling, and the reverse.

The differences are always larger than expected, and each one is a person whose data is going somewhere it should not.

Run it monthly, because it drifts continuously and the drift is invisible until it costs something.

Run the count monthly

The simplest check in this collection.

Records in each system, compared.

Who exists in payroll but not scheduling, and the reverse.

The differences are always larger than expected, and each one is a person whose data is going somewhere it should not.

It drifts continuously, which is why monthly beats annually and why an annual check finds a backlog rather than a cause.

Connect policy and data

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

Independent reference

For a thematic point of reference, see the National Institute of Standards and Technology. Use this established source as an outside check before turning the principle into a system rule.