The Difference Between a Grievance and a Complaint

HR perspective for employers across Sheffield and South Yorkshire

Not everything an employee raises is a grievance. And not everything that isn't a formal grievance should be treated as one.

That distinction matters more than most employers realise. Get it wrong in either direction and you create problems — either dismissing something that needed proper process, or escalating something that needed a conversation into something far more formal and adversarial than it had to be.

What a grievance actually is

A grievance is a formal concern raised by an employee about their work, working conditions, or treatment. Most organisations have a grievance policy that sets out how these should be handled — and under the ACAS Code of Practice, there's a minimum standard employers are expected to follow.

But not every concern an employee raises is a formal grievance. Someone mentioning they're unhappy with their workload in a one-to-one isn't raising a grievance. Someone emailing their manager to say they felt uncomfortable in a team meeting isn't necessarily raising a grievance. These are concerns — and they deserve a response, but not necessarily a formal one.

The problem is that employers often don't make that distinction clearly enough. Either they treat everything informally and miss the point where something needed proper process. Or they formalise everything and turn what could have been a straightforward conversation into a process that entrenches positions and damages relationships.

Why the distinction matters

Once something becomes a formal grievance the dynamic changes. There's documentation. There's an investigation. There's an outcome letter. The employee has the right to be accompanied. Managers get nervous. HR gets involved. What might have been resolvable over a coffee becomes something that follows everyone around for months.

That's not always avoidable. Some concerns are serious enough that formal process is the right response from the start. But a lot of grievances that end up going through full formal process didn't need to. They needed someone to take the concern seriously, have an honest conversation, and actually do something about it.

The informal stage most employers skip

The ACAS Code encourages employers to resolve issues informally where possible before moving to formal process. In practice that step gets skipped — either because the manager doesn't feel equipped to handle it, because the organisation doesn't have a clear process for informal resolution, or because by the time the concern is raised formally the relationship has already deteriorated to the point where informal feels inadequate.

The informal stage isn't about minimising the concern. It's about giving it the best chance of resolution without the collateral damage that formal process almost always brings.

What this looks like in practice

When a concern is raised — formally or informally — the first question worth asking is: what does this person actually need? Sometimes it's an apology. Sometimes it's a change in how they're being managed. Sometimes it's just to feel heard by someone with the authority to do something about it.

A good HR conversation at that early stage — before positions are entrenched, before solicitors are involved, before the formal process has taken on a life of its own — is often the most valuable intervention possible.

Across Sheffield and South Yorkshire, the employers who handle grievances well tend to have that kind of support available early. Not to manage the process. To help them understand what they're actually dealing with before the process takes over.

Dealing with a grievance or employee concern in Sheffield or South Yorkshire and not sure how to approach it? King HR Advisory provides senior HR support for employers who need experienced guidance without the full-time hire.