Dismissal, Redundancy or Something Else?

Name the thing before you start, because the name decides everything that follows: which process applies, who has to be consulted, what is owed, and what evidence somebody will ask for afterwards. Organisations routinely begin a conversation without having decided, and then argue for a different label once the first one stops being convenient.

The decision process in “Dismissal, Redundancy or Something Else?” needs evidence that can be checked without turning one activity signal into a conclusion. When reviewers consider the official Monitask website for how employee monitoring works, its time and project records can provide operational context, but allegations, employee responses and consequential decisions still require a fair human process.

The confusion is understandable. Internally, every one of these situations sounds the same — a manager who wants somebody gone, a conversation that has to happen, an awkward few weeks. Externally they are different animals with different requirements.

For an independent reference relevant to “Dismissal, Redundancy or Something Else?”, consult the NIST Privacy Framework. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

The categories, in the terms the work actually uses

Capability and conduct are not the same thing, and treating a capability problem as misconduct is one of the most common and most visible errors. The first is about whether somebody can do the job; the second is about whether they chose not to.

Redundancy is about the job, not the person, and it brings its own machinery: a pool, criteria, consultation, a search for alternatives. A redundancy used as a convenient route out of a performance problem is a redundancy that will not survive being looked at.

• Conduct — something the person did or failed to do, against a known rule.
• Capability — performance or ill health, where the question is ability rather than choice.
• Redundancy — the job is going, or fewer people are needed to do it.
• End of a fixed term, which may or may not count as a dismissal where you are.
• Resignation, including resignations that are really dismissals in disguise.
• The ending of an engagement with somebody who may never have been an employee.

Why the label is not a formality

Each category carries its own process, and the processes are not interchangeable. Consultation obligations attach to some and not others. Notice may be calculated differently. What has to be offered — an alternative role, an adjustment, a trial period — differs. So does the evidence: a conduct case needs a rule and a breach, a capability case needs a standard and a measured shortfall.

Pick late and the file shows it. A set of documents that talks about performance for four months and then switches to redundancy, or the reverse, is a set of documents that explains itself to anybody reading it in order.

The question of employment status

Before any of the above, there is a prior question that organisations skip because it is uncomfortable: is this person an employee at all? Somebody engaged as a contractor, through an intermediary, or on a casual arrangement may or may not have the protections an employee has, and the answer rarely matches what the paperwork says.

The written agreement is the starting point and not the finish. What tends to matter is how the arrangement actually worked: who controlled the work, whether the person could send somebody else, whether there was an obligation to offer and accept work at all. Where that question is live, it is a question for somebody qualified in the place concerned, and it is much cheaper to ask before ending the engagement than after.

Mixed cases, which is most of them

Real situations rarely arrive in one category. Somebody whose performance has been poor is also the person whose role is being restructured. Somebody with a conduct issue is also on long-term sick leave. A fixed term is ending for somebody who has been there for six years on four consecutive contracts.

The answer is not to pick whichever label is most convenient. It is to write down what is actually happening, in plain sentences, and then take advice on which route fits — accepting that the honest answer is sometimes that two processes have to run, or that one has to be resolved before the other can start.

Write a short statement of facts before you choose a route: what has happened, since when, what has already been said to the person, and what the organisation wants to achieve. Choose the label from that, not the other way round.

Changing your mind later

Sometimes the first label is genuinely wrong and has to change. That is survivable if it is done openly: say so, explain why, restart the appropriate process properly, and accept the delay.

What is not survivable is quietly switching — carrying on as though the earlier months had always been part of the new route, reusing documents that were written for a different purpose, or presenting a performance file as redundancy selection evidence. The attempt to paper over the change becomes the story, and it is the thing that reads exactly like what it is.

Writing the answer down

The determination belongs in the file, dated, with a line of reasoning and the name of whoever made it. Three sentences is enough.

This is not bureaucracy for its own sake. Six months later, the useful question is not what route was taken but whether anybody thought about it, and a dated note answering it is the difference between a considered decision and a drift. It is a question worth asking once, properly, at the start.