Grievance procedure

A grievance procedure is the formal route by which an employee raises a complaint about their work, their treatment or their conditions, together with the employer's committed process for handling it. It is the mirror image of the disciplinary procedure: one is how the company raises a problem with a person, the other is how a person raises a problem with the company.

Most companies treat it as a compliance document and are surprised when nobody uses it. The purpose is not to have a policy. It is to make sure that problems surface inside the company, early, while they are still solvable, rather than arriving later as a resignation, a lawyer's letter or a review on a public site.

What people actually raise

The distribution is fairly consistent. Treatment by a manager comes first by a distance, followed by bullying and harassment, then pay and contract terms, workload and hours, health and safety, discrimination, and disagreement with a specific decision such as a rating or a refused request.

The type matters because it determines who can handle it. A workload complaint can be resolved by the manager's manager in a week. A harassment complaint cannot be handled informally at all, and trying to do so is one of the more expensive mistakes an HR function can make.

Informal first, but not as a filter

Most grievances are better solved by a conversation than by a process, and a good policy says so. The failure is turning the informal stage into a gate: requiring someone to raise it with their manager first, when the manager is the subject, or sending them back to try again because the complaint was not serious enough yet.

The workable rule is that informal resolution is offered, not imposed, and that the employee decides which route to take. Anything involving harassment, discrimination, safety or a criminal allegation goes straight to the formal process regardless of what the employee prefers, because the company's obligation exists independently of how the individual wants to handle it.

What a formal procedure needs

• A written submission with a clear recipient. Not just your manager, but a named alternative for when the manager is the problem.
• An acknowledgement within a stated number of days. Silence in the first week is what convinces people the process is theatre.
• A handler who was not involved. The single most important structural rule, and the one most often broken.
• An investigation with a defined scope. Who will be spoken to, what will be looked at, roughly how long it will take.
• A meeting where the employee can be accompanied. By a colleague or a union representative, depending on jurisdiction.
• A written outcome with reasons. Including what was found, what was not, and what will happen next.
• An appeal to someone more senior and uninvolved. Without it, the first decision is final by accident.
• A confidential record. Kept separately from the employee's general file, visible only to those handling it.

Anonymity, confidentiality and retaliation

These three are constantly confused. Confidentiality means the company knows who raised it and limits who else is told. Anonymity means the company does not know either. Both have a place, and anonymous reporting is now a legal requirement in much of Europe rather than a nice-to-have: the EU whistleblowing rules oblige employers above a size threshold to operate an internal reporting channel that accepts anonymous reports, acknowledge receipt within seven days, and give the reporter feedback within three months. Poland's implementation follows the same shape, with an internal reporting procedure that has to be consulted with employee representatives before it takes effect.

Retaliation is the part that decides whether any of this works. Protection has to be explicit and it has to be visible in practice, because employees judge the system by what happened to the last person who used it, not by what the policy says. An anonymous channel also has a practical limit worth stating plainly: a report with no identifiable reporter can be investigated but rarely resolved to a disciplinary standard, which is why the useful design lets the reporter stay anonymous while still being able to answer follow-up questions.

Where grievance procedures fail

The first failure is routing: the complaint about a manager lands on that manager's desk, and the employee learns the lesson immediately. The second is silence, where a case is genuinely being investigated but nobody tells the person anything for six weeks. The third is an outcome delivered verbally, which leaves the employee with nothing and the company with no record of what it decided or why. The fourth is a procedure that exists in a policy nobody has read, so the first time anyone looks for it is when they are already angry.

There is also a measurement failure. Companies count grievances and treat a low number as good news. It usually is not. Zero formal grievances in a company of three hundred means either a genuinely healthy culture or a channel nobody trusts, and the two look identical in a report. The numbers worth watching are time to acknowledgement, time to outcome, the share of cases clustering around one team, and whether people who raised a grievance are still there a year later.

Running it in PeopleForce

Grievances run as cases in PeopleDesk, which gives the routing problem above a structural answer. Categories carry their own default assignee, so a complaint about a manager can be directed to HR or to a named handler by configuration rather than by the employee guessing who to email. Visibility is restricted by design: a case is visible to the assignee, to whoever raised it, to the employee it concerns and to people holding the case management permission, and to nobody else. Each case has a status that moves through new, in progress, on hold and closed, a priority, attachments and a message thread, so the exchange stays on the case instead of scattering across inboxes. There is a built-in seven-day service level, and a case still open past it is flagged as breached, which turns the silence failure into something visible on a list.

The anonymous channel is a separate case type with its own categories. When someone submits one they get a private link secured by a long random token, and that link is what lets them come back later to read replies and answer questions without ever identifying themselves. That is the design the whistleblowing rules are looking for, and it removes the usual trade-off where an anonymous report becomes a dead end. Cases carry the same audit stamps as other records, showing who created and last changed them, and closed cases keep their full history, which is what you need when a pattern across several complaints only becomes visible a year later.