Four Systems, Four Clocks

Scheduling looks a fortnight ahead. Time capture is live. Payroll has a cut-off. Corrections arrive after all three. None of these is wrong and together they conflict.

The four horizons

Forecasting: weeks to months.

Scheduling: published a fortnight ahead, then frozen.

Time capture: the current day, continuously.

Payroll: a fixed period with a hard cut-off.

Corrections: whenever someone notices, which is after the cut-off.

What the mismatch produces

A change made in scheduling after publication has to reach time capture, which is already running against the old version.

An absence approved after the rota is built leaves a shift with nobody in it.

A correction submitted the day after cut-off waits a full period or triggers an off-cycle payment.

And a reference data change mid-period splits the period into two structures, so the totals do not add up.

Deciding the cut-offs deliberately

Write down: when the rota freezes, when time data closes, when corrections must be in, when payroll runs.

In that order, with gaps between them.

Most organisations have three of these written and one assumed, and the assumed one is where the pressure lands.

A correction deadline that sits after the payroll cut-off is not a deadline.

Effective dating

The technical answer to structural change.

Every reference data record carries the dates it was valid, so a report spanning a reorganisation uses the right structure for each part.

Most workforce systems support this and most implementations do not use it, because it is extra work at setup and the cost appears a year later.

Ask whether your systems support it before you need it, because retrofitting effective dating is not practical.

The correction window

Corrections will arrive after every cut-off. Plan for it.

Decide: held to next period, off-cycle, or re-run.

Say which in advance, because the person's question is when they will be paid.

And track how many arrive late, because a high number means an upstream deadline is unrealistic rather than that people are careless.

The check

Take one period and map every deadline against when data actually arrived.

The gaps show which deadline is fictional.

Usually one of them is, and moving it is free.

Find the fictional deadline

One period of mapping reveals it.

Map every stated deadline against when data actually arrived.

Usually one of them is honoured by nobody and everything downstream absorbs the slack.

Moving it to where it actually is costs nothing and removes the weekly pressure that currently lands on whoever is last in the chain.

Connect policy and data

The choices in this note can be compared with open this project connection. 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 Internal Revenue Service. Its current material provides useful context beyond product documentation.