Skip to content
Playbook
IntermediateHRManagerPeopleOps

Grievance Handling: The Quiet 30% of an HRBP's Calendar

A practical, theory-grounded guide to receiving, triaging, and resolving employee grievances without escalating risk or eroding trust — the workflow that…

18 min read Updated 2026-05-24
On this page
60-Second Summary
  • A grievance is a request for procedural justice — handle the process and the outcome becomes negotiable.
  • Triage every intake on three axes: severity, evidence, and protected-class exposure.
  • Acknowledge in 48 hours, decide in 30 days, document at every step — silence creates liability.
  • Use Adams' Equity Theory to read the emotional charge, not just the facts.
  • Close the loop in writing, even when the answer is 'no'. Especially when the answer is 'no'.

Surveys from SHRM and CIPD consistently show that employee relations work — grievances, conflicts, investigations, accommodation requests — consumes roughly a third of an HR business partner's week. Yet most playbooks skip it entirely. This is the missing chapter.

What a grievance actually is

Organizational justice research (Greenberg, 1987; Colquitt, 2001) splits fairness into four dimensions: distributive (the outcome), procedural (the process), interpersonal (how you were treated), and informational (what you were told and when). Most grievances people file as 'about pay' or 'about my manager' are really procedural or informational — the employee is signalling that the system, not the answer, felt unfair.

The reframing HR experts teach new HRBPs

When someone files a grievance, ask yourself which of the four justices they feel was violated. The right intervention almost always lives there, not in the surface complaint.

Intake: the first conversation

The 20-minute structured intake
  1. 1
    1. Acknowledge
    Thank them for raising it. Confirm confidentiality limits in plain language — you cannot promise total secrecy if safety or legal duties are triggered.
  2. 2
    2. Narrate, don't interrogate
    Ask them to walk through events in time order. Capture verbatim quotes where possible. Avoid leading questions ('Did he yell at you?' → 'What did he say next?').
  3. 3
    3. Identify the ask
    Distinguish 'I want this to stop', 'I want an apology', 'I want a transfer', 'I want them disciplined'. The ask shapes the path.
  4. 4
    4. Set expectations
    State the timeline (acknowledgement in 48h, investigation in 30 days), who will be involved, and what they can expect to hear back.
  5. 5
    5. Document immediately
    Write the intake note within the hour while memory is fresh. Date, time, location, witnesses, ask, next step. Store it in your case-management system, not your inbox.

The triage grid

Three-axis triage used by experienced employee-relations teams
AxisLowMediumHigh
SeverityInterpersonal frictionPattern of behavior, performance impactSafety, harassment, discrimination, retaliation
EvidenceSingle account, no artifactsMultiple accounts or contemporaneous notesDocuments, messages, recordings, video
Protected-class exposureNo protected characteristic involvedPossible link to protected characteristicExplicit reference to protected characteristic or unequal treatment
The escalation rule employment lawyers repeat

Any case scoring High on severity OR High on protected-class exposure is no longer a grievance — it is an investigation. Switch protocols immediately and loop in counsel.

The 30-day clock

  1. Day 0–2: Acknowledge in writing. Open the case file. Decide investigator and scope.
  2. Day 3–10: Interview complainant in full, then any witnesses, then the respondent. Always in that order.
  3. Day 11–20: Gather artifacts — Slack/Teams exports, calendars, performance docs, badge logs if relevant.
  4. Day 21–25: Draft findings. Apply the 'preponderance of evidence' standard most HR functions use (more likely than not).
  5. Day 26–30: Communicate outcome to complainant and respondent separately. Document the closure.

Closing the loop

The most common HR error is going silent at the end. Even when the outcome is 'no action warranted', tell the complainant — in writing — what was reviewed, what standard was applied, and what (if anything) changes. Procedural justice research (Tyler, 1988) shows that perceived fairness of the process predicts whether the employee stays, far more than the outcome itself.

Anti-patterns HR leaders see most

  • Letting the complainant's manager investigate their own team — bias is structural, not personal.
  • Promising 'total confidentiality' on intake, then breaching it when legal duties trigger.
  • Treating verbal complaints as not-yet-real. The clock starts at first notice, written or not.
  • Skipping the respondent interview because the evidence 'looks clear'. Procedural justice requires the chance to respond.
  • Closing the file without a written outcome. If it isn't documented, it didn't happen — for tribunals and for trust.
Written by Pawan Joshi. Sources cited inline. Last updated 2026-05-24.