By S&S Co. Advocates & Solicitors · Published 27 July 2026 · Informational content, not legal advice — see our disclaimer
The Baseline: No Automatic Employer-Employee Relationship
When a company engages security, housekeeping, or facility management staff through a licensed contractor, no direct employer-employee relationship arises between the company (the 'principal employer') and the contractor's workers merely because the work happens on the company's premises. This distinction matters because vicarious liability under the Industrial Disputes Act, 1947 and general principles of the Indian Contract Act, 1872 generally attaches to the actual employer — here, the contractor — not to the principal employer, unless the principal employer has exercised a level of operational control that goes beyond simply hosting the contractor's staff.
The Contract Labour (Regulation and Abolition) Act, 1970 and, more recently, the Occupational Safety, Health and Working Conditions Code, 2020 (which consolidates and, in relevant states, replaces several older labour statutes) both proceed from this same structural premise: the contractor is the primary employer responsible for its workers' day-to-day supervision and welfare, while the principal employer carries a narrower, defined set of obligations rather than blanket liability for everything the contractor's staff do.
What the OSH Code Actually Requires of a Principal Employer
Section 6 of the OSH Code, 2020 imposes general duties on 'every employer' to keep the workplace free of hazards, comply with declared safety standards, and maintain a working environment safe for 'employees' at the establishment. Section 53 goes further and is specific to contract labour: it makes the principal employer directly responsible for the welfare facilities specified under Sections 23 and 24 of the Code — cleanliness, drinking water, latrine and washing facilities, and similar amenities — being provided to contract labour engaged at the establishment, regardless of who technically employs them.
This creates a genuinely bifurcated liability structure. The principal employer's OSH Code obligations toward contract staff are about the physical safety and welfare conditions of the workplace itself — not about supervising, disciplining, or being answerable for the personal conduct of the contractor's individual employees. Where an incident on the premises stems from a workplace hazard the principal employer should have addressed (an unsafe area, absence of required safety equipment, a defective structure), Section 53 liability can attach directly. Where the incident instead stems from the personal conduct, decisions, or state of mind of the contractor's employee — unconnected to any hazard in the premises itself — that is a different question, addressed below.
When Does Vicarious Liability Actually Attach?
Courts assess vicarious liability of a principal employer for a contract worker's conduct by looking at the substance of the relationship, not its label. The Indian Contract Act, 1872 supplies the underlying framework: Section 182 defines 'agent' and 'principal', and courts have consistently held that the true nature of a relationship — not the formal description given to it by the parties — determines whether one entity answers for another's acts. As the Supreme Court has put it in the context of agency relationships, the relevant inquiry is into the functions, responsibility and obligations actually exercised, not the contractual label attached to them.
Applied to outsourced staff, the practical question a court will ask is whether the principal employer exercised significant operational control or direct day-to-day supervision over the specific worker's tasks — as opposed to simply receiving the benefit of the contractor's general services under a facilities agreement. Absent evidence of that level of control, a principal employer is unlikely to be held vicariously liable under the Industrial Disputes Act or ordinary principles of agency for an outsourced worker's individual conduct, even though the conduct occurred on the principal employer's premises. This is precisely why maintaining a clean contractual and operational separation — the contractor supervises, trains, and disciplines its own staff; the principal employer does not — is the single most effective way to manage this exposure.
Practical Steps That Actually Reduce Exposure
Given this framework, the practical risk-management steps for any business running outsourced facility or security staff are fairly concrete. First, the contract with the service provider should clearly allocate responsibility for supervision, training, background checks, and welfare compliance to the contractor, while separately and explicitly recording the principal employer's own Section 53 welfare-facility obligations, so neither party is confused about who owes what. Second, incident response protocols matter: a principal employer that promptly arranges medical or emergency assistance, documents the incident, and escalates appropriately to the contractor demonstrates the kind of operational diligence that supports (rather than undermines) an argument against vicarious liability, since it shows the response was humanitarian and administrative rather than an assumption of the contractor's supervisory role.
Finally, where an incident potentially raises a police-reportable matter, the primary obligation to report typically rests with the direct employer (the contractor), but a principal employer that files its own factual incident report — describing what occurred on its premises, the assistance rendered, and steps taken — protects itself with a contemporaneous record regardless of how the contractor subsequently handles its own reporting obligations. None of this is a substitute for a properly drafted services agreement with the contractor at the outset; it is what makes that agreement actually defensible if something goes wrong.
Frequently Asked Questions
Does the OSH Code make a company liable for everything its security agency's staff do?
No — Section 53 of the OSH Code makes the principal employer responsible for specified welfare facilities (cleanliness, drinking water, sanitation and similar amenities) at the establishment, not for the personal conduct or individual decisions of the contractor's employees.
What actually triggers vicarious liability for a principal employer?
Courts look for evidence of significant operational control or direct supervision by the principal employer over the specific contract worker's tasks — a facilities or security services contract alone, without that level of control, is generally not enough.
Who is responsible for reporting a workplace incident involving contract staff to the police?
Primary responsibility generally rests with the direct employer (the contractor), though the principal employer may file its own incident report with the local police station if the contractor delays, particularly to create a contemporaneous factual record.
References & Further Reading
This article references the following statutes, rules and judicial decisions. Case citations link to the fuller discussion in our Legal Updates archive, verified against primary sources at the time of writing.
- Occupational Safety, Health and Working Conditions Code, 2020, Sections 6, 13, 23 and 53 — general duties of employers and specific welfare obligations of the principal employer toward contract labour.
- Contract Labour (Regulation and Abolition) Act, 1970 — the predecessor framework governing principal employer and contractor obligations.
- Indian Contract Act, 1872, Section 182 (definition of agent and principal); Bhopal Sugar Industries Ltd. v. Sales Tax Officer, (1977) 3 SCC 147, and Bharti Cellular Ltd. v. Assistant Commissioner of Income Tax, (2024) 462 ITR 247 — on courts examining the substance of a principal-agent relationship over its formal label.
- See our Employment & Labour Notable Judgments and Legal Updates — Employment & Labour archive.