Self-paced online · Start today

If Employees Are Afraid to Report Leadership, Is Your Compliance Program Really Working?

8 min read By Thompson Charles

If Employees Are Afraid to Report Leadership, Is Your Compliance Program Really Working?

Most providers can answer the basic questions about their compliance program. They have policies, employees complete required training, and there is usually a process for reporting concerns. Those pieces matter, but they do not answer one of the most important questions about whether the program works in real life: If an employee believes a supervisor or senior leader is doing something wrong, does that employee actually feel safe saying something?

 

That question changes how we think about compliance. A reporting process can exist on paper and still fail in practice if employees do not believe they can safely use it. The concern may not be the reporting form itself. Employees may understand exactly how to make a report but hesitate because they are thinking about what happens afterward. They may wonder whether their supervisor will treat them differently, whether the complaint will remain private, or whether speaking up could affect their schedule, opportunities, or job. When those fears become stronger than an employee's confidence in the reporting process, an organization can have a formal compliance program without having a strong culture of compliance.

 

A Reporting Policy Does Not Automatically Create Employee Voice

Consider a direct-care employee who notices that a supervisor regularly changes documentation after staff submit it. The employee does not know whether the changes violate a law or regulation, but something about the practice feels wrong. The organization's handbook says concerns should be reported, yet another fact enters the employee's decision: the supervisor in question also controls the weekly schedule. Reporting is no longer just a compliance decision. From the employee's point of view, it may carry personal risk.

 

This is where psychological safety becomes important. Psychological safety does not mean employees are protected from accountability, disagreement, or uncomfortable conversations. It describes an environment where people believe they can raise questions, acknowledge mistakes, or express concerns without being punished simply for speaking.

 

Research on inclusive leadership, psychological safety, and employee voice helps explain why this matters. In "Inclusive Leadership, Psychological Safety, and Employee Voice in Remote and Hybrid Work Employees," Keamogetse Mohase, Fiona Donald, and Nicky Israel found that inclusive leadership significantly predicted psychological safety, while psychological safety significantly predicted employee voice. Psychological safety helped explain how leadership behavior influenced employees' willingness to speak. In practical terms, the behavior employees experience from leaders can affect whether they believe using their voice is safe.

 

That finding has an important application to corporate compliance. An organization may tell employees to report violations, but the daily behavior of managers can send a different message. Employees form opinions about the organization by watching what happens when people disagree with someone who has authority. If employees see a coworker labeled "difficult" after questioning a decision, that experience may communicate more about speaking up than the organization's non-retaliation policy. Over time, employees learn whether leadership genuinely wants difficult information or simply says that it does.

 

This means providers should evaluate more than whether employees know where to report a concern. They should also determine whether employees trust what will happen after they report it.

 

Silence Can Look Like Good Compliance

 

Suppose an employee is instructed to document a service in a way the employee believes is inaccurate. When the employee questions the instruction, the manager responds that the organization has always done it that way and there is no reason to make the issue complicated.

 

The manager has not openly threatened the employee. There may be no obvious retaliation and no instruction to remain silent. Yet the interaction still teaches the employee something about how questions are received. If raising concerns is met with irritation or dismissal, the employee may hesitate before raising a more serious concern later.

 

Research examining trust and psychological safety provides useful context. The study "TMT Cognitive and Affective Trust, Psychological Safety and Corporate Entrepreneurship" found relationships among trust, psychological safety, candid communication, and constructive disagreement. Although the study did not specifically examine corporate compliance reporting, its findings support a broader organizational principle: people are more willing to take interpersonal risks when they trust the environment in which they are speaking.

 

That principle matters because employees are often closest to the first signs of compliance problems. A direct-care worker may notice questionable documentation. Billing staff may recognize a practice that does not seem consistent with service delivery. Another employee may become aware of a confidentiality concern, conflict of interest, boundary issue, or unsafe shortcut. Leadership may know nothing about these concerns unless the people closest to them are willing to speak.

 

For that reason, very few compliance reports should not automatically be viewed as evidence of a healthy organization. Low reporting can mean employees are experiencing few problems, but it can also mean employees do not trust the reporting process enough to use it. Providers need additional information before deciding which explanation is true.

 

Leadership Behavior Is Part of the Compliance System

 

Compliance and organizational culture are sometimes treated as separate responsibilities. Compliance staff manage policies, investigations, and regulatory requirements, while supervisors focus on operations and HR addresses workforce matters. Employees experience those functions as parts of the same organization, especially when deciding whether it is safe to raise a concern.

 

Research by Shaoping Qiu and Ruijuan Zhang offers another useful perspective. Their study, "The Relationship Between Workplace Incivility and Psychological Distress: The Moderating Role of Servant Leadership," examined 1,604 nurses and found that workplace incivility significantly predicted psychological distress. Higher perceived servant leadership was associated with lower distress and weakened some of the relationship between incivility and distress, although strong leadership did not eliminate the harmful effect entirely.

 

This was not a compliance-reporting study, and the findings should not be treated as direct evidence that servant leadership prevents compliance violations. The study does, however, reinforce an important organizational lesson: leadership behavior can shape the environment employees experience. A non-retaliation policy will have limited influence if employees regularly see managers respond poorly to criticism, questions, or disagreement.

 

Providers therefore need to build psychological safety into the operation of the compliance program rather than treating it as a separate leadership topic.

 

Step 1: Find Out Whether Employees Feel Safe Reporting Upward

 

An organization can begin by changing the questions it asks employees. Asking whether staff know how to report a compliance concern measures awareness, but it does not measure trust. A more useful assessment explores whether someone would feel safe reporting a direct supervisor and whether that confidence changes if the concern involves a senior executive. Providers should also ask employees what they believe would happen after a report was made.

 

These questions can be incorporated into anonymous culture surveys, compliance assessments, stay interviews, supervision reviews, or periodic workforce surveys. Anonymity can be especially important when the organization is first trying to understand whether employees trust existing systems.

 

Leadership should look beyond the organization-wide average. A provider may discover that employees generally trust the compliance process while one program, location, shift, or supervisory team reports much lower confidence. That difference can provide an early warning that the issue is not the written policy but the local culture surrounding it.

 

Step 2: Make Sure Employees Can Report Around the Chain of Command

 

A reporting system is vulnerable when every concern must travel through an employee's immediate supervisor. If that supervisor is involved in the concern, an employee may have nowhere psychologically safe to go even though a reporting procedure technically exists.

 

Organizations should provide reasonable alternatives that fit their size and structure. An employee might be able to contact a compliance officer, HR representative, executive leader, anonymous hotline, or another designated person outside the normal supervisory chain. Larger organizations may need formal escalation procedures for allegations involving senior executives, compliance personnel, or HR leadership.

 

Whatever system is selected should be easy to understand. Employees should not have to search through a lengthy handbook to determine how to report a serious concern. Training and policy should explain where concerns can be reported, whether anonymous reporting is possible, what employees can expect after making a report, and how to raise a concern about possible retaliation. The simpler the process is to understand before a problem occurs, the more useful it becomes when an employee is under stress and deciding whether to speak.

 

Step 3: Train Supervisors to Receive Concerns Properly

Organizations frequently train employees on how to report concerns without giving equal attention to the person who may receive the initial report. That first interaction can influence whether the employee continues cooperating with the process and whether coworkers later view reporting as safe.

 

Imagine an employee telling a supervisor about possible misconduct and hearing, "Are you sure? That's a serious accusation." Even if the supervisor does not intend to discourage reporting, the response may cause the employee to question whether speaking up was a mistake. A response such as, "Thank you for bringing this forward. Tell me what you observed," creates a very different experience without promising an outcome or assuming the allegation is true.

 

Supervisors should know how to listen without becoming defensive, document the essential information, protect confidentiality to the extent appropriate, and route the concern according to organizational procedure. They also need to understand the limits of their role. An untrained supervisor may start investigating independently, confront the accused employee, discuss the complaint with coworkers, or attempt to resolve a matter that should have been escalated. Training should make the expected response clear enough that supervisors do not have to invent a process in the moment.

 

Step 4: Look for Retaliation After the Report

 

Protection from retaliation requires more than a sentence in a policy. Providers need a method for identifying changes that occur after an employee raises a concern, particularly when the allegation involves someone who has influence over the employee's work.

 

Retaliation is not limited to termination. An employee may become concerned when hours decrease, preferred shifts disappear, supervision becomes unusually harsh, access to opportunities changes, or workplace relationships shift after a report. None of these changes automatically proves retaliation. Employees who make good-faith reports still remain responsible for meeting legitimate performance and conduct expectations. The problem arises when an adverse action is connected to the person's decision to raise a protected concern.

 

A practical compliance process should include planned follow-up after significant reports rather than placing the full burden on employees to recognize and prove retaliation themselves. Depending on the circumstances, the compliance or HR function might check in after an initial report and again several weeks later. The organization can ask whether the employee has experienced changes that appear connected to speaking up and review significant employment actions when circumstances warrant additional oversight.

This follow-up serves another purpose. It tells employees that the organization understands that reporting risk does not end when the investigation begins.

 

Step 5: Measure Trust Alongside Training Completion

 

Training completion remains an important compliance measure, but it answers a narrow question. A dashboard showing that 98 percent of employees completed annual corporate compliance training demonstrates participation. It does not demonstrate that those employees would report suspected misconduct involving a powerful leader.

 

A stronger view combines traditional compliance measures with information about employee confidence in the system. Leadership needs to know whether employees understand reporting channels, believe concerns will be taken seriously, and trust the organization's response. Patterns in anonymous reporting, resolution times, retaliation allegations, repeat concerns, and differences across programs can add context to those perceptions.

 

Reporting volume also requires careful interpretation. A sudden increase in complaints may indicate a developing problem, but it could also reflect greater employee confidence in a new reporting system. Likewise, unusually low reporting may reflect a strong ethical culture, or it may signal that staff see little value in speaking. Providers should avoid judging the health of the compliance program from report counts alone.

The more useful question is whether the organization has enough information to explain what those numbers mean. Combining reporting data with employee feedback gives leadership a better chance of distinguishing genuine improvement from silence.

 

Step 6: Make Sure Senior Leadership Can Be Reported

 

Perhaps the strongest test of a compliance program is what happens when the concern involves someone with significant authority. An employee reporting a coworker may trust the normal chain of command. That same process may become ineffective if the allegation involves the employee's supervisor, an executive, the head of HR, the compliance officer, or another person who normally receives escalated concerns.

 

Providers should identify this problem before an allegation occurs. Policies need an alternate path that allows serious concerns to move around a person who would normally control or influence the reporting process. Depending on the organization's governance structure, that may require escalation to an executive who is independent of the matter, outside counsel, a governing board, or a designated board committee.

 

The purpose is not to assume allegations against senior leaders are true. Senior leaders deserve fair and objective processes just as other employees do. The purpose is to prevent organizational authority from determining whether a concern can be raised or reviewed fairly.

 

This distinction is important because employees watch how power operates inside an organization. When leaders remain subject to the same ethical expectations as the rest of the workforce, the organization demonstrates that compliance is part of governance rather than merely a requirement imposed on front-line employees.

 

Compliance Is Tested When Speaking Up Feels Difficult

 

The strength of a compliance program is not fully revealed when everyone agrees and nothing appears to be wrong. It becomes clearer when an employee has information that leadership may not want to hear, particularly when the concern involves a respected supervisor, a high-performing manager, or someone with significant organizational authority.

 

That is why psychological safety belongs in the compliance conversation. Research on inclusive leadership and employee voice suggests that leadership behavior can influence whether employees feel safe speaking, while studies involving trust and workplace incivility reinforce the broader relationship between leadership practices and the environment in which employees take interpersonal risks.

 

Providers can translate those findings into practical action. They can measure whether employees feel safe reporting upward, create alternatives to the normal chain of command, prepare supervisors to receive concerns appropriately, monitor the period after significant reports for possible retaliation, interpret compliance data alongside measures of trust, and establish independent pathways for concerns involving senior leadership. Taken together, these practices help move compliance from a written system to one employees believe they can actually use.

 

So, can an organization honestly say its compliance program is fully working if employees are afraid to report a supervisor or senior leader? Not yet. The existence of the policy is important, but the real test is whether an employee who sees something concerning believes the organization wants to know, knows where to go, and trusts that raising the concern will not become a greater risk than remaining silent.

 

That may be one of the most important indicators a provider can measure. The most serious compliance concern is not always the one that reaches the hotline or lands on an executive's desk. Sometimes the greater risk is the concern an employee noticed, thought carefully about, and ultimately decided was safer to keep quiet.

 

References

Acheampong, S. M., Adomako, S., & Tarba, S. Y. TMT cognitive and affective trust, psychological safety and corporate entrepreneurship.

Mohase, K., Donald, F., & Israel, N. Inclusive leadership, psychological safety, and employee voice in remote and hybrid work employees.

Qiu, S., & Zhang, R. The relationship between workplace incivility and psychological distress: The moderating role of servant leadership.

Comments

Add a comment

Newsletter

Get practice resources monthly

New courses, guides and updates for helping professionals. About once a month.