Grievance or Complaint? How HR Should Tell the Difference

An employee emails their manager: "I'm not happy with how the rota is being done, it's always me on Saturdays." Is that a grievance? A complaint to be sorted informally? A whistleblowing disclosure? A possible discrimination issue? How HR classifies it decides which procedure applies, what timelines start and what records are needed. Get it wrong one way and a minor gripe becomes a formal process nobody wanted. Get it wrong the other way and a real grievance is handled informally and later found to have been ignored.

Working definitions

Terms vary by organisation and jurisdiction, so check your own policies. Generally:

• A concern or informal complaint is something an employee raises that can be resolved quickly by their manager, and that they have not asked to be handled formally.
• A formal grievance is a complaint about the employee's own treatment at work, such as pay, workload, bullying, discrimination or a manager's decision, that they want investigated and decided under the grievance procedure.
• A whistleblowing or speak-up report concerns wrongdoing that affects others or the public, such as fraud, safety breaches or legal violations, rather than the reporter's personal situation. It often carries specific protections and needs its own route; see handling whistleblowing reports confidentially.
• An external complaint about an employee, from a client or member of the public, is a different process again and may lead to an investigation or disciplinary route.

Questions that decide it

1. Whose interest is affected? The employee's own treatment points to a grievance; wrongdoing affecting others points to speak-up.
2. Has the employee asked for formal handling? If they say "formal grievance" or refer to the policy, treat it as one.
3. Does it allege discrimination, harassment or a safety risk? If so, do not leave it informal, whatever words were used.
4. Can the manager resolve it quickly and fairly? If the manager is the subject, it cannot stay with them.

Ask, then record the decision

When it is unclear, ask the employee how they want it handled, and explain the options. Then record the classification, who made it, when, and why. That single entry matters later if anyone says their grievance was ignored. If an informal concern later becomes formal, record that transition and date too.

Even informal concerns need a note

An informal resolution should still leave a short record: what was raised, what was agreed, the date. Patterns across several informal concerns about the same manager are often the first sign of a bigger issue, and they are invisible if nothing was written down.

Routing in practice

In Herarx, one way to set this up is a single intake template for anything raised by an employee, with a select field for the classification and the reason recorded beside it. Formal grievances then follow the grievance template with its own stages, parties in contact roles and restricted access; we described that structure in HR case files: handling a grievance. If it turns into a formal investigation, the same record continues rather than starting over, and the timeline shows each step. Per-case access keeps it visible only to the people handling it.

Review the mix

Once a quarter, look at what came in and how it was classified. A rising number of formal grievances, or of informal concerns about the same team, tells you something the individual cases do not.