Grievance Redressal Policy in India: A Practical Guide

Why every Indian employer now needs a written grievance redressal policy

A grievance redressal policy is the single cheapest piece of HR infrastructure an Indian company can build, and it is the one most SMBs skip. For years, the informal approach worked well enough: someone was unhappy, they spoke to their manager or to the founder, something got sorted out over chai, and everyone moved on. That model has quietly stopped working — partly because teams have grown beyond the size where everyone knows everyone, partly because remote and hybrid work has removed the corridor conversations that used to catch problems early, and partly because India's labour-code consolidation has pushed formal grievance machinery back onto the compliance agenda.

If you run people operations at a startup or an SMB in India, this guide is written for you. It walks through what a grievance actually is (and what it is not), how to design a grievance redressal policy that people will actually use, how to constitute a grievance redressal committee, what intake channels to offer, how to run a fair inquiry, what timelines to commit to, how to document everything defensibly, and what your grievance data should be telling you every quarter. There is a ready-to-adapt policy template section near the end, plus a 30-day implementation plan.

One caveat before we start: this article explains general principles and practical design. Indian labour law is a mix of central statutes, state rules, and sector-specific requirements, and thresholds and applicability change. Treat everything here as a starting point for discussion with a qualified employment lawyer or labour-law advisor who can confirm what applies to your entity, your headcount, and your states of operation.

What counts as a grievance? Definitions that prevent chaos

The most common failure in an employee grievance procedure in India is not a lack of process — it is a lack of definitions. When "grievance" means everything, the process means nothing. Your policy should draw crisp lines between four categories of employee voice, because each one has a different owner, a different legal footing, and a different timeline.

Feedback and suggestions. "The office Wi-Fi is slow." "Can we move the all-hands to Thursday?" These are inputs, not grievances. They deserve a response, but they belong in a suggestion box, a retro, or a manager one-on-one — not in a formal register with an inquiry officer attached.

Grievances. A grievance is a specific, personal dissatisfaction arising out of the employment relationship where the employee believes something is unfair, incorrect, or in breach of policy, contract, or law. Salary computed wrongly. Leave denied without reason. A promised transfer that never happened. Being excluded from a project. An abusive manager. Unsafe working conditions. The defining features are that it is individual (or affects a small identifiable group), specific, and the employee is asking for redress.

POSH complaints. Any complaint of sexual harassment at the workplace sits outside your ordinary grievance channel. Under the Sexual Harassment of Women at Workplace (Prevention, Prohibition and Redressal) Act — commonly called the POSH Act — such complaints go to your Internal Committee, follow the statutory process and timelines, and cannot be quietly "resolved" by an HR business partner. Your grievance policy's job is to recognise and route these, not to handle them.

Whistleblower or protected disclosures. Allegations of fraud, bribery, falsified records, data theft, regulatory breach, or conduct that harms the company or third parties rather than the complainant personally. These need an ethics or audit route, tighter confidentiality, stronger anonymity options, and often board-level visibility.

The routing table every policy should contain

Put a version of this table on page one of your policy. It saves more time than any other single element, because it lets employees and managers self-route correctly on day one.

Two design notes on that table. First, always allow a wrongly routed complaint to be re-routed without penalty — an employee who files a POSH matter as a general grievance should have it moved to the IC promptly, with an explanation, not rejected. Second, never let the routing table become a way to reject complaints. The receiving officer's job is to find the right home for every input, not to look for reasons to close it.

Why informal grievance handling breaks down

Founders often push back here: "We're forty people. If someone has a problem they can just tell me." That is genuinely true at twelve people. It stops being true somewhere between thirty and eighty, and the failure is rarely dramatic — it is slow and invisible.

Access becomes unequal. In an informal system, the people who get heard are the ones who are confident, well-networked, and comfortable walking into the founder's cabin. Quieter employees, junior staff, people on the shop floor, contract workers, women in male-dominated teams, and anyone whose first language is not the office's default language get systematically less airtime. The complaints you hear are not the complaints that exist.

There is no record, so there is no pattern. Three people leave in eight months because of the same team lead. Each exit interview mentions it vaguely. Nobody connects them because nothing was written down. A grievance register would have surfaced that pattern after the second conversation.

Outcomes become inconsistent. Two employees raise near-identical issues about shift allowances. One gets an adjustment because they escalated to a sympathetic manager; the other is told "that's the policy." Inconsistency is the fastest way to destroy trust in HR, and it is also the thing that looks worst if the matter ever reaches a labour authority or a court.

Escalation becomes personal. Without a defined ladder, an employee whose manager ignores them has only one option: go over the manager's head, loudly. That turns a solvable problem into a political fight, and it teaches everyone else that raising issues is dangerous.

Retaliation goes unchecked. When there is no record of who complained and when, there is also no way to detect that the complainant's ratings dropped, their project was reassigned, or their increment was skipped three months later.

Legal exposure accumulates. If an employee eventually raises a dispute externally, the first question asked is what internal mechanism existed and whether it was followed. "We handled it informally" is a weak answer. A dated register, a written acknowledgement, an inquiry note, and a communicated outcome are a strong one.

The legal backdrop, in general terms

You do not need to be a lawyer to design a good grievance mechanism, but you should understand the shape of the obligations.

Industrial relations law. India's industrial relations framework — historically the Industrial Disputes Act and, under the labour-code consolidation, the Industrial Relations Code — has long contemplated internal machinery for resolving individual disputes inside establishments above a certain size, typically constituted with representatives of both the employer and the workers. The consolidation exercise has renewed attention on this because employers reviewing their compliance posture against the codes are discovering that a formal grievance body is one of the items on the list. The exact headcount threshold, the composition rules, the maximum size of the committee, requirements around adequate representation of women, and the timelines for disposal are set out in the statute and in state rules — and applicability and commencement have varied. Confirm the current position for your establishment with your advisor rather than relying on any blog, including this one.

Standing orders. Establishments covered by standing-orders requirements (again, threshold- and state-dependent) typically need certified standing orders that cover conditions of service, misconduct, and disciplinary procedure. Your grievance policy should sit alongside these, not contradict them. If your certified standing orders say a charge-sheeted workman gets a specified process, your policy cannot offer less.

Shops and Establishments Acts. Most white-collar Indian SMBs are governed by their state's Shops and Establishments Act, which regulates hours, leave, holidays, and termination notice. Many grievances are fundamentally about these entitlements. State rules differ meaningfully — Karnataka is not Maharashtra is not Telangana — so a multi-state employer needs a policy that is uniform in process and locally correct in entitlements.

POSH Act. If you employ ten or more people (verify the current threshold and the counting rules for your set-up), you are expected to constitute an Internal Committee, with an external member, and to follow the statutory complaint process and reporting requirements. This is separate machinery. Do not fold it into your general grievance committee.

Other statute-specific channels. Provident fund, ESI, gratuity, maternity benefit, equal remuneration, and disability-inclusion obligations each have their own regulator and, in some cases, their own designated internal officer requirements. A grievance about a statutory entitlement should be flagged for specialist handling rather than treated as a routine ticket.

Contractors and gig workers. If a substantial part of your workforce is engaged through a contractor or on a services agreement, decide explicitly whether your grievance mechanism is open to them. Many employers extend intake to everyone on the premises and then coordinate the outcome with the contracting entity. Excluding them entirely is both a reputational risk and, depending on the arrangement, potentially a legal one.

How grievance redressal committees are typically constituted

The dominant Indian model — and the one your policy should mirror even if you are below any statutory threshold — is a small, standing, bipartite committee:

• Balanced representation. Equal or near-equal numbers of employer nominees and employee representatives. Employer nominees are usually the HR head, a functional or plant head, and sometimes a finance or legal representative. Employee representatives are ideally elected or nominated by the workforce rather than hand-picked by management, because perceived independence is the whole point.
• Adequate representation of women. Statutory schemes commonly require this, and it is good practice regardless. A committee of five men will not receive the grievances that most need receiving.
• A chair with authority. Usually the HR head or a senior functional leader. The chair must have enough seniority that their recommendations get implemented, and enough distance that they are not personally implicated in most cases.
• A member secretary. Someone who convenes meetings, maintains the register, tracks SLAs, and keeps the file. In a fifty-person company this is a part-time role for one person; do not leave it unassigned.
• A modest size. Large committees do not meet. Keep it to four to eight people with a defined quorum.
• Fixed tenure and rotation. Two-year terms with staggered rotation keep the body fresh and prevent it from becoming a fiefdom.
• A recusal rule. Any member who is the subject of, related to, or reporting into a party to a grievance steps out of that matter. Name an alternate in advance so recusal does not stall the case.

Designing the grievance redressal policy: scope, principles, definitions

A good grievance redressal policy is short enough to be read and specific enough to be used. Aim for six to ten pages, written in plain language, with the escalation table and the intake channels on the first two pages.

Scope

State clearly who is covered (permanent employees, probationers, interns, trainees, fixed-term staff, and — decide deliberately — contract and third-party personnel), which locations, and what is expressly out of scope. Common exclusions to name explicitly, with the correct alternative route alongside each:

• Sexual harassment complaints (route: Internal Committee under the POSH Act)
• Fraud, corruption, and regulatory breach (route: whistleblower/ethics channel)
• Disagreements with a completed disciplinary decision (route: the disciplinary appeal process, not a fresh grievance)
• Collective demands about wages or service conditions where a recognised union or works committee exists (route: the applicable collective mechanism)
• Performance rating disputes, if you run a separate calibration-appeal window — though if that window has closed, the grievance channel should still hear a claim of procedural unfairness

Principles

These five principles should be stated at the top and then actually reflected in the procedure that follows. Employees can tell the difference between principles that appear in the preamble and principles that appear in the mechanics.

1. Confidentiality. Information is shared only with those who need it to investigate or decide. Not with the complainant's team. Not with the respondent's friends. Not at the leadership offsite as an anecdote. Say what confidentiality cannot mean: you cannot promise the respondent will never learn the substance of the allegation, because natural justice requires they be able to answer it.
2. Non-retaliation. Retaliation against a complainant, a witness, or an investigator is itself misconduct, independently punishable, and the policy should say so in one unmissable sentence.
3. Natural justice. No one is judged without knowing the case against them and having a real opportunity to respond; no one decides a matter in which they have an interest. These two rules — audi alteram partem and nemo judex in causa sua — are the backbone of every defensible internal inquiry in India.
4. Proportionality. The process should fit the problem. A payroll error needs a correction and an apology, not a three-person inquiry panel. A bullying allegation needs a proper inquiry, not a WhatsApp message.
5. Good faith, both ways. Employees are protected when they complain honestly, even if the complaint is not upheld. Deliberately false or malicious complaints are a separate issue — but define that narrowly and use it rarely, because a broad "false complaint" clause is the fastest way to silence genuine ones.

Definitions

Define, at minimum: grievance, complainant, respondent, aggrieved employee, grievance officer, grievance redressal committee, inquiry, working day, escalation, and resolution. Define "working day" precisely — it determines every SLA in the policy, and ambiguity here is where timelines go to die.

Intake channels: making it easy to raise a grievance

Employees do not use channels they cannot remember, cannot access, or do not trust. Offer three to five, publicise them constantly, and make sure every one of them lands in the same register.

A few practical rules for intake:

• One register, many doors. Whatever channel is used, the matter must be logged in a single grievance register with a unique reference number. Multiple parallel logs mean you cannot count anything and cases fall through gaps.
• Acknowledge fast, always in writing. An acknowledgement within one or two working days, with the reference number, the name of the handler, and the expected timeline, does more for perceived fairness than almost anything else in the process.
• Accept grievances in the languages your workforce speaks. A form only in English in a plant where the floor speaks Hindi, Tamil, or Marathi is not a real channel.
• Do not require a prescribed format. Accept an email, a form, a handwritten note, or a verbal complaint transcribed by the receiving officer and read back to the complainant for confirmation.
• Publicise relentlessly. Induction, the intranet, notice boards, the HRMS home screen, and a reminder in the monthly all-hands. If you ask a random employee how to raise a grievance and they cannot answer in ten seconds, your channels are theoretical.

Triage and categorisation: the taxonomy that makes analytics possible

Every grievance that enters the register should be classified within one working day on four axes. This takes two minutes per case and unlocks everything you will later want to measure.

Axis 1 — Category. Keep this list short and stable. A workable starting taxonomy:

• Compensation and payroll (errors, deductions, reimbursements, F&F)
• Leave and attendance (application, approval, balances, shift rosters)
• Benefits and statutory (PF, ESI, insurance, gratuity, maternity)
• Working conditions and safety (facilities, equipment, hygiene, hazards)
• Workload and staffing (unreasonable hours, chronic understaffing)
• Behaviour and conduct (rudeness, bullying, verbal abuse, favouritism)
• Discrimination and inclusion (gender, caste, religion, region, disability, age)
• Career and performance (appraisal process, promotion, transfer, PIP fairness)
• Policy application and interpretation (inconsistent enforcement)
• Manager relationship (breakdown of the reporting relationship itself)
• Exit and separation (notice period, dues, relieving documents, experience letters)
• Other (review quarterly; if "other" exceeds a tenth of volume, your taxonomy needs a new category)

Axis 2 — Severity. Three or four levels, defined by consequence rather than by emotion:

• Low — individual inconvenience, easily corrected, no ongoing harm
• Medium — material impact on one person's pay, role, or working conditions
• High — allegations of misconduct, discrimination, safety risk, or statutory breach; multiple affected employees
• Critical — imminent safety danger, potential criminal conduct, or matters implicating senior leadership

Axis 3 — Route. Ordinary grievance, POSH referral, whistleblower referral, disciplinary process, or collective/union route.

Axis 4 — Conflict check. Does the case involve anyone in the normal handling chain? If yes, name the alternate handler immediately.

Triage should be done by a named grievance officer, not by whoever happens to open the inbox. It should take a day, not a week — a case sitting untriaged is a case where the clock is running and nobody is accountable.

The escalation ladder and stage-wise timelines

A grievance redressal policy lives or dies on its timelines. Vague commitments ("we will resolve grievances promptly") are worse than none, because they invite the complainant to define "promptly" for themselves. Publish a stage-wise ladder with numeric SLAs and stick to it.

Here is a four-stage ladder that works for most Indian SMBs. Adjust the day counts to what you can genuinely deliver — a missed 3-day SLA damages trust far more than an honoured 7-day one. Where a statute prescribes a timeline (POSH inquiries, for example), the statutory timeline governs.

Some rules that make the ladder function in practice:

• The clock runs from receipt, not from when someone gets around to it. Log the receipt date on day zero and calculate SLAs from there.
• Skipping stages is allowed for serious matters. A safety hazard, a discrimination allegation, or a complaint against a senior leader goes straight to Stage 3. Write this into the policy so the complainant does not have to argue for it.
• Extensions must be requested, justified, and communicated. If an inquiry needs more time because a witness is on leave, tell the complainant in writing, give a revised date, and log the reason. Silence during an extension is what turns a grievance into a resignation.
• Auto-escalation on breach. If a stage's SLA lapses without an outcome, the case should escalate automatically to the next level and notify the HR head. Configure this in your HRMS rather than relying on someone to notice.
• State clearly that the internal process does not waive statutory rights. No policy can require an employee to give up access to a labour authority, the IC, or a court. Saying so openly increases trust rather than encouraging escalation.

Conducting a fair inquiry

Most Indian SMBs are not bad at wanting to be fair. They are bad at the mechanics of fairness — and the mechanics are what a labour officer, a tribunal, or an aggrieved employee's lawyer will examine.

Step-by-step: running a grievance inquiry

1. Confirm scope and appoint the inquiry. Write down, in one paragraph, exactly what is being inquired into. Appoint the inquiry officer or panel in writing, confirm no conflict of interest, and record that confirmation. Scope creep is the most common reason inquiries take three months.
2. Preserve evidence early. Before anyone is interviewed, secure attendance logs, payroll records, approval trails, emails, chat exports, CCTV where lawfully available, roster sheets, and system access logs. Evidence disappears once people know an inquiry is running.
3. Give the respondent written notice. State the substance of the allegation in enough detail that they can meaningfully respond, provide copies of the documents relied on, and give reasonable time to reply — usually a few working days, not a few hours. A respondent who first hears the allegation in the room cannot answer it fairly.
4. Interview the complainant first, in full. Take a detailed statement. Ask for specifics: dates, times, locations, who else was present, what was said, what the impact was, what outcome they are seeking. Read the statement back and have it signed or confirmed by email.
5. Interview witnesses individually. Never in groups. Ask open questions before specific ones. Record who suggested each witness. Tell each witness about the non-retaliation protection and about the confidentiality expectation.
6. Interview the respondent. Put every material allegation to them explicitly and record their answer to each. Ask for their documents and their witnesses, and actually pursue them. An inquiry that does not test the respondent's version is not an inquiry.
7. Take contemporaneous notes. Date, time, location, attendees, questions asked, answers given, documents shown. Write them during or immediately after the meeting, not from memory a week later. Where possible, share the note with the interviewee for confirmation.
8. Evaluate on the balance of probabilities. Internal inquiries are not criminal trials. The standard is what is more likely than not, based on the evidence — not "beyond reasonable doubt", and not "whoever is more senior."
9. Write a reasoned report. Structure it as: allegation, process followed, documents examined, persons interviewed, findings of fact with reasons, conclusion on each allegation, and recommended action. The reasons matter more than the conclusion; a report that says only "allegation not substantiated" is indefensible.
10. Communicate the outcome in writing. The complainant is entitled to know the outcome, the reasoning at a summary level, the remedy, and their appeal rights. You may withhold details that would breach the respondent's privacy or expose a witness — but not the fact of the outcome.
11. Close the loop and diarise a follow-up. Set a check-in 30 to 60 days later to verify the remedy was implemented and no retaliation occurred. Log that check-in as part of the case file.

What not to do

• Do not let the accused's manager investigate their own team without oversight.
• Do not have HR act as investigator, prosecutor, judge, and appellate authority in the same case.
• Do not tell the complainant to "just sort it out between yourselves" when the allegation involves a power imbalance.
• Do not delay because a key person is busy; appoint an alternate.
• Do not record interviews covertly, and be cautious about recording at all — get consent, and be clear about how the recording will be stored and used.
• Do not decide the outcome before the respondent has been heard, however obvious the case seems.

Hard cases: grievances against a manager, an HR leader, or a founder

Every workplace complaint process is tested by the cases it least wants to handle. Design for these in advance, in writing, while nobody is emotional.

Against the reporting manager. The default rule is simple: a grievance is never handled by the person it is about. Your policy should state that where the manager is the subject, the matter enters at Stage 2 directly with the HRBP or grievance officer. Practical protections matter too — consider whether the complainant's next appraisal should be reviewed by a skip-level, whether project allocation decisions need a second signature for a defined period, and whether a temporary reporting change is appropriate. Frame any interim measure as neutral and protective, not punitive, and explain that framing to both parties.

Against an HR team member. If your grievance officer is the respondent, the case goes to the committee with the HR representative recused, or to an external investigator. Name the fallback in the policy — "the Chair of the Grievance Redressal Committee, or where the Chair is conflicted, an independent external investigator appointed by the Board" — so nobody has to invent it under pressure.

Against a founder, director, or CXO. This is where SMB processes usually collapse, because everyone in the chain reports to the respondent. The only credible answers are structural:

• A designated external member on the committee — a retired HR leader, an employment lawyer, or an independent director — who is available for exactly these cases.
• An independent external investigator retained in advance, so you are not shopping for one in a crisis.
• A reporting line to the board, an audit committee, or a designated independent director for cases above a defined severity.
• An explicit statement that the founder recuses themselves entirely, including from any decision about the complainant's employment, compensation, or role during the pendency of the matter.

If your company genuinely cannot investigate its own leadership, employees learn that quickly, and your entire grievance mechanism loses credibility — including for the routine payroll cases.

Anonymous complaints. Accept them, but be honest about their limits. An anonymous allegation with specifics — dates, documents, names, systems — can usually be verified without knowing the source. An anonymous allegation that is purely an impression ("people are unhappy in the sales team") is a signal to investigate the climate, not a case to adjudicate. Publish your approach: every anonymous complaint is logged and assessed; those with verifiable specifics are investigated; those without lead to a broader review such as a team listening session or a skip-level round. Also offer a middle path — "confidential, not anonymous", where the complainant identifies themselves to the grievance officer only, and their identity is not shared further without consent except where disclosure is unavoidable for a fair inquiry or is legally required. Many people who would never file anonymously will use this option.

Group grievances. When five people from one team file the same complaint, resist the urge to process five tickets. Log them individually for the record, then consolidate the inquiry, and be alert to whether the underlying issue is systemic — a broken shift roster, an unworkable target, an unsafe process — rather than individual.

Outcomes, remedies, and appeals

An inquiry that ends with a finding but no remedy is worse than no inquiry. Your policy should list the categories of outcome available, so both parties know what is realistically on the table.

Where the grievance is upheld, remedies typically include:

• Correction and restitution — arrears paid, leave restored, deduction reversed, records amended, documents issued
• Policy or process change — an approval workflow fixed, a roster redesigned, an entitlement clarified in writing to everyone affected
• Coaching, counselling, or mandatory training for the respondent
• A written warning, a formal reprimand, or an adverse note on record
• Reassignment, reporting-line change, or role change
• Formal disciplinary proceedings under standing orders or the disciplinary policy, where the conduct is serious
• An apology, where the complainant wants one and it is meaningful rather than coerced
• Interim protective measures continued for a defined period

Where the grievance is not upheld, say so clearly and explain why. Then ask a second question that most employers skip: was there still a real problem here? Many grievances are not substantiated as alleged but reveal a genuine process failure, an ambiguous policy, or a communication breakdown. Fix that anyway and tell the complainant you did. This one habit converts a large share of "lost" cases into restored trust.

Appeals. Give both parties a defined appeal window — commonly seven to fifteen working days from the outcome communication. The appellate authority must be someone not previously involved. Limit appeals to defined grounds — procedural unfairness, new evidence that was not reasonably available earlier, a finding unsupported by the evidence, or a disproportionate remedy — so the appeal is a review, not a re-run of the whole inquiry. State that the appeal decision is internally final, while making clear that the employee's statutory remedies remain available.

Documentation standards and retention

The quality of your grievance file is what stands between a fair process and an indefensible one. Assume every file may one day be read by someone hostile, and write accordingly.

Every case file should contain:

• The unique reference number and the date and channel of receipt
• The original complaint in the complainant's own words
• The written acknowledgement sent, with its date
• Triage classification: category, severity, route, conflict check, assigned handler
• Notice given to the respondent and their written response
• List of documents examined, with copies attached
• Dated interview notes for every person spoken to, confirmed where possible
• The reasoned findings or inquiry report
• The outcome communication to the complainant and to the respondent
• Any appeal, and the appellate decision
• Evidence that the remedy was implemented
• The post-closure retaliation check-in note
• A closure entry with the closure date and total cycle time

Documentation discipline:

• Write facts, not adjectives. "Raised his voice and used the words X and Y in the 11 a.m. stand-up on 12 March, witnessed by A and B" beats "behaved unprofessionally."
• Separate what you observed, what you were told, and what you concluded.
• Never backdate anything. Never edit a note after the fact — add a dated addendum instead.
• Keep grievance files out of the general personnel folder, on restricted access, with an access log.
• Keep POSH files entirely separate, under the IC's control, with tighter access than everything else.
• Redact third-party personal data before sharing any document with a party to the case.

Retention. Set a defined retention period for grievance records — many employers align it with their broader employment-records retention schedule and keep files for several years after closure or after the employee's exit, whichever is later. Retention periods interact with limitation periods for legal claims and with statute-specific record requirements, so set yours in consultation with your advisor rather than picking a number. Whatever you choose, apply it consistently, document the rule in the policy, and dispose of records securely when the period ends. Also account for India's data-protection expectations: grievance files contain sensitive personal data and should be stored with access controls, encryption where feasible, and a clear purpose limitation.

Protecting against retaliation

Retaliation is the risk that most damages a grievance mechanism, because a single visible instance teaches an entire workforce that the process is unsafe. Build active detection, not just a policy sentence.

• Define retaliation broadly in the policy: adverse changes to role, pay, ratings, shifts, projects, or reporting; exclusion from meetings or information; increased scrutiny; hostility; and pressure to withdraw the complaint.
• Tell both parties, in writing, at the start that retaliation is separately punishable and that the complainant should report any perceived retaliation immediately.
• Run a systematic post-case audit. For every complainant, check at 30, 90, and 180 days: performance rating trajectory, increment and bonus decisions, project allocation, attendance and leave approvals, any disciplinary action initiated, and resignation status. A dip that coincides with a complaint requires explanation, not assumption.
• Protect witnesses too. Witness intimidation is often more common than direct retaliation against a complainant.
• Watch for constructive retaliation. A complainant who is not punished but is quietly frozen out — no work, no meetings, no feedback — has been retaliated against just as effectively.
• Act visibly when it happens. The deterrent value of the rule comes entirely from enforcement.

Grievance analytics: what your numbers should be telling you

Once every grievance is logged with a category, a severity, dates, and an outcome, you have a dataset that is more honest about your organisation than any engagement survey. Review it monthly at the HR level and quarterly with leadership. The metrics worth tracking:

• Volume and rate. Total grievances, and grievances per hundred employees, tracked over time. Do not celebrate a low number — low volume in a large or stressed workforce usually means the channel is not trusted, not that everyone is happy. Rising volume after a policy launch is the expected and healthy pattern.
• Category mix. Which categories dominate, and how the mix shifts. A quarter where payroll grievances triple points at a specific process break, not at a rise in employee entitlement.
• Source mix by channel. If almost everything arrives through the anonymous box, people do not feel safe using their names. If nothing does, the anonymous channel may be invisible or distrusted.
• Cycle time. Median and 90th-percentile days from receipt to closure, by stage and by category. The 90th percentile is where the reputational damage lives — the few cases that take four months are the ones people tell each other about.
• SLA adherence. Percentage of cases acknowledged, triaged, and closed within committed timelines, by handler and department.
• Escalation rate. Share of cases escalating past Stage 1. A high rate suggests managers are not equipped or not trusted to resolve anything.
• Upheld rate. Share of grievances substantiated in whole or part. Persistently very low upheld rates warrant a hard look at investigation quality and impartiality.
• Repeat hotspots. Grievances per hundred employees by department, location, and manager. Three or more grievances against the same manager in a year is a signal that deserves a structured review regardless of individual outcomes.
• Repeat complainants and repeat respondents. Both are worth understanding, without prejudging either.
• Withdrawal rate. Complaints withdrawn before conclusion. A high rate can indicate pressure, fatigue with the process, or fear — investigate the pattern.
• Retaliation flags. Cases where a post-closure audit raised a concern, and what happened next.
• Attrition correlation. Exit rate among complainants in the twelve months after closure, compared with the general rate. This single number tells you whether your process actually protects people.

What the numbers should trigger

Analytics are only useful if they are wired to action. Agree the triggers in advance:

• Payroll or leave grievances above a threshold in a quarter → process audit of that workflow, not case-by-case firefighting
• Three or more grievances involving one manager in twelve months → structured review with the manager's leader, coaching plan, and a skip-level listening round with the team
• One location consistently above the company average → site visit, supervisor training, and a check on local statutory compliance
• Median cycle time drifting past your SLA for two consecutive months → capacity problem; add handlers or simplify Stage 1
• Anonymous share rising sharply → trust problem; audit confidentiality practice and retaliation handling
• Upheld rate near zero → investigation quality review, possibly with an external reviewer

Training managers: the highest-leverage investment

Most grievances are resolved — or created — at the first-line manager level. A half-day workshop, refreshed annually, changes outcomes more than any amount of policy drafting. Cover:

• Recognising a grievance when it arrives disguised as a complaint about workload or a casual remark
• The routing table: what must go to the IC, what must go to ethics, what they may handle themselves
• What they must never promise — absolute confidentiality, a guaranteed outcome, or that "nothing will change"
• How to take a factual note of a conversation on the same day
• The duty to log and escalate rather than sit on something
• Non-retaliation, including unconscious forms of it
• What to do when they are the subject of the grievance: cooperate, do not confront the complainant, do not discuss it with the team

Run the workshop with real, anonymised scenarios from your own register. Managers engage far more with "here is what happened here last year" than with generic case studies.

A ready-to-adapt grievance redressal policy template

Use this as a drafting skeleton. Adapt the language, fill in the bracketed items, and have it reviewed by your labour-law advisor before publication.

1. Purpose and philosophy. Why the company maintains a grievance redressal policy; commitment to fair, timely, and confidential resolution.
2. Scope and applicability. Employees covered, locations covered, effective date, and treatment of contract and third-party personnel.
3. Definitions. Grievance, complainant, respondent, grievance officer, committee, inquiry, working day, escalation, resolution, retaliation.
4. What is not covered, and where it goes instead. POSH complaints to the Internal Committee; fraud and regulatory breach to the ethics channel; disciplinary appeals to the disciplinary process; collective demands to the applicable mechanism.
5. Principles. Confidentiality, non-retaliation, natural justice, proportionality, good faith.
6. Intake channels. Each channel listed with the exact contact point, the form or link, and the languages supported.
7. Acknowledgement and triage. Timelines, classification axes, conflict-of-interest check, assignment of a named handler.
8. The escalation ladder. The stage table with handlers, scope, timelines, and outputs; direct-entry rules for serious matters; auto-escalation on SLA breach.
9. The grievance redressal committee. Composition, representation of women, tenure, quorum, chair, member secretary, recusal rules, meeting cadence.
10. Inquiry procedure. Notice, evidence, interviews, right to be heard, standard of proof, accompaniment rights (whether a colleague may accompany a party), report format.
11. Interim measures. What may be put in place pending inquiry and how they are framed as neutral.
12. Outcomes and remedies. The list of available remedies; communication of outcome to both parties.
13. Appeals. Window, grounds, appellate authority, timeline, finality.
14. Anonymous and confidential complaints. How each is treated and what the limits are.
15. Non-retaliation and protection. Definition, prohibition, reporting route, post-closure audit commitment.
16. False or malicious complaints. Narrowly defined; good-faith complaints expressly protected.
17. Documentation, confidentiality, data protection, and retention. What is kept, who can access it, how long it is retained, how it is disposed of.
18. Reporting and review. What is reported to leadership and how often; annual policy review date.
19. Statutory rights preserved. Explicit statement that internal processes do not restrict access to statutory forums.
20. Annexures. Grievance form, acknowledgement template, inquiry notice template, inquiry report format, outcome letter template, register format, and the routing table.

Common mistakes to avoid

• Writing a policy nobody can find. If it lives in a PDF in a shared drive folder from 2023, it does not exist. Put it in the HRMS where the raise-a-grievance button is.
• Committing to timelines you cannot meet. Publish honest SLAs and hit them. Ambition here is self-harm.
• Treating volume as failure. Grievances rising after launch means the channel is working.
• Letting HR own every role in the process. Investigator, decision-maker, and appellate authority must not be the same person.
• Confusing confidentiality with secrecy. Confidentiality protects participants; secrecy protects the process from scrutiny and destroys trust.
• Handling a POSH matter in the general channel. This is a compliance failure, not a procedural preference.
• No written outcome. A verbal "it's been handled" is not a resolution and leaves no record.
• Ignoring contract and field staff. They often have the most grievances and the least access.
• Forgetting the follow-up. The remedy that was recommended and never implemented is a recurring finding in internal audits.
• A committee that never meets. Set a fixed quarterly cadence even when there are no cases, and use the meeting to review analytics.
• Copying a multinational policy wholesale. A twelve-stage process designed for a 40,000-person company will simply not run in a 90-person startup.

A 30-day implementation plan

You do not need a quarter-long project. Thirty days is enough to move from informal handling to a working mechanism.

Days 1–5: Assess and decide. - Map what happens today: where do complaints actually go, and who handles them? - Pull the last twelve months of exit interviews and any complaint emails you can find; categorise them roughly to see your real hotspots. - Confirm with your advisor which statutory requirements apply to your entity, headcount, and states — grievance machinery, standing orders, POSH, and state Shops and Establishments rules. - Decide the committee model, the number of stages, and the SLAs you can genuinely honour.

Days 6–12: Draft. - Write the policy using the template skeleton above. Keep it under ten pages. - Build the routing table and the escalation table first; the rest of the policy follows from them. - Draft the annexures: grievance form, acknowledgement, inquiry notice, report format, outcome letter, register. - Get a legal review, and a plain-language review by someone outside HR.

Days 13–18: Constitute and configure. - Appoint the grievance officer, the committee members, and the member secretary in writing. Run an election or nomination for employee representatives. - Confirm the appellate authority and the external member or investigator for conflicted cases. - Configure the mechanism in your HRMS: a grievance ticket category, confidential visibility, stage-wise SLAs, auto-escalation on breach, and a dashboard. - Set up the anonymous channel and decide who monitors it and how often.

Days 19–24: Train. - Half-day workshop for managers on recognising, routing, logging, and escalating. - Deeper session for the committee and grievance officer on inquiry technique, note-taking, and report writing. - Brief the leadership team on what the analytics will show and what they must not do with the information.

Days 25–30: Launch and communicate. - Announce in an all-hands with a founder or CEO in the room. Sponsorship visibility matters. - Publish in all workplace languages, on notice boards and in the HRMS. - Add the policy to induction and to the employee handbook acknowledgement. - Run a pilot: process any live issues through the new ladder and fix friction before month two. - Diarise the first quarterly analytics review and the first annual policy review.

FAQ: grievance redressal policy questions Indian employers ask

Is a grievance redressal policy legally mandatory for my company? It depends on your establishment type, headcount, and state. India's industrial relations framework contemplates internal grievance machinery in establishments above a specified size, and separate statutory mechanisms exist under the POSH Act and other laws. Rather than guessing, ask your labour-law advisor to confirm current applicability and thresholds for your entity. Practically, though, even companies below every threshold benefit from having one — the cost is a week of work and the downside of not having one is disproportionate.

How is a grievance redressal committee different from a POSH Internal Committee? They are separate bodies with separate mandates. The Internal Committee is constituted under the POSH Act specifically for sexual harassment complaints, must include an external member, and follows a statutory process and timeline. A grievance redressal committee handles ordinary workplace grievances — pay, conditions, conduct, fairness. Members may overlap, but the processes, files, and records must not be merged.

Can employees raise grievances anonymously? Yes, and you should allow it. But be transparent that anonymity limits what can be done: an anonymous complaint with verifiable specifics can be investigated, while a vague one usually leads to a broader climate review instead of an adjudication. Offering a "confidential but not anonymous" option — where identity is known only to the grievance officer — often surfaces more actionable complaints than pure anonymity.

What if the grievance is against the founder or CEO? Your policy must name a route that does not run through the respondent: an independent external investigator, an external committee member, or a designated independent director or board committee. The respondent recuses from every decision touching the complainant during the process. If you cannot answer this question credibly, employees will not use your channel for anything serious.

How long should a grievance take to resolve? Set your own numeric SLAs and publish them. A common, achievable structure is acknowledgement in one to two working days, informal resolution in five to seven, formal review in ten to fifteen, and a committee inquiry in twenty to thirty. Where a statute prescribes a timeline, that governs. What matters more than the specific numbers is that you meet the ones you publish and communicate proactively when you cannot.

Should we keep grievance records, and for how long? Yes — the record is your evidence that a fair process was followed. Keep the full case file, restricted to those who need access, for a defined retention period aligned with your employment-records schedule and the limitation periods relevant to employment claims. Set the specific period with your advisor, apply it consistently, and dispose of files securely afterwards.

Our grievance count went up after we launched the policy. Is that bad? Almost always the opposite. A rise after launch means people have found a channel they trust and are using it instead of leaving quietly. The metrics to watch instead are cycle time, escalation rate, upheld rate, repeat hotspots, and attrition among complainants. Persistently near-zero volume in a workforce of any size is the number that should worry you.

Can an employee go to a labour authority or court without using our internal process first? Generally yes — internal mechanisms supplement statutory rights rather than replace them, and any policy clause suggesting otherwise is unlikely to hold. State plainly in your policy that statutory remedies remain available. Counter-intuitively, saying so increases the number of people who use your internal route first, because it signals that the process is offered in good faith rather than as a trap.

Bringing it together

A grievance redressal policy is not a compliance artefact you file and forget. It is an operating system for fairness: clear definitions so people know what belongs where, accessible intake so everyone can be heard, honest timelines so nobody waits in silence, a disciplined inquiry so decisions are defensible, real remedies so outcomes mean something, and analytics so patterns get fixed instead of repeating. The labour-code consolidation has given Indian employers a good reason to formalise this now — but the better reason is that a company where problems surface early is simply a better-run company.

Start small if you must. A one-page routing table, a named grievance officer, a logged register, and four honest SLAs will outperform a beautifully drafted twenty-page policy that nobody implements. Then build the committee, the training, and the dashboard over the following quarter.

If you would like the mechanics handled for you, CozyHR gives Indian SMBs a place to run all of this in one system — a confidential grievance intake channel, stage-wise SLAs with automatic escalation, restricted-access case files, and a dashboard that shows volume, cycle time, and hotspots by team and location, sitting alongside payroll, leave, and attendance data that most grievances turn out to be about. Explore CozyHR and see how quickly a formal grievance mechanism can go live for your team.

This article is general guidance and not legal advice. Applicability, thresholds, timelines, and state rules vary — please confirm your specific obligations with a qualified employment or labour-law advisor before finalising your policy.