The Gap.

We tell ourselves stories about process.

An employer tells herself that because the letter was correctly drafted, the process it describes must have been correctly followed. An employee tells himself that because the letter arrived on firm letterhead with statutory references, the institution behind it must have been thorough. A human resources manager tells herself that because the steps appear in the file in the right order, they must have occurred in that order.

These are stories. They are the stories people tell in order to proceed — to sign the letter, to file the document, to move on.

They are not, in my experience, descriptions of what happened.

The employer was referred to me by his accountant. He was a reasonable man. He had dismissed an employee and he believed the process had been properly conducted. The letter was correctly drafted. The statutory references were accurate. The tone was appropriate.

Who conducted the investigation?

The operations manager.

Who made the final decision?

The operations manager.

He did not see the problem. He was not evasive. He was not defensive. He simply did not see it.

A person who investigates an allegation, evaluates the evidence, and delivers the outcome has completed a cognitive sequence in which the conclusion precedes the meeting at which the employee is invited to respond. The meeting still occurs. The employee still speaks. The decision has already been made. That is not a matter of interpretation. It is a structural fact about the sequence, and it was visible in the answer to one question.

The letter was fine. What the letter described had not occurred in the way the letter described it.

We had approximately three weeks. We did not rewrite the letter. We rebuilt what was underneath it.

There is always a gap.

Between what a formal document claims and what the system behind it can actually support. Between the policy as written and the policy as followed. Between the process that was promised and the process that was experienced. Between what an organisation says it does and what it does on an ordinary Tuesday when the pressure is real and no one is watching.

The gap is not a technicality. It is not a loophole. It is the distance between the story an organisation tells about itself and what the organisation actually does. That distance is where most employment disputes originate. It is also where most of them are resolved — once it has been found, measured, and placed on the table in a way that neither side can explain away.

What happens next depends on which side of the table is looking at it.

For an employer, the gap is the thing that needs correcting — quietly, structurally, before it becomes the foundation of someone else's case. For an employee, the gap may be the case itself — the distance between what was supposed to happen and what did.

The same gap. Two uses. That duality is the practice.

The letter arrives on a Tuesday morning.

It is formal. It carries statutory references, procedural language, the particular weight of institutional correspondence. It was reviewed before it was sent. The language implies thoroughness. The letterhead implies resources. The overall effect is designed to convey that the matter has been carefully considered and the institution is prepared to defend its position.

Most people read a letter like that and feel the ground shift. They feel the weight and they assume the weight is structural — that the process behind the letter is as sound as the language suggests.

This is worth examining.

The formality of the language does not tell you whether the investigation was independent of the decision. The statutory references do not tell you whether the employee's response was treated as a genuine input or as a step that occurred after the outcome was already determined. The letterhead does not tell you whether the documentation reflects a real sequence of events or a narrative assembled retrospectively to support a conclusion that was reached before the process began.

None of the things that make a letter feel heavy are the things that make a process sound.

There is a kind of process that exists only to support a conclusion that has already been reached.

The documentation is assembled after the decision. The performance improvement plan is calibrated to produce a specific failure. The restructure eliminates one position held by one person. These are recognisable. They have a particular quality — a neatness that genuine processes do not have. A coherence that comes from being designed backwards, from outcome to evidence, rather than forwards, from evidence to outcome.

Building these is available work. There are practitioners who provide it.

This practice does not.

A process that strips someone of their livelihood without genuine fairness is wrong. That is not a word chosen for rhetoric — it is chosen for precision. And a manufactured process is also, structurally, a failed one. The neatness is the tell. The backward construction is the gap. It is usually the easiest thing in the file to see, and it is always the most expensive.

If that is the work being requested, the first meeting is where that conversation happens. Not the second. Not after the invoice. The first.

The question underneath all of this is simple: how does a structural failure in a document become visible?

The answer begins somewhere unexpected.

Civil law — the Napoleonic tradition, taught in a Colombian law faculty — is architectural in a way that common law training does not require. Years are spent building the underlying framework of a legal system before a case is ever approached. The study is not of rules applied to facts. It is of structures — load-bearing principles, the joints where elements connect, the places where elements that should connect do not. A legal document, read through that formation, says something different from what it appears to say. It reveals not its claims but its tolerances — what it can structurally support and where it will give way under weight.

An investigation report, read this way, is not a narrative about what happened. It is an architecture. The question is not whether it is well-written. The question is whether the structure underneath the writing holds.

That reading produces correspondence that looks different from what the other side typically expects. There is no argument in it. No escalation of tone. No matching of formality or volume. The structural failure is identified, presented with evidence and specificity, and the analysis stops. The person who receives it does not see a position to argue against. They see their own position described back to them with a precision that was not anticipated.

What follows is usually a different kind of conversation.

There is a thing that happens when you spend years alternating between sides of the same table.

From the employer's side, a process looks like a sequence of reasonable decisions made under pressure. The investigation was conducted. The meetings were held. The documentation was completed. The letter was sent. Each step feels, from inside the organisation, like it was taken in good faith and in the right order.

From the employee's side of the same process, different things become visible. The step that was compressed because someone was busy. The meeting where the outcome was already evident in the room before anyone spoke. The document that appeared in the file at a moment that does not survive examination. The response that was received, filed, and given no weight.

What accumulates, over time, from working both vantage points is pattern recognition. The failures recur. They occur in the same places, in the same patterns, in organisations that bear no resemblance to one another except in this: the distance between what the documentation describes and what the system does. After twenty-two years, the patterns are not hidden. They are simply not visible from one side of the table alone.

The gap is always there.

Sometimes it needs correcting — quietly, structurally, before it becomes the foundation of someone else's case. Sometimes it needs to be placed on the table, clearly and without drama, so that everyone in the room can see where things actually stand.

This is a practice based in Palmerston North. Employment advocacy. Independent workplace investigations. Mediation representation. Process review. Matters that cross employment, immigration, privacy, and official information simultaneously.

For employers: the gap in your process exists. The question is whether you find it before someone else does. A review now costs less than a defence later — and the output is not a report. It is a system that works.

For employees: the letter you received was designed to create a feeling. Whether the process behind it can support what the feeling implies is a question that has not been asked yet. The first conversation costs nothing.

Come and talk. The question that matters is not whether you can afford to find out.

The question is whether anyone has looked.