The conventional wisdom
If you manage a speak-up program in Europe, you've probably heard this: "Our reporting volumes are too low. We need more reports." The data seems to support this concern. Continental Europe records a median of 0.85 reports per 100 employees, compared with 1.65 globally and 1.86 in North America. That's less than half the North American rate.
The usual response is to launch awareness campaigns, send more reminder emails, add reporting channels, or even set targets for report volume. The assumption is clear: more reports equal a healthier program.
Why we disagree
Focusing solely on volume misses the point. You're not running a sales organization where higher numbers always mean better performance. You're managing a system for surfacing genuine concerns about misconduct.
Lower reporting rates don't automatically signal program failure or hidden misconduct. They might reflect other factors: different workplace cultures, varying attitudes toward authority, distinct communication norms, or even genuinely lower levels of misconduct in certain industries or regions.
Chasing volume as a primary metric can create perverse incentives. You don't want employees filing reports just to hit a target or because they've been bombarded with "use the hotline" messages. You want people to report when they've witnessed actual misconduct and believe their concern will be handled seriously.
The real question isn't "How do we get more reports?" It's "How do we ensure people who witness genuine misconduct feel safe and supported in coming forward?"
The evidence
Look at what the data actually tells you. In continental Europe, 58% of reports are submitted anonymously, compared with 52% in North America. This preference for anonymity suggests employees don't fully trust that identifying themselves is safe. If there were strong trust, you'd expect more people willing to put their name to a concern.
Meanwhile, 62% of reports come through web-based systems rather than traditional hotlines. This isn't just a technology preference. It reflects employees choosing channels that feel more private and less confrontational.
These patterns point to a trust gap, not a volume gap. Employees are finding ways to report when they need to, but they're doing it in ways that maximize their protection and minimize their exposure.
Consider what happens when you focus obsessively on driving up report numbers. You send constant reminders about the hotline. You plaster posters everywhere. You mention it in every all-hands meeting. What message does that actually send? Often, it comes across as "We expect to find problems" or "We're watching you." Neither builds trust.
What to do instead
Start by measuring what actually matters: trust, awareness of how the process works, and consistency in how you handle reports.
Survey employees about whether they understand what happens after someone files a report. Do they know who investigates? What the timeline looks like? Whether the reporter gets updates? In most organizations, the answer is no. That ignorance breeds anxiety, and anxiety suppresses reporting.
Make your investigation process visible without compromising confidentiality. Publish aggregate data about report types, investigation timelines, and outcomes. When you substantiate a report and take action, communicate that something happened (without identifying the reporter or the subject). Silence after a report feels like nothing changed.
Train your managers on what to do when someone raises a concern directly to them. Many employees never use formal reporting channels because they try their manager first. If that conversation goes badly, they won't escalate. If it goes well, you might resolve the issue before it needs a formal investigation. Either way, manager response matters more than hotline awareness.
Review your anti-retaliation safeguards not as a policy document but as a lived experience. Can you point to a specific instance where you protected someone who reported? Have you ever disciplined a manager for retaliating? If you can't answer yes to both questions, your safeguards exist only on paper.
For multinational programs, resist the urge to force identical processes across every country. The EU Whistleblower Directive sets minimum standards, but national laws differ on who's protected, whether Confidential Reporting must be accepted, and what procedures apply. A rigid one-size-fits-all approach creates compliance gaps while also feeling tone-deaf to local norms.
Instead, build a framework that allows for local variation within clear boundaries. Your core principles (confidentiality, anti-retaliation, thorough investigation) should be consistent. The specific mechanisms can flex to match local requirements and expectations.
When the conventional wisdom is right
Volume does matter in one specific context: when it drops suddenly or concentrates in unexpected patterns. A team that historically reported concerns but goes silent might signal a new manager who's suppressing dissent. A spike in anonymous reports from one location might indicate a genuine problem that needs attention.
Benchmark data also has value when used correctly. Knowing that your industry peers average 1.2 reports per 100 employees while you're at 0.3 should prompt questions. But the questions aren't "How do we get to 1.2?" They're "What might explain this difference? Do our employees know how to report? Do they trust the process? Are we in a lower-risk sector?"
And yes, awareness campaigns have a place, particularly right after you launch a new program or make significant changes. Employees can't use a channel they don't know exists. But awareness is just the starting point. Once people know the hotline exists, repeating that message louder doesn't build trust.
The maturity phase of Europe's whistleblowing programs isn't about driving volume. It's about building systems where people who witness misconduct believe that reporting will lead to fair investigation and appropriate action, without putting their career at risk. That's a harder goal to measure, but it's the one that actually matters.
