Rethinking What Hotline Data Can Tell Us: Silence as an Early Warning Signal

Most of us treat our hotline data like a scoreboard. Substantiation rates, open-to-close times, the raw count of calls we take to the board each quarter. But a scoreboard only reflects what people are willing to tell you, and the most important information is often the stuff that never makes it onto the board. The quiet units that never report. The department that used to raise its hand and suddenly went silent. The question no one ever asked.

In this Ethicsverse session, titled Rethinking What Hotline Data Can Tell Us, host Nick Gallo of Ethico sat down with Valerie Cloud, Chief Compliance Officer of Summa Health, to walk through the hidden signals inside speak-up data and how compliance teams can use them to see around the curve. Valerie is a researcher by training who returned to school for a doctorate because she felt compelled to find a different way to do this work, and she has led compliance across six organizations over more than two decades. The conversation moved from why silence is the loudest signal in the data, to the practical mechanics of reading patterns instead of volume, to the mindset shift required to move a program from reactive to genuinely predictive. What follows are the key takeaways.

Key Takeaways

What Is Your Silence Telling You?

For years the profession has focused almost entirely on open-to-close rates and trend counts, reporting to the board how many calls came in. Valerie’s challenge reframes the question: rather than asking what was said, ask what is not being said, and what you are not being told.
In her experience, many people know about an issue but assume someone else will call. That assumption means the concern never reaches you at all, so a low count can reflect diffusion of responsibility rather than the absence of a problem.
The audience filled the chat with reasons for silence: fear of retaliation, a lack of trust in the process, confusion about where to report in a matrixed organization, and the belief that nothing is ever done. As one participant put it, silence tells you people are not psychologically safe. As another noted, the raw number of hotline calls is often just a vanity metric with little real information value.

Low Volume Does Not Equal Low Risk

Valerie’s bumper-sticker line for the board is simple: low volume does not equal low risk. When she joined her current organization and reported a jump in hotline calls, leadership asked what had gone wrong. Her answer was that more reporting is what happens when you educate, communicate, and build relationships. People bring questions to you rather than taking them elsewhere.
Silence can be the loudest signal in the data. When people stop reporting, it is rarely because everything is going well. More often it is a greater risk, because the concerns still exist, they are simply not reaching you.
Nick reinforced the scale of the gap. Industry reporting runs somewhere around two reports per hundred employees, yet the true volume of risk intelligence sitting inside an organization is likely an order of magnitude higher, perhaps twenty times what a hotline actually captures.

The Iceberg of Hidden Risk

Valerie offered an iceberg as the mental model. Above the surface sits what has already been reported: the allegations and cases in your system. Below the surface sits culture, trust, power dynamics, and workload pressure.
Most of the real risk lives at and below that waterline, and much of it never enters the hotline at all. Over-focusing on substantiation rates can mask the systemic issues an organization is actually facing.
Nick added a broad rule that holds across the benchmark data: looking at any single metric in isolation tends to lead to the wrong conclusion. A high substantiation rate paired with half a report per hundred employees can create a false sense of security when the real reporting opportunity is far larger.

Set a Bigger Goal Than One More Report

If your program runs at roughly two reports per hundred and your goal is to reach three, you are not aiming high enough. Nick suggested a thought experiment with your team: what would it take to reach twenty, when there may be fifty genuine concerns per hundred sitting unspoken?
Reaching for that bigger number naturally forces the right behaviors: more education, more communication, and a real discipline around closing the loop so that every concern raised is acknowledged and followed through.
Expect substantiation rates to dip in the short term as more first-time and anonymous reports come in. People stepping onto the ice for the first time may not yet provide the who, what, when, and where that lets you substantiate a claim, and that is a sign of progress, not failure.

Close the Loop to Build Ambassadors

Psychological safety depends on closing the loop. Too often people bring something forward and never hear an outcome. You cannot always share every detail, but you can confirm that the concern was heard and addressed, and sometimes offer additional facts that reframe a person’s perception of what happened.
No compliance team has the human capital to do the entire body of work alone. Closing the loop turns the people who speak up into ambassadors, expanding the reach of the program far beyond the department itself.
Valerie framed the deeper point plainly: compliance is not a department, it is the privilege of doing work that lets clinicians care for patients and staff serve the community. When the community trusts that their information is safe, the whole organization benefits.

Read the Signals, Not Just the Count

Valerie pushed the audience to go beyond case counts and open-to-close times toward richer signals. Time to report is a favorite: when did someone first learn of an issue, and when did they finally come forward? A gap of three, six, or nine months is an opportunity to encourage earlier reporting, since an earlier report often means an earlier fix.
She tracks the ratio of anonymous to named reports as a trust indicator. At her organization, anonymous reports now sit below one percent, a sign that people feel safe attaching their names, which was not the case when she arrived.
She watches for repeated issue types and for patterns tied to specific leaders. A recurring category can reveal a process problem, such as staff telling patients to call the hotline for billing questions, which then surfaces as false fraud allegations. A pattern under one leader can reveal a manager who is not closing the loop, or a newly promoted manager who lacks the confidence to have hard conversations with former peers.

Triangulate the Data You Already Have

Hotline data is only one element of the story. Valerie combines it with turnover rates, audit findings, and exit interviews, and she pushes her team to ask departing employees both what they reported and what they never reported, and why.
Departures are a rich and underused source of risk intelligence. Someone leaving with a new job in hand has neither the fear of retaliation nor the worry that nothing will be done, so they are far more likely to share what has been on their mind for the last several months.
Nick’s reframe was to knock down the mental silos between hotline reports, manager conversations, and exit interviews. It is all risk intelligence. The more you can triangulate across turnover, speak-up data, exit interviews, and employee surveys, the more compelling and defensible the story you can tell.

Speak-Up Culture Is a Hard-Wired Safeguard

Valerie rejected the idea that speak-up culture is a soft control. It functions the same way an operational safeguard does. Her analogy was the surgical timeout in an operating room: a hard-wired process that creates a safety net every bit as real as a clinical control.
A credible internal speak-up system reduces the likelihood that employees escalate their concerns to an outside regulator. If people believe you are listening, most will come to you first, because they want what is right for the organization, their coworkers, and the community.
Enforcement agencies expect evidence of this: accessibility through multiple reporting channels, genuine non-retaliation, and proof that you use the data to prevent harm. Your ability to show that you listened, responded, and acted is exactly what regulators look for.

Speak-Up Culture as a Predictive Analytic

Compliance failures are rarely sudden. They are cultural, and they build over time. A healthy speak-up culture is a leading indicator that can signal trouble well before a violation occurs, while an eroding one shows up as hesitation to report and as workarounds that eventually become full control failures.
Read correctly, speak-up culture can predict where controls will fail and where leadership behavior is increasing risk. It can even hint at where regulators, who bring strong analytics of their own, are likely to look.
This is the heart of the shift from reactive to predictive compliance. By combining the data already in the compliance platform, teams can move from reporting problems after the fact to preventing them, anticipating failure points and acting before harm occurs.

Who Holds Leadership Accountable?

An audience member asked who is responsible when the trends point to leadership itself as the underlying issue. Valerie’s answer: accountability starts at the top, with the leader, and with strong HR partnership. The leader is accountable for holding the leader accountable, which means the next level up is responsible.
Data solidifies what people have been saying, turning perception into a documented pattern. Organizations then have to be willing to make hard decisions, including moving someone out of a role. Competence and integrity matter, but a leader who cannot lead by example may be more of a risk than a benefit in that seat.
These conversations are difficult, especially in healthcare, where long tenures create family-like bonds and a reluctance to confront. Valerie’s posture is to make sure leadership hears the concern and has the information, support the decision that the accountable leader makes, and return to the conversation, escalating if the issue recurs.

Reframe the Board Conversation

Valerie flips the typical bottom-up board presentation. Instead of walking through activity slides and hoping the board assembles the data into the right conclusion, she opens with the three things she needs them to know, the risk to the organization, and what has been done to mitigate it.
The raw numbers go in an addendum. Boards tend to fixate on a single figure, such as a spike to one hundred twenty reports in a month, so she keeps them available for questions but does not lead with them. The room now expects that she will not hand them a number, she will hand them a point of view.
She frames every presentation around a clear thesis: silence is the least visible and most dangerous signal, and compliance failures have early indicators. That lens reframes the compliance role from a back-office cost center into a function that has its finger on the pulse and is helping the organization see around the curve.

The Compliance Maturity Curve

Valerie closed with what she calls the compliance maturity curve: a program that starts reactive and trends toward predictive. Accelerating along that curve is itself evidence that the program is maturing.
Nick’s addition was that leaders should say this out loud, constantly. Board members are not spontaneously thinking that a team is building a predictive compliance program. Naming the ambition plants the idea, and helps the board see the effort behind it as strategic rather than administrative.
The larger message was one of optimism. Compliance professionals should not sell themselves short. With the right data, the right framing, and the discipline to listen and respond, the profession can anticipate failure points and protect patients, employees, and the organization before harm occurs.

Closing Thought

The throughline of the hour was a reframe: stop reading hotline data as a scoreboard and start reading it as one signal among many in a much larger risk picture. Valerie Cloud’s central argument, that silence is the loudest and most dangerous signal, asks compliance leaders to pay as much attention to what is not being said as to what is. Pair that instinct with time-to-report analysis, pattern recognition, and the triangulation of turnover, exit interviews, and culture data, and a program stops merely reporting the past and starts predicting the future.