Employee Grievance Redressal Committee: A Setup Guide

Employee Grievance Redressal Committee: A Setup Guide

Most Indian SMBs discover they need an employee grievance redressal committee at exactly the wrong moment — after a shop-floor argument turns into a work stoppage, after an ex-employee's lawyer sends a notice, or after a labour inspector asks a simple question the HR head cannot answer: "Who hears complaints here, and where is the register?" A grievance mechanism is one of those things that costs very little to build in a calm quarter and costs a great deal to improvise in a bad one.

This guide is written for HR managers, founders, plant HR leads and compliance owners at Indian SMBs and mid-size companies who want a working mechanism, not a policy PDF nobody opens. It covers what the committee is, how to constitute it, how to run cases stage by stage, what a defensible file looks like, and how to read the data the process throws off.

A plain note before we start: this is general guidance drawn from HR and IR practice, not legal advice. Thresholds, timelines and procedural requirements vary by state, by establishment type and by what has actually been notified. Verify the current rules applicable to you, and take qualified legal advice on any contested or high-stakes matter.

---

What an Employee Grievance Redressal Committee Actually Is

A grievance redressal committee is a standing internal body that hears individual employee complaints about the terms and conditions of their employment, applies the company's own rules and applicable law to the facts, and issues a reasoned decision within a stated time.

Three words in that sentence carry the weight.

Standing. It exists before the complaint arrives. You do not assemble a committee in response to a specific case — that invites accusations that the panel was picked to produce a particular result. Members are named in advance, for a fixed tenure, and the same panel handles whatever comes.

Individual. A grievance mechanism deals with a complaint by a person (or a small identifiable set of people) about how a rule was applied to them. It is not the forum for collective bargaining over what the rule should be. That distinction matters more than most HR teams realise, and we come back to it.

Reasoned. The output is not "we looked into it and closed the matter." It is a short written finding: what was alleged, what was checked, what was concluded, what happens next, and how to appeal. Reasoned outcomes are what make a mechanism credible internally and defensible externally.

Grievance versus complaint versus dispute

Practitioners use these words loosely; a policy cannot afford to.

• A concern is raised informally with a manager and resolved on the spot. Most workplace friction lives here and should stay here.
• A grievance is a concern that has been formally lodged because it was not resolved informally, or because the employee wants it on record.
• A dispute is a grievance that has exhausted internal stages and moved into a statutory or contractual forum outside the company.

A healthy organisation has a wide base of concerns, a modest layer of grievances and very few disputes. If your dispute count is high relative to your grievance count, the internal mechanism is not doing its job — people are skipping it because they do not trust it.

Why the topic is live again

For decades, the requirement for an internal grievance body in India sat inside older industrial legislation and applied mainly to factories and larger industrial establishments. Plenty of service-sector companies, IT firms and mid-size businesses treated it as somebody else's compliance problem.

That posture is getting harder to hold. India's consolidation of labour legislation into a set of codes — including the Industrial Relations Code — carries forward and, in the drafting, sharpens the expectation that establishments above a specified headcount will maintain a grievance redressal mechanism with a defined shape. At a principled level, the design contemplated looks like this:

• A committee at the establishment level, applicable once the establishment crosses a stated employee threshold.
• Representation from both the employer side and the worker side, in balance rather than an employer-only panel.
• Adequate representation of women on the committee, proportionate to the workforce.
• A bounded timeline for disposing of a grievance once it is received.
• An appeal or escalation route if the aggrieved employee is dissatisfied with the committee's decision, including onward routes outside the company.
• A cap on committee size so the body stays workable.

Read that as the architecture, not the specification. The exact headcount threshold, the exact number of members, the exact number of days for disposal, the exact appeal route and the record-keeping formats depend on the central rules and the state rules as notified, and on how your establishment is classified. States frame their own rules under the codes, and implementation has been staggered. Check the current position for your state and establishment type before you fix numbers in your policy. Where your existing standing orders, settlement agreements or state shops-and-establishments rules already prescribe something, those obligations continue to bind you until validly superseded.

The practical takeaway for an SMB: build the mechanism now in a shape that satisfies the architecture, and leave the specific numbers — threshold, panel size, day counts — as configurable parameters you can adjust when the applicable rules are confirmed. That is a far easier retrofit than building from zero under time pressure.

Why it is worth doing even where not strictly required

Set compliance aside for a moment. A functioning grievance mechanism does four things for a business.

It surfaces problems while they are small. A shift-allowance miscalculation caught as one grievance in March is an adjustment. The same error surfacing in November as forty employees' back-claims is a provision, a morale problem and possibly a conciliation meeting.

It reduces the attractiveness of external escalation. People go outside when inside does not work. Every credible internal resolution is a matter that did not become a legal notice.

It creates evidence of good faith. In any later proceeding, an organisation that can show it received a complaint, investigated it, heard the person and gave reasons is in a materially different position from one that can show nothing.

It generates management data. Grievance patterns are the cheapest diagnostic you will ever get on supervisor quality, payroll accuracy and site-level culture.

---

Which Forum Handles What: Grievance Is Not a Catch-All

The single most common design failure is a grievance channel that becomes the drain for every kind of workplace problem. Workplace complaints are not one species, and treating them as one is where most mechanisms go wrong. Harassment complaints, whistleblower disclosures, disciplinary charges and union demands each have their own logic, their own decision-makers and — in some cases — their own statutory machinery. Routing them all through one committee is not efficiency; it is a compliance risk and usually produces a worse outcome for everyone.

Your policy needs an explicit routing rule, and your intake needs to apply it on day one.

Grievance versus POSH complaint

A complaint of sexual harassment at the workplace has a dedicated statutory route in India through an Internal Committee constituted under the sexual harassment legislation, with its own presiding officer requirements, external member requirement, procedure, timelines and confidentiality obligations.

The grievance committee must not hear it, and must not "look into it first." If a matter that lands in the grievance channel discloses sexual harassment, the correct action is immediate, minimal-handling transfer to the Internal Committee, with the grievance case closed as "referred" and the substantive record moving to the IC. Do not investigate, do not interview the parties, do not circulate the complaint. Every additional person who reads it is a confidentiality problem you have created.

Train your intake handlers to recognise this. The complainant will rarely use the statutory vocabulary; they will say a supervisor is "behaving badly" or "making comments." Intake staff need enough training to ask one careful clarifying question and route correctly.

Grievance versus disciplinary matter

The direction of travel distinguishes them. A grievance flows upward — an employee complains about the organisation, a manager, a decision, a condition. A disciplinary matter flows downward — the organisation alleges misconduct by an employee and may impose a penalty.

They use different machinery. Discipline runs through charge sheet, explanation, domestic enquiry where warranted, enquiry officer, findings and disciplinary authority — governed by your standing orders or service rules. The grievance committee is not a disciplinary authority and should not purport to punish anyone.

The overlap is real and needs a rule. If a grievance investigation uncovers apparent misconduct by a manager, the committee's job is to record the finding on the grievance and refer the misconduct question into the disciplinary process. The complainant is told the grievance was upheld and that appropriate action is being taken — not the details of another employee's disciplinary proceedings.

The reverse pattern deserves suspicion. An employee who is under a disciplinary cloud and suddenly files a grievance against the investigating manager may have a genuine complaint, or may be building a retaliation narrative. Both processes continue independently; neither is paused because of the other; and the grievance is judged on its own facts. Document the sequencing carefully.

Grievance versus whistleblower disclosure

A grievance is about harm to the complainant. A whistleblower disclosure is about wrongdoing affecting the organisation or the public — fraud, bribery, falsified records, safety cover-ups, regulatory breach — where the discloser may have no personal stake.

These need separate channels because the handling requirements differ. Whistleblower matters typically need stronger anonymity, may require the complainant to be shielded from local management entirely, often route to audit committee or board level, and frequently need forensic rather than HR investigation. A vendor-kickback allegation should not be sitting in an HR case queue that the local plant head can see.

Keep the channels separate at intake and let each cross-refer.

Grievance versus performance dispute

Disagreement with a rating, a rating-linked increment, or a PIP is common and needs a firm boundary. The general rule: process complaints are grievances; judgment complaints are not.

If the employee alleges the appraisal process was not followed — no review conversation happened, the rating was changed after the discussion without explanation, the moderation ignored a documented achievement, the rater was not their actual supervisor — that is a legitimate grievance about process integrity.

If the employee simply believes they deserved a 4 and got a 3, the grievance committee is not an appellate performance rater. Route it to the performance-review appeal mechanism if you have one, or to the skip-level manager and HR business partner if you do not.

Say this explicitly in the policy. Ambiguity here floods the committee with cases it cannot usefully decide, and the resulting "no action" outcomes teach the workforce the mechanism is useless.

Grievance versus union demand

An individual complaint about non-payment of an agreed shift allowance is a grievance. A demand that the shift allowance rate be increased across the plant is a collective bargaining demand, and belongs in the industrial relations channel — works committee, union negotiation, long-term settlement discussions, or the conciliation machinery.

The line blurs when a union raises what is formally an individual case, or when many employees file materially identical grievances in the same week. Handle it this way: decide each individual case on its merits through the grievance process, and simultaneously flag the pattern into the IR channel as a policy issue. Do not refuse to hear an individual grievance because a union is involved, and do not let the grievance committee start negotiating rates.

Where your establishment has a recognised union and a settlement or standing orders that already prescribe a grievance procedure, that procedure governs. Your policy should sit consistently with it, not compete with it.

Routing table

Print a version of this table. Give it to every intake handler and every HR generalist. Most routing errors happen in the first four hours of a case, and they are expensive to unwind.

---

Designing the Grievance Policy

The committee cannot function without a policy that tells it what it is deciding and how. A grievance policy in India has to do two jobs at once: satisfy whatever the applicable rules require for your establishment, and give ordinary supervisors a usable rulebook for handling workplace complaints. Keep the document short — six to ten pages in plain language, translated into the languages your workforce actually reads.

Scope and coverage

State precisely who is covered. Options to consider and decide explicitly:

• Permanent employees — always covered.
• Employees on probation — cover them; excluding probationers creates a silent class of people with no voice, which is where problems incubate.
• Fixed-term employees — cover them.
• Trainees and apprentices — cover them, noting any separate statutory arrangements that apply.
• Contract workmen — this is a judgment call with legal consequences. Many establishments allow contract workers to raise grievances about site-level conditions (canteen, transport, safety, facilities, treatment by principal-employer supervisors) while directing employment-terms grievances (wages, PF) to their own employer, the contractor. Whatever you decide, write it down, brief the contractor, and take advice on how your arrangement interacts with contract labour obligations.
• Ex-employees — allow grievances relating to the employment period or separation for a defined window after exit, typically tied to full-and-final settlement. This is where a great many disputes originate and where the cost of not listening is highest.
• Interns, consultants, gig and platform workers — decide and state it, rather than leaving the question to be answered in a crisis.

Also state geographic and entity scope: which legal entities, which sites, which states.

Definitions

Define at minimum: grievance, aggrieved employee, working day, acknowledgement, committee, chairperson, appellate authority, retaliation, and confidential information. Ambiguity in these definitions is where timeline arguments start. "Working day" in particular — a plant running six days with rotating shifts and a corporate office on five days need one clear rule.

What can and cannot be raised

List inclusions and exclusions concretely. A workable exclusion list usually covers:

• Matters within the exclusive jurisdiction of the POSH Internal Committee.
• Matters under active disciplinary proceedings, where the disciplinary process provides the hearing.
• Business decisions as such — restructuring, site closure, policy design, promotion decisions properly made — as distinct from complaints that a decision was applied to the individual in breach of policy.
• Grievances already decided on the same facts, unless new material evidence has emerged.
• Anything already before a court, tribunal or statutory authority on the same facts, where continuing internally could prejudice the position. Take legal advice case by case here rather than applying a blanket bar.

Be careful with exclusion lists. They should prevent forum-shopping, not become a menu of ways to refuse to listen. Every exclusion should name where the matter goes instead.

Who can raise, and how far back

State whether a grievance must be raised by the affected employee personally, or whether a colleague, union representative or family member may raise it on their behalf. Practice varies; the safer position is to accept representation but require the affected employee's confirmation before proceeding substantively, except where the employee is incapacitated.

Set a reasonable time limit for raising a grievance after the triggering event — many companies use somewhere between thirty and ninety days — with a written discretion for the chairperson to admit a late grievance for good reason. A rigid bar produces injustice in exactly the cases where the employee was too intimidated to speak up early.

Anonymous complaints

This deserves a considered position rather than a reflex.

Anonymous grievances are hard to investigate: you cannot ask clarifying questions, you cannot assess the complainant's credibility, and you cannot give the respondent a fair chance to answer an accusation whose source is unknown. But refusing to accept them tells frightened employees the channel is not for them.

A workable middle position:

1. Accept anonymous submissions through a defined channel.
2. Act on them proportionately to their specificity. "Something is wrong in Stores" cannot be investigated. "Overtime hours for the B-shift in Stores were reduced in the register on 12, 14 and 19 of last month" can be, because it points at verifiable records.
3. Prefer record-based verification over interviews where the complaint is anonymous, so you can test the allegation without a witch-hunt.
4. Offer confidential-but-not-anonymous as an alternative and explain the difference clearly: identity known to the committee only, not disclosed to the respondent or to line management except as strictly required for fairness. Many people who reach for anonymity actually want confidentiality plus a credible non-retaliation guarantee.
5. Log every anonymous complaint in the case system even if the outcome is "insufficient information to proceed." Three vague anonymous complaints about the same department in six months is itself a finding.

Non-retaliation

The mechanism fails without a retaliation commitment people believe. Write it strongly and operationally:

• No adverse action — transfer, shift change, rating change, denial of overtime, exclusion from training, termination — against a complainant, witness or committee member because of participation in a grievance.
• Retaliation is itself misconduct, actionable through the disciplinary process independently of whether the underlying grievance was upheld.
• A defined watch period after closure — commonly three to six months — during which HR reviews any adverse action affecting the complainant before it is executed.
• A named person the complainant can approach if they believe retaliation has begun, distinct from their line management.

The watch period is the part that converts a promise into a control. Configure it so that a rating change, transfer or exit for a recent complainant triggers an HR review flag rather than sailing through.

Confidentiality

State who sees what. A working default:

• Full case file: committee members and the case administrator only.
• Respondent: the substance of the allegation in enough detail to answer it, plus the evidence relied on against them.
• Complainant's manager: informed only to the extent necessary for the process, and specifically not given complaint contents where the manager is implicated.
• Senior management: aggregate reporting; individual case details only where the decision requires their authority.
• Records stored access-controlled, not on shared drives or in personal mailboxes.

Add the honest caveat: confidentiality is maintained to the fullest extent consistent with conducting a fair investigation and meeting legal obligations. Never promise absolute secrecy you cannot deliver — a promise broken at the worst moment destroys the channel's credibility permanently.

Conflict of interest and recusal

Write a bright-line recusal rule. A committee member steps aside where they:

• are the person complained against, or their direct reporting line in either direction;
• were the decision-maker on the matter under complaint;
• have a family, financial or close personal relationship with either party;
• were a witness to the events;
• have already expressed a view on the merits.

State how recusal is invoked (self-declaration at case allocation, plus a party's right to request it with reasons), who decides a contested recusal request (the chairperson; the appellate authority if the chair is the subject), and how the alternate member steps in. Record every recusal in the case file — an unrecorded recusal is worth nothing when the fairness of the panel is challenged later.

Policy governance

Name a policy owner, a review cycle (annual, plus on any change in applicable law), a version number and an effective date. Capture employee acknowledgement at onboarding and on each material revision. When someone later says "I never knew there was a process," a timestamped acknowledgement record settles it.

---

Constituting the Committee

Size and balance

Keep it small enough to convene. Practical experience across mid-size Indian establishments points to a panel of four to eight members, with equal numbers from the employer side and the worker side, plus a chairperson arrangement that does not tilt the balance permanently.

The statutory design contemplated for establishments above the applicable threshold expects employer and worker representation in balance, a cap on total size, and adequate representation of women. Confirm the specific numbers against the rules notified for your state and establishment type, and where your standing orders or a settlement already prescribe a composition, follow that.

Employer representatives

Choose people with authority to implement an outcome, not just to opine. A typical mix:

• An HR lead who is not the day-to-day HR contact for the site in question, so they are not adjudicating their own advice.
• A functional or operations head from a department other than the one under complaint.
• A finance or payroll representative — invaluable for the large share of grievances that turn on calculation rather than conduct.

Avoid stacking the panel with the most senior people available. Very senior members attend erratically, and quorum failure is the number one cause of missed timelines.

Worker representatives

This is where most SMBs get nervous and where the mechanism's credibility is actually decided.

If a recognised union exists, worker representatives are usually nominated through it, per the settlement or standing orders. Where there is no union, options include election by the workforce, nomination by the works committee, or selection from a pool of volunteers with a rotation rule. Election is worth the administrative effort — a worker representative the workforce chose is trusted in a way that an HR-picked representative never will be.

Protect worker representatives explicitly: their committee role must not affect their appraisal, their shift allocation or their overtime opportunity. Give them paid time to prepare and attend. A representative who has to make up hearing hours after their shift will stop attending, and their absence will be read — correctly — as a signal.

Gender representation

Ensure adequate representation of women, proportionate to your workforce composition. Beyond the legal expectation, this is practical: a panel of five men hearing a woman's complaint about her supervisor will get less of the truth than a mixed panel, regardless of how fair-minded its members are.

In establishments with very few women, this takes deliberate effort — you may need to draw a member from another site or from a corporate function. Do it rather than declaring it impossible.

Chairperson

The chair runs the process, not the outcome. Responsibilities: convening, ensuring both sides are heard, keeping the record, enforcing timelines, drafting or approving the reasoned order, and signing off the closure.

Two patterns work. Neutral standing chair — a senior person outside the line of the departments most likely to feature in complaints (a plant head at a different site, a compliance head, a legal counsel), which is simple and consistent. Rotating chair — alternating between an employer-side and worker-side chair by case or by period, which signals balance strongly but requires more training investment.

Whichever you pick, name a deputy chair for cases where the chair recuses.

Quorum, tenure and alternates

• Quorum: require a minimum attendance that preserves both-side representation — a hearing with three employer members and no worker representative is not a quorum, whatever the headcount rule says. State that explicitly.
• Tenure: two years is a reasonable default. Long enough to build competence, short enough to prevent capture. Stagger member exits so the whole panel does not turn over at once.
• Alternates: name at least one alternate per member category at constitution. Recusals and travel are routine, and scrambling for a substitute is how deadlines slip.
• Decision rule: majority, with the chair holding a casting vote in a tie. Record dissent in the file. A written dissent is not a weakness; it is evidence the panel actually deliberated.

Multi-location and multi-state structures

A single central committee works to roughly one site or a few hundred employees. Beyond that, the travel and context problems get severe.

The pattern that works for growing companies is three tiers:

1. Site-level committee at each establishment above the applicable threshold, handling most cases with local context and local language.
2. Regional or corporate committee hearing appeals from site committees, and hearing at first instance any case involving a site head or where the whole site committee is conflicted.
3. Appellate authority — a named senior executive or a small panel, distinct from anyone who decided at earlier stages.

Multi-state operations add a wrinkle: rules under the labour codes are framed at state level, so composition requirements, registers and formats may differ between your Pune plant and your Hosur plant. Maintain a state matrix listing, for each site, the applicable rules, committee composition, prescribed timelines, register formats and display requirements. Keep it current and dated, and revisit it whenever notifications change. Build the policy so state-specific parameters are variables, and the common process is the same everywhere.

Composition and roles table

Publish the constitution — names, designations, contact routes, tenure dates — on the notice board and the HR portal. A committee nobody can name is a committee nobody will use.

---

Intake Channels: Many Doors, One Log

Offer several doors

Different people report differently. A supervisor's favourite worker will speak to the shift in-charge; a frightened contract worker will not. Offer at least:

• Line manager, for the many issues that should be resolved informally.
• Skip-level manager, for issues involving the immediate manager.
• HR portal or app form, structured and timestamped — the preferred channel for anyone with device access.
• Dedicated email address, monitored by two named people so a single absence does not stall intake.
• Physical drop box at plants and sites, in a location that is not under a supervisor's line of sight, opened on a stated schedule by two people together.
• Helpline or WhatsApp number, for workers who do not use email.
• Walk-in to HR, with the handler required to reduce the complaint to writing and read it back to the complainant.
• Union representative, where applicable, as a recognised route.

Adapt to your workforce. A drop box in a corporate office nobody uses is theatre; in a three-shift plant it may be your highest-volume channel.

One log behind all doors

Here is the operational rule that matters most: however a grievance arrives, it gets logged into one case register within a defined window — ideally the same working day.

A single log gives you:

• A reliable clock. Timelines run from receipt. If receipt is a WhatsApp message on a supervisor's personal phone, you cannot prove when the clock started or that you met your commitment.
• No lost cases. Email intake fails predictably — the handler goes on leave, the thread gets buried, the case is remembered three weeks later. Cases in a log with an owner and a due date do not vanish.
• Real analytics. You cannot count what you did not record. Cases scattered across inboxes cannot produce the manager-level and site-level patterns that make the whole exercise worth running.
• Defensibility. In a later challenge, an extractable, tamper-evident case record with a full action trail is worth more than any number of recollections.
• Access control. A case system restricts who can open a file. An email thread is forwarded by whoever holds it.

Whoever receives a grievance — supervisor, HR generalist, security guard emptying the drop box — has one obligation: get it into the log. Train for that, and audit it. Spot-check by asking a sample of employees whether they raised anything in the last quarter and cross-checking against the register.

Intake capture fields

Standardise what gets recorded at intake:

• Case ID (auto-generated, non-sequential per site if you want to avoid inference about volumes)
• Date and time of receipt; channel of receipt
• Complainant identity, employee code, location, department, shift (or "anonymous")
• Person(s) or decision complained against
• Category and sub-category (from a fixed taxonomy)
• Description in the complainant's own words, plus the language it was given in
• Relief sought
• Documents attached
• Whether the complainant sought informal resolution first, and what happened
• Immediate routing decision (grievance / POSH referral / whistleblower referral / disciplinary / performance appeal / IR)
• Assigned owner and due date

Fix the taxonomy at intake. Free-text categories make analytics worthless. Fifteen to twenty-five categories is usually right — enough granularity to be actionable, few enough that handlers pick consistently.

---

The Grievance Handling Process, Step by Step

What follows is a working process with indicative internal service levels. Every day-count below is a company-chosen internal SLA, not a statutory timeline. The applicable law and rules for your establishment may prescribe their own outer limits for disposal and appeal; where they do, your internal SLA must sit inside them. Verify the notified position and adjust.

Stage 0: Informal resolution

Encourage employees to raise the issue with their manager first, and require managers to attempt resolution within two to three working days.

Two guardrails. First, informal resolution is encouraged, not mandatory — an employee complaining about their manager cannot be forced to go to that manager. Second, log the informal attempt anyway, in a lightweight form. Informal-stage data tells you which managers resolve issues and which ones generate escalations.

Stage 1: Intake and acknowledgement

Target: same working day, at most one working day.

1. Log the grievance with a case ID.
2. Apply the routing rule. Refer out immediately if it belongs to POSH, whistleblower, disciplinary, performance appeal or IR.
3. Send a written acknowledgement — email, portal notification, or a stamped paper receipt where that is what the person can use. It states the case ID, the summary as understood, the assigned owner, the expected timeline and the confidentiality and non-retaliation commitments.
4. Assess for urgency. Anything involving safety risk, threat of violence, an ongoing act, or vulnerability of the complainant gets same-day interim protection — separation of parties, shift change for the respondent not the complainant, suspension of the disputed action — pending investigation.
5. Check for conflicts and allocate the panel, applying recusals.

Acknowledgement matters more than it looks. Most complainants have no idea whether their complaint reached anyone. A receipt with a case ID converts anxiety into a tracked expectation, and it dramatically reduces the "nobody responded so I escalated outside" pattern.

Stage 2: Preliminary assessment and scoping

Target: within two to three working days of acknowledgement.

The case owner establishes:

• Is the complaint admissible under the policy? If not, which forum takes it?
• Is it within the time limit, or should the chair admit it late?
• What precisely is alleged? Reduce it to numbered allegations. Vague complaints must be sharpened here, with the complainant's input, or the whole process wanders.
• What would resolve it? Sometimes the relief sought is straightforward and the case is really an error correction.
• What evidence exists, and where? Attendance logs, biometric records, payroll runs, rosters, approval trails, CCTV (subject to retention limits and privacy rules), emails, WhatsApp screenshots.
• Is this a record-check case or a conduct case? Record-check cases — allowance calculations, leave balances, deduction disputes — can often be closed in days by pulling the data. Conduct cases need interviews and take longer. Separating the two early is the single biggest driver of median closure time.

Preserve evidence now. Send a written hold notice to whoever controls relevant records, before CCTV overwrites, biometric logs roll off, or a register is "updated."

Stage 3: Fact-finding

Target: seven to twelve working days for standard cases; extendable with written reasons and notice to the complainant.

Principles that keep an investigation clean:

Start with documents. Records do not have a motive. Pull the payroll run, the roster, the punch data, the approval chain. In a large share of SMB grievances, the documents settle the matter and no interview is needed.

Interview the complainant properly. Not a two-minute corridor conversation. Set aside time, in a private room, in their language, with an interpreter if needed. Take notes, read them back, get a signature or a recorded confirmation of accuracy.

Give the respondent the substance. The person complained against must know what is alleged in enough detail to respond — dates, incidents, the specific decision. "Somebody has complained about your behaviour" is not notice; it is an invitation to a defective process.

Interview witnesses individually. Never together. Never with a supervisor in the room. Ask what they observed, not what they concluded.

Distinguish evidence from inference. The file should separate "the roster shows X worked the night shift on these dates" from "the committee therefore concludes the allowance was payable."

Apply the balance of probabilities. Internal grievance findings are civil-standard: more likely than not. You are not applying a criminal standard. Say so in the policy so committees do not paralyse themselves waiting for certainty.

Watch the clock and communicate. If the target will be missed, tell the complainant before the deadline passes, with a reason and a new date. Silence at the deadline is what pushes people to external forums.

Stage 4: Hearing

Target: within three to five working days of fact-finding completing.

For anything beyond a simple record correction, convene a hearing.

1. Issue written notice at least two to three working days ahead: date, time, place, the allegations, the documents relied on, and the right to be accompanied.
2. Check quorum, including both-side representation. If quorum fails, reschedule immediately — do not proceed with a rump panel.
3. Chair opens, states the scope, confirms confidentiality expectations, confirms no member has an undeclared conflict.
4. Complainant presents; committee asks questions.
5. Respondent (where there is one) responds to the specific allegations and answers questions.
6. Investigator presents documentary findings.
7. Both parties get a chance to add anything final.
8. Parties leave; committee deliberates in private.
9. Secretary records attendance, the sequence, key statements, and the decision, including any dissent.

Decide in advance whether the parties are heard together or separately. Separate hearings are usually safer where there is a power imbalance or fear of confrontation, provided each party still gets the substance of what the other said. Confrontation is not required by fairness; knowing the case against you is.

Stage 5: Decision and communication

Target: within three to five working days of the hearing.

The written outcome contains:

• Case ID, dates, panel members present
• The allegations as framed
• What was examined
• Findings on each allegation: upheld, partly upheld, not upheld, or not established on available evidence
• Brief reasons — three to six sentences per allegation is usually enough
• The remedy and who owns it, with a date
• The appeal route and the window to use it
• The non-retaliation reminder and the contact if retaliation is suspected

Communicate to the complainant in a language they read comfortably, and where literacy is a constraint, have it read out by the case administrator with a witness and record that it was done.

Tell the respondent the outcome affecting them. Tell the implementing manager only what they need to implement.

Where a grievance is not upheld, the reasons matter more, not less. A complainant who loses but can see the panel actually engaged with their case will usually accept it. One who receives "your grievance has been closed" will escalate.

Stage 6: Appeal

Target: appeal filed within seven to ten working days of receiving the outcome; decided within ten to fifteen working days of filing.

Design points:

• The appellate authority must not have decided at first instance. This is the whole point of an appeal.
• Appeal grounds should be stated: procedural unfairness, material evidence not considered, new evidence, or a decision no reasonable panel could reach on the material. Open-ended re-hearing of everything is expensive and slow.
• The appellate authority can uphold, reverse, vary the remedy, or remit for fresh consideration with directions.
• The appeal decision is written and reasoned, like the first-instance decision.
• State clearly what happens after internal appeal is exhausted, including the availability of external statutory routes. Verify the applicable external route for your establishment and state; do not paraphrase a specific mechanism you have not confirmed. Employees have external remedies regardless of what your policy says, and a policy that implies otherwise damages your credibility and may be read against you.

Stage 7: Implementation and closure

• Assign a named owner and a due date to every remedy — a payroll correction, a roster change, a manager coaching plan, a policy amendment.
• Verify implementation. "Payroll to correct in next cycle" is a promise; the closure evidence is the payslip.
• Confirm to the complainant that the remedy has been executed.
• Close the case only after implementation is verified, not at the point of decision. Companies that close at decision have a hidden backlog of unexecuted remedies, and every one of them is a repeat grievance waiting to happen.
• Start the retaliation watch period.
• Capture a root-cause tag — supervisor capability, policy gap, system error, communication failure, individual conduct, genuine misunderstanding. This field is what makes the analytics useful later.
• Optionally, a short satisfaction check on process (not outcome): were you heard, were you treated respectfully, was the timeline met.

Stage-wise escalation matrix

Note again: every duration above is your own choice. Where notified rules prescribe an outer limit for disposal or appeal, that limit governs, and your internal SLAs should be set comfortably inside it.

---

Natural Justice, in Plain Language

Committees do not need to be lawyers, but they must understand four ideas. Teach them in this form.

Tell people what the case is

Nobody can answer an accusation they have not been told. The respondent needs the substance of the allegation — what is said to have happened, roughly when, and in relation to what. The complainant needs to know what evidence is being weighed against their account. Vagueness is not kindness; it is a procedural defect.

Let people have their say

A real opportunity, not a formality: enough time, in a language they speak, in a setting where they can speak freely, with the chance to bring a colleague if the policy allows. If someone cannot attend for a genuine reason, reschedule once before proceeding in their absence — and record why you proceeded.

The decider must not have a stake

A person cannot judge their own decision, their own conduct, or a matter involving someone they are close to. Recusal is not an insult to the member; it is protection for the outcome. A decision by a conflicted panel is vulnerable no matter how correct it is on the facts.

Say why

A conclusion without reasons is indistinguishable from an arbitrary one. Reasons force the panel to test its own logic, they let the appellate authority review properly, and they show the complainant they were actually heard. Short is fine. Absent is not.

Two supporting habits: decide on the material before you — not on corridor gossip, not on the respondent's general reputation, not on what someone mentioned in passing to a panel member — and be consistent with how similar cases were decided before, or explain what makes this one different. Keeping a simple internal precedent note of past decisions by category makes this practical.

---

Documentation: What a Defensible File Contains

Assume every file may one day be read by someone unsympathetic — a tribunal, a regulator, an inspector, opposing counsel, a journalist. Build it accordingly.

A complete file has:

1. The original complaint as submitted, in the original form and language, with a translation if used.
2. Acknowledgement sent, with timestamp.
3. Routing and admissibility note, with reasons if the case was excluded or referred out.
4. Conflict declarations and recusals for every panel member, dated.
5. Panel allocation record.
6. Evidence hold notice and confirmations.
7. Documentary evidence, each item labelled with what it is, where it came from, who pulled it and when.
8. Interview records — who, when, where, present, what was said — confirmed by the interviewee where possible.
9. Notice of hearing to each party, with proof of delivery.
10. Hearing minutes, attendance, and material statements.
11. Deliberation note, including dissent.
12. The written reasoned order, signed and dated.
13. Proof of communication to complainant and respondent.
14. Appeal papers and appeal order, where applicable.
15. Implementation evidence — the corrected payslip, the revised roster, the training completion record.
16. Closure note with root-cause tag.
17. Retaliation watch log for the watch period.

Handling standards that matter:

• Contemporaneous. Notes written the same day. A hearing reconstructed from memory three weeks later reads exactly like what it is.
• Factual and neutral. Record what was said, not what you thought of the person saying it. Descriptors like "aggressive" or "clearly lying" in a file are damaging and rarely necessary.
• Attributed and dated. Every document should answer: who created this, when, from what source.
• Version-controlled. If a note is corrected, show the correction. Silent edits to a case file are the single worst look available in a later challenge.
• Access-controlled. Restricted to the panel and administrator, with an access log.
• Retained deliberately. Not "kept forever on a shared drive," and not deleted the moment the case closes.

Records and retention table

Retention needs a real decision, not a default. Too short, and you cannot defend a claim brought within its limitation period. Too long, and you are holding sensitive personal data with no purpose — which sits badly with data-protection expectations. Set the period with legal input, write it down, and apply it consistently, with an override that suspends deletion whenever a matter is live or reasonably anticipated.

---

Training the Committee

An untrained committee is worse than no committee: it produces defective decisions with the appearance of due process.

What to cover

A one-day foundation for new members, refreshed annually in half a day:

• Scope and routing — the taxonomy table, with worked examples, especially POSH recognition and immediate referral.
• Natural justice in the four plain-language principles above.
• Standard of proof — balance of probabilities, and what that means in practice.
• Interviewing — open questions, avoiding leading, handling distress, handling aggression, working through an interpreter.
• Evidence — what documents to pull for the most common categories, chain of custody basics, limits on CCTV and personal device material.
• Bias — recency, similarity, seniority deference, the assumption that a long-serving supervisor must be right.
• Writing a reasoned order — with two or three model orders, including one where the grievance was not upheld.
• Confidentiality and data handling — what goes in the case system, what never goes on WhatsApp.
• Retaliation — recognising it, and the watch-period control.
• The system — hands-on with the case log, including how to attach evidence and record time.

How to train

Case simulation beats lecture. Run three mock cases: a payroll calculation dispute, a supervisor behaviour complaint, and a case that turns out to be a POSH matter in disguise. Have the panel run each end to end and draft the order, then critique the drafts.

Include worker representatives in the same training as employer representatives, at the same time. Separate training signals a two-tier committee and undermines the balance you built.

Train intake handlers separately and more widely — supervisors, security staff who empty drop boxes, HR generalists, the reception desk. They need less depth but they need the routing rule cold, plus one instruction: log it, do not filter it. Intake handlers deciding which complaints are "worth" logging is a common and corrosive failure.

Keep training records. In a later challenge, evidence that the panel was trained before it decided is worth having.

---

Communicating the Mechanism So It Gets Used

A grievance mechanism nobody uses is not evidence of a happy workplace. It is usually evidence of a channel people do not trust or do not know about. Silence should worry you.

Make it visible

• Notice boards at every site, in the languages of the workforce, with committee names, contact routes and the drop-box location and opening schedule. Refresh when members change — a board listing someone who left last year does real damage.
• Onboarding, with a walk-through, not just an acknowledgement click. Five minutes on day one, and again in the first-month check-in.
• Shift briefings at plants — the highest-reach channel you have for a non-desk workforce.
• HR portal, with the policy, the form, and case status visible to the person who raised it.
• Payslip footer or app banner carrying the helpline number. It costs nothing and reaches everyone monthly.
• Manager cascade, so supervisors present the mechanism as legitimate rather than as an insult to their authority.

Make it credible

Visibility without credibility produces nothing. Three things build credibility:

Publish aggregate outcomes. Once or twice a year, share numbers: cases received, categories, proportion upheld, median closure time, examples of changes made. Anonymised, obviously. Nothing persuades a workforce that the channel works like evidence that complaints were upheld and things changed.

Have leaders name it. When a plant head says in a town hall that a grievance about roster fairness was upheld and the roster was changed, that lands harder than a policy circular.

Enforce non-retaliation visibly at least once. The first time retaliation is identified and acted on, the whole workforce learns what the commitment is worth. The first time it is ignored, they learn that too.

Manage the manager problem

Supervisors often experience the grievance mechanism as a threat — a channel for their people to go over their head. Address it directly:

• Frame grievance volume as a detection metric, not a failure metric, in manager communications and reviews.
• Distinguish clearly between "grievances raised in this team" (often just a function of team size and psychological safety) and "grievances upheld against this manager" (a genuine signal).
• Give managers the informal-resolution stage as their opportunity to resolve well, and recognise those who use it.
• Coach after upheld grievances rather than only punishing. Most supervisor-related grievances stem from capability gaps — nobody taught them how to refuse leave properly — not malice.

A manager population that fears the mechanism will suppress complaints, and suppressed complaints surface later, larger, and outside your control.

---

Grievance Analytics: Reading the Data

Once cases live in one log with a fixed taxonomy, you get a diagnostic instrument. Most companies never use it.

The core measures

Volume by category. Which grievance types dominate? A concentration in pay and allowance categories points at payroll configuration or communication, not at employee unreasonableness.

Volume by location. Normalise per hundred employees. One plant running at four times the group rate has a specific, findable problem. One running at zero probably has a suppression problem.

Volume by manager and by department. Handle carefully — read raw counts alongside team size and tenure. The number that matters is upheld grievances per manager over time.

Repeat themes. Same category, same site, three times in a quarter means the earlier remedies were individual patches on a systemic fault.

Time to closure. Track the median and the tail, by stage. The tail is where trust dies. A median of nine days with three cases open for four months is a worse story than a median of fourteen days with nothing over thirty.

Upheld rate. Watch both extremes. An upheld rate near zero suggests a committee that reflexively defends management, or an intake that filters. A very high rate suggests systemic process failures upstream that should be fixed rather than adjudicated case by case.

Stage distribution. What proportion resolves informally, at committee, on appeal? A high appeal rate points at weak first-instance reasoning.

Channel mix. If everything arrives through one channel, the others are decorative. If the drop box is the only channel that works, people fear being seen.

Repeat complainants and repeat respondents. Both need attention, in different ways.

Withdrawal rate. Complaints withdrawn before decision deserve a quiet look. Genuine resolution is fine. A pattern of withdrawals from one department is a retaliation signal.

From data to root cause

The measures are only worth collecting if something happens. Run a quarterly review with HR, operations and finance:

1. Take the top three categories by volume.
2. For each, read the root-cause tags on the closed cases.
3. Ask whether the fix is a system change (payroll rule configuration, roster tool logic), a policy change (an unclear leave rule), a capability change (supervisor training), or a communication change (people did not know the allowance rule).
4. Assign an owner and a date to the systemic fix, and track it like any other project.
5. Check the next quarter's numbers in that category to see whether the fix worked.

That loop — from individual complaints to a systemic fix to a measurable reduction — is what turns a compliance obligation into a management tool. A committee that resolves fifty allowance grievances beautifully and never asks why fifty arose is doing half the job.

Reporting up

Give the leadership team a one-page quarterly view: volume and trend, category mix, site comparison, median and tail closure times, upheld rate, systemic fixes underway with owners, and any red flags — retaliation cases, missed SLAs, repeat respondents. Where you have a board or audit committee, this belongs in their pack alongside the whistleblower summary.

---

Data Privacy and Confidentiality in Practice

Grievance files hold some of the most sensitive personal data an employer processes: health information, family circumstances, allegations about named individuals, financial details. Handle them accordingly, and expect scrutiny to increase as India's data protection regime matures. Confirm current obligations with your legal or privacy adviser rather than relying on general practice.

Working principles:

Collect only what the case needs. Do not pull a complainant's entire file because they raised a roster complaint. Scope evidence to the allegations.

Restrict access by role, and log it. The site head does not need to read a case about their own site's supervisor. Access logs matter — the ability to show who opened a file is a genuine control.

Separate identity from analytics. Reporting should run on de-identified data. Nobody needs names to see that a site has a roster problem.

Never route sensitive case content through personal channels. No WhatsApp forwarding of complaints, no personal Gmail, no photos of complaint forms on a supervisor's phone. Say this explicitly in the policy and enforce it.

Set retention and honour it. Define the period, suspend deletion when a matter is live, and delete when the period passes.

Be careful with recordings and surveillance. If you record hearings, tell participants and get consent; store the recordings with the same controls as the file. CCTV pulled as evidence should be extracted for the specific window needed, not handed over as a full day's footage.

Handle special categories with extra care. Health, disability, caste, religion, sexual orientation and union membership carry heightened sensitivity. Keep them out of summaries and MIS unless the case genuinely requires them.

Cross-border access. If your HRMS or a group HR team abroad can see case data, understand and document that flow. Take advice on the transfer position.

---

Running the Mechanism in an HRMS Instead of Email

Most SMBs start with email and a spreadsheet. It works for the first few cases and then fails, always in the same ways: the clock is unprovable, cases vanish when someone is on leave, access spreads uncontrollably, analytics are impossible, and the record that gets produced under scrutiny is a forwarded thread with commentary in it.

A case-log approach fixes the structural problems.

What the case log should do

Intake capture from multiple channels into one queue, including a walk-in form the administrator fills in for workers without device access, and an anonymous submission route.

Auto-generated case IDs with a timestamped receipt sent to the complainant.

Fixed-taxonomy categorisation at intake, so analytics are possible.

Routing rules that push POSH, whistleblower and disciplinary matters into their separate restricted workflows rather than the general grievance queue.

Stage-wise workflow matching your process, with owners and due dates per stage, and a visible SLA clock.

Conflict and recusal capture at panel allocation, with the system blocking a member from a case where a declared conflict exists.

Evidence attachment in the case, not in an email thread, with upload metadata preserved.

Role-based access with an audit trail — who opened what, when, what they changed. Immutable action history.

Notice and communication templates for acknowledgement, hearing notice, decision and closure, in the languages you need, generated from case data so nothing is retyped and mis-typed.

Escalation automation — alerts before a due date, escalation after it, and mandatory reason capture for extensions.

Closure gating on implementation evidence, so a case cannot be closed on a promise.

Retaliation watch flags that surface when a rating change, transfer, or exit is initiated for an employee with a recent grievance.

Dashboards on volume, category, site, closure time, upheld rate and stage distribution, exportable and de-identified.

Retention rules that apply the defined period and support legal hold.

Connect it to the rest of HR

The value multiplies when the case log sits alongside the rest of your employee data:

• Payroll integration — a large share of grievances are calculation disputes. Being able to pull the actual payroll run, attendance data and allowance configuration inside the case, rather than requesting a report and waiting three days, transforms closure times.
• Attendance and roster data for shift, overtime and leave grievances.
• Policy acknowledgements, so the file can show what the employee was told and when.
• Committee records — constitution, tenure, training completions — stored where an auditor or inspector can be shown them.
• Manager and org data, so analytics can roll up by reporting line without manual mapping.

Migrating from email

If you are running on email today, migrate deliberately:

1. Freeze new email intake on a stated date; keep the address alive but auto-forwarding into the case queue.
2. Load open cases into the log with their original receipt dates, so timelines stay honest.
3. Archive the closed-case email history into the record store with an index, rather than leaving it in individual mailboxes.
4. Retrain intake handlers on the one obligation: log it.
5. Audit the first quarter — reconcile a sample of employee-reported complaints against the register to test for unlogged cases.

---

Illustrative Scenario: A Shift Allowance Dispute

This scenario is illustrative and fictional. Names, numbers and dates are invented to show the mechanics of the process. It is not a description of any real case, and it does not state what the law requires.

Background

A mid-size auto-components manufacturer runs three shifts at a plant with around 320 workers. Company policy pays a night-shift allowance for shifts starting at or after 22:00. A production associate, "R," works a rotating pattern.

Day 1 — Intake

R drops a handwritten note in the shop-floor drop box: for the previous month, night allowance was paid for six shifts, but he worked nine night shifts. He says he raised it with his shift in-charge twice and was told "the system will correct it."

The box is opened at 09:30 by the HR executive and the elected worker representative together, per schedule. The note is logged the same morning as case GRV-PLT2-0431, category "Pay and allowances — shift allowance," sub-category "non-payment/short payment." R is called to the HR office, the case is read back to him, and he confirms it. He is handed a printed acknowledgement with the case ID, the assigned owner, the expected timeline, and the non-retaliation contact.

Routing check: this is a service-conditions grievance. Not POSH, not whistleblower, not disciplinary. It stays with the grievance committee.

Day 2 — Preliminary assessment

The case owner frames one allegation: three night shifts in the relevant month were worked but not compensated with night allowance.

She classifies it as a record-check case rather than a conduct case, and issues an evidence hold to the time office and payroll for the biometric log, the approved roster, the shift-change register, and the payroll run for the month.

She notes a preliminary risk: R says he raised it twice with the shift in-charge and it was not escalated. If that is right, there is a second issue about the informal stage failing — a supervisor-capability matter, separate from the payment question.

Days 3–6 — Fact-finding

The documents tell a layered story.

• The biometric log shows R present for nine shifts starting at or after 22:00.
• The approved roster shows him on six night shifts. Three shifts were swapped with a colleague mid-month.
• The shift-change register contains the swaps, signed by the shift in-charge — but they were never entered into the roster system.
• The payroll run calculated allowance from the roster system, not from biometric data. So payroll was internally correct and substantively wrong.

The case owner interviews R (fifteen minutes, in Hindi, notes read back and signed) and the shift in-charge, who confirms he approved the swaps, wrote them in the register, and assumed the time office would pick them up. He also concedes R raised the shortfall with him twice and that he did not escalate it, because he expected an automatic correction.

The payroll executive confirms the allowance logic pulls only from the roster system.

The case owner then asks the question that turns a case into an improvement: how many other people were affected? A query on the month's shift-change register against the roster system finds eleven employees with unposted swaps, seven of whom were underpaid allowance.

Day 8 — Hearing

The committee convenes: the chair (a compliance manager from another site, on video), an HR representative, an operations head from Maintenance, a payroll representative, and two elected worker representatives, one of them a woman. Quorum is met, with both-side representation.

No conflicts are declared; the operations head confirms he has no reporting relationship with R or the shift in-charge.

R presents. The case owner tables the biometric log, roster, register and payroll extract. The shift in-charge attends as a witness — not as a respondent, since the grievance is about payment, not his conduct — and confirms the swaps. Committee members ask about the register-to-system posting process. The payroll representative confirms the underpayment can be corrected in the next cycle, and that the eleven-employee list can be verified within three working days.

The committee deliberates privately. The finding is unanimous.

Day 10 — Decision

The written order records:

• Allegation: three night shifts worked but not paid night allowance.
• Finding: upheld. Biometric and shift-change register evidence establishes nine qualifying shifts; the roster system reflected six because approved swaps were not posted. Payroll computed correctly on incorrect input data.
• Remedy: arrears for three shifts in the next payroll cycle, itemised on the payslip so R can verify it. Owner: payroll manager. Due: next payroll run.
• Systemic remedy: payroll allowance logic to reconcile against biometric data where a shift-change entry exists; time office to post shift-change entries within twenty-four hours; the seven other affected employees to be identified and paid arrears without requiring them to file individual grievances. Owner: plant HR head with payroll manager. Due: fifteen working days.
• Supervisor remedy: the shift in-charge to be coached on the escalation obligation — a worker's pay query raised twice must be logged, not left to the system. Owner: production manager. Due: seven working days. Recorded as coaching, not as a disciplinary penalty, since the failure was a process gap rather than misconduct.
• Root cause tag: system error (integration gap), with a secondary tag of supervisor capability.
• Appeal route and window stated. Non-retaliation reminder and contact included.

R receives the order in Hindi, and the case administrator reads it out and records that this was done.

Days 11–25 — Implementation and closure

• Payroll processes the arrears; the payslip is attached to the case as implementation evidence.
• The seven other employees are identified and paid; that action is logged as a linked systemic remedy, referencing GRV-PLT2-0431, so the analytics show one grievance producing eight corrections.
• The integration change is raised as a ticket with the HRMS vendor and tracked to closure.
• Coaching is completed and recorded.
• The case is closed on Day 25 with verified implementation, and the three-month retaliation watch begins on R's record.

What the case produced

One handwritten note in a drop box produced: a corrected payment for the complainant, seven proactive corrections nobody had to ask for, a fixed system integration, a coached supervisor, and a data point in the quarterly review — where "shift allowance" appears as a category with a closed root cause.

It also, quietly, produced eight people who now believe the drop box works. That is the return on the whole mechanism.

The counterfactual

Had the same note been handed to the shift in-charge and forgotten: R raises it a third time and gets nowhere; he mentions it in the canteen; four colleagues discover the same shortfall; a union representative raises it as a collective grievance; the company now faces a claim covering several months across an unknown number of employees, with an argument about whether it was deliberate. The cost difference between those two paths is measured in lakhs and in months of trust.

---

Common Failure Modes

Patterns that show up repeatedly in Indian SMBs and mid-size companies.

The committee that exists only on paper

Named in a policy, never convened, members unaware they are members. Usually surfaces when someone asks for the minutes. Fix: convene at least quarterly even with no cases, review analytics and refresh training, and minute the meeting.

Email as the case system

Cases in inboxes, no clock, no access control, lost cases when someone leaves. Fix: one log, one register, one owner per case.

The intake filter

A supervisor or HR generalist decides which complaints are "real" and logs only those. Destroys analytics and destroys trust when it becomes known — and it always becomes known. Fix: train handlers that logging is mandatory; audit by reconciling employee-reported complaints against the register.

Routing failures

A POSH complaint investigated by the grievance committee. A whistleblower disclosure sent to the manager who is implicated. A performance rating argument occupying the panel for weeks. Fix: the routing table, trained cold, applied at intake.

The conflicted panel

The department head hearing a complaint about their own department. Technically fair-minded people producing procedurally indefensible decisions. Fix: recusal rules, pre-named alternates, recorded declarations.

Decisions without reasons

"Your grievance has been examined and closed." Guarantees escalation. Fix: a mandatory reasoned-order template the system will not let you skip.

Closure without implementation

Case closed at decision; remedy never executed; the same grievance returns in six weeks with added distrust. Fix: gate closure on implementation evidence.

Silent timeline breaches

The deadline passes, nobody tells the complainant, they conclude the process is a sham. Fix: automated pre-deadline alerts, mandatory written extension notice with reasons.

Unaddressed retaliation

The complainant's rating drops, their overtime dries up, they are moved to an inconvenient shift. Nobody connects it to the grievance. Everyone else does. Fix: watch period, flagged reviews of adverse actions, and acting visibly the first time it happens.

Zero-volume complacency

"We have no grievances, so everything is fine." In a workforce of any size, zero grievances means the channel is invisible, distrusted or filtered. Fix: treat zero volume as a red flag; check awareness directly through skip-levels and surveys.

Treating symptoms forever

Fifty allowance corrections, zero questions about why fifty were needed. Fix: root-cause tagging and a quarterly systemic-fix review with named owners.

Stale constitution

Members who left the company still on the notice board; tenure expired; no woman member after a resignation. Fix: tenure tracking with renewal reminders, and a constitution review whenever a member exits.

Over-legalising

Cross-examination, lawyers, adjournments, formal pleadings. Slow, intimidating, and it pushes ordinary employees away from a mechanism designed for them. Fix: keep it fair and simple; reserve formality for serious conduct cases, and take legal advice where a matter is genuinely high-risk.

Under-legalising

The opposite error: treating a serious allegation as a chat, no notice, no record, a verbal outcome. Fix: a severity assessment at Stage 2 that determines the level of formality applied.

---

A Practical Rollout Sequence

For a company starting from nothing, a workable order:

1. Week 1–2: Map applicable requirements per site and state; confirm what your standing orders, settlements or state rules already prescribe. Take legal input on thresholds and timelines.
2. Week 2–3: Draft the policy — scope, definitions, exclusions and routing, anonymity position, non-retaliation, confidentiality, recusal, stages and internal SLAs.
3. Week 3–4: Fix the category taxonomy and the intake fields. Configure the case log.
4. Week 4–5: Constitute the committee — elect or nominate worker representatives, appoint employer representatives, ensure gender representation, name the chair, deputy chair, alternates and appellate authority, and set tenure dates.
5. Week 5–6: Train the committee (full day, with simulations) and intake handlers (short session, routing plus log-it-do-not-filter).
6. Week 6: Launch communications — notice boards in local languages, shift briefings, portal, onboarding update, payslip footer.
7. Week 7 onward: Run cases. Review the first ten closely as a panel — what went well, where the process was clumsy, what the template missed.
8. Quarter 1 close: First analytics review; first systemic fix identified with an owner.
9. Quarter 2: Publish aggregate outcomes to the workforce. Audit intake for unlogged cases.
10. Annually: Refresh training, review the policy against current notified rules, refresh the constitution, and re-verify the state matrix.

None of this is expensive. The main cost is attention in the first six weeks and discipline thereafter.

---

FAQ

Is an employee grievance redressal committee mandatory for my company?

It depends on your establishment type, headcount and location. India's labour codes, including the Industrial Relations Code, contemplate a grievance redressal mechanism at establishments above a specified employee threshold, and older legislation, standing orders, state rules and settlements may already impose obligations on you. Check the rules notified for your state and establishment type, and confirm with a qualified adviser. Regardless of the strict legal position, a functioning mechanism is worth having well before you are required to have one.

What is the difference between a grievance committee and a POSH Internal Committee?

They are separate bodies with separate jurisdictions. The Internal Committee constituted under India's sexual harassment law handles complaints of sexual harassment at the workplace, with its own composition requirements including an external member, its own procedure and its own timelines. The grievance committee handles complaints about service conditions, pay, treatment by managers and similar matters. If a sexual harassment allegation arrives through the grievance channel, refer it to the Internal Committee immediately without investigating it.

Should we accept anonymous grievances?

Accept them, but be honest about the limits. Anonymous complaints are hard to investigate because you cannot ask follow-up questions or fairly test the account, so act on them in proportion to how specific and verifiable they are — allegations pointing at records can be checked, vague ones often cannot. Offer confidential-but-not-anonymous as an alternative, since many people who want anonymity actually want protection from retaliation. Log every anonymous complaint anyway; patterns across several vague complaints are themselves a finding.

How long should a grievance take to resolve?

Your policy should set internal service levels for each stage and stay comfortably inside any outer limit prescribed by the rules applicable to you — verify what has been notified for your state and establishment. Many companies target acknowledgement within one working day and a first-instance decision within three to four weeks for standard cases, with a defined appeal window after that. Record-check cases such as allowance calculations should close much faster. What matters as much as the target is telling the complainant, before the deadline passes, when a case will take longer and why.

Can the same person sit on both the grievance committee and the disciplinary panel?

It is better to keep them separate, and essential to separate them within a single connected matter. Someone who investigated a grievance against a manager should not then sit as the disciplinary authority deciding that manager's punishment, because they have already formed a view on the facts. In small companies with limited senior bench strength, complete separation is hard, so at minimum apply a strict rule that nobody decides at two stages of the same case, keep alternates ready, and record the allocation reasoning in the file.

What should we do if an employee goes to a lawyer or an external forum while their grievance is pending?

Do not treat it as a betrayal or shut the internal process down reflexively. Employees retain external remedies whatever your policy says. Take legal advice promptly on whether continuing the internal process could prejudice your position or the employee's, preserve all evidence immediately, and avoid any action that could look like retaliation. In many cases the internal process can continue with legal guidance, and a fair, well-documented internal file strengthens rather than weakens your position.

How do we stop the grievance mechanism from being used to settle scores?

Mostly through the process itself: clear admissibility rules, fact-finding based on records rather than assertions, both parties heard, and reasoned decisions that say plainly when an allegation is not established. Track repeat complainants alongside repeat respondents, but be careful — someone raising several grievances may be persistently mistreated rather than vexatious, and assuming the latter is a classic bias failure. Where a complaint is found to be knowingly false and made in bad faith, your policy can allow disciplinary referral, but set that bar deliberately high and use it sparingly, because employees will hear about it and a low bar will silence genuine complainants.

---

Closing

A grievance mechanism is not a document. It is a committee that actually convenes, an intake that actually logs, a clock that actually runs, and a decision that actually gives reasons. Most Indian SMBs already have the ingredients — an HR team, supervisors who know their people, and a workforce willing to speak if speaking is safe. What is usually missing is the structure that turns those ingredients into a process that holds up when tested.

Build it in a quiet quarter. Name the panel, elect the worker representatives, fix the taxonomy, set your internal SLAs inside whatever the notified rules require, train the people who will run it, and tell the workforce it exists. Then watch the data and fix the causes it reveals rather than adjudicating the same complaint forty times.

And keep the legal reality in view: thresholds, timelines, composition rules and record formats under the labour codes vary by state and establishment type and continue to evolve. Verify the position that applies to you, revisit it annually, and take proper legal advice on any contested or serious matter. This article is general guidance, not legal advice.

CozyHR gives you a logged, auditable place for grievance cases, policy acknowledgements and committee records — intake from multiple channels into a single case log, stage-wise owners and timelines, restricted access with a full action trail, and the payroll and attendance data sitting right where the committee needs it. If your grievance process currently lives in an email thread and a spreadsheet, that is usually the first thing worth moving.