Skip to content
Standing Date

Telling People It Went Wrong

How a payroll error is communicated matters more than the error. The same mistake can be a non-event or the thing people remember about working there.

Nobody elseif the person who does this is away

Home / When it goes wrong

When it goes wrong · Analysis

How a payroll error is communicated matters more than the error itself. The same mistake, handled two ways, is either a forgotten administrative hiccup or the thing somebody mentions about the business years later.

The exception in “Telling People It Went Wrong” needs evidence that can be checked rather than one unexplained total. Used for hourly timesheet template, a practical route to hourly timesheet template can provide time and project context, but a payroll correction should still rely on approved records, the payroll ledger and a documented human review.

The difference is almost entirely in the first hour.

For an outside reference relevant to “Telling People It Went Wrong”, consult Trello workflow guide. Compare general guidance with the employer’s jurisdiction, contracts and current payroll process.

Tell them before they find out

The single most important thing. An error you report is a business that checks its work; an error they discover is a business that does not.

What the first message contains, and nothing else:

  1. What happened.
  2. That it was the business's error.
  3. What is being done.
  4. When it will be resolved.

The cause comes later, if they want it. Most will not.

The same correction, the same money, a completely different reading.

How fast

Immediately on knowing, before you know the cause. Waiting until you have a full explanation feels responsible and is experienced as concealment.

What the first message contains

What happened, that it was the business's error, what is being done, and when it will be resolved.

Four things, short, with no explanation of the mechanism.

What to leave out at this stage

The cause. People do not want to hear about the software, the timesheet that arrived late, or how payroll works, and in the first hour all of it reads as excuse.

The explanation can come afterwards if they want it, and most will not.

Who says it

Whoever is senior enough that it is clearly being taken seriously. In a small business that usually means the owner, even if the payroll person found it.

An error reported by the person who made it is fine; an error reported only by them can look like it was not escalated.

Individually or to everybody

Individually if it affected individuals. A general message about a payroll error leaves everybody checking their own payslip and some concluding wrongly that they were affected.

A general message is right only when everybody was affected.

Saying sorry once

Once, plainly, without elaboration. Repeated apologising shifts the conversation to your discomfort, which the person is not interested in and now has to manage.

Sentences that make it worse

That it is unusual, when it is the second time. That the software did it. That it will not happen again, unless you have actually changed something.

The last is the one that costs most, because it is checkable.

Saying what changed

Afterwards, briefly: here is what we have changed so this does not recur. It is the part that restores confidence, and it requires actually having changed something.

When it affects somebody's own position elsewhere

If the error has consequences for the person with a third party — a lender, an authority, another employer — say so explicitly rather than leaving them to discover it.

When more than one person is affected

Tell all of them, including the ones who have not noticed. A business that corrects the complainers and stays quiet with everybody else has created a worse problem for the day it comes out.

Keeping a note of what happened

What happened, who was told, when, what was done. Short, and kept.

Patterns in payroll errors are visible only across months, and nobody remembers accurately.

What people actually judge

Not accuracy, which they assume. Speed, honesty about fault, and whether it recurs. A business can be forgiven two errors handled well and not one handled badly.

What an hour of delay actually buys

Nothing, in every case. The cause will be no clearer for being investigated first, the correction will take the same time, and the only thing that changes is whether the person heard it from you.

Businesses wait because telling somebody feels like a step that should follow understanding. For the person affected it is the step that should precede everything.

Saying it to somebody who is already angry

Some of these conversations start badly, particularly where it is the second occurrence or where the person has been short of money because of it.

The approach that works is the same, more slowly: the facts, the fault, what is being done, when. Defending the business at that moment achieves nothing and is what turns an apology into an argument.

The follow-up a week later

Short, and worth sending: this is what we changed.

It is the part that distinguishes a business that handled an error from one that merely survived it, and it costs two sentences.

The thing worth holding on to

The error is about money somebody is relying on. Every minute of delay and every sentence of deflection is read in that light, and the whole of handling it well is remembering that before replying.