The Shape a Fair Process Has Everywhere

Almost every system asks for the same six things: tell the person what is alleged, show them the evidence, give them time to prepare, hold a meeting where they can respond, decide and give reasons, and allow an appeal. What differs between jurisdictions is the detail — the timing, the formality, who may attend, what the consequences of failure are — not the shape.

The workflow in “The Shape a Fair Process Has Everywhere” becomes more reliable when work records, approvals and later corrections can be distinguished. For teams exploring how to calculate idle time, this workforce tool can provide practical context, while policy ownership, employee explanation and final decisions remain with accountable people.

That is genuinely useful for an organisation operating in more than one place, because it means one internal standard can be built, with local variation layered on top. It is also dangerous, because the detail is where cases are lost, and the detail is exactly what a general shape omits.

For an independent reference relevant to “The Shape a Fair Process Has Everywhere”, consult the Verizon Data Breach Investigations Report. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

The six elements

The order matters as much as the content. Evidence shared at the meeting rather than before it defeats the purpose of giving time to prepare, and a decision written before the meeting defeats the purpose of the meeting.

1. The person is told, in writing, what is alleged and what the possible outcomes are.
2. They are given the evidence that will be relied on, in advance.
3. They are given enough time to consider it and prepare a response.
4. A meeting is held at which they can respond, ask questions and put their own case.
5. A decision is taken by somebody able to take it, and given in writing with reasons.
6. They are told they may appeal, to whom, and by when.

Nothing in that list is expensive. The failures are almost never failures of resource; they are failures of sequence.

Where the detail differs, and why it matters

Notice periods, the right to be accompanied and by whom, whether a particular category of dismissal requires consultation, how long an appeal has to be lodged, whether anything has to be filed with an authority, what compensation attaches to a procedural failure — all of these vary, and some of them vary within a single country by sector or by agreement.

An organisation running one process across several places should treat the six elements as a floor and ask locally what sits above it. The answer is a question for somebody qualified in each place concerned, and it is worth getting once and writing down rather than asking case by case.

What "enough time" means

The commonest procedural complaint is not that a meeting was unfair but that it was arranged for the following morning. Time to prepare means time to read the evidence, think, take advice and arrange for somebody to come with them.

What counts as enough is contextual and sometimes specified. As a working rule, if the person has not had the evidence for at least a few working days before the meeting, the organisation should expect to be asked why.

Deciding before the meeting

Everyone involved knows the likely outcome before the hearing, and pretending otherwise is not required. What is required is that the decision is actually open, which means two things: the decision-maker has to be capable of being persuaded, and nothing in the file can suggest the outcome was settled.

Draft dismissal letters dated before the hearing, calendar invitations for the handover meeting, an advert for the role — these appear in disclosure and they are decisive. The rule is simple: do not prepare the consequences of a decision that has not been taken.

If the outcome has in fact been decided before the meeting, the process is not a process, and the most useful thing anybody can do is say so internally and take advice before going further.

Reasons, not conclusions

A decision letter that says the allegations were upheld has not given reasons. Reasons explain what was found, on what evidence, what the person said about it, and why that did not change the outcome.

This is the part most often skipped, usually because the letter is written quickly by somebody who finds it uncomfortable. It is also the part that is read most carefully afterwards, and the part that makes the difference between a decision that is defensible and one that is merely final.

One standard, with local additions

For an organisation in several places, the workable structure is a single internal procedure built on the six elements, plus a short annex per jurisdiction covering what each place adds to the six: timings, who may accompany, any filing or notification, and anything that has to be offered.

The additions are short — usually a page — and they go out of date, which is the part that fails. Date them, name who confirmed them and when, and review them on a schedule rather than when somebody notices. A procedure that was correct in 2022 and has not been looked at since is more dangerous than having none, because people rely on it.

The appeal is part of the process

An appeal is not an optional courtesy appended at the end. In many systems it is capable of curing earlier defects, which means an organisation that got something wrong at the hearing stage has one chance to put it right.

That only works if the appeal is real: heard by somebody new, capable of reaching a different answer, and conducted after the person has been told what they may appeal against. An appeal offered in a sentence at the bottom of a letter, to a person who has already signed the decision, is not one.