Whistleblowing at Work: What This Month’s Cases Tell Us About Power, Protection and the Limits of the Law

Advertisements
Close-up of a person blowing into a silver whistle.

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

Court Says Old Employer Still to Blame for Staff Mistakes Made Before Job Transfer

Advertisements

High Court ruling clarifies what happens under TUPE when employees move jobs but past harm is alleged

407 words, 2 minutes read time.

In the case ABC v Huntercombe (No. 12) Ltd and others, the High Court has ruled that employers cannot pass the blame for their workers’ past mistakes onto a new company just because the staff have been transferred. The decision has important implications for businesses, workers, and anyone affected by workplace negligence.

The Claimant in the case suffered harm while receiving care at a hospital operated by Huntercombe. She claimed that two hospital staff members were responsible. But by the time she took legal action, those two workers had moved to a different company—Active Young People Ltd—through a process known as TUPE.

What is TUPE?

TUPE, short for Transfer of Undertakings (Protection of Employment), is a UK regulation that protects employees when the business or service they work for changes hands. It ensures that workers keep their jobs, pay, and employment terms even when a new employer takes over.

TUPE also means that many of the old employer’s responsibilities—like holiday pay, notice periods, or ongoing grievances—transfer over to the new employer.

But there are limits.

What did the court decide?

The key issue was whether vicarious liability—where an employer is legally responsible for their staff’s actions—also transfers. The Claimant said it should, and argued the new employer should be held responsible for harm caused by staff before the transfer.

The court disagreed. It ruled that TUPE is designed to protect employees, not to make new employers responsible for everything the staff may have done in the past. It said that only legal duties and obligations that exist between the employer and the employee are transferred. Responsibilities for injuries or damage to third parties, like patients or customers, are not.

The court also rejected a previous case, Doane v Wimbledon Football Club, that had suggested the opposite. That earlier case should no longer be followed, it said.

Why it matters

This ruling helps clarify that past liabilities stay with the old employer, even if staff move under TUPE. New employers taking over services or contracts won’t be unexpectedly hit with claims for things that happened before they were in charge.

It also tells Claimants where to aim their legal actions: even if the person responsible has changed employers, the company that employed them at the time of the incident is still the one legally accountable.

By Patrick Harrington

Picture credit: By sjiong – https://www.flickr.com/photos/sjiong/109817932/, CC BY-SA 2.0, https://commons.wikimedia.org/w/index.php?curid=6380215