Cookies on this site
Strictly necessary cookies keep the site working. Our analytics and advertising tags — Microsoft Clarity and Google Tag Manager — stay switched off, and write no cookie, until you accept them. Privacy Policy
Cookie preferences
Choose which categories may run. Your choice is stored on this device and is remembered for six months. You can change it at any time from the “Cookie preferences” link in the footer.
Security, session integrity, your light/dark theme choice, and this cookie preference itself. The site cannot work without these, so they cannot be switched off.
Microsoft Clarity (session replay and heatmaps) and Google Analytics via Google Tag Manager. Used to see which pages help and which confuse. Off by default.
Google advertising tags via Google Tag Manager, used to measure which campaigns lead to a demo booking and to show relevant ads. Off by default.
An employee grievance is a formal complaint an employee raises about their employment: their treatment, their conditions, a decision affecting them, or the conduct of someone they work with. What separates it from ordinary feedback is that it is raised deliberately, recorded, and obliges the employer to respond through a stated procedure rather than informally.
Three things, and all three have to be present. It is raised deliberately, as a complaint rather than as a remark in passing, so both sides know what has happened. It is recorded, which means it exists independently of the memory of the people involved. And it obliges a response: once something has been received as a grievance, the employer has to do something and be able to show what. Feedback has none of those properties. An employee can say a rota is unfair in a one-to-one and nothing formal follows, which is often the right outcome for both of them. The distinction matters because it decides what happens next, and the most common failure in this area is a complaint that was plainly a grievance being handled as a conversation.
A named route for raising one that does not run only through the person being complained about. An acknowledgement, so the employee knows the complaint has been received rather than absorbed. An investigator who is not implicated in the events. The employee's ability to be accompanied at any meeting, where that applies. A decision communicated with reasons rather than as a bare outcome. And an appeal to somebody who did not make the first decision. Those elements recur across very different legal systems because they answer the same practical problems: who receives it, who looks into it, who decides, and what happens if the employee thinks the decision is wrong. What each of them must look like in a given place is a separate question, and not one to answer from a template.
Because the outcome will eventually be examined by somebody who was not there. A grievance handled well and documented badly is indistinguishable, months later, from one that was ignored. The record is also what makes patterns visible: three complaints about the same manager over two years look like three unrelated incidents to three different handlers and look like something else entirely in one list. And a proper audit trail protects the people who acted correctly, including the manager complained about, who is otherwise defended only by recollection. What has to be kept, how long it may be kept, and who may see it are governed by data protection and employment rules that differ by jurisdiction, so the retention question needs answering with advice rather than by habit.
Through a route the employee can use without going to the person they are complaining about. This is the single most common structural defect in grievance procedures: the document says raise it with your line manager, the complaint is about the line manager, and so the procedure has no entrance. Naming at least one alternative, such as a second manager, a human resources contact, or a named senior person outside the reporting line, costs nothing and removes the failure. The route also has to work for someone who does not want to write a formal document. Many grievances arrive as a conversation that turns serious halfway through, and the person receiving it has to be able to recognise that moment, say plainly that what is being described sounds like a grievance, and explain what will happen if it is treated as one. Leaving the employee to work out on their own that they needed a form is how genuine complaints end up unrecorded.
Acknowledgement is the next step and it is almost free. Confirming in writing that the complaint has been received, what it is understood to be about, and what happens next removes most of the anxiety of the first week and creates the first entry in the record. Getting the summary written down early also prevents the scope arguments that otherwise arrive later, when the employee says the complaint was about something broader than what was investigated. What must be offered at this point, what must be in writing, and what timescales apply are set by law and by any collective agreement in force, and they differ by jurisdiction and change. Have the procedure, including whatever is promised at acknowledgement, reviewed by an employment lawyer in the relevant jurisdiction before it is published, and again whenever it is amended. The acknowledgement is also the point at which to say who will handle the matter and how the employee can reach them, because a named person is the difference between a process and a silence.
Somebody who is not implicated in what is being complained about, which sounds obvious and is breached constantly. The most frequent version is that the investigation is handed to the respondent's own manager, on the reasoning that they know the team best. They do, and that is the problem: they made the appointment, they may have approved the behaviour, and their own judgement is in scope whether or not anyone says so. An investigation run by somebody with an interest in a particular finding is not rescued by the investigator being fair-minded, because it will not be believed by the employee and it will not survive being examined later. Where the organisation is too small to find anyone genuinely independent, the honest answer is to bring somebody in from outside rather than to pretend the problem does not exist. It is worth deciding who the fallback investigator is before a case arrives, since choosing one under pressure tends to produce the convenient answer rather than the defensible one.
The investigation itself should establish what happened before anyone considers what to do about it, and those two questions should be kept apart. Interview the people involved separately, take notes the interviewee can see, and keep the documents that existed before the complaint, such as rotas, messages and appraisal records, because they are more reliable than anyone's recollection. Where the employee is entitled to be accompanied at a meeting, that has to be offered rather than granted on request, since an employee who does not know about the entitlement cannot ask for it. Whether such an entitlement exists, who may accompany, and what they may do differ by jurisdiction and by any agreement in place. This is another point at which the procedure needs review by a qualified employment lawyer rather than adaptation from a document written for somewhere else. It is also worth agreeing at the outset what the investigation is not covering, because an investigator who quietly widens the scope produces a finding nobody asked for and leaves the original complaint unanswered.
The decision should be communicated to the employee with reasons, in writing, and the reasons should engage with what was actually alleged. An outcome letter saying the grievance was not upheld tells the employee nothing except that they lost, and it is the version most likely to be appealed, escalated externally, or simply raised again. Setting out what was investigated, what was found, and why the finding follows takes an extra page and resolves a large proportion of cases that would otherwise continue, because most people can accept a decision they disagree with far more easily than one they cannot understand. Where something is upheld, the letter should say what will change, since a finding with no consequence attached reads as an acknowledgement designed to close the file. Where something cannot be shared, because it concerns another employee's confidential outcome, say that it cannot be shared rather than leaving a silence.
The appeal has one structural requirement: it goes to somebody who did not make the first decision. An appeal reviewed by its own author is not an appeal, and everybody involved knows it. In a small organisation this is genuinely difficult and is still the point that has to be protected, which may mean a non-executive, a director from another part of the business, or an external reviewer. The appeal should also be a review of the decision rather than a fresh trial of the same facts, unless new evidence has appeared, or the process becomes indefinite. What the employee must be told about appealing, in what form, and what follows are governed by rules that differ by jurisdiction and change over time, so this part in particular should be settled with an employment lawyer in the relevant jurisdiction rather than drafted internally from an example found elsewhere.
Three, in roughly descending order of frequency. The first is informal resolution that leaves no trace. A manager hears something serious, deals with it quietly and well, and writes nothing down, so when the same issue recurs eighteen months later with a different employee there is no history and the second complaint is treated as a first. Informal resolution is often the right approach, and it is not incompatible with a note on file recording that a concern was raised and how it was addressed. The second is the investigator with an interest in the outcome, usually the respondent's manager, which taints a finding that may well have been correct. The third is delay, and it is the one employees complain about most. Each of these is a process defect rather than a matter of bad faith, which is why they recur in organisations that believe they handle grievances well.
Delay deserves separating out because of how differently the two sides experience it. From the employer's side a grievance sits alongside other work and moves when somebody has time. From the employee's side they have made an accusation about people they still work with and are waiting to learn what will happen to them, and every week of silence is read as a decision. Most of the delay is avoidable and comes from the same places: nobody was assigned, the investigator had a day job, or the decision waited on a diary. Assign an owner at the point of receipt and tell the employee who it is. A case that lives in one person's inbox is the one that stalls; a case recorded in the organisation's HR software at least has a visible owner and a date. Where the process will take longer than expected, say so and say why, rather than letting the silence carry the message.
Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. Everything on this page β sourcing, screening, interviewing, offers β runs in one pipeline.
Free for 1 user Β· No credit card Β· Talk to a real hiring expert
Pitch N Hire unifies sourcing, screening and hiring decisions on one AI-native platform. Book a quick demo on your real roles.
Prefer to talk? Book a demo Β· Talk to sales Β· View pricing
Free 1-user plan Β· No credit card Β· Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you β our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
β Free 1-user plan Β· No spam Β· Talk to a real hiring expert