Rolling Out PoSH Compliance for the First Time

At Ungender, when organisations tell us they are “rolling out PoSH compliance for the first time,” what they are often describing is not a lack of intent, but a lack of sequencing. Everything feels important at once. Policies, committees, trainings, reporting obligations, portals, documentation—each requirement appears urgent, and teams are unsure where to begin without exposing themselves to risk or fatigue.

The result is usually one of two extremes. Either compliance is rushed through in a compressed burst—documents drafted, sessions scheduled, names announced—or it is delayed indefinitely because the organisation fears doing it incorrectly. Neither approach builds a system that can actually function when it is needed.

Rolling out PoSH compliance is not a launch event. It is infrastructure-building. And like all infrastructure, it works best when it is built in layers, with each element supporting the next.

This piece is about that sequencing.

Why First-Time Rollouts Feel Heavier Than They Need To

PoSH compliance is often introduced to organisations through legal obligation rather than organisational design. When compliance enters the room as a mandate, teams naturally focus on risk: penalties, notices, escalation, reputational exposure. This risk-led framing creates urgency without clarity.

What we see repeatedly is that overwhelm does not come from the volume of work—it comes from trying to do everything simultaneously, without understanding how the pieces fit together. When policy, IC constitution, awareness, and reporting are treated as independent tasks, the rollout feels chaotic. When they are treated as a sequence, the same work feels manageable.

The first shift, therefore, is conceptual: PoSH compliance is not four parallel tracks. It is one system, built in stages.

Step One: Start with a Policy That Sets Expectations (Not Fear)

The policy is almost always the first tangible step in a PoSH rollout, and rightly so. It establishes the organisation’s position, defines unacceptable behaviour, and outlines the mechanism for redressal.

What often goes wrong at this stage is that organisations treat the policy as a legal artefact rather than a communication tool. Overly technical language, copied clauses, and inaccessible formats create documents that employees do not read, even if they are circulated.

In a first-time rollout, the policy’s primary job is not to cover every hypothetical scenario. It is to set clear expectations:

• What behaviour is prohibited
• Who the policy applies to
• How concerns can be raised
• What process the organisation commits to following

A policy that is readable, approved, and actually circulated creates the foundation for everything that follows. Without this clarity, later steps feel disconnected.

Step Two: Constitute the Internal Committee Before You Need It

Once the policy exists, the next layer is the Internal Committee. This is where many organisations hesitate—often because they are unsure about seniority, roles, or the visibility that comes with naming individuals.

From our experience, delaying IC constitution until a complaint arises creates far more risk than clarity. It forces people to step into roles mid-crisis, without orientation or shared understanding.

In a well-sequenced rollout, the IC is constituted quietly and deliberately, soon after the policy is finalised. Members are identified thoughtfully, documentation is completed, and the committee is oriented before it is ever called upon to act.

This sequencing matters. A committee that exists before it is needed functions very differently from one assembled under pressure.

Step Three: Orient the IC Before You Speak to the Organisation

One of the most common sequencing mistakes we see is rolling out employee awareness before the IC itself is prepared. This creates a gap between promise and readiness.

When employees are told that a system exists, they reasonably expect it to function. If the IC has not yet been oriented—if members are unclear about roles, timelines, or boundaries—this expectation becomes a source of anxiety rather than trust.

A first-time rollout works best when the IC is:

• Formally constituted
• Oriented on process and roles
• Clear about confidentiality and neutrality

before the organisation is informed in detail. This does not require months of preparation, but it does require intentional sequencing.

Step Four: Communicate the System—Not Just the Policy

Once the policy exists and the IC is prepared, the next layer is communication. This is the point at which the organisation is formally introduced to the PoSH framework as a living system.

Effective first-time communication does not overwhelm employees with legal detail. It focuses on usability:

• Who the IC members are
• How a concern can be raised
• What confidentiality and non-retaliation mean in practice
• What employees can expect if they come forward

We often advise organisations to think of this stage as introducing a process, not enforcing a rule. The tone set here influences how safe and accessible the system feels in its earliest days.

Step Five: Awareness as Orientation, Not Alarm

Awareness sessions are often treated as the “big moment” of a PoSH rollout. In reality, they are most effective when they function as orientation rather than intervention.

In first-time rollouts, awareness should:

• Clarify boundaries and definitions
• Explain the process step by step
• Reinforce the organisation’s commitment to fairness
• Reduce fear rather than create it

Sessions that are overly legalistic or alarmist tend to shut down engagement. Those that are clear, measured, and grounded help employees understand how the system works and when to use it.

Awareness is not about teaching the law. It is about making the system intelligible.

Step Six: Set Up Reporting and Record-Keeping Early—But Simply

Reporting and documentation often feel like the most intimidating part of PoSH compliance, especially for first-time organisations. The mistake here is assuming that sophistication is required from day one.

In a first rollout, what matters is not complexity, but consistency:

• Clear channels for receiving complaints
• Secure storage of records
• Basic logs of training, appointments, and actions

These systems can evolve over time. What is important is that they exist early enough to support continuity and later reporting.

Step Seven: Treat Annual Reporting as the Outcome, Not the Starting Point

Annual reporting, including the ACR, often looms large in the minds of organisations even before the rollout begins. This backward framing adds unnecessary pressure.

When policy, IC constitution, awareness, and documentation are sequenced thoughtfully through the year, reporting becomes a natural outcome rather than a scramble. The ACR simply reflects what already exists.

First-time organisations benefit greatly from seeing reporting as a reflection of practice, not a compliance event to be managed in isolation.

What a Well-Sequenced First Rollout Achieves

When PoSH compliance is rolled out in this order—policy, IC, orientation, communication, awareness, documentation—several things happen quietly but powerfully.

The organisation is not overwhelmed.
IC members feel prepared rather than exposed.
Employees understand the system without fear.
Leadership sees compliance as a process, not a fire drill.

Most importantly, the system is real before it is tested.

A Closing Reflection from the Ungender Team

Rolling out PoSH compliance for the first time is not about doing everything at once. It is about doing the right things in the right order.

When organisations resist the urge to rush and instead focus on sequencing, PoSH compliance stops feeling like an external imposition and starts functioning as internal infrastructure—steady, defensible, and humane.

At Ungender, we see the strongest rollouts not as the most ambitious ones, but as the most deliberate. The ones that give the organisation—and its people—room to understand, adapt, and trust the system as it takes shape.

Need professional help? Reach out to Ungender’s compliance team at contact@ungender.in with the subject line “Advisory POSH Compliance”