Running the Correction Process

Corrections are not a sign of a failing system. Ignoring them is.

The route

The worker submits it themselves, from the app, in seconds.

With a reason from a short list: no fix, no signal, phone unavailable, forgot, wrong site.

A named approver, with a deadline before the pay period closes.

Approved or queried, never left, because an unresolved correction becomes an underpayment.

Visible to the worker throughout, so they know it is in hand.

What not to require

Finding a manager in person, which costs both of them time and produces corrections that never get submitted.

A written explanation, which is a barrier and rarely adds information beyond the reason code.

Approval from someone who was not there, which is theatre.

Evidence, which for a technical failure the worker cannot produce.

Reading the volume

Corrections per site, per week.

By reason.

A site with many "no fix" corrections has a coverage problem, and the correction volume is the cheapest way to find it.

A person with many corrections usually works at that site, which is why the site view comes first.

Rising volume overall follows a phone update or a vendor release more often than anything else.

The approval load

Exception-based, not every correction individually scrutinised.

Approve the ordinary ones in a batch; look at the unusual.

Measure time to resolution, which is the worker's experience.

If the approver is overloaded, the fix is the refusal rate, not a faster approver.

What to record

The original punch attempt, if there was one.

The correction, its reason, who approved it and when.

The resulting paid time.

Because this is the chain someone will ask about in a dispute, and a correction with no record of what it replaced explains nothing.

The signal worth watching

Corrections falling to near zero is not necessarily good.

It can mean the system improved.

It can also mean people stopped bothering — working unpaid minutes rather than submitting a form.

Ask a few people. The answer is more reliable than the number at that point.

Approve generously at first

A policy for the opening fortnight.

Volume will be high because the system is new.

Querying corrections at that point teaches people not to submit them, and absorbed unpaid minutes are the result.

Tighten later, once the refusal rate has settled and an ordinary correction is distinguishable from an unusual one.

An implementation prompt

During configuration, the service-team example can prompt questions about fields, ownership and output. Confirm current capabilities and document each plan, integration or policy assumption.

Independent reference

For an external point of reference, see the GOV.UK service. This popular specialist source offers a useful reference beyond product documentation.