2. POSH Compliance Made Simple (2026)
3. What does Relevance in POSH Compliance Mean?
4. Is Your POSH Compliance Framework Ready to Handle Reality?
5. Is Your POSH Framework Employee-Friendly?
6. Is Your POSH Framework Credible and Legally Defensible?
7. How to Review Your POSH Compliance Framework?
8. Quarter 1 (Q-1) POSH Compliance Checklist
11. Blog Corner: Insights You Shouldn’t Miss
From the Editor’s Desk
About the Author
Psychologist, Subject Matter Expert at eLearnPOSH.com
Maya Sreenivasan brings hands-on experience in workplace compliance, specializing in the POSH Act, 2013 and Industrial Psychology. With over 7 years of experience in advising organisations on POSH policies and training Internal Committees, she plays a critical role in shaping the content and legal accuracy of eLearnPOSH.com’s training programs.
Workplace is Digital, The POSH Framework Must Be Too
For a long time, organisations treated the workplace as a physical space an office, a floor, a cabin. Policies were written with that assumption. Training followed that assumption. Even behaviour was judged within that boundary.
But that boundary no longer exists.
Work happens on WhatsApp. Feedback is given on Teams. Relationships build on Slack. And sometimes, lines are crossed there too.
Most POSH policies still speak the language of physical workplaces. They refer to premises, offices, and visits. They rarely define what acceptable behaviour looks like on messaging platforms, or where familiarity crosses into discomfort in digital conversations.
Digital behaviour is different. It is persistent. It leaves records. It can also blur intent. A message read in isolation may not reflect the full context. A joke may travel beyond its original setting. Patterns may build quietly over time.
There is also a deeper challenge. Digital workplaces remove visibility, but not power dynamics. A manager’s message still carries weight, whether it comes in a boardroom or a private chat. Silence is still interpreted. Discomfort still goes unreported often more easily.
The question is not whether POSH applies to digital spaces. The answer is already clear.
The real question is whether your framework recognises how work actually happens today.
Are employees being trained on digital boundaries – not just what is inappropriate, but what is ambiguous? Late-night messages, tone, persistence, familiarity.
Is your Internal Committee equipped to interpret screenshots, chat trails, and context? With AI tools making it easier to manipulate or generate conversations, verifying authenticity is becoming just as important as interpretation.
Do your policies acknowledge that harassment can happen outside office hours, but within work relationships?
Because if your workplace has already gone digital, your POSH framework cannot remain physical.
POSH Compliance Made Simple (2026)
First quarter of the financial year is one of the most useful points in the year for organisations to revisit POSH compliance. A new financial year has just begun, budgets and priorities are being aligned, and teams are already reviewing how systems will run in the months ahead. That makes this a natural time to pause and ensure that your POSH framework is not only in place, but also current, practical, and easy to rely on.
For many organisations, the foundations are already there. There is a workplace sexual harassment policy, an Internal Committee, some level of awareness, and a general understanding of POSH Act compliance. That is an important starting point. The opportunity in April and May is to build on that foundation and make sure the system continues to support the organisation well through the year. There is still room for thoughtful review and opportunity to amend the mistakes from last year to come back stronger.
A practical way to do this is by assessing your system across four key areas:
- Relevance – Does your framework reflect how people work today?
- Readiness – Is your system prepared to handle real cases?
- Usability – Can employees easily access and use the system?
- Consistency – Is the process applied fairly and uniformly across cases?
What does Relevance in POSH Compliance Mean?
Workplace interactions today extend far beyond office premises. Conversations happen across messaging platforms, virtual meetings, travel, and informal settings and across time zones and outside traditional work hours.
A POSH framework that does not reflect these realities can quickly become outdated.
From a practical standpoint, relevance should be reviewed across three areas:
1. POSH Policy
- Does the policy explicitly cover digital workplace interactions?
- Does it include off-hours communication within work relationships?
- Does it extend to interactions during travel, offsites, and virtual meetings?
2. Internal Committee (IC)
- Is the IC equipped to interpret digital evidence such as chat trails and screenshots?
- Can it assess behaviour in contexts beyond physical workplaces?
3. Training & Awareness
- Are employees trained on digital boundaries and grey areas such as tone, persistence, and familiarity?
Having a policy and an Internal Committee in place is only the starting point. Readiness is about whether the system can function effectively when a real situation arises.
In practice, cases often involve complexity. hesitation or fear on the part of the complainant, workplace gossip, lack of cooperation from the respondent, a hostile work environment for both parties, the need to maintain strict confidentiality, and questions around its role when a police complaint is also filed. A system that is not prepared for these realities can struggle at critical moments.
So, let’s review the readiness of the POSH Framework across a few critical areas:
1. POSH Policy
- Are complaint processes, roles, and responsibilities clearly defined?
2. Internal Committee (IC)
- Are members trained to handle real-world complexities, not just procedural steps?
- Are they comfortable managing sensitive situations with neutrality and care?
3. Training & Awareness
- Do managers know how to respond when concerns are raised informally?
- Are IC members regularly trained on inquiry handling, documentation, and confidentiality?
4. Statutory Timelines
Is the POSH system equipped to handle the timelines:
- Complaint to be filed within 3 months from the date of (extendable by 3 more months if there is sufficient cause for the delay)
- Inquiry to be completed by the IC within 90 days
- Findings Report to be submitted by the IC within 10 days
- Action to be taken by the employer within 60 days
5. Employer Responsibility
- Is the organisation actively supporting the IC with resources, access, and a safe working environment?
Is Your POSH Framework Employee-Friendly?
A Even well-designed systems fail if they are not visible, easily accessible, understandable, or trusted by the employees.
Usability is often where the real gap lies; not in the absence of policies, but in the difficulty of using them.
A usability check should consider:
1. POSH Policy
- Is the policy written in simple, clear language?
- Does it explain what an employee should do if a concern arises?
2. Internal Committee (IC)
- Are IC members visible and approachable?
- Are their contact details easily accessible?
3. Training & Awareness
- Do employees know where to report and whom to approach?
- Do they understand what happens after a complaint is raised?
- Are managers equipped to respond appropriately and guide employees to the correct process?
Is-Your-POSH-Framework-Credible-and-Legally-Defensible?
It is not just about having processes in place, but about applying them in a fair and uniform manner across situations.
Inconsistent handling can lead to perceptions of bias, loss of trust, and increased compliance risk.
Consistency should be reviewed across:
1. POSH Policy
- Are definitions and expectations clearly laid out?
2. Internal Committee (IC)
- Is there a standard inquiry process followed across cases?
- Are similar situations assessed using consistent reasoning?
3. System & Documentation
- Are documentation formats structured and uniform?
- Are timelines followed consistently?
- Are decisions supported by clear reasoning and evidence?
4. Confidentiality
- Is information shared strictly on a need-to-know basis?
- Are records handled with restricted access and discipline?
- Do managers avoid informal discussions or parallel handling of cases?
How to Review Your POSH Compliance Framework?
The gaps across relevance, readiness, usability, and consistency rarely exist in isolation. They typically show up across policy, Internal Committee capability, training, and underlying systems.
Addressing them requires structured action across these areas.
1. POSH Policy
A POSH policy should reflect how work actually happens today, not just meet legal requirements. Many policies remain technically compliant but fail to address the realities of new era workplaces, which is where most ambiguity arises.
Expanding the Scope of the Policy
One of the most important updates is to clearly define the scope of the workplace in modern contexts. For instance:
“For the purpose of this Policy, ‘workplace’ includes communication through email, messaging platforms, virtual meetings, and any digital medium arising out of employment, irrespective of time or location.”
This ensures that employees understand that workplace behaviour extends beyond physical office spaces.
It is equally important to address interactions that take place outside regular working hours but are connected to work:
“Sexual harassment may occur outside regular working hours where such interaction arises out of or is connected to employment.”
What conduct should the policy clearly cover?
A policy should go beyond listing obvious forms of harassment and provide clarity on behaviour that is often dismissed as informal or harmless. Employees should not be left guessing whether certain actions are acceptable.
This includes:
- Repeated personal comments or remarks on appearance
- Intrusive personal questions or suggestive jokes
- Unwelcome messages or persistent communication
- Sharing inappropriate content through email, chat platforms, or social media
It is important to clarify that such conduct may occur:
- During virtual meetings, calls, or messaging
- At offsites, work travel, and office events
- In interactions involving clients, vendors, or other third parties
Finally, policies should reflect how conduct is assessed in practice:
“The determination of sexual harassment shall consider the nature of the conduct and its impact on the aggrieved individual, regardless of intent.”
How to include confidentiality in policy?
A POSH policy should mandatorily explain confidentiality in a way that employees can understand and rely on. Consider adding a clause that says:
“All information relating to a complaint shall be treated as confidential and shared strictly on a need-to-know basis, in accordance with applicable law.”
To know more about enforcing confidentiality, please check out – Strengthen confidentiality through systems
2. Internal Committee (IC)
The effectiveness of POSH compliance depends heavily on the capability of the Internal Committee.
Organisations can strengthen IC capability through simple, practical steps:
- Conduct short workshops using sample chat trails or email scenarios
- Run mock inquiries to simulate real-world complexity
- Organise IC – HR discussions (brown-bag sessions) to align on approach
- Create a simple SOP to guide inquiry structure and documentation
3. Training & Awareness
POSH training is most effective when it is tailored to the roles individuals play within the organisation.
Training should focus on real workplace scenarios such as late-night messages from managers, personal comments in team chats, or communication that feels “friendly” but becomes persistent. Using 3 – 4 relatable examples and prompting discussion with questions like, “Would you be comfortable with this?”, helps build practical understanding. Sessions should conclude with clear guidance on what employees should do next if they experience or witness such behaviour.
Managers:
The emphasis should be on first-response handling. They should be trained on what to say when a concern is shared, and equally on what not to do, such as conducting their own investigation, offering personal advice, or dismissing the issue. Providing a simple response script, such as “Thank you for sharing this. Let’s ensure this is handled through the right process,” can help managers respond appropriately. Role-play scenarios, including informal disclosures or concerns involving peers, can further build confidence.
Internal Committee members:
Training should go beyond legal provisions and focus on practical case handling. Workshop-style sessions can include discussion of sample complaints, review of chat or email-based evidence, and exercises on identifying behavioural patterns, asking neutral questions, and structuring findings.
Reinforce reporting channels
Employees often don’t report because they don’t know how or where.
Make reporting unavoidable to miss:
- Add IC contact details in 3 fixed places: Employee intranet / portal and Office notice board / digital dashboard
- Run quarterly “POSH Reminder Mail”
- Add POSH reporting slide in induction decks
POSH Training Checklist
- Use simple and clear language in training material
- Include real workplace examples that employees can easily relate to
- Conduct separate sessions for employees, managers, and Internal Committee members
- Hold short refresher sessions during the year instead of depending on one annual session
- Explain the reporting process step by step
- Share reminders regularly through email, notice boards, or internal platforms
- Review from time to time whether employees actually understand the system
4. Structured Systems & Processes
Consistency in POSH compliance depends on having structured systems in place rather than relying on individual judgment. When processes are clearly defined and uniformly followed, organisations are better equipped to handle cases fairly, maintain confidentiality, and demonstrate compliance when required. Two obvious steps can significantly strengthen this. First, standardising documentation by creating templates for key stages such as complaint intake, notices, hearing records, witness statements, and final inquiry reports. Second is establishing a simple SOP for the Internal Committee that maps the end-to-end inquiry workflow.
Strengthen confidentiality through systems
When a concern is raised, details such as the identity of the parties, statements, evidence, and the inquiry process should not be casually discussed or shared beyond those directly involved in handling the matter.
Confidentiality must be ensured through structured systems rather than relying on individual discretion.
- Organisations should ensure that such access is limited to authorised members of the Internal Committee.
- Case records should be stored securely with controlled access, and informal sharing of information through emails, messages, or discussions should be strictly avoided.
- Wherever possible, avoid long email chains for case-related communication. Instead, use controlled folders or data sharing tools to manage and share information.
- All documents related to a case should be clearly labelled, such as “Confidential – POSH Matter,” to reinforce the sensitivity of the information.
- Communication during the inquiry process should follow defined channels, and care should be taken in how documents are shared, meetings are conducted, and records are maintained.
Introduce periodic case reviews
This can involve reviewing a small number of past cases in an anonymised manner to assess whether timelines were followed, documentation was complete, and decisions were well-reasoned. Such reviews help identify patterns, highlight gaps, and improve the overall quality of the process over time.
Track timelines systematically
Organisations should maintain a simple tracking mechanism to monitor key stages such as receipt of complaint, inquiry duration, report submission, and final action. This can ensure that deadlines are met consistently and reduce the risk of delays.
- Review and update POSH policy to reflect current work realities
- Validate IC structure, readiness, and training
- Ensure reporting channels are visible and accessible
- Conduct role-based POSH training for employees, managers, and IC members
- Strengthen confidentiality and documentation practices
- Review timelines, past cases, and annual reporting
- Align HR and leadership on compliance priorities
Closing Thought
Most organisations already have the basics of POSH compliance in place. This is the right time make that framework stronger, clearer, and easier to rely on.
A thoughtful review now can help ensure that the workplace sexual harassment policy stays relevant, the Internal Committee remains prepared, training becomes more effective, confidentiality stays protected, and the overall system feels more usable through the year. That is what makes a POSH compliance checklist valuable at the start of the financial year.
POSH Update or Judgement:
Dr Mohinder Kumar v. The Chairman, NABARD
Dr Mohinder Kumar, an employee of NABARD, was accused of recording videos of female colleagues at the workplace during office hours. The complaint was examined by NABARD’s Central Complaints Committee (CCC). After inquiry, the CCC concluded that the conduct did not amount to sexual harassment under the POSH Act. Even so, it recommended that NABARD take suitable disciplinary action against him under the NABARD Staff Rules. Acting on that recommendation, the competent authority issued a reprimand. Dr Mohinder Kumar challenged both the recommendation and the reprimand before the Bombay High Court.
Issue and Analysis
The main question before the Court was whether a complaints committee can recommend punishment after finding that sexual harassment is not proved.
The Bombay High Court said it cannot. It noted that the committee had itself found that the conduct did not fall within the definition of sexual harassment under the POSH Act. Once that finding was reached, the committee’s role under the POSH process came to an end.
The Court relied on Section 13(2) of the POSH Act, which says that where the complaint is not proved, the committee must recommend that no action is required to be taken in the matter. This meant that the committee could not, after rejecting the complaint under POSH, still ask the employer to punish the employee through the same route.
The Court also held that NABARD could not simply act on that recommendation without separately considering whether it was legally valid. Although this case involved NABARD’s Central Complaints Committee, the same principle applies to an Internal Committee in a private organisation, since both perform the same role under the POSH law.
Judgement
The Bombay High Court set aside both the CCC’s recommendation and the reprimand order, affirming the reasoning outlined above.
Key Takeaways
- A POSH committee cannot recommend punishment after holding that sexual harassment is not proved.
- The committee’s role is limited to the POSH Act; it is not a forum for general misconduct.
- Any non-POSH misconduct must be dealt with separately under the employer’s disciplinary framework.
- HR should independently review whether the IC’s recommendation is legally sustainable before acting on it.
- The employer must match the complaint to the correct process: POSH for sexual harassment, disciplinary framework for other misconduct.
Another judgment worth noting →
FAQ Corner
Blog Corner: Insights You Shouldn’t Miss
Want deeper insights on compliance & workplace training?
Explore our complete collection of expert-written blogs and guides.