Executive Summary If you’re “struggling with POSH policy” (often referring to India’s POSH/anti-sexual harassment framework), the usual root causes are: unclear reporting pathways, weak case-handling ownership, poor awareness/training, and documentation that doesn’t translate into a practical process. The fix is to turn your POSH policy from a document into an operating system—who does what, how complaints move, timelines, confidentiality, and manager enablement.

Key Recommendations

1. Make the policy operational (not just a statement)

• Convert your POSH policy into a simple “end-to-end workflow” users can follow:
• How to raise a complaint
• Who receives it (internal committee + designated points of contact)
• What happens in the first 48 hours
• Investigation stages
• Interim measures (if needed)
• Decision/closure and communication
• Appeals/review pathway (as applicable to your internal process)
• Ensure the policy clearly defines roles:
• Internal Committee (members, chair, alternate)
• HR/Compliance SPOC
• Legal/External counsel (when required)
• Management stakeholders for interim protections

1. Fix the “front door” for complaints

Common failure: employees don’t know where/how to report, or fear retaliation.

• Publish multiple reporting channels:
• Email / physical form / confidential dropbox (as appropriate)
• A dedicated hotline/number or shared inbox monitored by HR/committee admin
• Clearly state confidentiality approach and non-retaliation principles.
• Provide a “What to expect” one-pager for complainants:
• timelines, support options, and what information is needed

1. Strengthen case handling readiness (committee capability)

Even a good policy fails if the committee can’t execute consistently.

• Create standard operating procedures (SOPs) for the committee:
• appointment & quorum rules
• meeting cadence
• evidence collection rules
• note-taking, records retention
• hearing/interaction rules
• Train committee members specifically on case process and documentation discipline.
• Assign an “Admin/Case Coordinator” person (often HR) to reduce chaos and missed steps.

1. Build interim protection mechanisms

Most complaints require immediate risk management. Your policy should include:

• What interim measures can be taken (e.g., workplace separation, temporary reporting line changes)
• Who approves them and how fast
• How confidentiality is maintained during interim action

1. Close the awareness and training gap (biggest behavioral lever)

• Mandatory training schedule (company-wide + managers + committee members)
• Use role-based training:
• Employees: how to report, rights, expectations
• Managers: how to respond to an incident/report, do/don’t, non-retaliation
• Committee: process and evidence handling
• Refresh training at least annually, plus onboarding sessions.

1. Align POSH with culture and manager behavior

A POSH policy becomes “ineffective” when leaders handle reports inconsistently.

• Create a “manager response protocol”:
• listen, record basic facts, don’t investigate informally, escalate to POSH channels immediately
• Track manager accountability through HR dashboards (see KPIs below).

Business Impact

• Reduces legal and reputational risk by improving predictability and governance.
• Increases employee trust (better reporting, fewer silent cases).
• Improves decision quality and speed through standardized processes.
• Protects leadership time by removing ad-hoc, informal handling.

Risks (if you don’t fix the operational gaps)

• Under-reporting (employees stop coming forward).
• Process inconsistency (committee actions become difficult to defend).
• Retaliation concerns (even accidental) damaging culture.
• Documentation gaps that delay closure and increase escalation risk.

Immediate Next Steps (practical 30-day plan) Week 1: Diagnose the gaps

• Run a quick POSH “policy-to-process” gap review:
• Do employees know how to report?
• Are roles and timelines executable?
• Does your committee SOP exist and get followed?
• Are interim measures defined and workable?
• Identify top 3 failure points (usually reporting awareness, committee readiness, or documentation).

Week 2: Operationalize

• Publish/refresh the reporting workflow and “what to expect” one-pager.
• Document committee SOPs and interim measure process.
• Set up a POSH case file template (for consistent records).

Week 3: Capability + rollout

• Train committee members and HR POSH admin coordinator.
• Train managers on response protocol (do/don’t + escalation).
• Launch awareness sessions (in-person or short video + quiz).

Week 4: Monitor and improve

• Create a lightweight POSH dashboard (KPIs below).
• Run a committee mock drill (case simulation) to improve readiness.

KPIs to manage POSH effectiveness

• % employees trained (by role)
• % managers trained (by role)
• Time to “acknowledge receipt” of a complaint (target: very fast, operationally defined)
• Time from complaint receipt to first committee meeting
• Closure rate within defined internal timelines
• Number of cases where interim measures were considered/applied (track for consistency)
• Audit score of case documentation quality (internal review)
• Employee awareness score from pulse survey (e.g., “I know how to report POSH”)

Three quick questions (only to tailor the right operating model)

1. Is your POSH issue mainly about employees not reporting, committee process/documentation, or policy clarity/communications?
2. Do you already have an Internal Committee and SOPs, or is it mostly policy-only on paper?
3. Which state/country are you operating from (so the training/handling expectations match your local context)?

If you need help implementing these recommendations or would like expert guidance tailored to your organization, the team at Zunavish would be happy to assist.