For years, POSH training lived in a legal grey zone that a lot of employers quietly exploited: the Act clearly requires it, but early enforcement rarely checked for it directly. That gap is closing fast. Labour commissioners in multiple states — Rajasthan among them — have begun conducting proactive workplace inspections specifically checking for POSH compliance, not waiting for a complaint to trigger a review. A Board Report disclosure requirement introduced in mid-2025 now puts a company’s compliance status in front of investors and clients. And a growing body of guidance confirms that training is evaluated not on whether a policy document exists, but on whether real, periodic, documented sessions actually happened.

Here’s the part that catches employers off guard most often: even a technically constituted Internal Committee doesn’t protect you if training never happened. An inquiry conducted by an IC that was never properly oriented, in an organisation where staff were never sensitised to what the Act actually covers, is one of the most common reasons a POSH inquiry gets challenged after the fact — precisely when the stakes are highest.

A policy nobody was trained on isn’t a defence in an inquiry. It’s evidence the inquiry needed to happen in the first place.

It’s worth being specific about why 2026 is the year this stopped being a low-risk gap to ignore. Three separate developments converged: state labour departments moved from complaint-triggered review to proactive inspection; the Ministry of Corporate Affairs folded POSH compliance status directly into the annual Board’s Report that companies file with the Registrar of Companies; and the Supreme Court’s directions around SHe-Box registration created a national, searchable record of which organisations even have a properly constituted committee in the first place. None of these three, on their own, would have forced much change. Together, they’ve made a training gap something that’s now genuinely likely to surface — through an inspector, an auditor, an investor’s due-diligence questionnaire, or a challenged inquiry — rather than something that simply never comes up.

This piece walks through exactly what the law requires around training — not “best practice guessing,” but the actual statutory basis, the accepted frequency standard, the content that has to be covered, the paperwork that proves it happened, and what enforcement looks like when it doesn’t. By the end, you’ll be able to answer, with confidence, whether your organisation’s current training programme would actually survive a labour department inspection or a challenged inquiry.

Training under the POSH Act isn’t a recommendation layered on top of the law — it’s written directly into the employer’s statutory duties. Section 19 of the Act, which lists the employer’s obligations, includes at clause (c) a specific requirement to organise workshops and awareness programmes at regular intervals to sensitise employees to the provisions of the Act. Rule 13 of the POSH Rules, 2013 reinforces this, tying awareness-building directly into the compliance framework the Act establishes. Separately, the Act places a second, distinct training obligation on employers: orientation and skill-building programmes specifically for Internal Committee members — a different, more specialised training track from general staff awareness sessions.

What’s important — and frequently misunderstood — is that the Act itself doesn’t specify an exact number of sessions per year in the statute’s text. That absence of a hard-coded number is precisely what let many employers treat “regular intervals” as “once, a long time ago.” But the absence of a fixed number in the statute is not the same as the absence of a standard. Government advisories, implementation guidance, and consistent enforcement practice have clarified what “regular” means in practice — covered in full in Chapter 4 — and courts and auditors increasingly treat that accepted standard as the bar an employer must clear, statute wording notwithstanding.

It also helps to understand why the Act frames this as a continuing duty rather than a one-time setup task. Section 19 groups the training obligation alongside other ongoing employer responsibilities — displaying the penal consequences of harassment prominently, providing a safe working environment, and assisting in the inquiry process — rather than treating it as a box to tick once when the Internal Committee is first constituted. That framing matters practically: an employer who trained staff diligently in the year the IC was formed, then let the programme lapse for the following three years, is not meeting a “continuing” duty just because it was once satisfied. The obligation resets with every reporting cycle, which is precisely why the annual and onboarding cadence covered in the next chapter functions as a floor, not a one-time achievement.

“All employees at the workplace” is the phrase the Act uses, and employers routinely underestimate how literally that gets applied. It’s not limited to permanent, full-time staff on the payroll. It extends to contractual workers, consultants, interns, trainees, and apprentices — anyone working at or from the location, regardless of their formal employment classification. Remote and hybrid workers are included too; working from home doesn’t remove someone from the workplace as the Act defines it, and digital or work-from-home harassment scenarios fall squarely within its scope.

Foreign employers and multinational subsidiaries are frequently caught off guard by a related point: the POSH Act applies to every workplace situated in India, irrespective of whether the employer is an Indian entity, a foreign company, or an MNC subsidiary. A global harassment policy drafted for headquarters in another country doesn’t automatically satisfy Indian law — it has to be localised to meet India-specific statutory requirements, training obligations included.

Gig and platform workers are an increasingly common edge case worth flagging separately, since they don’t fit neatly into “employee” or “contractor” as traditionally understood. Where a company exercises meaningful control over how and where the work happens — a delivery hub, a shared warehouse floor, a co-located gig-worker lounge — the safer, more defensible position is to treat that space as a workplace under the Act and extend the same awareness obligations to the people working from it, rather than assuming platform-worker status alone puts them outside its scope. Regulatory guidance in this specific area is still evolving, which is exactly the kind of ambiguity worth resolving with legal counsel rather than assuming the narrowest possible reading protects you.

The Act and its Rules don’t prescribe an exact number of sessions per year in the statutory text itself — a fact several employers have historically stretched to mean “whenever convenient.” Guidance from the Ministry of Women and Child Development, and the accepted standard across compliance practitioners, closes that gap decisively: at minimum, one comprehensive sensitisation workshop per year for all staff, with new joiners trained during onboarding — commonly benchmarked at within 30 days of joining — and separate, more detailed orientation for Internal Committee members specifically.

2026 has pushed that accepted floor higher still. Multiple current compliance guides describe quarterly micro-training for all staff, supplemented by a full annual capacity-building session for the IC, as an emerging regulatory expectation — not just aspirational best practice. Managers in particular are increasingly expected to receive more frequent refreshers than general staff, given their front-line role in spotting and responding to early warning signs.

It’s worth addressing the practical objection this frequency standard usually provokes: won’t quarterly sessions just become background noise employees tune out? The evidence from organisations that have actually implemented this cadence suggests the opposite happens when it’s done well — shorter, more frequent “micro-training” sessions (fifteen to twenty minutes, focused on a single scenario) tend to land better than one long annual session precisely because they’re less likely to feel like a compliance ritual and more likely to connect to something an employee just experienced. The quarterly standard isn’t asking for four full workshops a year; it’s asking for four genuine touchpoints, which is a meaningfully lighter lift than it initially sounds.

Running a session on schedule doesn’t automatically make it compliant. Effective POSH training requires role-specific content, not a single generic deck presented to everyone from a security guard to a department head — a distinction that current compliance guidance treats as central to whether training actually satisfies the Act’s intent, not just its letter.

There’s a subtler content requirement worth naming directly, because it’s the one most decks quietly skip: training has to explain not just what harassment is, but what happens procedurally after someone reports it. Employees who understand the definition of harassment but have no idea whether a complaint stays confidential, how long an inquiry typically takes, or whether they’ll face retaliation are, in practice, far less likely to actually use the reporting system the rest of the training just described. Covering the process end-to-end — not just the definitions at the start of it — is what separates training that builds real trust in the system from training that’s technically accurate but functionally useless.

A training session that happened but wasn’t documented is, from a compliance-evidence standpoint, nearly indistinguishable from one that never happened at all. Attendance registers, session dates and content summaries, and completion certificates aren’t bureaucratic overkill — they’re what evidences compliance and directly populates the annual report due to the District Officer by 31 January each year.

Practically, this means treating your training calendar and your documentation system as one process, not two. A session that happens without a signed attendance register and a dated content summary creates work later that a five-minute logging habit would have avoided entirely — and it’s the difference between a training programme that looks compliant and one that can actually prove it, under pressure, on short notice.

A simple, low-effort system tends to outperform an elaborate one that nobody maintains consistently. A shared folder organised by financial year, with a subfolder per session containing the attendance sheet, a one-page content summary, and the date and trainer name, is enough to satisfy most audit requests — the goal is consistency across every session, not sophistication in any single one. The organisations that struggle most in an inspection aren’t usually the ones with a messy system; they’re the ones with no system at all, where reconstructing “did this happen and when” becomes a scramble through old calendar invites and half-remembered meetings.

Non-compliance under Section 26 of the Act — which covers failure to constitute an IC, failure to conduct training, or failure to act on a complaint — carries a fine of up to ₹50,000 for a first offence. Repeat violations aren’t just a doubled fine on paper; they carry real escalation risk, including cancellation or non-renewal of the business licence or registration required to operate.

The genuinely new development for 2026 is the shift from complaint-triggered to proactive enforcement. Labour commissioners in multiple states, Rajasthan among the most active, have begun conducting workplace inspections that specifically check for POSH compliance — meaning an organisation can now be flagged for a training gap even where no complaint has ever been filed. That changes the risk calculation significantly: “we’ve never had an incident” is no longer a meaningful shield, because inspections check for the existence of the compliance programme itself, not just its track record.

Beyond the direct financial penalty, organisations face legal proceedings, regulatory scrutiny, and reputational damage that outlasts the fine itself — and, since mid-2025, a visible line item in the company’s own Board Report that investors, clients, and prospective senior hires can all see. The fine is the smallest part of the actual cost.

There’s a second-order enforcement risk worth flagging that’s easy to overlook: a training gap discovered during an unrelated inspection or audit — a labour compliance review triggered by something entirely separate, like a wage dispute — can surface a POSH finding as a side effect, not the original purpose of the visit. Compliance gaps rarely stay contained to the specific issue an inspector originally came to check. Treating POSH training as isolated from your broader statutory compliance calendar, rather than as one line item within it, is a common blind spot that this kind of cross-contamination risk should close.

A handful of misconceptions about training specifically — as distinct from broader POSH compliance — come up repeatedly enough to be worth addressing directly. Most of them share a common thread: reading the absence of an explicit rule as permission, rather than checking what the accepted standard actually requires.

None of these myths persist out of bad faith — most come from a genuine, reasonable-sounding reading of a statute that leaves some specifics to guidance rather than hard-coding every number. The fix isn’t cynicism about the law’s intent; it’s simply checking the accepted standard rather than assuming the most convenient interpretation is the safe one.

Answer five quick questions honestly and this will tell you where your programme actually stands — not just a score, a specific read on what to fix first.

Everything in this article points to the same practical conclusion: running compliant POSH training in 2026 requires someone in the organisation who genuinely understands the legal framework — not just someone who can book a conference room and run a slide deck once a year. That’s a distinct, learnable skill set, and it’s increasingly one employers actively look for, whether they’re hiring an HR generalist, appointing an IC member, or engaging an external trainer.

A structured POSH certification gives the person running this programme the legal literacy to design role-specific content, structure a defensible training calendar, and build the documentation habits that hold up under an inspection — rather than reconstructing all of it from scattered blog posts under pressure, after a gap has already been flagged.

There’s also a quieter shift worth naming: organisations are increasingly distinguishing between someone who can present a slide deck and someone who’s certified to actually design a compliant training programme end to end — the curriculum, the cadence, the documentation system, and the judgment to know when a generic template needs to be adapted for a specific workforce. That distinction shows up in hiring for dedicated compliance and HR roles, and it shows up just as clearly when a company is choosing which external trainer or consultant to engage for its annual sessions. A verifiable credential answers the “why should we trust this person’s programme design” question before it’s even asked.