Dancing on the Edge of “Information”: Capeling v TFX Group Ltd [2026] EAT 57

Some cases arrive at the Employment Appeal Tribunal like thunderclaps, reshaping doctrine or unsettling long‑held assumptions. Others arrive quietly, almost modestly, but leave behind a sharper understanding of the law’s boundaries. Capeling v TFX Group Ltd is firmly in the second category: a small case with a precise point, a reminder that whistleblowing protection is not a catch‑all shield but a carefully defined statutory mechanism with limits that matter.

At its heart, this appeal was about a single question: when does a workplace concern cross the line from a vague complaint into a protected disclosure? The answer, as the EAT makes clear, is not when the claimant believes it should — but when the law says it does.

The Story Behind the Appeal

Mrs Capeling had been employed as a National Sales Manager from March to September 2022. Her dismissal was abrupt — immediate, with only a week’s wages in lieu of notice — and justified by the employer as a response to poor performance. She, however, saw a different narrative: one in which she had raised concerns about health and safety, only to be punished for speaking up.

This disclosure, according to the claimant, was a warning that the company lacked written contracts with certain Dispensing Appliance Contractors (DACs), and that this absence was putting patient safety at risk — a risk she suggested might even be deliberately concealed.

She brought claims of automatic unfair dismissal and detriment for making protected disclosures. Three alleged disclosures were put forward, but by the time the case reached the EAT, only one remained in dispute: the so‑called third disclosure.

It sounds dramatic. It sounds like the kind of thing whistleblowing law was designed to protect. But the Tribunal — and later the EAT — were not persuaded.

The Legal Fault Line: “Information” vs. “Allegation”

The Tribunal’s reasoning, upheld on appeal, turned on two deceptively simple points.

1. The claimant did not disclose “information”

The EAT agreed that what the claimant provided was essentially:

a factual statement: some DAC contracts are missing, and
a broad, unparticularised assertion: this is putting health and safety at risk.

The Tribunal was entitled to conclude that this second part — the health and safety claim — was too general, too unsubstantiated, to amount to “information” under the statutory test

Whistleblowing law draws a line between:

information (which can qualify), and
allegations (which often do not).

A protected disclosure must convey facts, not just fears. It must tell the employer something concrete, not simply gesture toward a risk.

2. Any belief in a health‑and‑safety link was not reasonable

Even if the claimant genuinely believed that missing contracts endangered patients, the Tribunal found — and the EAT accepted — that this belief was not reasonable for someone in her position, with her knowledge of the business.

This is a crucial point. Whistleblowing protection does not require the worker to be right, but it does require them to be reasonably wrong. A belief that is speculative, unresearched, or disconnected from the worker’s actual role will not suffice.

Why This Case Matters

On the surface, Capeling is a narrow decision. But beneath it lies a broader message about the architecture of whistleblowing law.

1. The law protects disclosures, not anxieties

The claimant’s concern may have been sincere. But sincerity is not the test. The law demands specificity: facts, details, something that can be investigated. A generalised “this could be dangerous” will rarely be enough.

2. Reasonableness is contextual

The Tribunal looked at the claimant’s role, her knowledge, and the nature of the contracts. It concluded that she lacked a reasonable basis for linking missing paperwork to patient harm. This is a reminder that whistleblowing protection is not a free‑floating right — it is tethered to what the worker actually knows and can reasonably infer.

3. The EAT will not rescue weak appeals

The judgment is crisp, almost brisk. The EAT saw no error of law, no misdirection, no misapplication of the statutory test. The appeal was dismissed without ceremony.

The Human Story Beneath the Legal One

What lingers after reading this case is not the legal test — though that is important — but the human texture beneath it.

A worker dismissed abruptly. A belief, perhaps honestly held, that she was raising something important. A sense of injustice that propelled her through the Tribunal and into the EAT. And then the cold clarity of the law: not every workplace concern is a protected disclosure, and not every dismissal following a complaint is whistleblowing retaliation.

There is a melancholy to cases like this. They remind us that employment law is not a moral tribunal; it is a statutory framework with defined thresholds. The claimant may have felt she was doing the right thing. The Tribunal may even have believed she acted in good faith. But good faith alone is not enough.

The law asks:
What did you say?
What did you know?
And was your belief reasonable?

In Capeling, the answers did not meet the statutory bar.

Conclusion: A Small Case with a Sharp Edge

Capeling v TFX Group Ltd will not make headlines. It will not reshape doctrine. But it will sit quietly in the background of future whistleblowing cases, reminding lawyers and claimants alike that:

vague assertions are not disclosures,
belief must be grounded in reason, and
the law protects information, not speculation.

It is a case about boundaries — the boundary between concern and disclosure, between belief and reasonable belief, between dismissal and protected dismissal. And like all boundary cases, it sharpens the edges of the law.

By Pat Harrington

From post‑employment retaliation to managers hiding behind “innocent” decision‑makers, this month’s whistleblowing judgments reveal a legal landscape still struggling to keep pace with the realities workers face. These cases show how employers manoeuvre, how tribunals interpret the law, and why collective strength remains the surest protection for anyone who speaks up.

Introduction

Whistleblowing law in Britain has always been a patchwork: some protections strong in theory, others riddled with loopholes, and all of it dependent on tribunals willing to look beneath the surface of an employer’s story. The latest run of cases shows just how contested this terrain remains. Workers continue to face retaliation long after their employment ends; managers can escape liability by hiding behind “innocent” decision‑makers; and the courts themselves are split on how far whistleblowing detriment law should stretch.

Below is a worker‑centred breakdown of the key cases — what happened, what the courts decided, and what it means for anyone who raises concerns in the workplace.

Case Summaries

1. Post‑employment retaliation still counts: Day v Lewisham & Greenwich NHS Trust

This case confirms something workers have long known: retaliation doesn’t stop just because your employment does. Dr Day argued that statements the Trust made after settling an earlier whistleblowing case amounted to detriment. The tribunal initially said post‑employment acts weren’t covered — but the Employment Appeal Tribunal disagreed.

The EAT held that post‑employment detriments can fall within s.47B ERA when they’re closely tied to the employment relationship. As the document puts it, the statements were made “in the context of earlier tribunal proceedings about disclosures made during Dr Day’s employment” .

However, the Trust ultimately escaped liability because the tribunal found the statements weren’t materially influenced by his disclosures, but by “media scrutiny” and a desire to defend itself.

Worker takeaway:
Protection doesn’t end when the job does — but employers will still argue their motives were “something else.”

2. Persisting after an investigation can undermine protection: Argence‑Lafon v Ark Syndicate Management

Here, the worker raised concerns about a potentially fraudulent claim. After a full investigation found no fraud, he continued to accuse the company of wrongdoing. The tribunal held that his later statements were no longer protected because it was no longer “reasonable” for him to hold that belief.

He was dismissed for refusing a PIP and for continuing to allege fraud. The EAT agreed the dismissal wasn’t automatically unfair for whistleblowing — it was his behaviour, not the disclosures, that drove the decision.

But the tribunal had failed to consider whether the dismissal was unfair on ordinary grounds, especially the role of the appeal process. That part was sent back.

Worker takeaway:
Employers often weaponise “reasonableness” to shut down continued concerns. And once a PIP enters the picture, the narrative shifts fast.

3. The limits of Jhuti: decision‑makers vs manipulators in Henderson v GCRM

This case tackles a recurring problem: what happens when the person who fires you doesn’t know about your protected disclosures, but the manager feeding them information does?

The tribunal originally found the decision‑maker (R3) liable for detriment by dismissal, imputing the whistleblowing‑related motive of R2 (the line manager). The EAT said this was wrong. The Jhuti principle — looking behind the decision‑maker’s stated reason — applies to automatic unfair dismissal, not to detriment claims.

Applying Jhuti here would create “potentially unlimited liability on an innocent party” .

The s103A dismissal claim was sent back for reconsideration, but the detriment findings were overturned.

Worker takeaway:
Managers who manipulate processes may escape detriment liability unless the dismissal claim itself succeeds. The law still struggles to capture behind‑the‑scenes retaliation.

4. Dismissal can be a detriment: Rice v Wicked Vision & Barton Turns v Treadwell

These joined appeals deal with a long‑running legal contradiction: can a worker bring a detriment claim based on the dismissal itself?

The Court of Appeal said yes — not because it agreed with the earlier Osipov decision, but because it was bound by it. As the summary puts it, “It is plainly unsatisfactory that the construction of this legislation has now produced conflicting decisions at three levels of court” .

Both workers were allowed to proceed with detriment claims based on dismissal by co‑workers, with employers potentially liable via vicarious liability.

Worker takeaway:
The law is messy, contradictory and ripe for reform — but for now, workers can pursue detriment claims even where the detriment is dismissal.

5. Secondment isn’t employment: Bank of Africa v Hassani

This case is a reminder that employers will use technicalities to avoid responsibility. The worker was employed by BCME but seconded to the Bank of Africa. The tribunal wrongly found her employment had transferred, making the Bank liable for dismissal and detriment.

The EAT overturned this. The secondment agreement was clear: she remained employed by BCME. That meant:

The Bank couldn’t be liable for unfair dismissal.
Detriment claims needed proper analysis under s.43K ERA (extended definition of worker), which the tribunal hadn’t done.
The tribunal also wrongly treated all respondents as jointly responsible — a “composite approach” the law doesn’t allow.

Worker takeaway:
Seconded workers fall into a legal grey zone. Employers exploit that ambiguity, and tribunals often get it wrong.

Conclusion

Across these cases, a pattern emerges: whistleblowing law remains a battleground where employers test the limits, tribunals disagree, and workers are left navigating a system that often feels designed to trip them up. Whether it’s post‑employment retaliation, managerial manipulation, or technical arguments about employment status, the message is clear — legal protection is only ever part of the story.

Solidarity, collective action and union support remain the real safeguards for workers who speak up. The law may shift, but our responsibility to defend each other does not.

By Pat Harrington

Tag: Whistleblowing