WHO’s Zero Tolerance in Practice: What Institutional Inaction Means for Workplace Safety

WHO’s 2026–2029 strategy treats inaction as an accountability concern. This practitioner guide helps Indian employers examine stalled handovers, missing support and limited oversight while keeping committee findings independent.

PoSH Compliance • October 3, 2026 • 12 views • By Ungender Content Team

Illustration of people along a tree-lined path with branching coloured lines, circular markers and a bus in the background.

A workplace safety policy should explain what happens when the organisation itself fails to act. If a reporting route goes unanswered, committee members cannot obtain records, or a protective measure is approved but never implemented, reviewing only the alleged misconduct leaves a separate question unresolved: who was responsible for making the process work?

WHO’s Zero Tolerance in Practice, its strategy for 2026–2029, provides a useful starting point. Published on 12 May 2026, it is not a new October announcement.[2] Its continuing relevance is the accountability question it makes explicit: zero tolerance extends to misconduct, inaction and retaliation.[1]

For Indian employers, the useful exercise is to examine their own response arrangements through that lens. The practical checks below are recommendations, not additional statutory duties created by WHO.

What WHO’s strategy does, and does not, establish

The official strategy covers WHO’s headquarters, regional and country levels, alongside IARC, the United Nations International Computing Centre and UNITAID.[1] Its use of sexual misconduct includes exploitation, abuse and harassment; it should not be treated as interchangeable with India’s statutory PoSH framework.[1][7]

WHO makes inaction a formal accountability concern and proposes monitored investigation and post-investigation case management.[1] Those commitments are a basis for comparison, not proof that every implementation problem has been solved. Nor does this organisational strategy create a new legal obligation for Indian employers.[1][7]

The question worth borrowing is specific: can your organisation identify a response failure without waiting for the underlying complaint to reach a conclusion?

Make inaction visible without prejudging the complaint

Hypothetical example: An employee submits a complaint through the designated route. It reaches the correct committee, which asks the employer for access to relevant records. The request then sits between HR and IT because neither function knows who can authorise retrieval.

The employer need not decide whether harassment occurred to resolve that administrative blockage. It can identify the authorised recipient, arrange secure access and record completion while leaving the committee to assess the material.

For each handover, record the task, responsible role, request date, next review date and escalation route. Describe a delay accurately. A disputed request requiring clarification is different from an unanswered request; a recorded procedural reason is different from silence.

Keep this operational record proportionate. It should help the right person act, not become a parallel account of witness credibility or management’s preferred findings.

Start with the employer’s Indian legal duties

Section 19 of the PoSH Act already requires employer action: a safe working environment, awareness and committee orientation, necessary inquiry facilities, assistance securing attendance, required information and monitoring timely IC reports.[7]

These duties provide a more useful starting point than importing WHO’s terminology into a policy. Review each obligation against an actual arrangement. Who releases members from conflicting work? Who retrieves requested records? Who follows up an unfulfilled facilities request?

Separate responsibility from support purchased outside the organisation. Ungender’s guide to PoSH partners, trainers, investigators and advisors helps define those service boundaries.[8] Use it to check the scope, then name the internal owner who will arrange the employer’s part of the work.

Hold leaders responsible for support, not a preferred verdict

A leadership review should ask whether the committee has what it needs and whether required actions are being completed. It should not ask members to change a finding because a respondent is commercially important or a complaint is inconvenient.

For employee respondents, section 11 links the inquiry to applicable service rules, or prescribed procedure where those rules do not exist; it also provides hearing safeguards where both parties are employees.[7] A zero-tolerance slogan is not a substitute for that process.[7]

Recommended oversight questions include whether a resource request has an owner, whether a conflict has been raised for resolution, and whether a handover remains outstanding. Avoid asking for an informal assessment of guilt during an operational update.

If leaders want faster progress, require them to identify what support they can provide. Do not turn urgency into pressure to skip an opportunity to respond or reach a predetermined result.

Review protection separately from the final finding

Recommend a clear route for concerns about pressure, exclusion or adverse work changes while a matter is pending. Ask who will receive the concern, how a conflict will be handled and when the person raising it will hear back. Do not assume that every work change is retaliatory, or that an ordinary management explanation resolves every concern.

Section 12 provides a specific interim-relief route: during an inquiry, on the aggrieved woman’s written request, the committee may recommend transfer, leave or other prescribed relief; the employer must implement its recommendations.[7] This is distinct from the broader operational checks recommended here.

Where a workplace adjustment is considered, document the reason and review its effect. Avoid making the person seeking protection carry an unnecessary professional disadvantage. Keep support decisions separate from any conclusion on the allegation.

Give oversight the right information

A review of institutional response should not require unrestricted circulation of complaint files. Section 16 restricts publication or disclosure of protected complaint and inquiry information to the public, press and media.[7]

For routine management oversight, recommend a limited view of unresolved support tasks, delay reasons and actions awaiting implementation. Decide access according to the recipient’s actual function; do not grant access simply because someone is senior. Aggregate figures also need care where a small team or distinctive circumstances could identify a person.

Ungender’s discussion of complaint records and the trusted inbox develops the distinction between oversight and access.[4] The focus here is what leaders should do with a properly limited update: remove a blockage, assign responsibility and check that the promised action happened.

Test the process before calling it effective

Run a hypothetical exercise rather than opening a real case file in a general management meeting. Start with a complaint reaching the designated route, introduce an unavailable contact or delayed records request, and ask participants to demonstrate the next authorised step.

Record the gaps the exercise exposes. Give each corrective action an owner and a review date. Re-test the failed step after the change; issuing a revised document does not demonstrate that the route works.

If the exercise exposes unclear policy or support responsibilities, commission a defined review. Ungender’s PoSH compliance advisory is a relevant service to discuss for that work.[3] Specify the expected output and retain ownership of implementing it.

A useful leadership review should end with decisions about the organisation’s own performance: what remained unanswered, what support was missing, what has been corrected and what still needs follow-up. That makes institutional inaction something the organisation can recognise and address without taking over the committee’s judgment.

This article offers comparative analysis and practitioner recommendations. WHO’s strategy is not Indian law. Apply the relevant law, service rules and facts to any particular matter.

Sources

Key takeaways

Review stalled support tasks separately from the merits of a complaint.
WHO's strategy is a comparative governance reference, not an Indian employer mandate.
Give leaders limited operational visibility and make them accountable for removing blockages, not directing findings.