Filing a grievance isn’t something most people get excited about. It’s a horrible necessity because all the conventional avenues have failed. Conversations go in circles, the story keeps changing, or you’re getting treated differently and nobody will say why.
If you’re already hovering over “send,” it helps to know how these situations usually unfold. Not in a dramatic courtroom way, but in the everyday reality of employee grievance disputes, where what you write, what you ask for, and what you can back up tends to shape what happens next.
One other thing that clears the fog fast is understanding unfair vs unlawful. Plenty of workplace behavior is unfair, petty, or biased in a way you can feel. But not all of it breaks the law. The legality however doesn’t mean you have to tolerate it, it just changes the best approach.
Question 1: What exactly happened, and what “bucket” does it fit into?
Before you make it formal, do a simple exercise: write the simple version of events and conditions in a few lines, as if you’re explaining it to a friend who has no context.
Bad: “My manager is targeting me and trying to get me fired.”
Better: “On January 9, my manager told me my tone was ‘aggressive’ in a meeting. On January 15, I was removed from the client rotation. On January 22, I asked for clarification and was told I’m ‘not a culture fit.’”
That second version is boring, and that’s the point. Boring is credible.
Then label the bucket, roughly:
- Discrimination or harassment tied to a protected trait
- Retaliation after you raised a concern
- Wage or scheduling issues (hours shaved, overtime ignored, misclassification)
- Safety concerns
- Policy violations, favoritism, or inconsistent discipline
You’re not writing a legal brief. You’re making it easy for a reasonable person to understand what happened.
Question 2: What outcome do you want, in plain language?
This is where a lot of grievances fall apart. People pour their whole emotional experience onto the page (understandably), but never actually say what needs to change.
Pick one clear outcome, plus a fallback. Examples:
- “I want the comments to stop and for reporting lines to change.”
- “I want my pay corrected and a written explanation of how the shortfall happened.”
- “I want the warning removed, or I want the documented basis for it.”
A good grievance doesn’t just accuse, it requests. If you’re stuck, this framing helps: state your ask clearly. Put the ask near the top, not buried after three pages of background.
Also, avoid making the only acceptable outcome “fire them.” You can feel that privately, but it often turns a solvable situation into a standoff.
Question 3: What evidence do you have, and what should you document right now?
You don’t need perfect evidence. You do need a clean record.
Start with a simple folder and collect:
- Dates and a timeline (even a notes app is fine)
- Key messages (email, Slack, texts)
- Performance proof (reviews, metrics, positive feedback)
- Pay records and schedules if money or hours are involved
- Witness names and what they directly observed
Here’s a common scenario: you’re told your performance “suddenly dropped.” If you’ve got consistent metrics or prior reviews, that claim becomes less believable without you needing to argue. The documents do the talking.
And keep your own notes factual. “Manager yelled, called me stupid” is usable. “Manager is a narcissist” is not.
Question 4: Are there risks, and what’s your escalation plan if things get worse?
People worry about retaliation because it can be real, and it isn’t always obvious. It can look like being frozen out of meetings, losing hours, getting nitpicked, or being set up to fail.
So make an escalation ladder before you file:
- If it’s safe, try one direct conversation (brief, calm, documented)
- File the formal grievance (facts, impact, ask, timeline)
- If it stalls, escalate internally (HR, ethics line, senior leader, depending on your org)
- If stakes are high, get outside advice and consider external routes
It’s like any plan where you want a result: you define the goal, then the path. Same basic logic as building customer reach. Without a path, you just create noise.
A quick “ready to file” checklist
- I can summarize the issue in 5 sentences with dates
- I can explain what outcome I want
- I’ve saved the key messages and written my timeline
- My tone is firm, but factual
- I know what my next step is if this is ignored
A grievance is a tool. Use it like one: clear, specific, and built to move something forward.
