POSH Compliance for GCCs in India: Building a Local Framework Within a Global Ethics System

Consider a hypothetical complaint. An employee in an Indian Global Capability Centre reports sexual harassment through the company’s global hotline. Her reporting manager is overseas. Global employee relations interviews her and two witnesses, collects messages held outside India and begins preparing findings. The Indian Internal Committee learns about the matter weeks later.

Nobody intended to bypass Indian law. Yet the organisation must now decide who owns the inquiry, what can be used from interviews already conducted, and what the employee was entitled to expect when she first reported.

POSH compliance for GCCs in India needs an explicit connection between global reporting systems and the statutory process. India’s POSH Act assigns inquiry responsibilities to the competent Internal Committee (IC), or Local Committee (LC), rather than to whichever corporate investigation team receives an allegation first.[1] A global ethics framework cannot simply replace that authority.

For GCC heads, CHROs, legal leaders and global ethics teams, the work is to make the two systems function together without making the employee navigate the organisational chart.

Why a GCC needs more than an India policy annexure

Test your framework against a matrix organisation: an Indian employing entity, a foreign functional manager, shared offices occupied by several group companies, and investigators whose reporting line sits at headquarters. Add deputations, contractors, remote work, business travel and a reorganisation that changes the employer midway through a case.

The Act’s definitions of employee and workplace are broader than permanent staff inside an office; they include specified contract arrangements and places visited in the course of employment.[1] Nevertheless, overseas conduct and respondents require a fact-specific jurisdiction assessment. An Indian connection does not establish unlimited worldwide IC authority.

A global policy may protect all genders and prohibit conduct beyond statutory sexual harassment. Preserve that wider protection while clearly identifying the Act’s protection for women and its statutory route.[1] Different definitions should produce clear routing, not an argument about which policy has the better values.

Six questions when the global hotline receives the complaint first

1. Can the global inquiry continue?

It need not mean that every global activity stops. Evidence preservation, safety arrangements and logistical support can continue. Separate code-of-conduct allegations may also require investigation. But global ER should not finish deciding the POSH allegation and ask the IC to endorse its conclusion. Section 11 places the statutory inquiry with the competent committee.[1]

Agree scope and sequencing promptly. Record which team handles each allegation, who interviews whom, and how evidence will reach the IC. Avoid competing interviews or an overseas conclusion that prejudges an unfinished Indian proceeding.

2. Is a separate IC inquiry needed?

A qualifying complaint must follow the competent statutory process; a global report is not its substitute.[1] That does not require mechanically repeating every interview. The IC must own the inquiry, assess the material and provide the applicable procedural safeguards. Conciliation is a distinct statutory option before inquiry, at the aggrieved woman’s request, without monetary settlement as its basis; it is not compulsory HR mediation.[1]

3. Can the IC rely on interviews already conducted?

Existing material can inform its work, but reliance needs procedural care. Section 11 and Rule 7 require the applicable hearing safeguards and natural justice.[1][2] Obtain original records, the questions asked, interview context, translations and any corrections. Let parties meaningfully respond to adverse material and challenge discrepancies through an IC-controlled process. Recall a witness where necessary. An ER summary saying that someone was credible cannot replace the IC’s reasoning.

4. What can headquarters receive?

Section 16 restricts publication or communication of complaint and inquiry information to the public, press and media; it is not a blanket prohibition on every necessary overseas disclosure.[1] Nor does it give headquarters automatic access to the full file. Assess each recipient’s actual role, purpose, required information and applicable privacy obligations. Consent alone does not cure every confidentiality or procedural problem.

For governance, prefer restricted status information. For a necessary implementation decision, provide only the information that decision-maker needs, through a controlled route. Keep a disclosure record and prevent onward circulation.

5. Which entity and IC have jurisdiction?

Map the employing and workplace entities, locations, complainant, respondent and relevant service rules. Section 4 requires written constitution and addresses offices or administrative units in different places; a shared brand is not a blanket basis for one group IC.[1] Shared offices, deputations and intercompany reporting lines need documented assessment, not an automatic payroll-only answer.

Section 6 provides the LC route for establishments without an IC because they have fewer than ten workers, and complaints against the employer himself.[1] Identify the statutory employer rather than assuming every senior manager fits that description. For foreign respondents or witnesses, examine employment relationships, territorial connections and practical participation or enforcement limits with counsel. Do not promise powers the IC cannot exercise.

6. Which clock starts when?

Keep distinct dates rather than treating hotline receipt as a universal trigger for every deadline:

• Complaint period: section 9 provides three months from the incident, or last incident in a series. The committee may extend this by up to another three months where the statutory conditions are met, recording reasons.[1]
• Service and response: under Rule 7, the committee sends the complaint copy within seven working days of receipt; the respondent’s reply is due within ten working days of receiving the specified documents. Read this with section 11 and applicable service rules.[2]
• Inquiry: section 11(4) requires completion within ninety days. It does not expressly make every report to a global hotline the start date. Record complaint receipt, routing and inquiry commencement; obtain advice where the legally relevant trigger is disputed.[1]
• Report and action: section 13 requires the report within ten days of inquiry completion and action on recommendations within sixty days of receipt by the employer or District Officer.[1]
• Appeal: section 18 provides ninety days from the recommendations for the appeal it covers.[1]

Internal routing targets should be quicker than statutory outer limits. A company cannot responsibly use its own handoff delay as a reason to postpone attention to the complaint. Preserve the original reporting date even where the statutory status of that first communication requires assessment.

Six operating layers for a workable GCC framework

The following is a recommended operating model, not a claim that the law prescribes this particular organisational design.

1. Governance architecture

Maintain an entity-and-site map linked to valid constitution orders, membership and contacts. Section 4 specifies a senior woman Presiding Officer, at least two employee members, an eligible external member, at least half women, and nominated terms not exceeding three years.[1] Check eligibility, vacancies and conflicts when members transfer, resign or change roles. Rule 7 also requires at least three members, including the Presiding Officer or Chairperson, when conducting the inquiry.[2]

Recheck the map after acquisitions, new offices, shared-service changes and reorganisations. Central coordination can maintain standards and resources; it should not turn a regional HR leader into an appeals authority over IC findings.

2. Reporting channels that connect

Give IC email, local HR, managers, the hotline, ethics and ER a common routing protocol. Conduct describes multilingual incident reporting and routing workflows.[4] If used alongside a global hotline, test the handoff to the appropriate local IC; do not assume an existing integration or let a second reporting tool create a second intake queue. Intake staff should recognise a possible India POSH matter, preserve the account, check conflicts and arrange competent referral. They should not screen out the merits before the IC can consider it.

Explain to the employee who will contact her, what is being shared and what the statutory process involves. Section 9 requires a written complaint and reasonable assistance where the woman cannot make it in writing.[1] Anonymous intelligence may warrant safety or broader conduct responses, but it is not automatically a procedurally complete statutory complaint. Do not promise an entirely anonymous inquiry when fair notice and participation may require identification.

3. Ownership, including interim measures

Name an Indian employer-side owner for facilities, attendance support and implementation, while keeping adjudicative decisions with the committee. Section 19 assigns employer duties to support the inquiry and provide information and facilities.[1]

During an inquiry, section 12 permits specified recommendations on the woman’s written request, including transfer and additional leave up to three months; Rule 8 addresses removing the respondent’s performance-reporting role.[1][2] Translate the recommendation into actual controls: who changes the reporting line, approves leave or prevents an overseas manager from rating the employee?

Remote-working adjustments or communication restrictions may also need consideration under applicable policy and advice. Document their basis and review them. Interim protection is not a finding of guilt. Indian HR, the global manager, legal and the disciplinary authority should know their respective responsibilities, deadlines and escalation route.

4. Evidence and cross-border information

For cross-border investigations, preserve originals and metadata before accounts close or retention settings delete messages. Record provenance, custodians, collection dates, versions and transfers. Keep an audit trail of access and downloads. A screenshot without context may omit the surrounding conversation.

Plan interviews around time zones and participation needs. Decide how recording, transcription and translation will work lawfully. Preserve originals alongside translations, identify the translator and allow corrections where meaning is disputed. Automated transcription should be checked before it becomes an inquiry record.

Agree access permissions, retention and legal holds with legal, privacy and IT teams. This article does not prescribe a universal localisation rule or treat all Indian data-protection provisions as already operative. Assess applicable requirements and their commencement at the time of processing. Global evidence systems should support the IC’s access and independence rather than leave it dependent on a curated headquarters summary.

5. A procedural record that explains decisions

Maintain receipt and routing dates, jurisdiction assessment, conflict checks, notices, evidence shared, questions and responses, and the reasons for procedural choices. Record deviations and remedial steps honestly. Preserve findings, recommendations, delivery acknowledgements and implementation evidence.

A polished final report cannot explain away missing hearing opportunities. Where both parties are employees, section 11 expressly provides for hearing them and making findings available so they can make representations before the committee.[1] Build that stage into the workflow instead of discovering it after global management has announced a decision.

Keep global and Indian records consistent about facts, scope and status. Where separate allegations produce different findings, explain why. This matters when the organisation must account for its process in appeals, litigation, audits or acquisition diligence; it does not guarantee immunity from challenge.

6. Leadership visibility without case-file access

Give authorised leaders a restricted governance view: IC validity, learning coverage, case ageing against the correct legal milestones, pending recommendations and annual-report completion. Review repeat risk patterns without exposing complainants or inviting leaders to reassess credibility.

Sections 21–22 and Rule 14 govern annual reporting, including complaint and disposal information and cases pending beyond ninety days.[1][2] A governance dashboard is not a substitute for those obligations. Suppress or combine small categories where an entity, location or distinctive allegation could identify someone. Set a recurring review cadence, such as quarterly, as an operating choice rather than a supposed statutory frequency.

Six failure patterns to test before a live complaint

These are diagnostic scenarios, not claims about how frequently GCCs fail.

1. The IC learns late. A hotline case stays in global triage. The risk is lost time, delayed protection and uncertainty over procedural dates. Test the handoff with a sample report.
2. ER substitutes for the IC. Headquarters supplies findings for signature. The risk is an inquiry without independent statutory decision-making. Define supporting and deciding roles separately.
3. Channels contradict each other. An employee hears that the hotline is sufficient while local HR asks her to start again. The risk is confusion, repeated disclosure and missing records. Provide one explained referral journey.
4. Headquarters requests every document. Distribution expands because leaders want visibility. The risk is unnecessary disclosure and influence over pending findings. Require a purpose-specific access decision.
5. The committee survives only on paper. A reorganisation leaves expired appointments or vacancies. The risk is a challenge to constitution or participation. Link organisational changes to an IC review.
6. An overseas participant is treated as unreachable. Scheduling difficulty becomes an unexplained absence. The risk is incomplete evidence or unfair procedure. Document efforts, assess authority and follow applicable safeguards rather than assume non-participation proves anything.

Two illustrative worked examples

A. Connecting a global hotline with the Indian process

Imagine a GCC where a hotline vendor sends every complaint to regional ER. The India location is a searchable field but has no routing consequence. The opening scenario could occur even if everyone follows the existing global workflow.

A proposed redesign would flag the India connection, preserve the original submission and send a restricted alert to the designated competent recipient after conflict checks. The IC would assess the statutory route and control its inquiry. ER could organise overseas document collection or examine a separate conduct allegation under a recorded scope. The employee would receive a clear explanation of both processes.

Test the design using a fictional complaint against an overseas manager. Check receipt timestamps, the conflict fallback, access permissions and who can implement interim measures. Success in this exercise means the handoffs work; it is not evidence that any real case ended successfully.

B. Coverage across a large, multi-entity GCC

Imagine several Indian group companies sharing premises and HR operations. A single spreadsheet names one committee, but does not identify the constitution order covering each employer and office. Following a business transfer, one member no longer works for the appointing entity.

The proposed response starts with legal-entity and workplace mapping. Review constitution orders, eligibility and tenure; resolve gaps through properly authorised action; and publish accurate contacts. Create a routing guide for deputed employees and cases involving more than one entity. Keep central coordination while preserving each competent committee’s authority.

Test a complaint involving an employee of one entity and a manager of another. Record the jurisdiction reasoning and how cooperation will work. Do not silently pool all case files into a group repository.

Both examples are hypothetical operating exercises, not anonymised Ungender client cases or claims of delivered outcomes.

Train each role for the decisions it actually makes

Section 19 and Rule 13 require awareness and committee learning; a GCC should adapt delivery to each audience.[1][2]

Indian employees need to understand conduct, reporting options, the IC and what follows a hotline report. Local managers need to receive a concern without testing its credibility, promising secrecy or attempting independent mediation. Global managers need to understand India-specific routing and their role in implementing protective measures across reporting lines.

Global HR and ER need practice separating statutory and code-of-conduct scopes, preserving evidence and avoiding premature conclusions. Conduct’s e-learning offer includes multilingual, self-paced modules.[4] Use these for accessible baseline learning, then agree tailored India and global manager, HR and ER orientation rather than assume a generic module covers these handoffs. Advanced IC learning should cover jurisdiction, conflicts, questioning, documentary contradictions, cross-border participation, natural justice and reasoned reporting. Use realistic exercises and revisit them when the organisation changes. An attendance certificate cannot tell you whether someone can handle the opening scenario.

Choosing a POSH partner for GCCs

A GCC does not need a POSH vendor who simply delivers activities. It needs a partner who can translate between Indian law, global governance expectations and the organisation’s operating reality.

Assess procedural judgment, multi-entity experience, communication with global teams, independence, quality assurance and capacity to support multiple locations. Ask how the partner handles conflicts, urgent referrals, overseas evidence and a disagreement with headquarters. Review technology access controls and security evidence rather than accepting certification logos or guaranteed outcomes.

Ungender’s public services cover policy and IC constitution, external-member support, training, audits and case guidance.[3] For a GCC engagement, define a scope that connects policy harmonisation; entity mapping, renewals and conflicts; employee, manager, global-HR and advanced IC learning; and external-member procedural support through conciliation, inquiry and reporting. Include advice on interim measures and implementation without transferring the committee’s decisions to the adviser.

Agree timeline monitoring, quarterly governance reviews, annual compliance reporting, applicable SHe-Box support, audits and continuing reviews as explicit deliverables. Do not assume a generic retainer includes every item.

Conduct’s public product page describes case management with role-based IC access, inquiry calendars and reminders, evidence management and audit trails.[4] In a GCC demonstration, test entity-specific permissions, evidence separation and the distinct statutory timelines rather than assume these match your structure by default. Verify configuration and contractual scope; technology should not decide credibility, replace statutory judgment or promise a legally unchallengeable result.

Ten questions for your next GCC governance review

1. Do all global reporting channels route possible India POSH concerns promptly to a competent, conflict-checked recipient?
2. Are all employing entities and relevant sites mapped to valid IC arrangements or the applicable LC route?
3. Are membership changes, eligibility, vacancies and nomination tenures reviewed and documented?
4. Can global ER and the IC coordinate without duplicative investigations or substituted findings?
5. Is there a cross-border evidence and confidentiality protocol covering originals, disclosure, translations and access?
6. Can an overseas manager implement interim measures through a named, accountable employer-side owner?
7. Do employees know what to expect after reporting through the global hotline?
8. Have local HR, global HR and ER been trained on the Indian statutory process and their limits?
9. Is there a reliable audit trail from first receipt through findings, recommendations and action?
10. Can leadership see governance risks without routine access to identifiable case files?

Are you an HR leader in a GCC? Write to us at contact@ungender.in to explore how Ungender can partner with your team on PoSH governance in India.

Pallavi Pareek, Founder, Ungender and Conduct

Sources

[1] https://www.indiacode.nic.in/bitstream/123456789/2104/1/A2013-14.pdf — act
[2] https://shebox.wcd.gov.in/assets/uploaded_content/SH_Rules,_20132.pdf — rules
[3] https://www.ungender.in/services — services
[4] https://www.ungender.in/conduct-posh-compliance-platform — conduct