Night-Shift Labour Law in India’s BPO and Call Centre Industry
Abstract
India’s business process outsourcing (BPO) and call centre industry runs largely after dark because it serves clients sitting in time zones half a world away. That single operational fact has forced Indian labour law to confront a question it was not originally built to answer: how does a legal system that once treated night work, especially for women, as inherently dangerous now regulate an industry where night work is the norm rather than the exception? This paper traces that shift through the Constitution, the Factories Act, 1948, a patchwork of state-level exemption notifications, the newly enforced Occupational Safety, Health and Working Conditions Code, 2020, and the Sexual Harassment of Women at Workplace Act, 2013, and situates it against the international framework set by the ILO’s Night Work Convention, 1990, and the accumulating medical literature on the health costs of working against the body’s own clock. It also revisits the 2005 rape and murder of a Bengaluru BPO employee returning from her night shift, a case that did more to shape Indian corporate night-shift policy than any single statute has managed since. Drawing entirely on secondary material, the paper argues that while India’s statutory framework for night-shift work has become considerably more protective on paper over the last two decades, the gap between what the law promises and what actually happens on the ground, particularly around transport, harassment redressal, and health monitoring, remains wide. The paper closes with a set of practical suggestions rather than sweeping policy prescriptions, since the latter tend to travel poorly from the seminar room to the shop floor.
1. Introduction
Walk past almost any large tech park in Bengaluru, Hyderabad, Gurugram or Pune at eleven at night and you will find it more awake than the residential colonies around it. Cabs queue at the gate, security guards check badges under floodlights, and inside, thousands of employees are on calls with customers in Ohio or Manchester who have no idea it is the middle of the night on the other end of the line. This is the basic economics of the BPO and IT-enabled services (ITeS) sector in India: it sells time-zone arbitrage, and time-zone arbitrage means someone in India has to be awake while someone in the West is at their desk.
That arrangement has been extraordinarily good for employment generation, particularly for young, English-speaking graduates in cities that otherwise struggle to absorb them, and for women, who make up a substantial share of the entry-level workforce in this sector. Call centre and BPO work was, for a certain generation of urban Indian women graduating in the early 2000s, one of the first large-scale opportunities to earn a salary comparable to their male peers straight out of college, travel independently, and build a professional identity outside the home. That is not a minor social fact, and it is worth stating before the paper turns, as it must, to everything that has gone wrong with the arrangement.
The trouble is that this arrangement collided with a body of labour law that, for most of the twentieth century, took a fairly protective and paternalistic view of night work. Section 66 of the Factories Act, 1948 simply barred the employment of women between 7 p.m. and 6 a.m., full stop, on the assumption that night travel and night work exposed women to risks the state was not prepared to regulate its way around. That assumption made a certain kind of sense in the context of 1948, when ‘night work’ typically meant a woman alone on a factory floor or walking home through an unlit industrial area; it makes considerably less sense, or at least a differently shaped kind of sense, when the ‘night work’ in question is answering a customer support call from an air-conditioned office with a guard at the gate and a company cab supposedly waiting outside. The word ‘supposedly’ matters here, and the paper will return to why.
Over the past twenty-five years, Indian labour regulation has been quietly renegotiating that old bargain. States began granting sector-specific exemptions to let IT and BPO firms employ women at night, courts weighed in on whether an outright ban was even constitutional, a shockingly violent incident in Bengaluru forced the entire industry to confront the gap between its safety rhetoric and its safety practice, and, most recently, Parliament folded the whole regulatory question into a single consolidated labour code. This paper lays out that legal and social journey in one place, connects it to the specific realities of BPO and call-centre work, and tries to be honest about where the law’s promises and the industry’s practice still don’t quite line up. It also takes seriously a dimension that a purely doctrinal account tends to skip over: night work is not just a scheduling inconvenience or a security risk, it is a documented occupational health exposure, and any account of night-shift ‘rights’ that stops at transport and harassment without mentioning sleep, metabolism and long-term illness is only telling half the story.
2. Literature Review
There is no shortage of writing on Indian labour law reform in the abstract, and a fair amount on the BPO sector’s working conditions in general, but the two literatures don’t always talk to each other very well. Labour law commentary on the four codes tends to be written by law firms for corporate clients and reads accordingly: careful, compliance-focused, and light on what workers actually experience. Sociological and HR-focused writing on the BPO sector, on the other hand, has produced a genuinely useful body of work on night-shift fatigue, attrition, and the particular social pressures placed on young, often unmarried, women working what has sometimes been called, not kindly, the ‘graveyard shift’, but it rarely engages closely with the statutory text.
A third strand, easy to overlook in a purely legal study but hard to justify ignoring, is the occupational health literature on shift work generally. The International Agency for Research on Cancer has classified night shift work involving circadian disruption as a probable human carcinogen, on the strength of accumulating evidence linking long-term night work to elevated risks of breast cancer and other conditions. Broader reviews of shift-work research describe a fairly consistent pattern: disrupted sleep architecture, metabolic and cardiovascular strain, and mood disturbance, all traceable to the mismatch between a work schedule set by a client’s time zone and a circadian rhythm that evolved around the earth’s rotation, not around service-level agreements. None of this literature is India-specific, and very little of it has been extended into Indian occupational health policy in any binding way, but it forms the backdrop against which the industry’s welfare obligations, transport, rest intervals, medical check-ups, ought to be read.
At the international law level, the ILO’s Night Work Convention, 1990 (No. 171) is the relevant benchmark, even though India has not ratified it. The Convention moved international labour standards away from the older, blunt approach of simply prohibiting women’s night work and toward a framework of health assessment, transfer rights for workers found unfit for night work, compensation reflecting the burden of night work, and access to social services, applied to night workers generally rather than to women specifically. It has attracted comparatively few ratifications worldwide, but it is frequently cited in Indian legal commentary as the normative direction domestic law has been drifting toward, even without a formal treaty obligation to do so, since the OSHWC Code’s own list of employer duties overlaps substantially with what the Convention asks of ratifying states.
Legislative-monitoring bodies such as PRS Legislative Research have tracked the drafting history of the labour codes in detail, including the point at which the central government’s own draft rules under the Occupational Safety, Health and Working Conditions (OSHWC) Code left gaps around welfare-facility standards that the Code itself expects the government to fill in later. Law-firm client alerts, meanwhile, have been the most reliable running commentary on implementation dates, since the codes sat in a strange limbo for roughly five years after being passed by Parliament before actually coming into force. Finally, journalistic and case-based material, particularly coverage of the 2005 Pratibha Murthy case discussed in Section 5 below, supplies something the doctrinal and HR literatures both tend to lack: a concrete, human account of what happens when the gap between stated policy and actual practice is at its widest. This paper draws on all four strands, statute, legislative tracking, occupational health research, and case material, to build a single narrative rather than treating ‘the law’, ‘the industry’ and ‘the worker’s body’ as three separate subjects.
3. The Legal Framework, Piece by Piece
3.1 The Constitutional Starting Point
Any discussion of night-work regulation in India eventually has to reckon with Articles 14, 15 and 16 of the Constitution, which guarantee equality before the law, prohibit discrimination on grounds including sex, and guarantee equality of opportunity in public employment. These provisions became the legal lever used to dismantle the older, protective-but-restrictive framework: if a law bars women, and only women, from a category of work purely on account of sex, without any corresponding restriction on men, that law is vulnerable to challenge as discriminatory rather than protective. Article 42, a Directive Principle, cuts the other way, instructing the state to secure just and humane conditions of work — a phrase that has been read, at different points, both to justify restricting night work and to demand that the state instead regulate its safety rather than ban it outright. The tension between these two constitutional impulses, equality on one side and protection on the other, runs through everything that follows.
3.2 The Factories Act, 1948 and Its Slow Unwinding
Section 66(1)(b) of the Factories Act, 1948 is the provision most directly at issue. It prohibited the employment of women in a factory except between 6 a.m. and 7 p.m., which as written would rule out night shifts entirely. The provision survived unchallenged for decades, in part because a large share of factory-style manufacturing genuinely did involve physically demanding or hazardous conditions where the case for restriction was easier to make.
The turning point came from the Madras High Court, which held Section 66(1)(b) unconstitutional as a violation of Articles 14, 15 and 16, on the reasoning that where the nature and hours of work are otherwise identical for male and female employees, there is no rational basis for excluding women alone from night work. That judgment did not repeal the section; only Parliament or a state legislature acting under its own amending power could do that. But it gave state governments the legal cover to issue exemption notifications carving women’s night work back into permissibility, subject to safeguards.
Karnataka is the most thoroughly documented example. In November 2019, the state’s Labour Department issued a notification permitting women to work night shifts in registered factories, citing the Madras High Court ruling directly, and attached roughly two dozen conditions: employers had to obtain written consent from each woman before rostering her for night work, could not make night shifts compulsory, had to employ women in batches of not fewer than ten with women making up at least two-thirds of the night workforce in mixed teams, had to appoint women wardens and provide separate canteen facilities, and had to arrange CCTV-monitored premises with footage retained for a minimum period. A parallel and slightly earlier exemption already existed for Karnataka’s IT and ITeS establishments specifically, which is the route the BPO sector itself actually used, since the 2019 factory notification was aimed at manufacturing rather than services. Other states, including Telangana, Tamil Nadu, Madhya Pradesh, Andhra Pradesh, Haryana, Himachal Pradesh, Odisha and Uttar Pradesh, followed with their own notifications over the following years, each carrying its own list of conditions, which is precisely the kind of regulatory patchwork that made a single national code attractive in the first place.
3.3 State Shops and Establishments Acts
Because most BPOs and call centres are registered as commercial establishments rather than factories, the more operationally relevant law for a large share of the sector has actually been the state Shops and Establishments Acts, not the Factories Act. States such as Karnataka, Tamil Nadu and Telangana amended their rules under these Acts specifically to permit night employment of women in IT/ITeS and BPO establishments, again subject to conditions around transport, security and consent, well before the equivalent factory-sector exemptions arrived. This is worth flagging because popular commentary sometimes conflates the Factories Act position with the BPO sector’s actual legal position, when in practice the Shops and Establishments route was the one the industry relied on from early on.
3.4 The Occupational Safety, Health and Working Conditions Code, 2020
The most significant recent development, and one that a study written even a year ago would have had to describe as still pending, is that the OSHWC Code, 2020 is now actually in force. It was passed by both Houses of Parliament in September 2020 and received presidential assent shortly after, but its commencement was deferred for roughly five years while the central government worked out supporting rules, a delay common to all four labour codes passed around that time. The Ministry of Labour and Employment finally notified the commencement of the OSHWC Code, along with the Code on Wages, the Industrial Relations Code and the Code on Social Security, with effect from 21 November 2025. The Central Rules that operationalise the Code’s more granular obligations followed several months later, in May 2026, at which point procedural compliance requirements such as registration, licensing formats and returns became fully functional at the central level; several states continue to notify their own rules, since labour sits on the Concurrent List and both central and state governments retain rule-making power.
Substantively, Section 43 of the OSHWC Code addresses women’s employment directly. It entitles women to be employed in all establishments and for all types of work, including work that begins before 6 a.m. or continues past 7 p.m., subject to the woman’s consent and to conditions the employer must satisfy relating to safety, security, dignity and adequate working conditions. In effect, the Code takes the state-by-state exemption regime that had built up piecemeal since the 2000s and writes a version of it into central law, removing the outright night-work bar that Section 66(1)(b) of the Factories Act had maintained on paper even after courts and states had chipped away at it in practice.
What the Code and its accompanying rules ask employers to actually provide reads, unsurprisingly, a lot like the conditions states had already been attaching to their own exemption notifications: safe transport to and from the workplace, adequate lighting extending to areas such as washrooms and parking, CCTV surveillance, the presence of women supervisors or wardens on night shifts, medical aid and reasonable rest intervals, and a functioning Internal Complaints Committee under the POSH Act. The Code also caps ordinary working hours at eight a day, down from the ceiling the Factories Act had allowed, and requires overtime to be both consented to and paid at twice the ordinary wage rate. None of this is radical by international standards, but it is a meaningful tightening relative to what the Factories Act, read narrowly, ever required.
It is worth being candid, though, about a limitation that legislative trackers flagged even at the draft-rules stage: the Code leaves a fair amount to subordinate rule-making, and the rules notified so far have not fully specified welfare-facility standards to the level of granular detail the Factories Act’s own schedules once did. A code that says employers must ensure ‘safety, security and dignity’ is not self-executing; it depends on rules, inspection capacity and enforcement culture to mean anything in practice, which is exactly the gap this paper is ultimately interested in.
3.5 The Sexual Harassment of Women at Workplace Act, 2013
If the OSHWC Code addresses the physical infrastructure of night work, lighting, transport, supervision, the POSH Act addresses what happens when that infrastructure fails to prevent harassment. Section 4 requires every employer with ten or more employees to constitute an Internal Complaints Committee (ICC) at each office or administrative unit, with a woman presiding officer at a senior level, at least two members with relevant experience or a demonstrated commitment to women’s causes, and one external member drawn from an NGO or similar body working on women’s issues; at least half the committee must be women. For a BPO with multiple shift-based locations, this is not a formality. Night-shift harassment complaints, almost by definition, tend to involve fewer witnesses, less immediate access to security or HR staff physically present at two in the morning, and a workforce more reluctant to escalate given how central the job often is to a young worker’s independence and mobility.
The Act’s practical record, though, is decidedly mixed. Commentary and case law, including the Supreme Court’s 2023 intervention insisting that ICC inquiries follow natural justice and that committees be properly constituted and trained, point to a recurring set of problems: ICCs that exist on paper but are never actually convened or trained, presiding officers unclear on procedure, and a persistent gap between the statutory three-month complaint window and the practical difficulty of a night-shift employee finding the time, privacy or confidence to use it. None of this is unique to night-shift work, but night work compounds it, since the informal social checks that operate during the day, more people around, supervisors on-site, easier transport home, are thinner after dark.
4. Case Studies in Night-Shift Safety and Harassment Law
4.1 Vishaka v. State of Rajasthan (1997): The Legal Root of the ICC System
Any case-study discussion of night-shift harassment redressal has to start earlier than the BPO boom itself, with a case that had nothing to do with call centres at all. Vishaka and Others v. State of Rajasthan arose out of the 1992 gang rape of Bhanwari Devi, a government social worker in rural Rajasthan who was attacked in apparent retaliation for her work opposing child marriage. The criminal prosecution that followed largely failed, and the incident exposed a much broader gap: Indian law in the early 1990s had no dedicated civil framework at all for addressing sexual harassment at the workplace, leaving women to rely on scattered and ill-fitting provisions of the Indian Penal Code. A group of women’s organisations petitioned the Supreme Court by way of public interest litigation, and in August 1997 a three-judge bench led by Chief Justice J.S. Verma delivered a judgment that did something Indian courts rarely do: it did not merely interpret an existing law, it wrote a temporary one.
The Court held that sexual harassment at the workplace violated the fundamental rights to equality under Articles 14 and 15, to practise any profession under Article 19(1)(g), and to life and personal dignity under Article 21, and it drew on India’s obligations under the Convention on the Elimination of All Forms of Discrimination Against Women to fill the legislative vacuum. The resulting Vishaka Guidelines required every employer to take preventive steps, to constitute a complaints mechanism headed by a woman, with at least half its members women and one third-party member from outside the organisation, and to treat sexual harassment as misconduct under service rules. These guidelines carried the force of binding law, under Article 141 of the Constitution, for sixteen years, until Parliament finally codified and expanded them as the Sexual Harassment of Women at Workplace Act, 2013.
The relevance of Vishaka to this paper is structural rather than incidental. Every Internal Complaints Committee that a BPO or call centre is required to constitute under Section 4 of the POSH Act, discussed in Section 3.5 above, traces its lineage directly to a judgment written a full eight years before the Pratibha Murthy case and more than two decades before the OSHWC Code. It is worth noting, too, that Vishaka was itself a response to institutional failure rather than institutional design: the country’s harassment-redressal architecture exists in its current form because the ordinary machinery of criminal law and service rules failed a woman in rural Rajasthan, in much the same way the industry’s later transport safeguards exist because ordinary corporate security failed a woman in Bengaluru. Legal protection for night-shift workers in India has, on this evidence, tended to arrive after a failure rather than in anticipation of one.
4.2 Pratibha Murthy and the BPO Transport Failure (2005)
No account of night-shift safety regulation for women in India’s BPO sector is complete without the case that, more than any single statute, actually changed how companies behaved: the rape and murder of Pratibha Srikanth Murthy, a 24-year-old employee of HP GlobalSoft in Bengaluru, on the night of 13 December 2005. Pratibha was picked up for her shift, which began around 2 a.m., by a man posing as her regular driver after the company’s transport desk failed to verify that the substitution had actually been authorised. She was raped and murdered, and her body was found two days later. The driver, Shivakumar, was convicted and his life sentence was later upheld by the Karnataka High Court.
What made the case a turning point rather than just a tragedy was the specific failure it exposed: HP’s own transport department reportedly knew that Pratibha had been collected by an unscheduled driver, and when she failed to report for her shift, she was simply marked absent rather than flagged as missing. In other words, the company had a transport system, a duty roster, and a database of registered drivers, exactly the kind of infrastructure that Karnataka’s later 2019 notification and the OSHWC Code both now formally require, and the system still failed at its most basic function: knowing where an employee actually was. NASSCOM, the industry’s apex body, came under public pressure in the aftermath, and its then president, who had also been HP GlobalSoft’s managing director, was named in criminal proceedings over the company’s alleged failure to ensure the safety of its night-shift transport arrangements.
The case triggered a wave of voluntary industry measures well ahead of any legal mandate: GPS tracking for cab fleets, mandatory verification calls before pickup, a second staff member (typically male) accompanying women on late drop-offs when a route involved multiple stops, and, in several companies, an outright policy against a woman being the last passenger dropped off on a route. Some of this eventually found its way into the state notifications and industry codes discussed above, though it took years, and it is difficult to avoid the conclusion that corporate practice moved faster than statute in the immediate aftermath, only for statute to formalise and generalise those practices much later through instruments such as the OSHWC Code.
4.3 The 2014 Delhi Cab-Aggregator Case and the Limits of Employer-Only Regulation
The third case study moves outside the BPO sector’s own fleet of company-run cabs to a related and increasingly overlapping problem: the app-based taxi aggregators that a growing number of night-shift employees, particularly at smaller firms that do not run dedicated transport, use to supplement or entirely replace employer-provided vehicles. On the night of 5 December 2014, a 25-year-old finance-company employee in Delhi hired an Uber cab to take her home after dinner with friends; the driver, Shiv Kumar Yadav, drove her to a secluded spot and raped her. The investigation that followed found that Yadav held no valid commercial driving badge, that Uber had never independently verified his background beyond accepting the documents he supplied, and that the company itself was registered in India merely as a technology intermediary rather than as a transport provider, a structure that had let it argue it was not directly responsible for driver conduct. Yadav was convicted on charges including rape, abduction and criminal intimidation and was sentenced to life imprisonment.
The regulatory aftermath was swift and, unlike the BPO sector’s post-2005 response, came from government rather than industry self-regulation. Delhi’s transport department banned Uber from operating in the city within days, the Home Ministry directed all states to suspend unlicensed app-based cab aggregators until they registered with local transport authorities, and Uber itself publicly committed to police verification, document verification and an in-app emergency response system across its global operations. The episode fed into the central government’s subsequent framing of app-based cab safety as a matter requiring direct regulatory oversight rather than voluntary corporate commitment, culminating years later in the Motor Vehicle Aggregator Guidelines issued under the Motor Vehicles (Amendment) Act, 2019, which impose mandatory driver verification, in-app tracking and grievance-redressal obligations on aggregators as a condition of their operating licence.
For this paper’s purposes, the case is a useful counterpoint to Pratibha Murthy rather than a repetition of it. Where the BPO sector’s transport safeguards emerged mostly from internal corporate policy shaped by public pressure, cab-aggregator regulation emerged because a state transport authority stepped in directly, banned the service, and eventually wrote binding conditions into the licences aggregators need to operate at all. That difference matters for night-shift workers specifically, since a rising share of them, especially at smaller BPOs, start-ups and vendor operations that do not maintain their own vehicle fleets, now depend on these very aggregator apps to get home after a shift, meaning their safety increasingly rests on a regulatory regime built for the taxi industry generally rather than one built with night-shift employment in mind at all.
Read together, the three cases in this section trace a single, uncomfortable pattern: each significant advance in night-shift worker protection in India, the ICC system, corporate transport protocols, and now aggregator-licensing conditions, followed a specific, well-publicised failure rather than preceding it. Subsequent incidents, including a gang-rape of a BPO employee in a moving company vehicle reported roughly a decade after Pratibha Murthy, drew explicit comparisons back to 2005 and produced the same recommendation each time: that labour authorities examine whether the employer had, in fact, provided the transport and verification safeguards it was legally required to provide. That this same recommendation keeps recurring across a thirty-year span, from Bhanwari Devi in 1992 to the present, is itself a data point about how much of the enforcement gap this paper is concerned with has actually closed.
5. Research Problem
Put simply, India now has a reasonably comprehensive legal framework covering night-shift work, women’s night employment specifically, and workplace harassment. What is much less clear, and what existing secondary literature only partially answers, is whether BPOs and call centres actually deliver on these protections day to day, or rather, night to night. Media reports of assaults on women returning from night shifts, recurring complaints about unreliable or unsafe transport arrangements, and the generally patchy record of ICC functioning all suggest that the distance between statute and shop floor is real, even if it is hard to measure precisely without primary fieldwork, which this study does not attempt.
6. Objectives
- To map the laws that apply to night-shift workers in India, from constitutional principle down to specific statutory conditions.
- To understand how the rules for women’s night work in BPOs and call centres evolved from a blanket restriction to a conditional permission.
- To examine the Occupational Safety, Health and Working Conditions Code, 2020, including its 2025–26 commencement, and its specific night-shift provisions.
- To assess how the POSH Act, 2013 is meant to function as a safety net for night-shift workers and where that mechanism tends to break down.
- To identify, from existing secondary material, the recurring problems in translating these rules into practice.
- To suggest practical, low-cost improvements rather than another round of legislative redrafting.
7. Research Questions
- What is the current legal architecture governing night-shift work in India, and how did it get here?
- Under what conditions can women be employed at night in BPOs and call centres, and how consistent are those conditions across states?
- What does the OSHWC Code, 2020, now that it is actually in force, require of employers running night shifts?
- How does the POSH Act’s complaint mechanism hold up specifically in a night-shift context?
- Where does secondary evidence suggest the gap between legal entitlement and lived experience is widest, and what would help close it?
8. Research Methodology
This is a doctrinal and desk-based study. It relies on primary legal texts, namely the Constitution, the Factories Act, 1948, the OSHWC Code, 2020, the POSH Act, 2013, and state notifications under the Shops and Establishments Acts, supplemented by secondary material such as law-firm commentary, legislative trackers, news coverage of specific state notifications and incidents, occupational health literature on shift work, and existing academic and policy writing on BPO working conditions. The case-study material in Section 4 is drawn entirely from contemporaneous and retrospective news reporting and court records as summarised in secondary sources, not from original interviews. No primary data was collected from workers or employers; this is a limitation the paper accepts rather than works around, and any claims about what actually happens in specific companies should be read as inferences from documented patterns rather than as findings from original fieldwork.
9. Scope and Limitations
The study is confined to night-shift work in the BPO/ITeS and call-centre sub-sector, not the wider universe of night work in India, since mining, health care, transport and manufacturing all raise overlapping but distinct issues. It focuses on central legislation and a small number of illustrative state notifications rather than attempting an exhaustive state-by-state comparison, which would be a study in itself. It draws on international standards, primarily the ILO’s Night Work Convention, as an interpretive benchmark rather than as binding law, since India has not ratified that Convention. Because the OSHWC Code’s implementing rules are still being notified at the state level as of this writing, some of the compliance picture described here will necessarily continue to shift, and later research will need to revisit it. Finally, the health-effects literature cited here is drawn from the general occupational health field rather than from India-specific epidemiological studies of BPO workers, which remain comparatively scarce; this paper treats that scarcity itself as a finding worth flagging rather than papering over it with international data presented as if it were local.
10. Discussion: Where Law and Practice Diverge
Five patterns stand out from the material surveyed for this paper, some legal, some organisational, and one that has less to do with regulation than with basic biology.
10.1 Transport Compliance and Monitoring
First, the transport promise is the one most consistently made and most inconsistently kept. Nearly every state exemption notification and the OSHWC Code itself treat safe transport to and from work as a non-negotiable condition of night employment for women. Yet transport-related incidents involving BPO employees, particularly women travelling alone in company cabs at odd hours, recur often enough in news coverage, from the 2005 Pratibha Murthy case through to comparable incidents roughly a decade later, to suggest that ‘provide transport’ and ‘provide safe, monitored, accountable transport’ are not the same commitment, and regulators have generally been better at requiring the former than auditing the latter. It is worth noting that the specific failure in the 2005 case, an unverified substitute driver, was not a gap in the rules of the time so much as a gap in whether the employer’s own internal verification process was actually followed. That distinction matters for policy: no amount of additional statutory drafting closes a compliance gap that is really an enforcement and monitoring gap.
10.2 Internal Complaints Committee Functioning
Second, ICC functioning tends to lag furthest behind in exactly the workplaces where night shifts are most common. Larger, more established IT and BPO firms with mature HR functions tend to have properly constituted and reasonably active ICCs. Smaller BPOs, vendor and sub-contracted call-centre operations, and newer entrants, which collectively employ a significant share of the sector’s night-shift workforce, are more likely to have committees that exist to satisfy an audit checklist than ones an employee would actually think to approach after an incident at three in the morning.
10.3 Expansion of Women’s Employment Opportunities
Third, the shift from a blanket prohibition to a conditional-permission regime has genuinely expanded women’s access to this segment of employment, which is worth stating plainly rather than treating the whole story as one of regulatory failure. The old Section 66(1)(b) position, taken at face value, would have made most of the BPO sector’s night-shift female workforce illegal. The move to consent-plus-safeguards, first through scattered state notifications and now through the OSHWC Code, has been a real expansion of opportunity. The critique here is not that the legal direction of travel is wrong, but that enforcement infrastructure, inspections, penalties that actually bite, and worker awareness of their own entitlements, has not kept pace with the expansion of the permission itself.
10.4 Occupational Health and Night Work
Fourth, Indian night-shift regulation remains almost entirely focused on physical safety and harassment, with comparatively little attention paid to the health dimension that international standards treat as central. The ILO’s Night Work Convention builds its entire framework around periodic health assessment and the right to transfer out of night work on health grounds; the OSHWC Code, by contrast, mentions ‘medical aid’ as one item among many welfare provisions without establishing anything like a systematic health-monitoring obligation specific to night workers. Given what the occupational health literature says about the cardiovascular, metabolic and sleep-related costs of sustained night work, and the International Agency for Research on Cancer’s classification of night shift work involving circadian disruption as a probable carcinogen, this is a real gap, not a cosmetic one. A twenty-four-year-old employee who joins a BPO for a few years before moving on may not notice the cumulative cost; an employee who stays in night-shift roles for a decade or more, which a meaningful share of the sector’s more senior operations staff do, is a different case entirely, and current Indian law has essentially nothing to say about her long-term health monitoring.
10.5 Regulatory Patchwork and Compliance Complexity
Fifth, the regulatory patchwork itself, useful as a historical staging ground, has become a source of confusion in its own right. An HR manager at a mid-sized BPO trying to work out exactly which conditions apply to her company’s night shift may need to check her state’s Shops and Establishments rules, any specific IT/ITeS night-work notification, the Factories Act position if any part of the business is factory-registered, and now the OSHWC Code and its rules, all of which cover overlapping ground with slightly different specific requirements. Larger companies with dedicated compliance teams absorb this cost easily; smaller BPOs and third-party vendor operations, which is where a good deal of actual night-shift headcount now sits given the sector’s heavy reliance on outsourced and sub-contracted centres, are the ones most likely to fall through the cracks of a system that assumes a level of compliance sophistication not every employer actually has.
11. Suggestions
- Make transport compliance auditable, not just declaratory. Requiring GPS-tracked vehicles, mandatory driver-identity verification calls before every pickup, and a grievance channel specifically for transport incidents would convert a general safety obligation into something an inspector or an employee can actually check against, rather than a box ticked once during onboarding.
- Tie ICC functioning to renewal of the sector’s own compliance certifications, such as those required under state Shops and Establishments registrations or IT/ITeS-specific night-work permissions, rather than leaving POSH compliance as a separate, lower-visibility obligation that can lapse quietly without affecting a company’s ability to keep operating night shifts.
- Publish simple, worker-facing summaries of night-shift rights, covering consent requirements, transport entitlements and ICC contact details, in the appointment letters and onboarding material the OSHWC Code already requires employers to issue, rather than burying them in a separate policy document nobody reads.
- Introduce periodic, night-shift-specific health screening as a condition of the OSHWC Code’s welfare obligations, along the lines the ILO’s Night Work Convention already models, rather than leaving ‘medical aid’ as an undefined and largely reactive obligation.
- Encourage state labour departments to publish night-shift inspection data, even in a basic form, so that the current gap between ‘law exists’ and ‘law is checked’ becomes visible rather than anecdotal, and so that repeated failures of the kind seen in 2005 and again a decade later can actually be tracked as a pattern rather than treated as one-off tragedies each time.
- Extend the same conditions-plus-consent model consistently across the Factories Act, Shops and Establishments Acts and the OSHWC Code, since the current layered history has left a slightly different vocabulary and slightly different conditions applying depending on which statute technically governs a given establishment, a source of confusion for smaller employers trying to comply in good faith.
- Require third-party vendor and sub-contracted call-centre operations, which employ a growing share of the sector’s night-shift workforce but often sit outside the direct compliance oversight of the client brand, to certify night-shift safety compliance as a contractual condition, not merely a statutory one, so that the principal company cannot treat outsourcing as a way of also outsourcing responsibility.
Conclusion
This paper set out to place India’s night-shift labour law, especially as it applies to women in the BPO and call-centre sector, in one continuous narrative rather than treating each statute, and each tragedy, as a separate and unconnected event. What that narrative shows is a genuine and fairly steady liberalisation: from an absolute night-work bar under the Factories Act, through a decade and a half of state-by-state exemption notifications shaped as much by court judgments and corporate scandal as by legislative planning, to a single consolidated code that, as of November 2025, finally puts women’s conditional right to work at night on a national statutory footing, backstopped by the POSH Act’s harassment-redressal machinery. The direction of that history is worth acknowledging on its own terms, and so is the fact that a shockingly large share of the concrete safety practices now written into law, verified transport, CCTV coverage, women wardens on night shifts, trace their origin not to a legislative committee but to the response of one company, and then an entire industry, to a single crime in December 2005.
At the same time, it would not be honest to end on that note alone. Secondary evidence, from legislative trackers, law-firm compliance alerts, occupational health research, and recurring media coverage of transport and harassment incidents separated by more than a decade but disturbingly similar in their specifics, points consistently to the same conclusion: the newest and most protective version of Indian night-shift law is still only as good as the inspection, awareness, health-monitoring and enforcement structures built underneath it, and those structures currently lag the statute book by a fair distance. Closing that gap, and extending the law’s attention beyond transport and harassment to the slower, quieter health costs of working against the body’s own clock, will likely do more for night-shift workers over the next five years than any further redrafting of the substantive rules themselves.
References
- Government of India. The Constitution of India.
- Government of India. The Factories Act, 1948.
- Government of India. The Occupational Safety, Health and Working Conditions Code, 2020.
- Government of India. The Sexual Harassment of Women at Workplace (Prevention, Prohibition and Redressal) Act, 2013.
- Ministry of Labour & Employment, Government of India. Notifications on the commencement of the four labour codes, 21 November 2025.
- Karnataka Labour Department. Notification permitting employment of women in night shifts in factories registered under the Factories Act, 1948, 20 November 2019.
- PRS Legislative Research. Draft Rules under the Occupational Safety, Health and Working Conditions Code, 2020.
- Nishith Desai Associates. Graveyard Shift in India: Employers in Bangalore/Karnataka Permitted to Engage Women Employees at Night in Factories (2019); DEI Series Part 1: Female Employees Working in Night Shift in India — Recent Updates.
- Lakshmikumaran & Sridharan Attorneys. What Changed on 21 November 2025; Central Government Notifies Commencement of All Four Labour Codes.
- EY India. New Labour Codes Implemented Across the Country, Effective 21 November 2025.
- Various state Shops and Establishments Acts and rules (Karnataka, Tamil Nadu, Telangana), as amended to permit night employment in IT/ITeS and BPO establishments.
- Secondary commentary on Internal Complaints Committee functioning and POSH Act implementation, including Supreme Court and High Court decisions on ICC procedure (2018–2023).
- International Labour Organization. Night Work Convention, 1990 (No. 171), and accompanying Night Work Recommendation, 1990 (No. 178).
- International Agency for Research on Cancer. IARC Monographs, Volume 124: Night Shift Work (2019).
- Kecklund, G. and Axelsson, J. ‘Health consequences of shift work and insufficient sleep.’ BMJ, 355:i5210 (2016).
- Vishaka and Others v. State of Rajasthan and Others, AIR 1997 SC 3011; (1997) 6 SCC 241 (Supreme Court of India, three-judge bench).
- News coverage and case records relating to the 5 December 2014 Delhi Uber cab rape case (State v. Shiv Kumar Yadav), including Delhi transport department orders banning app-based cab aggregators and the driver’s subsequent conviction and life sentence (2015).
- Ministry of Road Transport and Highways, Government of India. Motor Vehicle Aggregator Guidelines, issued under the Motor Vehicles (Amendment) Act, 2019.
- News coverage and case records relating to the rape and murder of Pratibha Srikanth Murthy, HP GlobalSoft, Bengaluru (December 2005), including Karnataka High Court appellate proceedings (2010–2011).
- Outlook India. ‘The Wolf Strikes’ (December 2005); Deccan Chronicle and Deccan Herald retrospective coverage of the Pratibha Murthy case and subsequent BPO transport-safety incidents.


