Telling the People Affected

Tell people what was wrong, for how long, what they are owed and when they will get it — in that order, in writing, before the money arrives. A payment that appears with no explanation generates more alarm than the error did, because an unexplained change in pay is indistinguishable from a new mistake.

The correction process in “Telling the People Affected” requires a visible history rather than an overwritten total. If this practical resource supports attendance sheet template, administrators should test amendment, approval and export workflows so a later review can distinguish the original entry, the question asked, the correction and the person who accepted it.

The communication is also the part of a correction that gets delegated latest and written fastest, which is how a competent piece of remedial work ends up being remembered for a badly worded letter.

For an independent reference relevant to “Telling the People Affected”, consult the Asana work-management resources. Use it to test record quality, working-time definitions, access, retention and exception handling against the organisation’s real payroll process.

What the letter contains

• What went wrong, described plainly enough that the person recognises it.
• Which periods are affected, by date.
• What they are owed, gross, with the breakdown attached.
• When it will be paid, with a date.
• What has been done so it does not recur.
• Who to contact with a question, by name, with a real route.

Six items. The fifth is the one people actually want and the one most often left out, because it requires the organisation to describe its own fix.

Explaining the cause

"Due to a system configuration issue" explains nothing and reads as evasion. "The rate used to calculate overtime included your basic pay but not your shift allowance, so every overtime hour since April 2022 was paid at a lower rate than it should have been" explains it.

The second version takes one more sentence and it is the difference between a letter that closes the matter and one that produces a round of questions from people who suspect there is more.

The order to tell people

1. The people affected, individually, in writing.
2. Their managers, shortly before or at the same time, with the same facts.
3. Any representative body, where one exists, usually before the individuals.
4. Former employees affected, by whatever route reaches them.
5. Anybody internally who will be asked about it.
6. Nobody else, unless there is a specific reason.

Step two is routinely missed and it produces the worst version: a manager asked about a letter they have not seen, guessing, and guessing wrongly.

Apology, briefly

Say it once, plainly, and move on. A letter that apologises at length reads as managing the recipient rather than informing them, and it delays the information they actually want, which is the figure and the date.

What is worth saying explicitly is that the person did nothing wrong and that raising a question about it will not cause any difficulty. In some workplaces that is not obvious and the sentence costs nothing.

People who will ask about other things

An underpayment letter prompts questions about everything else on the payslip, from people who now have a reason to look.

That is a legitimate consequence and worth preparing for: a short reference for whoever answers, covering the most likely adjacent questions, prevents the inconsistent answers that turn one issue into several.

Where the amount is small

Small corrections still need the letter, and the letter can be shorter. What it cannot do is omit the explanation, because an unexplained £4.20 raises exactly the same question as an unexplained £420.

Where the amount is large

Large corrections need the letter, the breakdown, and a conversation offered — not required — with somebody who can answer.

Offer a conversation for anybody who wants one and do not insist on it. A correction letter that requires the person to attend a meeting before being paid turns a remedy into an obstacle.

What to say to people who were not affected

Corrections become known, and people outside the affected group will ask whether they are included.

Have an answer ready: who was affected, why, and how somebody can check. A vague response produces a wave of individual queries from people who now suspect their own pay, which costs more than the original communication would have if it had anticipated the question.

Where the error is still being investigated

Sometimes people have to be told before the scope is settled — because word has got out, or because the first payment is going to a subset.

That is survivable if it is said plainly: what is known, what is not yet known, and when the next update will come. What damages confidence is a confident statement of scope that is then revised twice, which is what happens when an organisation communicates before it has finished counting.

The file the correction leaves

A copy of every letter, the date sent, the route, and any response. With the model and the breakdown, that is the complete record of the correction.

It is also what the organisation will need if the same question arrives from outside. An employer that can produce the letter it sent, on the date it sent it, with the figures attached, has answered most of what anybody will ask about how it handled the error.