What Sits Between the Modules

Workforce management is usually described as a set of functions. In practice it is a chain, and chains fail at the links.

The chain

Forecast produces a requirement.

Scheduling turns that into a rota.

Time capture records what happened against it.

Absence explains the gaps.

Payroll turns the result into money.

Each of those five works reasonably well in isolation. Four joins sit between them, and those are where the trouble is.

What a join actually is

A handover of data between two systems that model the world differently.

Scheduling thinks in shifts; time capture thinks in punches; payroll thinks in pay codes.

A shift that was scheduled, partly worked, partly covered by someone else and partly absent has to arrive at payroll as a set of amounts, and every step of that translation is a decision someone made once and wrote down nowhere.

The four failures

Identity. The same person exists in four systems with four identifiers, and one of them is a name.

Reference data. Departments, cost centres and locations differ between modules, so totals do not reconcile.

Timing. Scheduling is a fortnight ahead, time capture is live, payroll has a cut-off, and corrections arrive after all three.

Rules. Overtime is calculated in two places with slightly different definitions, and neither owner knows the other exists.

Why nobody owns them

Each module has an owner: operations owns the rota, HR owns absence, finance owns payroll.

The joins belong to whoever was in the room when the integration was built, who has usually left.

So when a figure is wrong, the investigation crosses three departments and stalls in the middle.

That is the single most common workforce management failure and it is organisational rather than technical.

What this collection covers

The joins, specifically: what crosses each one, in which direction, and who is accountable for it.

Identity and reference data, which underlie all four.

Buying decisions — a suite or several products — framed around the joins rather than the features.

Implementation sequencing, which is mostly about which join to build first.

And the reconciliations that catch a broken join before payroll does.

What it does not cover

How to build a rota, record attendance, manage absence or run payroll.

Those are subjects in their own right. This is about what happens between them, which is the part that is nobody's job.

Who this is for

Three audiences with different reasons to be here.

Whoever has been asked to fix a figure that crosses two systems and has found that each department's answer is correct.

Whoever is evaluating a purchase and needs the questions that separate products rather than the ones every vendor answers yes to.

And whoever will run the estate afterwards, which in most organisations is nobody in particular — a problem this collection returns to repeatedly.

A practical configuration prompt

During configuration, use workforce time tracking platform to prompt questions about identifiers, ownership and output. Treat the page as a starting point and document each assumption.