How to implement whistleblowing procedures?

How to implement whistleblowing procedures?

We have already covered what an exemplary procedure for reporting irregularities looks like, and what a model implementation of a whistleblowing system looks like in practice. Both pieces stop short of one specific question: how does the procedure document actually start binding the people who work for you? Drafting it is not adopting it, and adopting it is not making it enforceable.

From "establishing channels" to a binding workplace document

Article 8 of the EU Whistleblower Directive obliges every legal entity with at least 50 workers to set up internal reporting channels and procedures. The directive uses the verb "establish", which is deliberately abstract, because each member state was left to decide what "establish" means in its own legal order. Some treat the procedure as a workplace regulation under labour law; others treat it as an internal compliance act adopted by the governing body. The Commission's whistleblower-protection page tracks transposition status; every member state has now transposed, several with multi-year delays.

In practice this means you cannot simply tell HR to "open an inbox" and call yourself compliant. The channel needs a written procedure that names the people in the loop, fixes the timeframes, and survives the departure of whoever wrote it.

What the procedure must contain

National transpositions vary, but the directive's minimum content list is more or less invariant. A compliant procedure names a designated unit or individual authorised to receive reports, and an impartial unit or individual responsible for follow-up. Those two roles can sit in the same place, but if they do, the impartiality of the follow-up has to be defended on other grounds.

It lists the accepted submission channels: at minimum oral and written, and an in-person meeting on the reporter's request. It states whether anonymous reports are accepted (member states differ here). It commits to acknowledging receipt within 7 days and to providing feedback within a 3-month window from acknowledgment. And it explains the external reporting routes (the national competent authority and, where relevant, EU institutions), so a reporter who chooses not to use the internal channel knows where else they can go. A procedure that omits the external-reporting paragraph funnels everything inward, which is exactly the failure mode the directive was written to prevent.

Consult before you adopt

Most national transpositions require some form of workforce consultation before the procedure binds. The form varies (works council in some countries, recognised trade unions in others, elected employee representatives where neither exists), and the time window varies too, typically a small handful of working days between presenting the draft and finalising the text. A few national laws make consultation a precondition of validity: skip it and the procedure is technically not in force, no matter how nicely it is printed.

The reasoning is not formalism. A reporting channel adopted unilaterally rarely earns the trust it needs to function; the people who would actually use it want some signal that the rules were agreed, not imposed. A short consultation, properly documented, is also the cheapest piece of evidence you can produce later when a regulator asks how the procedure was put in place.

Adopt, communicate, then respect a notice period

The adoption decision follows the corporate form of the entity. In capital companies it is typically the management board; in partnerships, the partners; in public-sector bodies, the head of the authority; in associations and foundations, the body authorised by the statutes. The decision should be in the form the entity uses for its other internal acts (usually a board resolution or written decision), so that there is a paper trail of who adopted what, and when.

Most transpositions also include a short notice period between making the procedure known and it taking effect. The directive's spirit is that workers must have a real opportunity to read the rules before those rules start governing what happens to them. Publish the procedure on the intranet, the noticeboard, or whatever channel the workforce actually checks, and record the date of publication. The procedure binds from that recorded date plus the statutory notice period, not from the day the board signed it.

Penalties for ignoring it

National sanctions vary. Some member states impose administrative fines on the entity; others add criminal liability for individuals who actively obstruct a report or retaliate against a reporter. The numbers are large enough to be meaningful for mid-sized employers, and small enough to be missed in a year-end risk register if no one has flagged the obligation.

The bigger shift, though, is upstream. On 6 March 2025 the Court of Justice of the EU fined five member states for late or absent transposition: €34 million against Germany, €2.3 million against the Czech Republic, €1.75 million against Hungary, €375,000 against Luxembourg, and €500,000 plus €1,500/day against Estonia. The CJEU press release sets out the reasoning. Once the Commission has shown it will actually pursue infringement to the point of penalty, national regulators tend to harden their own enforcement posture. The cost of having no procedure is not just the headline fine. It is the audit attention that follows.

The procedure document is administrative scaffolding. It has to exist, it has to be lawfully adopted, it has to be communicated, and it has to say the right things. None of that, on its own, makes the channel work. The harder problem is convincing the people who would use it that the channel is safe to use, that the impartial follow-up is actually impartial, and that the company is more interested in fixing what was reported than in finding out who reported it. For that work, the voluntary ISO 37002 standard is a useful reference: a maturity model rather than a compliance baseline, intended to sit alongside the statutory procedure rather than replace it. ISO 37002 defines the management-system view; the procedure document is just the entry point.

Updated at
Did you find the article interesting? Share it with others
You may be also interested in