Followers

When HACCP Meets COSHH and the Fog Suddenly Gets Nervous

When HACCP Meets COSHH and the Fog Suddenly Gets Nervous

There is a moment in every long-running dispute when the tone changes.

Up until that point the system assumes you are just another complaint file.
Another email.
Another form.
Another person who will eventually run out of steam and disappear into the polite fog of “we will review this matter in due course.”

Then something slightly inconvenient happens.

You turn up with structure.

Not noise.
Not outrage.
Structure.

And if that structure happens to come from industries where mistakes actually kill people, the entire atmosphere shifts.

Because suddenly the conversation is not about opinions anymore.

It is about risk control.


---

Two Things Bureaucracy Fears

In the funeral trade, and in professional kitchens before that, I learned two systems that make even the most relaxed regulator sit up straight:

HACCP and COSHH.

They sound technical—and they are—but the idea behind them is brutally simple.

Identify the risk.
Control the risk.
Document the risk.

If something goes wrong, you don’t argue about feelings. You follow the record.

That mindset becomes extremely interesting when it is applied outside kitchens and laboratories and into something like institutional accountability.

Because suddenly the question changes.

Not “What do you think happened?”

But:

“Where is the control point?”


---

HACCP: The Discipline of Control

HACCP stands for Hazard Analysis and Critical Control Points.

It is used in food safety around the world, but the logic is universal.

You break a system into steps.

Then you ask a very uncomfortable question at every stage:

Where could this go wrong?

Not theoretically.
Practically.

Where is the point where one mistake triggers a cascade?

Those points are called critical control points.

And once you identify them, you monitor them relentlessly.

Temperature logs.

Process records.

Verification checks.

Because when something fails, you need to know exactly when and where it failed.

---

COSHH: The Other Half of the Equation

COSHH—Control of Substances Hazardous to Health—comes from a different angle.

Instead of focusing on process steps, COSHH focuses on exposure to harm.

Chemicals.

Biological hazards.

Anything that could damage a worker or the public.

The system asks three basic questions:

What is the hazard?
Who could be harmed?
What controls prevent that harm?

Again, everything is documented.

Because when an incident happens, the first thing investigators ask is not “who is angry?”

They ask:

“Where is the risk assessment?”


---

Now Apply That Thinking to Institutions

Here is where things become quietly amusing.

Take those same principles and apply them to an administrative system.

Suddenly the entire fog starts to thin.

Because every event becomes part of a chain.

Incident.

Report.

Response.

Outcome.

Each stage becomes a control point.

And control points produce records.

Records produce timelines.

Timelines produce accountability.

Which is exactly why large organisations normally maintain strict documentation policies.

The irony, of course, is that sometimes those policies work both ways.


---

The Archive That Wasn’t Supposed to Exist

When people imagine complaints, they imagine a letter or two and a bit of back-and-forth.

What they don’t expect is an archive built like a compliance file.

Chronology.

Exhibits.

Correspondence.

Integrity records.

Chain-of-custody logs.

In other words, the same type of documentation used in industries where regulators take safety very seriously.

When that level of organisation appears in a personal dispute, the reaction can be… interesting.

Because suddenly the conversation is not about personality or narrative.

It is about evidence architecture.


---

Experts Don’t Read Everything

Here is something most people do not realise.

When an expert reviewer, investigator, or ombudsman looks at a large archive, they do not read it like a novel.

They scan for control points.

They want to know:

Where did the event occur?
Who was notified?
What action was taken?
What documentation exists?

If those four questions align clearly, the entire story becomes visible in minutes.

Which is why the structure of an archive matters more than its size.

Ten thousand documents are useless if they are chaotic.

Fifty documents can be decisive if they are organised.


---

When Systems Meet Their Own Rules

There is a quiet irony when HACCP-style thinking enters a dispute with institutions.

Because many of those institutions already operate under compliance frameworks of their own.

Audit trails.

Governance standards.

Record-keeping obligations.

Transparency rules.

When a well-structured archive appears, it essentially mirrors the logic of those systems back at them.

It says:

“Here are the steps.
Here are the records.
Here is the timeline.”

At that point the fog becomes harder to maintain.



The Real Lesson

None of this is about winning arguments.

Arguments are cheap.

What matters is traceability.

Can an independent person follow the events from start to finish?

Can they see the moment where something changed direction?

Can they identify the point where a system should have acted but did not?

Those are the questions regulators care about.

Everything else is commentary.


---

Why This Matters Beyond One Case

The deeper lesson here is not personal.

It is structural.

Modern systems—legal, financial, administrative—are incredibly complex.

That complexity creates distance between institutions and the people they serve.

Documentation bridges that distance.

Not dramatically.

Not emotionally.

But methodically.

And once a methodical record exists, reality becomes difficult to ignore.


---

The Quiet Power of Order

There is an old principle in both kitchens and mortuaries.

If something goes wrong, you do not panic.

You check the logbook.

Because the logbook tells the truth.

Temperature recorded.

Time recorded.

Signature recorded.

The same principle applies to disputes.

When the record is clear, the fog eventually clears with it.


---

The Mindspire View

Mindspire was never about shouting into the void.

It was about structure, clarity, and lived experience translated into evidence.

Life is messy.

Systems are rigid.

Bridging those two worlds requires patience and organisation.

Sometimes a lot of organisation.

But when experience is documented properly, something interesting happens.

The story becomes visible not just to the person living it—but to anyone willing to examine the record.

And that is where real understanding begins.

---

Michael P. Lennon Jr
Bellaghy
Mindspire Blogs
Life, Death, and the Gap Between

KEY Notes

Maladministration is usually identified through patterns of poor administration. Investigators and ombudsmen look for specific types of failures in how a public authority handled a matter. The following list reflects the kinds of issues commonly recognised in UK administrative oversight.

Delay in dealing with a matter when action should have been taken sooner.

Failure to follow the organisation’s own procedures or statutory rules.

Ignoring relevant evidence, records, or witness statements.

Taking into account irrelevant factors when making a decision.

Failure to keep proper records or documentation.

Providing inaccurate or misleading information to the public.

Failing to explain a decision clearly or provide reasons.

Poor communication with the person affected by the decision.

Failure to investigate a complaint properly.

Losing documents, files, or evidence that should have been retained.

Inconsistent treatment of similar cases without a clear justification.

Bias or the appearance of bias in decision-making.

Failure to consult or notify people who should legally have been informed.

Applying rules incorrectly or misunderstanding the law or policy.

Failure to act on information that indicated a problem or risk.

Passing responsibility between departments without resolving the issue.

Administrative negligence that results in financial loss or other harm.

Failure to implement decisions that were already agreed or approved.

Refusing to review a decision when a review process exists.

Providing incomplete responses to formal complaints or enquiries.

Oversight bodies such as the Northern Ireland Public Services Ombudsman and the Local Government and Social Care Ombudsman typically assess these factors when deciding whether maladministration occurred.

In simple terms, maladministration is not about whether a person liked the outcome. It is about whether the process was handled fairly, competently, and according to proper administrative standards.