What it takes to make PoSH compliance work across a large organisation

We have been working with enterprises for more than a decade now. My starting point for a large organisation’s PoSH mandate is whether someone at its least connected workplace can use the system, and whether the organisation can respond properly when they do.

A policy approved at headquarters has to reach a contractor on a different shift. An Internal Committee needs practical preparation and dependable support. Leadership needs visibility without receiving copies of complaints.

Buying training, appointing an external member and installing software separately can leave the handoffs unowned.

The model below is an illustrative composite operating design, not a client case study or a report of outcomes achieved by Ungender. The sector examples are hypothetical. They show how I would approach an enterprise mandate, including the choices that should be settled before rollout.

Start with how people actually work

Consider four different settings. These are planning examples, not assumptions about every organisation in a sector.

In manufacturing, the access map might include production shifts, contractor induction, local languages and restrictions on phones inside a plant. I would ask the site HR lead to test a reporting route that does not require a company email address, and the operations lead to release people for awareness sessions across shifts.

In pharma, a laboratory, a production facility and a travelling field team may need different examples. A session for field staff could address work travel, professional meetings and interactions outside company premises. Regional managers should arrange learning time without making confidential reporting dependent on their approval.

In banking, financial services and insurance, I would map branches, contact centres, outsourced teams and field roles separately. A centrally recorded webinar should not be the only option for someone working around customer appointments or using a restricted device.

For an NGO, field offices, volunteers, partner organisations and community interactions may need distinct reporting explanations. The legal and safeguarding leads should clarify where the PoSH process applies and where another safeguarding or grievance route is needed. A referral should have a receiving owner rather than leave someone to start again.

The first deliverable should be a workforce access map: entity, location, work pattern, language, employment arrangement and available reporting routes. HR should own its upkeep, with site leads checking it when operations change.

Make the policy usable beyond the intranet

I would retain an authoritative policy and build shorter formats around it: illustrated scenario cards, translated explainers, captioned videos, audio versions, noticeboard material and a plain-language reporting guide. Each should carry a version date and point to the current policy and relevant contacts.

Creative formats must not quietly change the rules. A short explainer that omits a route or suggests that a manager must approve a complaint is a policy problem, however attractive its design.

The statutory foundation includes regular employee awareness and IC orientation under section 19; Rule 13 also addresses policy dissemination, IC capacity building and contact details.[1][2] The formats and distribution plan I propose are ways to make that work locally, not a legally prescribed media checklist.

Give the communications lead responsibility for approved materials and the site lead responsibility for placement. Include contractor onboarding and shift briefings. A QR code can supplement a visible contact route; it should not replace one.

Then test access. Ask a sample of workers to locate the relevant IC contact and explain how they would seek help without telling you about a personal incident. Record where they get stuck. A distribution receipt proves that something was sent, not that someone can use it.

Coordinate the programme without creating a super-committee

The legal map must come before the central dashboard. Section 4 addresses IC constitution across offices or administrative units at different places or divisional levels; section 6 specifies Local Committee jurisdiction, including complaints against the employer.[1]

I would have legal and HR map the entities, locations, constitution orders, member terms, conflicts and relevant committee routes. A group-level programme owner can maintain this map and resolve administrative gaps. That role should not become an authority that overrides the competent IC or Local Committee.

Standardise the support: current templates, access rules, appointment reminders, orientation and administrative assistance. Preserve the committee’s independent assessment of each matter. Where a concern crosses entities or involves a contractor, obtain a reasoned jurisdiction assessment rather than automatically assigning it to headquarters.

Backups also need definition. An administrative coordinator can have a deputy. An appointed committee member cannot simply send an unappointed colleague to take their place; changes in membership need the appropriate formal process.[1]

Give ICs a learning rhythm, not just an induction

I would propose a monthly IC learning session, supported by a short legal and judgment newsletter. This is a recommended programme cadence, not a claim that the Act mandates monthly meetings or that every Ungender engagement already includes this package.

The newsletter should identify the source, the procedural issue, the context of the ruling and what members should review. A judgment from a particular employment setting should not become a universal instruction stripped of its facts.

Use the session to practise a task: preparing a neutral notice, identifying a conflict, separating an allegation from evidence, or explaining why a conclusion follows from the record. Adapt the exercises to the organisation’s workplaces.

Quarterly calibration meetings can compare procedural understanding and documentation standards across committees. They must not align verdicts or circulate identifiable live cases. I would use fictional exercises and public judgments, with the facilitator recording training needs rather than ranking committees by outcomes.

The programme coordinator should maintain attendance and unresolved learning questions. A designated legal reviewer should approve the newsletter. New members should receive orientation when appointed instead of waiting for the next annual event.

Design awareness for different responsibilities

Employees need to understand conduct, reporting options and what happens next. Managers need practice in receiving a concern without investigating it themselves, promising secrecy they cannot deliver, or discouraging formal reporting. IC members need a separate, deeper learning programme.

For a large workforce, I would combine e-learning, external facilitators and train-the-trainer support. E-learning can provide a common baseline where people have suitable access. Facilitated sessions allow contextual questions. Internal trainers can extend reach across shifts and locations, provided their role has limits.

Conduct’s e-learning modules offer self-paced learning in multiple languages, with progress and completion tracking.[6] I would use them as one part of this plan, matching the available modules and languages to the workforce access map. Facilitated and on-ground options still matter where device access or reading comfort makes digital learning difficult.

A train-the-trainer programme should include observed practice, an approved facilitator guide, periodic refreshers and a route for questions the trainer cannot answer. Trainers should not collect personal stories in a group session or become informal complaint adjudicators.

The learning lead should review coverage by audience, shift, location and language, not only a company-wide completion percentage. Short scenario checks and the ability to find reporting contacts are more useful tests of understanding than attendance alone.

Bring reporting channels together without making access harder

I would design a central receipt and coordination function alongside direct IC access and on-ground channels. An employee should be able to reach an appropriate person, use a written route, or access an approved digital channel without first persuading a line manager.

Conduct’s incident-reporting tools can support the digital route alongside direct committee access.[4] Before rollout, I would test how a report reaches the authorised recipient and how someone receives help if they cannot use that channel. A platform should make the handoff clearer, not become the only door into the process.

The receiving person needs a script and a secure handoff process: explain their role, record only what is necessary, identify urgent safety needs and connect the person with the appropriate committee. Section 9 provides for reasonable assistance in putting a complaint in writing where the woman cannot do so.[1]

A single coordinated view should mean controlled records and clear ownership, not a group-wide shared folder. Restrict identifiable files to authorised people for that matter. Give programme staff only the information needed to coordinate their tasks, and leadership an aggregate view.

Separate an initial concern, an anonymous signal and a formal statutory complaint in the workflow. Do not advertise anonymity as a guarantee that every report can proceed through the same inquiry process. Explain the available options and their limits.[1]

A hypothetical handoff, before and after

Take an illustrative manufacturing site with contract workers and multiple shifts. A woman wants to raise a concern but cannot use the corporate intranet.

In the hypothetical starting arrangement, she tells a supervisor. The supervisor forwards a message to site HR, which emails corporate HR. Someone asks her to complete an online form. No one confirms which committee has received the complaint. Copies accumulate while ownership remains unclear.

I would redesign that workflow as follows:

1. At first contact, the trained site contact explains the available routes, arranges a private conversation and promptly helps connect her to the appropriate committee. The supervisor’s permission is not a prerequisite.
2. On receipt, the authorised coordinator records the receipt date and channel, creates a restricted reference and arranges acknowledgement. A proposed internal target might be one working day; urgent safety needs require immediate attention. This is an operational target, not a statutory deadline.
3. At routing, the designated legal adviser supports the jurisdiction check. The competent committee confirms its role, addresses conflicts and determines the lawful next steps. Central coordination must not become a queue that delays access.
4. During the process, the committee owns the inquiry and procedural decisions. The coordinator manages authorised scheduling and reminders. HR provides facilities and implements employer responsibilities without deciding the committee’s findings.
5. At completion, record the report, communication to the appropriate recipients, action on recommendations and any applicable follow-up or appeal status. Keep these stages distinct rather than marking everything closed when a report is drafted.

The proposed change is specific: each handoff has an owner, receipt is traceable and duplicate circulation is reduced by design. It is not evidence of a faster or better client outcome. Those effects would need to be measured after implementation.

Technology should track acknowledgement, routing, inquiry milestones, recommendations and employer action separately. The Act distinguishes the inquiry’s 90-day limit, the report within ten days of completion, and action on recommendations within sixty days of receipt.[1] A shorter internal service goal cannot replace those requirements or justify rushing a party’s opportunity to participate.

I would review missed targets weekly with the authorised task owners. Record the reason, corrective action and next owner; do not reset the clock to improve a dashboard. Fair process and supported participation matter more than a competitive case-closure ranking.

Keep records that explain the process

Documentation should let an authorised reviewer understand what happened without reconstructing it from personal inboxes.

Maintain constitution orders and appointment records separately from complaint files. Within each matter, preserve the relevant communications, notices, evidence, hearing records, procedural decisions, reasons, reports and implementation records. Assign responsibility for version control and approval.

Conduct’s case-management tools provide document and evidence management, process timelines, reminders and access controls.[7] I would assess the configuration against the committee map and the separate inquiry, report and employer-action stages described above. These tools support record-keeping and coordination; the competent committee retains responsibility for its procedure and independent judgment.

Templates should support the committee’s reasoning, not substitute for it. If transcription or drafting tools are used, require human review before a record is adopted. Establish the rules for recording meetings and handling those recordings before switching the feature on.

For the programme itself, keep a separate record of policy versions, distribution checks, training coverage, committee learning and corrective actions. This lets operational gaps be addressed without opening confidential case files to everyone involved in compliance.

Give the board visibility without distributing case details

I would recommend a quarterly, access-controlled governance report for the board or relevant governing body. Include committee coverage, training access gaps, aggregate receipt and disposal information, ageing, missed process milestones and overdue employer actions. Attach owners and dates to corrective work.

Exclude names, narratives and details that identify people indirectly. Small sites may need combined reporting categories. Section 16 restricts public disclosure of complaint and inquiry information; internal reporting also needs carefully limited access.[1]

This governance report is separate from statutory reporting. Sections 21 and 22 and Rule 14 address annual reporting obligations; the company secretary or legal lead should separately confirm the applicable corporate disclosures and filing requirements.[1][2] A quarterly board presentation is not a substitute.

I would not present fewer complaints as proof of a safer workplace. Read complaint volumes alongside reporting access, awareness and process performance. Otherwise, leadership may reward a number without understanding what produced it.

Treat information security as part of partner selection

A PoSH partner may handle highly sensitive material. I would expect procurement, legal and information security to assess the actual service and deployment before sharing case data.

Ask for evidence of hosting arrangements, subprocessors, encryption, role permissions, access logs, incident response and business continuity. Test whether one entity’s users can access another entity’s files, whether access is removed when someone leaves, and how administrative access is authorised and reviewed.

Agree retention periods by record category, with legal holds where needed. Establish deletion procedures and evidence, including the treatment of backups. Test the export of evidence, metadata and audit history so an organisation can change providers without losing its record.

Where AI or transcription is proposed, ask which providers receive the data, whether it is used for model training and how recordings and derived outputs are retained. A confidentiality clause or a security badge should not end that discussion. Apply these questions to Ungender too; the answers should be demonstrated and documented for the engagement.

Choose a partner for the operating model you need

An experienced individual consultant can be an excellent adviser or external member. The enterprise buying decision should turn on the work required, not an assumption that individual practitioners are less capable.

For a distributed organisation, I would assess whether the support arrangement can provide continuity during absence, more than one specialist when needed, documented quality review, controlled handovers and dependable programme administration. An organisational partner should be able to explain those arrangements in the contract. Hiring a firm does not transfer the employer’s duties or the committee’s judgment.

Ungender offers policy and IC support, external member empanelment, IC training, documentation reviews and case guidance.[3][5] Conduct is our technology offering for reporting, learning and case-management workflows, including role-based access and tracking.[4] Advisory and technology should be evaluated together, with the scope of each made explicit.

For an enterprise considering working with us, I would start with your entity and location map, workforce access needs, committee structure, learning calendar and a sample governance report. Bring information security into that discussion before any complaint records are shared.

Are you an HR leader in a large organisation? Write to us at contact@ungender.in to explore how Ungender can partner with your team on PoSH governance across entities and locations.

By Pallavi

Sources

[1] https://www.indiacode.nic.in/bitstream/123456789/2104/1/A2013-14.pdf

[2] https://shebox.wcd.gov.in/assets/uploaded_content/SH_Rules,_20132.pdf

[3] https://www.ungender.in/services

[4] https://www.ungender.in/conduct-posh-compliance-platform

[5] https://www.ungender.in/contact-us

[6] https://www.ungender.in/conduct-posh-compliance-platform/education-modules

[7] https://www.ungender.in/conduct-posh-compliance-platform/case-management