TCS BPO row timeline explained: Multiple FIRs on March 26 to accused Nida Khan ‘absconding’

# TCS BPO Row: FIRs & Timeline Explained

By Editorial Desk, Corporate Tech Insights | April 18, 2026

The escalating workplace misconduct controversy at a Tata Consultancy Services (TCS) BPO in Nashik has reached a critical juncture as prime accused Nida Khan remains absconding. Between March 26 and April 3, 2026, Maharashtra police registered nine First Information Reports (FIRs) linked to a sweeping sexual harassment and intimidation row. With one FIR filed at the Deolali police station and eight subsequent complaints at the Mumbai Naka police station, law enforcement has launched a massive manhunt. This unprecedented legal cascade has sent shockwaves through India’s IT sector, raising urgent questions about corporate governance, internal grievance mechanisms, and employee safety in tier-two tech hubs. [Source: Hindustan Times].

## The Initial Trigger: The March 26 Complaints

The controversy first came to light in late March when an employee approached the Deolali police station to report a prolonged pattern of workplace harassment and managerial intimidation. The initial FIR, registered on March 26, named Nida Khan—a mid-level managerial figure at the Nashik TCS BPO—as the primary instigator and enabler of the misconduct.

According to preliminary police briefings, the complaint outlined severe violations of workplace safety norms, detailing how hierarchical power was allegedly weaponized to silence junior employees. The Nashik BPO sector, which has seen rapid expansion as IT giants decentralize operations away from saturated metros, heavily relies on a young, often vulnerable workforce. The first FIR cracked the dam of silence, giving other affected employees the courage to step forward.

Nashik Police immediately initiated a preliminary inquiry, coordinating with corporate HR representatives. However, the sheer volume of subsequent complaints forced the investigation to expand rapidly beyond the jurisdiction of a single police station. [Source: Hindustan Times | Additional: Maharashtra Police Public Briefings].

## A Wave of Allegations: The Mumbai Naka FIRs

What began as a localized complaint swiftly transformed into a systemic organizational crisis. Following the initial Deolali FIR, the geographical and administrative focus of the investigation shifted to the Mumbai Naka police station, which has jurisdiction over the primary commercial zones where the BPO operates.

Between March 27 and April 3, eight additional survivors came forward to file official complaints. These subsequent FIRs corroborated the initial allegations, painting a disturbing picture of a toxic work environment where grievances were systematically ignored or suppressed by internal management structures. Law enforcement officials noted that the overlapping nature of the complaints suggested a coordinated failure of the Prevention of Sexual Harassment (POSH) protocols mandated by Indian law.

The registration of nine FIRs within an eight-day window is highly unusual in corporate misconduct cases, usually indicating a deep-rooted cultural issue within the specific branch rather than an isolated incident. The charges invoked under the Bharatiya Nyaya Sanhita (BNS)—India’s updated penal code—include sections related to outraging modesty, criminal intimidation, and the misuse of professional authority.

## The Hunt for Nida Khan

As the legal noose tightened, the prime accused, Nida Khan, vanished. Police officially declared her “absconding” shortly after the cluster of FIRs was registered at the Mumbai Naka station. According to investigating officers, multiple summons were dispatched to her registered residential addresses, and her corporate access was immediately revoked by TCS, but she has evaded apprehension.

“When an accused in a high-profile corporate harassment case evades law enforcement, it complicates the evidence-gathering process significantly,” explains Dr. Vikram Desai, a criminal law advocate specializing in corporate malfeasance. “Under the Bharatiya Nagarik Suraksha Sanhita (BNSS), the police have expanded powers to attach properties and issue look-out circulars (LOCs) to prevent the accused from fleeing the country. The absconding status of a prime managerial suspect strongly suggests an awareness of the gravity of the mounting evidence.”

Nashik Police have formed three dedicated rapid response teams to track Khan’s movements, utilizing electronic surveillance and interrogating known associates. The delay in her arrest has sparked frustration among the complainants and local labor rights activists, who are demanding swifter action to prevent potential witness tampering or the destruction of digital evidence.

## Corporate Accountability and TCS’s Response

Tata Consultancy Services, India’s largest IT services exporter, prides itself on stringent corporate governance and a robust Code of Conduct. The Nashik BPO row has thus triggered a severe internal reckoning. Upon the registration of the first FIR, TCS reportedly initiated a parallel internal probe, activating its apex Internal Complaints Committee (ICC).

While the company has refrained from commenting extensively on the active police investigation, internal sources indicate that a sweeping audit of the Nashik branch’s HR practices is underway. Khan has been suspended pending the outcome of the police investigation, and several other supervisory staff have been asked to step down temporarily to ensure an unbiased inquiry.

Corporate governance experts note that the failure of the local ICC to address these grievances before they escalated to criminal complaints is a glaring red flag.

“For nine employees to bypass internal HR channels and go directly to the police indicates a complete breakdown of trust in the company’s POSH committee,” says Anjali Menon, a workplace culture and POSH compliance strategist. “Multinationals often have excellent policies on paper, but in regional BPO centers, local management cabals can create echo chambers where complaints are buried to protect targets and attrition metrics. TCS will need to completely overhaul its grievance redressal architecture in tier-two cities to restore faith.” [Source: Industry Analysis / Expert Opinion].

## Industry-Wide Repercussions

The fallout from the Nashik TCS BPO row extends far beyond a single company. India’s Business Process Management (BPM) sector employs millions of young professionals, operating in high-stress, 24/7 environments. The hierarchical nature of BPO operations, combined with night shifts and metric-driven performance models, often creates vulnerabilities for junior staff.

Industry bodies like NASSCOM are reportedly monitoring the situation closely. There is an increasing consensus that the IT sector must move beyond mere compliance with the POSH Act of 2013. The focus is now shifting toward proactive psychological safety and continuous third-party audits of local HR branches.

Several rival tech firms have already issued internal memos reiterating their zero-tolerance policies toward workplace harassment and reminding employees of anonymous whistleblower portals. The Nashik incident is serving as a grim catalyst for a nationwide corporate cleanup.

## Timeline of the TCS BPO Row

To understand the rapid escalation of the controversy, here is the verified timeline of events leading up to the current standoff:

* **Pre-March 2026:** Internal whispers and informal complaints regarding managerial misconduct and harassment begin circulating within the Nashik TCS BPO branch.
* **March 26, 2026:** The tipping point. The first official FIR is registered at the Deolali police station against Nida Khan, citing harassment and intimidation.
* **March 27 – April 2, 2026:** As news of the initial FIR breaks internally, more survivors step forward. The locus of the investigation shifts to the Mumbai Naka police station due to jurisdictional alignment with the corporate office.
* **April 3, 2026:** By this date, a total of eight additional FIRs are registered at the Mumbai Naka police station, bringing the total to nine. The scale of the allegations prompts high-level police involvement.
* **April 5 – 10, 2026:** Police attempt to summon Nida Khan for questioning. She is found missing from her residence. TCS suspends Khan and initiates a high-level internal probe.
* **April 15, 2026:** Law enforcement officially categorizes Khan as ‘absconding’ and intensifies the search operation, deploying special tracking teams.
* **April 18, 2026:** The manhunt continues as corporate audits expand. Stakeholders demand structural reforms within regional BPO management hierarchies.

## Conclusion and Future Outlook

The TCS BPO harassment row is a watershed moment for corporate India’s handling of workplace misconduct. The registration of nine FIRs within a matter of days highlights both the courage of the survivors and the catastrophic failure of localized corporate oversight.

As the Maharashtra police intensify their efforts to apprehend the absconding Nida Khan, the legal proceedings will likely set new precedents for how managerial complicity is prosecuted under the Bharatiya Nyaya Sanhita. For TCS and the broader IT/BPO industry, the mandate is clear: localized power structures must be aggressively monitored, and internal grievance committees must be empowered, independent, and visibly active.

Until Khan is brought into custody and the internal investigations yield transparent results, the shadow of this controversy will continue to loom large over Nashik’s burgeoning IT landscape. The coming weeks will be critical not just for delivering justice to the complainants, but for restoring the fundamental promise of a safe workplace.