Employee Grievance Redressal Policy in India: 2026 Guide

Employee Grievance Redressal Policy in India: Process, Committee & Template Guide

An employee grievance redressal policy is the piece of HR infrastructure most Indian SMBs build last and need first. Every company — 20 people or 2,000 — generates grievances: a disputed increment, a shift allocation that feels punitive, a manager who plays favourites, an expense claim stuck for months, a colleague's behaviour that falls short of harassment but corrodes the workday. What separates healthy organizations from toxic ones is not the absence of grievances; it is whether there is a trusted, predictable, time-bound way to raise and resolve them.

This guide gives HR managers, founders, and people-operations teams in India a complete playbook for grievance redressal: the legal backdrop (including where a Grievance Redressal Committee is expected), the types of grievances you should design for, a step-by-step process with realistic timelines, committee composition, documentation standards, non-retaliation safeguards, metrics, and a policy template outline you can adapt. Throughout, the emphasis is practical: a grievance system that works on paper but not at 6 p.m. on a Friday is not a system.

Why Grievance Redressal Deserves Real Investment

The business case is unglamorous but overwhelming:

• Grievances that have nowhere to go do not disappear. They convert into disengagement, absenteeism, quiet resignation followed by actual resignation, negative employer reviews, and — in the worst cases — legal disputes or labour department complaints that a 30-minute internal conversation could have prevented.
• Early signals are cheap; late signals are expensive. A pattern of small grievances about one manager or one process is the earliest warning system a company has. Companies without a channel simply receive the information later, in exit interviews and attrition dashboards.
• Fair process is retention. Research on organizational justice consistently finds that employees judge companies less by whether decisions favour them and more by whether the process was fair, transparent, and respectful. A credible grievance mechanism is procedural fairness made visible.
• Regulators and courts expect it. As set out below, elements of Indian law formally require grievance machinery in various contexts — and in disputes, the existence and use of a fair internal process consistently works in the employer's favour.

The Legal Backdrop in Plain Language

There is no single "Grievance Act," but several threads of Indian law converge on the same expectation. (Orientation only — verify current provisions for your establishment with counsel.)

Industrial disputes framework and the Grievance Redressal Committee

Industrial disputes legislation has long provided for a Grievance Redressal Committee (GRC) in establishments above a specified workforce threshold — a bipartite body with employer and worker representatives to resolve individual grievances internally, with prescribed size limits, representation norms (including women's representation provisions), and timelines for resolution and appeal. The Industrial Relations Code carries this machinery forward with updated thresholds and details. If your establishment employs workmen-category staff at or above the applicable threshold, a functioning GRC is not optional good practice; it is expected machinery. Check the currently applicable threshold and composition rules for your establishment.

Standing orders and service rules

Establishments covered by standing orders frameworks typically embed grievance and disciplinary procedures in their certified standing orders. Where standing orders apply, your grievance policy must align with them.

POSH: the mandatory separate track

Sexual harassment complaints follow the POSH Act's Internal Committee process — with its own composition rules, timelines, confidentiality requirements, and consequences. Your grievance policy must route such complaints to the IC, never absorb them. A general grievance committee handling a sexual harassment complaint is itself a compliance failure.

Other statutory channels that touch grievances

Wage disputes, PF/ESI issues, and safety complaints all have statutory authorities employees can approach directly. A good internal system does not (and legally cannot) block those routes; it resolves issues early enough that employees rarely need them. Some sectors and government-linked employers carry additional grievance obligations; and works committees in larger industrial establishments serve adjacent functions.

The common-law thread

Across employment disputes generally, Indian courts respond to the same fundamentals: was there a fair process, was the employee heard, was the outcome reasoned and documented? An internal grievance system that embodies natural justice — notice, hearing, impartiality, reasoned outcomes — is both an ethical baseline and practical legal protection.

Know What You Are Designing For: A Grievance Taxonomy

Design the system around the actual mix you will receive:

Two design consequences. First, not everything needs the full committee — most pay and facilities issues need speed, not solemnity; a two-tier system (informal/managerial resolution, then formal committee) matches effort to stakes. Second, routing rules matter more than forms — the intake step must recognize POSH matters, whistleblowing, and safety issues and send each to its proper track immediately.

The Grievance Redressal Process: Step by Step

Stage 0: Open channels and intake

Employees should be able to raise a grievance through more than one door: a written form (HRMS module, email, or portal), their manager, HR directly, or — where the manager is the subject — a skip-level or designated HR contact. Anonymous channels are valuable for pattern intelligence, though anonymous complaints have practical limits for individual redressal (you cannot give an outcome to someone you cannot identify). Every intake, whatever the door, lands in one register with a unique ID and date stamp — the register is the system.

Stage 1: Acknowledgment and triage (within 2–3 working days)

• Acknowledge receipt in writing with the reference ID and what happens next
• Triage: POSH → IC immediately; safety hazards → immediate operational response plus the grievance record; whistleblowing → ethics channel; everything else → informal or formal track by seriousness and employee preference
• Check for urgency flags: ongoing harm, retaliation risk, imminent exits

Stage 2: Informal resolution (target: 7–10 working days)

For the majority of grievances — pay corrections, facilities, scheduling, first-instance manager friction — a designated resolver (HR partner or the appropriate manager) investigates facts, speaks to the employee, fixes what is fixable, and records the outcome. The employee explicitly confirms whether they consider the matter resolved. If yes, close with a written summary. If no, escalate to the formal track as the employee's right, not HR's discretion.

Stage 3: Formal committee review (target: 15–30 days)

For escalated, serious, or contested grievances:

1. Committee convenes (composition below); members with a conflict of interest recuse
2. Written statement from the aggrieved employee; documents gathered (policies, records, communications — your HRMS attendance, payroll, and appraisal trails often decide factual disputes)
3. Hearing: the employee is heard in person, may bring a colleague where policy permits; respondent parties (e.g., a manager whose conduct is questioned) are equally heard — natural justice runs both directions
4. Enquiry: witnesses and records as needed, kept proportionate — this is grievance redressal, not criminal trial
5. Reasoned decision in writing: findings, decision, actions, and timeline — delivered to the employee and tracked to completion
6. Implementation check: HR verifies that promised actions actually occurred; an upheld grievance with unimplemented remedies is worse than a rejected one

Stage 4: Appeal (target: 15 days)

One appeal level — to a senior authority not involved earlier (founder/CEO in SMBs, or an appellate committee in larger firms). The appeal reviews process and reasonableness; it is not an automatic re-hearing. The appellate decision closes the internal process, without prejudice to the employee's statutory rights.

Timelines summary

Publish these timelines in the policy and report adherence — a grievance system's credibility is measured in calendar days.

Committee Composition and Conduct

Composition principles

• Bipartite balance where the statutory GRC applies: equal employer and worker representatives within prescribed size limits, with the chairing arrangements and women's representation the rules provide. For general (non-statutory) grievance committees, mirror the spirit: mixed levels, mixed functions, gender diversity.
• Small enough to convene fast — three to six members typically; a committee that cannot meet within a week is a bottleneck wearing a badge.
• Trained — members need basic instruction in natural justice, confidentiality, evidence handling, bias awareness, and writing reasoned outcomes. An untrained committee produces confident, indefensible decisions.
• Conflict rules — automatic recusal where a member is the subject, a witness, or in the reporting line of either party.

Conduct standards

Confidentiality on a need-to-know basis; no discussion of cases outside proceedings; equal hearing for both sides; decisions based on records and testimony, not corridor reputation; and written reasons for every outcome, including rejections — especially rejections, because a reasoned "no" preserves trust in ways a silent "no" never can.

Non-Retaliation: The Clause That Determines Everything

Employees do not use grievance systems they fear. The policy must state — and leadership must visibly enforce — that raising a grievance in good faith will never trigger adverse consequences: no transfer-as-punishment, no appraisal markdowns, no shift-allocation games, no social freezing tolerated from managers. Practical safeguards:

• Monitor post-grievance outcomes (appraisals, increments, transfers) of complainants for 12 months; unexplained adverse patterns get HR review
• Treat proven retaliation as serious misconduct in its own right, and say so in the policy
• Distinguish good-faith grievances that fail on facts (protected) from knowingly false, malicious complaints (actionable, with a high bar of proof and committee-level decision)

One visible instance of retaliation costs more trust than fifty well-resolved grievances earn.

Documentation and the Grievance Register

Maintain, for every grievance: the intake record, acknowledgment, triage decision, investigation notes, hearing records, decision with reasons, implementation confirmation, and appeal trail. Retain per your document retention policy and any applicable statutory requirements.

The register aggregates: ID, date, category, parties (access-controlled), track, stage dates, outcome, and implementation status. Run it in your HRMS if it has a case module, or a rigorously access-controlled tracker if not. The register is what converts individual cases into organizational learning — and what demonstrates, to an inspector, an auditor, or a court, that your process is real.

Metrics: The Health Dashboard

Review quarterly:

• Volume and category mix — rising facilities complaints mean a facilities problem; rising manager-conduct complaints in one team mean a manager problem
• Timeline adherence — percentage of cases meeting each stage target
• Resolution at informal stage — a healthy system resolves most cases early
• Appeal and reopen rates — high appeal rates signal weak first-instance quality
• Post-resolution satisfaction — a simple two-question pulse to complainants after closure ("was the process fair?" / "was the outcome explained?"), regardless of outcome
• Retaliation flags — post-grievance adverse-action reviews
• Repeat subjects — individuals or processes appearing across multiple grievances

Then act on the patterns: coach or move the repeat-subject manager, fix the payroll error class that generates a quarter of tickets, adjust the policy that everyone misunderstands the same way.

Policy Template Outline

Adapt this structure into your employee handbook:

1. Purpose and principles — fair hearing, timeliness, confidentiality, non-retaliation
2. Scope — who may raise (employees; decide explicitly on contract staff — extending access is good practice), and what is covered
3. Exclusions and routing — POSH → IC; whistleblowing → ethics channel; collective/union matters → their own machinery; appraisal outcomes contestable via the appraisal process first
4. Channels — the doors, including the route that bypasses one's manager
5. Process and timelines — the stages and day-counts above
6. Committee — composition, tenure, quorum, recusal, statutory GRC alignment where applicable
7. Rights of parties — to be heard, to bring a colleague where permitted, to written outcomes, to appeal
8. Non-retaliation and false complaints
9. Records and confidentiality
10. Review — annual policy review with metrics

Publish it, include it in onboarding, and — this is the step most companies skip — have leadership reference it approvingly in public settings. Employees calibrate to what leaders signal, not what handbooks contain.

Implementation Roadmap for an SMB (30–45 Days)

Week 1–2: Draft policy from the outline; check statutory GRC applicability for your headcount and category mix; align with standing orders if covered. Decide channels and build the register (HRMS case module or controlled tracker).

Week 3: Constitute and train the committee; brief all managers — especially on non-retaliation and on their role as the informal-resolution front line, since most grievances should be resolved by good management before reaching any committee.

Week 4: Launch to employees: a short all-hands explanation beats a policy PDF drop. Emphasize the timelines and the manager-bypass route.

Week 5–6: Run the first cases with extra HR attention; review intake quality and timeline adherence; fix friction. Schedule the first quarterly metrics review.

A Case Walkthrough: One Grievance, Start to Finish

Abstract processes become real in a single case, so follow one through:

An accounts executive at a 90-person company files a grievance through the HRMS portal: her overtime for the March closing sprint — approved verbally by her manager — was never paid, and when she followed up twice, the manager told her to "stop counting hours." The system generates ID GRV-2026-014 and HR acknowledges within one working day.

Triage classifies it as two issues: a pay dispute (factual, informal track) and a manager-conduct concern (the dismissive response). No POSH or safety dimension. The HR partner takes the informal track first: attendance records in the HRMS show 22 extra hours logged in the March window; the payroll register confirms no overtime element paid; email trails show the sprint was assigned. The factual half resolves in six working days — overtime computed per policy and paid with the next cycle, with a written note to the employee confirming the correction and the reason it was missed (the manager never converted verbal approval into a system approval).

The conduct half is not dropped. The HR partner speaks with the manager, who acknowledges the exchange. Because it is a first instance and the employee prefers resolution over escalation, the outcome is a documented coaching conversation with the manager, a fix to the process (overtime approvals now flow through the HRMS, not verbally), and a follow-up with the employee at 30 days to confirm no residue or retaliation. She confirms resolution; the case closes with both actions recorded.

Quarterly review later finds GRV-2026-014 is the third overtime-related grievance across two teams — pattern evidence that verbal approval culture is systemic. The fix goes company-wide, and overtime grievances disappear from subsequent quarters.

Total elapsed time: eleven working days. No committee needed, no drama — but every step written down, and a process improvement extracted. Most grievances should look like this; the formal machinery exists for the ones that cannot.

Mediation: The Underused Middle Path

Between "manager sorts it out" and "committee adjudicates" sits mediation — a structured conversation between the parties, facilitated by a neutral (a trained HR partner or senior employee), aimed at a mutually acceptable resolution rather than a verdict. It suits interpersonal grievances: peer conflict, communication breakdowns, friction that is real but not misconduct.

Ground rules that make workplace mediation work: participation is voluntary for both parties; the mediator has no stake and no reporting-line relationship to either side; what is said in mediation stays out of personnel files except the agreed outcome; and any agreement is documented and followed up at 30 and 90 days. Mediation is inappropriate where power imbalance or misconduct is central — never mediate a harassment allegation — but for the broad middle of workplace friction it is faster, cheaper, and less scarring than adjudication, and it leaves working relationships repairable, which a verdict rarely does.

Grievances in Remote and Hybrid Workplaces

Distributed teams change the grievance mix and the mechanics. Expect more grievances about invisibility — appraisal fairness, presence-based favouritism, unequal access to opportunities — and fewer about facilities. Adjust the system accordingly:

• Digital-first intake is no longer optional: portal or HRMS-based filing, acknowledged automatically, matters more when there is no HR desk to walk up to
• Hearings by video are valid — record logistics carefully (with consent where recording), and take extra care that the employee has a private setting for sensitive conversations
• Evidence shifts to chat logs, email, and system records; your data access and privacy discipline must keep pace — collect what is relevant, not everything
• Watch remote-specific patterns: complaint categories that cluster among remote staff versus office staff are telling you where hybrid equity is breaking

Training Managers: The Front Line the Policy Forgets

Most grievances are born in — and most should die in — the manager relationship. A grievance system paired with untrained managers is an emergency room with no primary care. Train every people-manager, at promotion and annually, on four things:

1. Receiving complaints well — thank, listen, take notes, never mock or minimize; the first sixty seconds of a manager's reaction determines whether the employee uses channels or leaves
2. What must be escalated immediately — POSH-related conduct, safety hazards, integrity issues, anything involving themselves — and that sitting on such complaints is itself misconduct
3. What they can resolve — routine pay, workload, scheduling, and interpersonal friction, with documentation habits that create the record the formal system depends on
4. Non-retaliation in practice — what subtle retaliation looks like (roster games, exclusion from meetings, appraisal drift) and that the company monitors for it

An hour of this training, twice a year, does more for grievance outcomes than any clause you will ever draft.

Common Mistakes That Kill Grievance Systems

• The suggestion-box launch. A channel announced once, never referenced again, with no published outcomes. Employees test systems with small complaints; if the small ones vanish into silence, the big ones go to the labour department or Glassdoor instead.
• HR as judge in its own cause. Grievances about HR decisions (payroll errors aside) reviewed solely by HR erode neutrality. Build the alternate routes before you need them.
• Timeline theatre. Publishing 15-day timelines and routinely taking 60 days is worse than publishing 30 and meeting it. Credibility compounds; so does its absence.
• Confidentiality by rumour. Committee members who discuss cases socially destroy the system faster than any procedural flaw. Make confidentiality breaches a conduct issue and enforce once, visibly.
• Resolving the person, not the pattern. Paying one employee's missed overtime while leaving the approval process broken guarantees the same grievance next quarter with compounding cynicism.
• Punishing the messenger softly. No one is fired for complaining — they are just mysteriously passed over, re-rostered, and left off invites. This is the failure mode employees fear most, and the one your monitoring must be designed to catch.
• Scaling nothing. The 30-person company where the founder resolves everything over chai works — until 80 people, two offices, and a manager layer arrive. Build the lightweight formal system before the informal one breaks, because it breaks silently.

What a very small company actually needs

If you are under the statutory thresholds and under ~50 employees, you do not need committee ceremony. You need four things in writing: a named person (plus one alternate not in the reporting chain) to receive grievances; a promise to acknowledge in two days and respond in ten; a routing rule for POSH and safety matters; and a one-page log. That is a complete, credible system for a small company — and the skeleton the full framework grows on later.

FAQ: Employee Grievance Redressal in India

Is a grievance redressal committee mandatory in India? For establishments employing workmen-category staff at or above the threshold specified under the industrial disputes/industrial relations framework, a Grievance Redressal Committee with bipartite composition is statutorily provided for. Thresholds and details have changed across amendments and the Industrial Relations Code, so verify the currently applicable requirement for your establishment. Separately, the POSH Act mandates an Internal Committee for sexual harassment complaints in establishments with 10 or more employees — a distinct, non-negotiable requirement.

Can sexual harassment complaints be handled by the general grievance committee? No. POSH complaints must go to the Internal Committee constituted under the POSH Act, which has its own composition, process, and timelines. Your grievance policy should route such complaints to the IC immediately upon identification.

What is a reasonable timeline to resolve an employee grievance? Acknowledge within 2–3 working days, resolve informal-track grievances within 7–10 working days, and complete formal committee reviews within 15–30 days, with a 15-day appeal stage. Publish your timelines and measure adherence — predictability is half the trust.

Should contract workers have access to the grievance system? Extending access to contract staff for matters within your control (safety, facilities, conduct on your premises) is good practice and increasingly expected, with contractual matters routed via the contractor. Principal-employer duty-of-care expectations continue to broaden.

What if the grievance is against the HR head or a founder? The policy must pre-define an alternate route — typically directly to the CEO, the board, or an external ombudsperson arrangement — so no one is the gatekeeper of complaints against themselves.

Can an employee still go to the labour department or court if we have an internal process? Yes. Internal mechanisms cannot bar statutory remedies. Their value is resolving issues early and fairly enough that external escalation becomes rare — and demonstrating good faith if a dispute does go external.

How should anonymous complaints be handled? Log them, mine them for patterns, and investigate what is verifiable. Be transparent in policy that individual redressal usually requires an identifiable complainant, while safety and integrity issues will be investigated regardless.

What records should we keep, and for how long? The complete case file — intake, triage, hearings, decision, implementation, appeal — plus the register, retained per your retention policy and applicable statutory requirements. In later disputes, the contemporaneous file is your best evidence of fair process.

How Your HRMS Multiplies the System

A grievance process runs on records, and records are what an HRMS produces as a by-product of daily operations. Practical integration points: intake through the employee self-service portal with automatic ID generation and acknowledgment; stage-wise status tracking with escalation alerts when timelines slip; access-controlled case files so confidentiality is enforced by permissions rather than promises; and — most decisive in practice — instant retrieval of the attendance, payroll, leave, and appraisal records that settle factual disputes in minutes instead of weeks. When the register, the timelines, and the evidence live in one system, the grievance process stops depending on any individual's diligence, which is exactly what "institutionalized" means.

Conclusion: Build the System Before You Need It

An employee grievance redressal policy in India is cheap to build, and its absence is expensive in exactly the ways that are hardest to see until late: trust that quietly erodes, patterns that surface only in attrition data, and disputes that escalate because there was no credible place to be heard. The blueprint is straightforward — multiple channels, honest triage, two tracks, real timelines, a trained committee, ruthless non-retaliation, and a register that turns cases into learning.

The operational layer is where good intentions usually leak: intake tracking, stage timelines, document trails, and the attendance, payroll, and appraisal records that decide factual disputes. CozyHR keeps employee records, attendance, payroll, and HR documentation in one system built for Indian SMBs — so when a grievance turns on the facts, the facts are a search away. Try CozyHR and give your people a process worthy of their trust.

This guide is general information, not legal advice. Statutory thresholds, committee requirements, and procedures vary by establishment type and are periodically amended — verify current requirements with qualified counsel or official sources.