When a Workplace Complaint Never Reaches HR

Introduction

Imagine an employee has a problem at work. Maybe their manager keeps giving them unreasonable deadlines. Maybe something inappropriate happened in the team. Maybe they have noticed a safety problem. So, the employee thinks, "I should tell HR."

But then they start thinking about what could happen. What if HR tells the manager? What if everyone finds out? What if the manager starts treating them differently? What if nothing changes anyway?

So, the employee decides not to complain.

This happens more often than we may think. Sometimes the problem is not that HR does not care. The problem is that the complaint never reaches HR in the first place.

This is where employee voice becomes important. Employee voice basically means giving employees a safe and useful way to share their opinions, concerns, problems and suggestions with the organization. So, if employees do not feel that they can speak up, HR may only see a small part of what is actually happening inside the workplace.

And this creates a strange situation. HR may think everything is fine because there are very few complaints, while employees may actually have many problems that they simply do not report.

The Problem

The problem starts when employees do not feel comfortable raising concerns.

For example, imagine an employee notices that their manager is regularly shouting at team members. The employee thinks it is wrong, but they also know that the manager controls their performance review. So, they stay quiet.

Another employee may see a safety problem but think, "Someone else will probably report it." Another employee may have a problem with their workload but worry that complaining will make them look lazy.

So, the complaint never reaches HR.

Sometimes the employee may tell a colleague instead. The colleague tells another colleague. Soon, everyone knows about the problem except HR.

This can become a serious issue because HR cannot solve a problem that it does not know about. So, by the time HR finally hears about it, the problem may have become much bigger.

There is also another problem. If employees only have one way to raise concerns, like speaking to their direct manager, they may not speak up when the manager is the actual problem.

So, having a grievance policy on paper is not enough. Employees also need to know how to use it, trust the process and feel that raising a concern will not create another problem for them.

Analysis of the Problem

One important concept here is employee silence. Employee silence basically means that employees have something to say but choose not to say it. According to the CIPD, employees may stay silent when they believe the risks of speaking up are greater than the benefits, such as when they are worried about job security or negative treatment.

So, silence does not always mean that employees are happy. Sometimes silence means that employees do not believe speaking up will help.

Another important concept is the voice climate. This means the overall feeling employees have about whether speaking up is accepted in the organization. So, in one company, employees may feel comfortable saying, "I think this process is not working." In another company, they may think, "Better not say anything."

Then there is the idea of speak-up culture. A speak-up culture is basically a workplace where employees are encouraged to raise concerns, and the organization actually listens and responds. So, it is not just about telling employees, "You can speak up." The organization also has to show employees that speaking up leads to proper attention and action.

Confidentiality is another major issue. Employees may want to know that their concern will be handled carefully. This does not always mean promising complete secrecy because some complaints may need to be investigated and information may have to be shared with the right people. But HR should explain what confidentiality means and who may need to know.

There is also the problem of escalation. Imagine an employee's manager is the person they are complaining about. If the only reporting route is that manager, the system has basically created a dead end.

So, organizations need different routes for different situations. Employees should be able to raise concerns with HR, another manager, an employee representative or another appropriate reporting channel when needed. CIPD guidance also recommends that employees should have a way to bypass their line manager when the concern involves that manager.

Finally, there is closed-loop communication. This simply means that when someone raises an issue, the organization should communicate back about what happened next, as far as confidentiality allows.

Because imagine speaking up about a serious problem and then hearing absolutely nothing. The next time you have a problem, you may think, "Why bother?"

A Real-Life Case: NMCN

A useful real-life example comes from NMCN, a UK civil engineering, building and mechanical and electrical supply company. The organization grew very quickly, from around 400 employees in 2015 to almost 2,000. It also brought several different business divisions together. So, communication became much harder as the organization became bigger.

Many employees worked on construction sites across different locations. Some site workers did not have easy access to computers, email or work phones. So, traditional communication methods did not always reach everyone.

NMCN also had a strong command-and-control culture, which is common in parts of the construction industry. The case found that middle managers could become a barrier between employees and senior leaders. Some employees felt that managers were not receptive to personal concerns or simply did not have enough time to listen.

There was another important issue. Some workers were worried about speaking out because of job insecurity. So, even when employees had something to say, they did not always feel comfortable saying it.

This created a classic employee voice problem. The organization wanted to hear from employees, but the structure and culture made it difficult for some employees to speak up.

So, NMCN started looking at employee voice differently. Instead of depending on one communication channel, it started creating several ways for employees to communicate with the organization.

Case and HR Theories, Frameworks, Models and Concepts Reflected in the Problem

The first concept reflected here is employee silence. The NMCN case shows that employees can have concerns but still choose not to raise them because of workplace culture, management behaviour, job insecurity or a lack of easy communication channels.

The second concept is voice climate. If employees believe that speaking up will create problems or will not lead to anything, they are less likely to use their voice. So, HR needs to create an environment where speaking up becomes normal rather than unusual.

The third concept is upward communication. This simply means information moving from employees to managers and senior leaders. In a very top-down organization, information mostly moves in the opposite direction. Leaders give instructions, but employees do not always get enough opportunity to share what is happening on the ground.

So, if an employee on a construction site notices a problem, but that information never moves upward, senior management may make decisions without knowing what employees are actually experiencing.

Another concept is voice channel diversity. This means giving employees more than one way to speak up. For example, there can be team meetings, surveys, suggestion systems, digital platforms, employee representatives, HR meetings and direct conversations with senior leaders.

This matters because not every employee will feel comfortable using the same channel. Someone may not want to speak in a meeting but may be comfortable submitting a suggestion online. Another employee may prefer speaking directly to HR.

Another useful concept is escalation pathways. This means employees should know where to go if their first reporting route does not work. So, if the manager is part of the problem, the employee should not be forced to stop there.

Confidentiality is also important. Employees need to understand how their information will be handled. So, HR should not promise something like "Nobody will ever know you complained" if that cannot actually be guaranteed. Instead, HR should explain how information will be protected and who may need to see it.

Finally, the case reflects closed-loop communication. When employees raise issues, organizations need to show that the information went somewhere. This does not mean HR must reveal confidential investigation details. It can simply mean telling employees that the issue was reviewed, what kind of action was possible, or what general change was made.

Solution Using HR Theories, Frameworks, Models and Concepts

The first step should be to create multiple voice channels. HR should not depend only on the employee's manager. So, employees could have access to HR, employee representatives, surveys, suggestion systems, team meetings and other formal or informal channels.

The second step is to create a clear escalation path. Employees should know what to do if their manager is the problem. For example, they could contact HR or another senior manager directly. This makes the system more useful because the employee does not have to report a problem to the person causing it.

The third step is to explain confidentiality clearly. HR should tell employees what information will remain private, what information may need to be shared during an investigation, and who will have access to it.

The fourth step is to train managers to listen. This sounds simple, but it is actually very important. A manager does not have to agree with every employee concern. But they should be able to listen without immediately becoming defensive or angry.

The fifth step is to create a response system. So, when an employee raises a concern, HR should acknowledge it, record it, decide who should handle it and communicate the next steps.

The sixth step is to close the feedback loop. If HR cannot share the full outcome because the matter is confidential, it can still say something like, "Your concern was reviewed and appropriate action was taken." This shows employees that speaking up did not simply disappear into a black hole.

The seventh step is to monitor silence itself. HR should not only track the number of complaints. A sudden drop in complaints may not always be good news. It could mean employees have stopped trusting the system.

So, HR could look at the number of concerns raised, the type of concerns, which channels employees are using, how long cases take to respond to and whether employees receive follow-up.

The basic process could be:

Give employees different ways to speak → Make escalation easy → Protect confidentiality → Listen properly → Investigate when needed → Take action → Communicate back → Check whether employees still trust the system.

Actual Solution Implemented in Real Life

NMCN responded by creating several new ways for employees to communicate with the organization. One example was iConnect, a digital platform designed to help employees access information across different parts of the company. NMCN also introduced "Bright Ideas", which worked like a digital suggestion box where employees could submit ideas about improving work and wellbeing.

The response was actually much bigger than just creating a digital tool. NMCN introduced leadership briefings where employees could directly interact with senior leaders and raise issues. Senior leaders also became more visible on work sites and used site visits to understand practical problems employees were facing.

The company also worked on changing its management style from mainly top-down communication toward more two-way communication. It introduced a listening forum and focused on creating a more open culture.

One particularly interesting part was manager development. A trained psychologist developed a programme for NMCN that focused on skills such as active listening and understanding emotions during workplace conversations. So, the company was not only telling employees to speak up. It was also trying to improve the ability of managers to actually listen.

The "Bright Ideas" system also showed why having a voice channel is only the first step. NMCN received around 550 ideas in two quarters. So, employees clearly had a lot to say, but the company then had to figure out how to review all those ideas without making employees feel ignored.

This is a very important HR lesson. If you create a place for employees to speak but nobody responds, the system can eventually lose trust.

CIPD's more recent guidance makes a similar point. It says that effective employee voice needs complementary channels, leadership support and managers who listen and act on feedback. It also notes that employee silence can happen when people believe the risks of speaking up are greater than the benefits.

Conclusion

When a workplace has very few complaints, it is easy for HR to think, "Looks like everything is fine."

But sometimes no complaints do not mean no problems. Sometimes it simply means employees have stopped speaking.

So, HR needs to look beyond the number of grievances. It needs to ask whether employees actually know how to raise concerns, whether they trust the process, whether they can bypass their manager when necessary and whether they believe something will happen after they speak up.

For me, this is what makes employee voice so interesting. HR cannot understand the employee experience if employees are afraid, unable or unwilling to talk about it.

And honestly, a suggestion box, survey or grievance portal is not enough. The real question is what happens after the employee clicks "submit."

Because a workplace where employees can speak is good. But a workplace where employees believe someone will actually listen is much more meaningful.