The Resignations That Were Really Dismissals

Check every resignation against what happened in the six months before it, because a departure recorded as voluntary is not necessarily voluntary and the organisation's own records will not tell you which is which. The field says resignation because the person sent a letter, and the letter was sent the week after a conversation nobody wrote down.

The decision process in “The Resignations That Were Really Dismissals” needs evidence that can be checked without turning one activity signal into a conclusion. When reviewers consider this team-management platform for step rate compensation, its time and project records can provide operational context, but allegations, employee responses and consequential decisions still require a fair human process.

This matters individually, because a resignation that follows pressure may be characterised differently afterwards. It matters more in aggregate, because an organisation that classifies these as voluntary has a turnover picture that is systematically wrong.

For an independent reference relevant to “The Resignations That Were Really Dismissals”, consult the AWS incident-response guide. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

What to look for

• A resignation within weeks of a disciplinary or capability conversation.
• A resignation following a change of role, reporting line or duties the person objected to.
• A resignation after a grievance, particularly one that was not upheld.
• A resignation with immediate effect, or with no notice worked.
• A resignation following a return from long-term absence.
• A resignation where the letter is unusually short, or unusually long.

None of these means anything on its own. Together with a file that contains no contemporaneous notes, each of them is worth a question before the departure is closed.

The conversation that preceded it

The specific pattern worth knowing about is the offer to resign: a manager tells somebody that a process is coming and that resigning would be tidier.

Managers do this believing it is kind, and sometimes it is. It is also the thing most likely to turn a departure into a dispute, because what was said is not recorded and the two accounts of it will differ. Where the possibility of settlement is genuinely being raised, there is a proper way to do it, and what that is where you operate is a question for somebody qualified in the place concerned.

Resignations given in the moment

Somebody resigns in anger, in a meeting, or by message at eleven at night. Taking it at face value is legally possible in many systems and operationally unwise.

The usual practice — acknowledge, do not act immediately, give the person a short period to confirm in writing when calmer — costs a few days and resolves a large proportion of these without anything further. Accepting on the spot and processing it the same afternoon is what produces the argument about whether it was a resignation at all.

Recording the real reason

The leaver record should carry two fields: the route out, and the reason. Resignation is a route. "Resigned during a capability process" and "resigned to move abroad" are both resignations and they are not the same event.

Adding a reason field, with a short list of consistent values, is a change that costs nothing and makes every subsequent aggregate honest. Without it, the organisation's own data is organised to obscure exactly the thing a review is looking for.

What the aggregate shows

An organisation with nine resignations in a year, four of which followed a process within six weeks, has a different situation from one with nine unrelated departures — and no standard report distinguishes them.

Making that distinction once a year is usually how the pattern is found. It tends to concentrate: the four will frequently come from one or two places, which is a finding about management practice rather than about turnover.

Constructive dismissal, briefly

Where somebody resigns because of something the organisation did, that may be treated as a dismissal in its own right in many systems, with consequences attached.

The threshold, and what counts, differ and are a question for somebody qualified in the place concerned. The operational point is narrower: a resignation preceded by a grievance about something the organisation did is a resignation worth taking advice about before it is simply processed.

Asking at the time

The simplest intervention is a short conversation with anybody who resigns, by somebody outside their management line, within a few days: is there anything about how this came about that we should know?

Most people say no. The ones who say something else are the cases this page is about, and finding out while the person is still employed is substantially better than finding out afterwards through correspondence.

Closing these properly

Where a resignation follows a process or a dispute, the file should contain the same material as any other exit — the notes, the correspondence, the reason — rather than being closed as routine because the person chose to go.

The record is thinner precisely where it is most likely to be needed, which is the pattern this whole collection keeps returning to: the file is assembled according to how much trouble the organisation expects, and the expectation is frequently wrong.