Not getting misconduct reports? How to diagnose what the silence means

A reporting channel that stays quiet is telling you something. The hard part is working out what. Low or zero misconduct reports can mean your culture is healthy and people have little to raise. It can also mean concerns are alive in the organization and none of them are reaching you. Those two situations look identical on a dashboard, and only one of them is safe to ignore.

For most organizations, the second reading is the more likely one. When compliance leaders look closely, the reports that never arrive are often the ones that matter most, held back by employees who don't trust the channel, can't find it, or doubt that using it will change anything. So before you read a low number as a clean bill of health, run the diagnosis.

Start with the numbers you already have

A low report count on its own is not a diagnosis. Read it alongside the measures that show whether people trust and use the channel: how many reports you receive relative to headcount and how that moves over time, the split between named and anonymous reports, whether reporters come back to answer follow-up questions, and how long cases take to close. SpeakUp sees a 49% reporter check-back rate, where reporters return to continue the conversation even while staying anonymous, and a rate near zero is a signal in itself, because the exchange dies at intake. Our guide to the KPIs every compliance program should measure sets out the full set and how to baseline them.

Two kinds of silence, and how to tell them apart

Healthy quiet and suppressed quiet produce the same headline number. The difference shows up underneath it.

Healthy quiet lines up with other evidence that people feel safe. Engagement surveys suggest people would raise a concern if they had one. The reports you do receive span the full range of issues, not only the minor or convenient ones. Different parts of the organization report at broadly similar rates once you account for size.

Suppressed quiet is the more common and more dangerous version, because it looks calm from the top. Writing in Forbes, Diane Hamilton describes how pluralistic ignorance takes hold in organizations: people privately see a problem but assume everyone else is fine with it because no one says anything out loud, and leaders read the resulting quiet as agreement. On a reporting dashboard, that dynamic shows up as reports clustering in one or two regions while whole entities stay dark for years, or as a channel where everything that arrives is either anonymous or trivial. When exit interviews and public employer-review sites surface issues that never reached your channel, the calm inside the system is the thing to distrust.

A diagnosis you can run this quarter

You can work through the likely cause without new tooling. Four checks get you most of the way.

Test whether people can find the channel. Awareness decays fast after onboarding. Ask a sample of employees, across sites and languages, whether they know how to report and what happens when they do. If a meaningful share can't answer, low volume is an awareness problem before it is a trust problem.

Look at where reports come from, and where they don't. Map volume by entity, region, and language. Silent regions rarely mean problem-free regions. They more often signal a channel that doesn't work in the local language, or a workforce where challenging a manager carries real risk. Research on psychological safety finds that employees from more hierarchical cultures can find it markedly harder to voice concerns, so a one-size rollout will underperform in exactly the places you hear from least. Our guide to solving multilingual whistleblowing covers why language and access change reporting rates.

Check the reporting experience yourself. Submit a test report through every channel you offer, including the phone line. Time the interpreter wait. Notice where the process asks for information a nervous or anonymous reporter wouldn't want to give. Friction you feel in a calm test is friction that stops a real reporter cold.

Read the trend, not the snapshot. A single quarter tells you little. A channel that was busy and went quiet points to a specific change: a reorganization, a lost sponsor, or a case that was handled badly and traveled by word of mouth.

What your numbers can't tell you

A diagnosis narrows the cause, but it can't fully explain why any individual employee chooses silence, and that is where the deeper work sits. The reasons have shifted as the workforce has, with five generations now reporting concerns in different ways and raising different kinds of issues. We cover that side in 7 reasons employees aren't using your speak-up program, which pairs with this diagnosis: use the numbers here to locate the problem, and that piece to understand the behavior behind it.

Most of what turns a quiet channel into a used one comes down to belief: whether people think reporting is safe and worthwhile, which grows from visible follow-through and steady communication rather than a single onboarding mention. That belief is hardest to rebuild in a guarded culture where people have learned to stay careful, and Forbes contributor Julie Kratz argues that leaders have to actively invite friction and dissent before employees will risk it. Building a speak-up culture sets out how to build that belief inside your own program, and what to look for in secure and anonymous reporting channels covers the trust signals employees look for before they act.

When the channel itself is the problem

Sometimes the diagnosis points back at the tooling. A phone-only hotline can't offer the anonymity, the languages, or the two-way follow-up that reporting now depends on. Guided, multi-channel intake (web, mobile, and AI-assisted voice, named or anonymous) removes the friction that stops reports before they start, and structured case management keeps the conversation going after intake. That combination is what SpeakUp Report and our whistleblowing software are built for. Once reports are flowing, Sienna Insights lets you ask your own case data where risk is concentrating, so a quiet quarter becomes a question you can answer instead of a number you have to guess at.

If you suspect the silence is hiding risk rather than proving safety, see how it works with a short demo.