Voice in the Delivery Chain: Building Speak-Up Assurance Across Public Service Supply Chains

Public services are increasingly delivered through contractors, joint ventures and arm's-length vehicles. That can bring expertise and capacity. It can also create a speak-up gap. A worker employed by a contractor may see unsafe practice or financial impropriety, but may not know whether to raise it with their employer, the public body or a regulator. The public body may be accountable for the service but not be the employer. The result can be a concern that travels nowhere—or travels too late.

The legal baseline: protected disclosures

The Public Interest Disclosure Act 1998 provides protection for workers who make qualifying disclosures. It does so by inserting protections into the Employment Rights Act 1996. A qualifying disclosure is, broadly, a disclosure of information that tends to show one or more specified types of wrongdoing, such as a criminal offence, a breach of a legal obligation, a miscarriage of justice, a danger to health and safety, environmental damage, or the concealment of any of those matters.

Protection depends on the status of the discloser, the nature of the disclosure and the person to whom it is made. Employees and many other workers are covered. Contractors' staff will usually have PIDA rights against their own employer, not automatically against the public body that commissions the service. That legal boundary is important, but it is not the end of the governance question. Public bodies cannot assume that a contractual chain discharges their responsibility for an open culture, effective escalation and proper handling of concerns.

Where the gap opens

The gap is rarely caused by a single bad clause. It emerges from fragmentation. A contractor's whistleblowing policy may be sound on paper but unknown to staff. Confidentiality clauses may be read—wrongly—as a bar to speaking up. A joint venture may have no shared route for concerns that touch more than one party. An arm's-length vehicle may have its own board, policies and reporting lines, leaving the commissioning body at a distance.

There is also a cultural risk. Workers in a commercial supply chain may fear that raising a concern will jeopardise their job, their employer's contract or their relationship with the public body. Managers may lack confidence in handling disclosures. Boards may see only aggregated assurance and not the individual cases that reveal whether the system works.

Contracting for voice

Contracts are not a substitute for statutory protection, but they are a practical tool for closing the gap. Public bodies should require suppliers to maintain a whistleblowing policy that is consistent with PIDA, communicate it to staff and subcontractors, and provide clear routes for concerns. The contract should make clear that nothing in it prevents a protected disclosure or requires prior approval before a concern is raised.

Useful clauses include:

• a requirement to report to the public body any concern that affects service safety, financial propriety or regulatory compliance, subject to appropriate confidentiality;
• an obligation to cooperate with investigations and to protect reporters from detriment;
• a prohibition on confidentiality or non-disparagement terms that could deter protected disclosures;
• audit and assurance rights, including access to anonymised data on speak-up cases;
• clear escalation routes for concerns involving the public body, a joint venture or a subcontractor; and
• consequences for failure that are proportionate and focused on remedy and improvement.

Joint ventures and arm's-length vehicles need particular attention. Shareholder agreements and governance documents should identify who owns the speak-up route, how concerns are escalated across owners, and how board-level oversight operates. A concern that falls between two owners can too easily fall through both.

Board oversight and assurance

Whistleblowing is a board issue, not merely a human resources process. Boards should receive regular assurance on the volume, nature and outcome of concerns, trends, timeliness and any retaliation allegations. A named executive should own the framework, with independent challenge from a non-executive director or audit committee. For public-private delivery, the public body's board should also understand how supplier and joint-venture arrangements are performing.

Assurance should be tested, not assumed. Scenario exercises can ask: if a contractor's employee reported a safety concern to the public body tomorrow, who would receive it, how would it be triaged, what would be disclosed to the employer, and how would the reporter be protected? The answers often reveal gaps in routing, confidentiality and record-keeping.

Handling concerns without retaliation

A sound process starts with accessible routes and ends with feedback. Concerns should be triaged by someone independent of the subject matter, with conflicts managed and confidentiality respected. Investigations should be proportionate, documented and timely. The reporter should be told what can be shared, without promising outcomes. Retaliation—whether dismissal, demotion, exclusion from work or informal ostracism—should be treated as a serious breach and monitored even when the original concern is not upheld.

Public bodies should also avoid language that discourages disclosure. Describing concerns as 'malicious' before investigation, requiring employees to raise matters only through line management, or using broad confidentiality clauses without a protected-disclosure carve-out can create legal and reputational risk. A concern handled well can be an early warning system. A concern suppressed can become a regulatory investigation, a media story or a serious incident.

A practical assurance framework

Public bodies and delivery partners should consider five steps:

1. Map the workforce and routes. Identify who delivers the service, including subcontractors, and where they can raise concerns.
2. Review the documents. Check policies, contracts, joint-venture agreements and confidentiality clauses for consistency with PIDA and practical accessibility.
3. Name accountability. Assign executive ownership and board-level oversight, with clear reporting to the commissioning body.
4. Test the system. Use scenarios, case reviews and feedback from reporters to identify blockages.
5. Monitor and improve. Track outcomes, retaliation allegations and repeat concerns, and report annually.

The speak-up gap is not inevitable in public-private delivery. It closes when public bodies treat voice as part of governance, contract for it deliberately and oversee it at board level. The legal baseline matters, but culture and practical routing determine whether a concern reaches the people who can act on it.