Understaffing, and the work that never becomes extra pay

What follows is an argument about understaffing, and about where the received version of it stops being true.

Where the work goes

When a colleague leaves and the post is not filled, the tasks do not disappear; they are absorbed by the people who remain. That absorption is usually informal, unrecorded and framed as temporary, which is why it so often becomes permanent. The employer saves an entire salary while output holds up, which makes the arrangement look successful in every internal report.

The cost sits with individuals as longer hours, dropped tasks and a slow expansion of what the job involves. Because none of it is written down, none of it appears when pay is next discussed.

Why it becomes permanent

A team that copes is evidence that the post was not needed, which is precisely the wrong lesson but a very convenient one. Recruitment is expensive and slow, and a vacancy that produces no visible failure is easy to leave unfilled. People who absorb work quietly are frequently the most conscientious, which means the burden lands unevenly.

The failure, when it comes, tends to be a resignation rather than a missed target, and by then the cause is hard to attribute. Making the cost visible earlier is the only mechanism that changes the decision.

Documenting scope rather than complaining

A complaint about workload invites a conversation about resilience; a record of tasks invites a conversation about resourcing. List what you did before the vacancy, what you do now, and what has been dropped or delayed as a result. Attach dates, since the timeline is what demonstrates that the change followed the vacancy rather than preceded it.

Where it helps most, send it in writing to a manager, because a verbal account does not survive being repeated upward. The same document is the basis of a pay case later, which is the second reason to write it.

The pay argument that follows

Where a role has permanently absorbed responsibilities from a more senior or a departed post, that is a change in the job. Most pay structures have a mechanism for regrading or for an acting allowance, and it is reasonable to ask which applies. The strongest version of the argument compares your current duties against the job description for the post whose work you absorbed.

For most people, framing it as the organisation getting two roles for one salary is factual and difficult to dispute.

Where the answer is no, the request for a defined review date and criteria is the fallback worth securing.

Dropping work deliberately and safely

Where capacity genuinely does not exist, the responsible action is to say what will not be done rather than to fail quietly. Asking a manager to prioritise, in writing, transfers the decision to the person who is paid to make it. That protects you and it produces a written record of the resourcing position, which is useful for both sides.

In safety-relevant or regulated work, unrecorded gaps carry consequences well beyond pay, and they should be escalated formally. A manager who will not prioritise is themselves under pressure, which is information about where the real constraint sits.

Deciding what to do about it

Understaffing that management has acknowledged and is actively recruiting for is a temporary problem worth tolerating. Understaffing that has been normalised for a year, with no recruitment and no pay recognition, is the design of the job.

Distinguishing between the two changes whether the right response is patience or an external search. Colleagues raising the same issue collectively carry considerably more weight than the same points raised individually. Where a union or staff forum exists, resourcing levels are a standard and legitimate matter for it to take up.

The takeaway

Write down what changed and when; absorbed work only becomes pay if somebody recorded it.

The version you keep doing is the version that works.