Statutory framework: fragmented definitions across labour codes and legacy Acts
India does not have a single, unified test for distinguishing employees from independent contractors. Instead, worker classification turns on a fragmented statutory landscape in which different labour laws define covered workers differently, and each definition carries its own set of employer obligations.
## The legacy framework: workman vs. employee
The Industrial Disputes Act, 1947 (IDA) governs collective labour relations and individual termination disputes. Section 2(s) defines "workman" as any person (including apprentices) employed in any industry to do manual, unskilled, skilled, technical, operational, clerical or supervisory work for hire or reward, but excludes persons employed mainly in a managerial or administrative capacity, and persons employed in a supervisory capacity earning wages exceeding ₹10,000 per month (or such higher sum as may be notified). The focus is on the nature of work and the fact of employment, not the label given to the relationship.
The IDA definition is substantive, not formalistic: courts look to whether the person works under the direction and control of the employer, whether the employer has the power to hire and fire, and whether the work is integral to the employer's business. A person styled as a "consultant" or "contractor" may still be a workman if these indicia of employment are present. The leading Supreme Court decision in Dharangadhara Chemical Works Ltd. v. State of Saurashtra (1957) established that the existence of an employment relationship is a question of fact, turning on the degree of control exercised by the principal over the manner in which the work is done.
The Contract Labour (Regulation and Abolition) Act, 1970 (CLRA) applies to establishments employing 20 or more contract labour and contractors who employ 20 or more workers. Section 2(1)(b) defines "contract labour" as a workman hired in connection with the work of an establishment through a contractor (an intermediary who undertakes work through contract labour). The CLRA imposes registration and licensing obligations on principal employers and contractors, mandates parity in certain working conditions, and empowers the government to prohibit contract labour in core or perennial activities. A worker engaged through a contractor for core functions may be deemed to be directly employed by the principal employer if the contractor's engagement is sham or if the prohibition on contract labour applies.
The CLRA came into force on 10 February 1971. Its constitutionality was upheld by the Supreme Court in Gammon India Ltd. v. Union of India (1974).
## The new labour codes: employee, gig worker, and platform worker
The Code on Social Security, 2020 (enacted 28 September 2020, not yet in force as of May 2026) consolidates nine earlier social-security enactments and introduces three new categories:
- Employee (Section 2(26)): any person employed on wages (including part-time and fixed-term employees) in or in connection with the work of an establishment, excluding apprentices and certain categories notified by the government. This definition is broader than "workman" because it does not exclude managerial or supervisory staff.
- Gig worker (Section 2(35)): a person who performs work or participates in a work arrangement and earns from such activities outside of a traditional employer-employee relationship. This category covers freelancers, on-call workers, and others who are neither employees nor platform workers.
- Platform worker (Section 2(62)): a person engaged in or undertaking platform work—work arranged through an online platform (an "aggregator") to access organisations or individuals to solve problems or provide services in exchange for payment.
The Code mandates that the Central Government or a State Government may frame social-security schemes for gig and platform workers (life and disability cover, accident insurance, health and maternity benefits, old-age protection), funded in part by a levy of 1–2% of the aggregator's annual turnover (capped at 5% of payments to workers). It also establishes a National Database of Unorganised Workers assigning each worker a unique identification number portable across state boundaries (Section 114).
The Code on Social Security, 2020 has been enacted but awaits notification of commencement by the Central Government; as of May 2026, the pre-existing Acts (Employees' State Insurance Act, 1948; Employees' Provident Funds Act, 1952; Payment of Gratuity Act, 1972; Maternity Benefit Act, 1961) remain in force.
## Practical consequence: classification is statute-specific
An individual may simultaneously be a "workman" under the IDA (entitled to pursue an unfair-dismissal claim), "contract labour" under the CLRA (if engaged through a contractor), and—once the Code on Social Security is notified—an "employee" for EPF and ESI purposes or a "gig worker" for the social-security fund. There is no single master test. Practitioners must identify which statute governs the obligation in question (termination protections, minimum wage, social insurance, safety) and apply that statute's definition and case-law gloss.
Misclassification risk is highest at the boundary between employment and genuine independent contracting. Indian courts and labour commissioners apply a multi-factor control-and-integration analysis drawn from common-law principles and ILO Recommendation No. 198 (2006), but the ultimate inquiry is whether the arrangement fits the relevant statutory definition of "workman," "employee," or "contract labour."
Source: Industrial Disputes Act, 1947 (as amended) Source: Contract Labour (Regulation and Abolition) Act, 1970 Source: Code on Social Security, 2020 — Press Information Bureau Source: Code on Social Security, 2020 — gig and platform workers (PIB)
The judicial control test: how Indian courts determine employment status in disputed cases
When the statutory definitions in the Industrial Disputes Act, 1947 (IDA) or the Contract Labour (Regulation and Abolition) Act, 1970 (CLRA) are met but the arrangement is disputed, Indian courts apply a multi-factor, fact-intensive analysis derived from decades of Supreme Court precedent. The inquiry is not whether the parties labeled the relationship as employment or independent contracting, but whether the economic and operational reality establishes the hallmarks of an employer-employee or master-servant relationship.
## The foundational control test: Dharangadhara Chemical Works (1957)
The Supreme Court established the control test as the starting point in Dharangadhara Chemical Works Ltd. v. State of Saurashtra (1957). The Court held that the prima facie test for an employment relationship under IDA Section 2(s) is "the existence of the right in the employer not merely to direct what work was to be done but also to control the manner in which it was to be done." Control over both the subject of work and the mode of performance distinguishes a contract of service (employment) from a contract for services (independent contracting).
In Dharangadhara, salt workers (agarias) were paid by output (piece-work), could hire helpers, and worked seasonally. The employer argued this proved independent-contractor status. The Court disagreed: the employer appointed supervisors who controlled the salt-production process, no salt could be delivered without supervisor approval, and the employer bore the business risk. Piece-work payment and the ability to engage assistants do not negate workman status when the principal retains supervisory control over how the work is performed and the worker's labor is integral to the principal's business.
Dharangadhara remains the leading authority. Subsequent decisions refine but do not displace its control-and-integration framework.
## Evolution: the organization (integration) test
In the decades following Dharangadhara, Indian courts adopted the integration test (also called the organization test) from English common law. A person is an employee if their work is integrated into the employer's business—part of the organization—rather than an accessory to it. A driver employed to deliver the employer's goods is integrated; a one-off delivery contractor engaged for a single project is not.
The integration inquiry asks: Is the person's work core or perennial to the establishment's operations, or incidental and temporary? Under the CLRA, this distinction is outcome-determinative: Section 10 empowers the government to prohibit contract labor in activities that are "ordinarily" part of the establishment's core work, and workers in such roles may be deemed direct employees of the principal employer if the contractor's engagement is a sham.
## The modern multifactor test: General Manager, U.P. Cooperative Bank v. Achchey Lal (2024)
In September 2024, a Supreme Court bench comprising Justices J.B. Pardiwala and Sandeep Mehta synthesized the case law in General Manager, U.P. Cooperative Bank Ltd. v. Achchey Lal & Anr. The Court outlined four overlapping tests that have evolved through Indian labour jurisprudence:
- Control test — Does the hirer control not only what work is done but how it is done?
- Integration test — Is the work integral to the employer's business or merely accessory?
- Multifactor test — Consideration of: (a) who pays wages and deducts statutory contributions (PF, ESI); (b) who supplies tools and bears business risk; (c) whether the worker performs labor for themselves or for a third party; (d) the degree of economic dependence.
- Refined multifactor test — As articulated in Sushilaben Indravadan Gandhi v. New India Assurance Co. Ltd. (2021), modern jurisprudence looks for a "sufficient degree of control" rather than absolute supervision, and weighs economic dependence, remuneration structure, and the reality of day-to-day operations over formal contractual labels.
The Court emphasized that no rigid formula applies; the determination is a mixed question of law and fact, and each case turns on the totality of the evidence. The burden of proving that a person is not an employee (i.e., is an independent contractor) lies on the party asserting that status.
## Piercing sham arrangements: substance over form
Indian courts will pierce the veil of intermediary contractor arrangements when the structure is designed to evade statutory obligations. In Steel Authority of India Ltd. v. National Union Waterfront Workers (2001) and Workmen of Nilgiri Coop. Mktg. Society Ltd. v. State of T.N. (2004), the Supreme Court held that where the contractor is a mere nominal intermediary and the principal employer exercises effective control, the workers will be deemed direct employees of the principal for purposes of the IDA and ESI/EPF coverage.
Evidence courts examine includes: appointment and wage records (who issues them?), supervision logs, disciplinary authority, the contractor's financial capacity, and whether the contractor undertakes any independent business risk. A finding that the contractor arrangement is a sham is fact-based and cannot be disturbed on appeal unless wholly unsupported by evidence.
## Practical consequence for global employers
A foreign company hiring workers in India through a local staffing agency or "contractor" must ensure the contractor is a genuine, independent business that hires, pays, supervises, and assumes liability for its workforce. Day-to-day operational control, provision of tools or workspace by the principal, or integration of the workers into core functions will tilt the analysis toward direct employment, triggering IDA termination protections, minimum-wage obligations under the Code on Wages (once notified) or legacy Acts, and EPF/ESI liability.
Misclassification risk is highest for:
- Workers performing core, perennial functions (manufacturing-line labor, IT support staff integrated into the principal's systems, customer-service roles).
- Long-tenured workers on successive fixed-term or project contracts with the same principal.
- Workers who wear the principal's uniform, use the principal's email, and report to the principal's managers, even if nominally employed by a contractor.
Practitioners should document the contractor's independence (its own business registrations, bank accounts, supervision structure, and commercial contracts with other principals) and limit the principal employer's direct supervision to output quality and timelines rather than daily task-by-task direction.
Source: Industrial Disputes Act, 1947 (as amended) — Ministry of Labour & Employment Source: Contract Labour (Regulation and Abolition) Act, 1970 — Chief Labour Commissioner
The 240-day rule: automatic deemed continuous service and the retrenchment-protection threshold
A worker who actually worked for 240 days or more within any 12-calendar-month period is deemed to have completed one year of continuous service under the Industrial Disputes Act, 1947 (IDA), regardless of interruptions or gaps in the engagement. This statutory fiction, codified in Section 25B(2)(a) of the IDA, is the gateway to retrenchment protections under Section 25F: mandatory one-month notice (or pay in lieu), statutory retrenchment compensation of 15 days' average pay for every completed year of service, and notice to the government.
The 240-day threshold operates automatically by statute—not through judicial application of the control test. It converts temporary, casual, or intermittent engagements into protected employment for purposes of termination rules, even when the parties label the relationship as "casual labour," "daily wage," "temporary," or "contract worker."
## Section 25B: the definition of continuous service
Section 25B(1) establishes that a workman is in continuous service if he is in uninterrupted service, including service interrupted by sickness, authorized leave, accident, a legal strike, a lockout, or a cessation of work not due to the workman's fault.
Section 25B(2)(a) creates a deeming fiction: where a workman is not in continuous service within the meaning of clause (1)—i.e., where his service is interrupted by breaks not covered by the exceptions—he shall nonetheless be deemed to be in continuous service for a period of one year if, during any period of twelve calendar months preceding the relevant date, he has actually worked for not less than 240 days.
The Explanation to Section 25B(2) clarifies which days count toward the 240-day threshold: the number of days a workman has actually worked includes days on which he was (i) laid off under an agreement, standing orders, or statute; (ii) on earned leave with full wages; (iii) absent due to temporary disablement from a work-related accident; and (iv) in the case of a female workman, on maternity leave (capped at twelve weeks).
## The 240-day count: calendar months, not employment anniversary
The Supreme Court held in Employers in Relation to Digwadih Colliery v. Their Workmen (1965) that the 240-day threshold does not require unbroken service. A badli (substitute) workman who worked more than 240 days with interruptions in each of the calendar years 1959 and 1960 satisfied Section 25B, because the statute converts "service of 240 days in a period of twelve calendar months into continuous service for one complete year." The employer's argument that each year's service must be 240 consecutive days was rejected: "neither before the amendments nor after, is uninterrupted service necessary, if the total service is 240 days in a period of 12 calendar months."
Importantly, the 12-month window is a rolling lookback. The relevant "period of twelve calendar months" is measured backward from the date with reference to which the calculation is made—typically, the date of retrenchment. A workman who completed 240 days of service in the 12 months before termination is deemed to have one year of continuous service even if those 240 days were spread across multiple short engagements separated by unpaid gaps.
## Consequences: Section 25F retrenchment protections triggered
Once a workman has completed 240 days (and thus is deemed to have one year of continuous service), Section 25F of the IDA prohibits retrenchment unless three conditions are met:
- One month's written notice indicating the reasons for retrenchment, or payment in lieu of notice for the notice period;
- Retrenchment compensation at the time of retrenchment, equivalent to 15 days' average pay for every completed year of continuous service or any part thereof in excess of six months; and
- Notice to the appropriate government (or specified authority) in the prescribed manner.
Failure to comply with Section 25F renders the termination illegal. The remedy is reinstatement with full back wages from the date of illegal retrenchment, as confirmed by labour courts and tribunals nationwide. Courts have held that a workman who proves 240 days of service in a calendar year is entitled to Section 25F protection, and that termination effected without the three statutory safeguards is automatically void.
## Misclassification trap: successive short-term contracts and sham "breaks"
Employers who engage workers on successive 89-day or 6-month contracts—each ending just short of the next threshold—risk a finding that the breaks are sham arrangements designed to circumvent the 240-day rule. In Haryana State Electronics Development Corporation v. Mamni and similar cases, the Supreme Court has struck down "intentional breaks of a few days given by the employer after the completion of every 89-day fixed-term contract" as mala fide attempts to avoid permanent employment obligations.
Courts apply a totality-of-service analysis: if a worker performs the same role in the same location under the same supervision across multiple "contracts," the sum of days actually worked in any rolling 12-month period is counted toward the 240-day threshold. The workman's identity-card records, attendance registers, and wage-payment slips are critical evidence. Labour courts will pierce nominal contractor arrangements and count all days worked for the principal employer if the contractor is a sham intermediary.
## Fixed-term employment exception (2018 reforms and pending Code)
The Industrial Employment (Standing Orders) Central (Amendment) Rules, 2018, which came into force on 16 March 2018, introduced a new category of fixed-term employment workman: a worker engaged on a written contract for a fixed period, entitled to proportionate statutory benefits (including gratuity after one year of service) but exempted from Section 25F retrenchment protections upon non-renewal. The 2018 Rules specify that "no notice of termination of employment shall be necessary" if the fixed-term contract simply expires without renewal.
The 2018 Rules prohibit employers from converting existing permanent workers into fixed-term employees as of 16 March 2018. However, the Rules do not eliminate the 240-day rule for workers not engaged under a compliant fixed-term written contract. A worker hired without a written fixed-term agreement—or whose fixed-term contract is found to be a sham covering a permanent arrangement—remains subject to the IDA's ordinary retrenchment-protection regime once the 240-day threshold is crossed.
The Code on Industrial Relations, 2020 (enacted but not yet in force as of June 2026) consolidates the IDA and the Industrial Employment (Standing Orders) Act, 1946, and carries forward the fixed-term-employment framework. However, the Code's text does not include the 2018 Rules' explicit prohibition on converting permanent workers to fixed-term status, raising concerns among labour advocates that employers may attempt post-commencement conversions unless states issue protective notifications.
## Practical consequence for global employers
A foreign company hiring workers in India—whether directly or through a local contractor or employer-of-record (EOR)—must track every worker's cumulative days worked on a rolling 12-month basis. Once the 240-day threshold is crossed, the worker is entitled to the full suite of IDA retrenchment protections: one month's notice, 15 days' pay per completed year, and government notification before any termination.
The 240-day rule is not limited to "permanent" employees. It applies equally to:
- Casual or daily-wage workers performing the same or similar work repeatedly across calendar months.
- Badli (substitute) workers covering for absent permanent staff.
- Workers engaged through contractors if the principal employer exercises effective control (making them deemed direct employees of the principal under the CLRA framework).
- Temporary project workers whose contracts are renewed or extended such that the total days worked in any 12-month window reaches 240.
To avoid inadvertent regularization, employers must either:
- Maintain genuine fixed-term written employment contracts compliant with the 2018 Rules (equal pay, proportionate benefits, clear contract-end dates documented in writing), and ensure those contracts are not renewed in a manner that creates a permanent arrangement in substance; or
- Accept that workers who cross the 240-day threshold become protected employees subject to Section 25F, and budget for notice, retrenchment compensation, and unfair-dismissal risk if termination becomes necessary.
Attendance and payroll records are litigation evidence. Indian labour courts routinely order production of attendance registers, ESI/EPF contribution records, and contractor payment vouchers to reconstruct a worker's actual days worked. Gaps of a few days between contracts, or payment through different contractor entities for the same work at the same site, will not prevent aggregation if the court finds continuity of employment in fact.
Gig and platform workers under the Code on Social Security, 2020: statutory definitions and aggregator obligations
The Code on Social Security, 2020 (Code No. 36 of 2020) is the first Indian national law to create statutory categories for "gig workers" and "platform workers," reflecting the rise of digital work arrangements and the expansion of the platform economy. These categories are distinct from traditional employees or contract labour, and are central to understanding compliance obligations for aggregators, online platforms, and companies hiring task-based or freelance labour at scale.
Statutory definitions:
- Gig worker (Section 2(35)) means a person who performs work or participates in a work arrangement and earns from such activities outside the traditional employer-employee relationship. This definition is broad—covering non-platform freelancers, flexible task-based workers, and others who fall outside of direct employment.
- Platform worker (Section 2(61)) is "a person engaged in or undertaking platform work." "Platform work" (Section 2(60)) refers to a work arrangement outside the traditional employer-employee relationship, where a digital intermediary (an 'aggregator') connects workers to organisations or individuals needing services or solutions, and payment is facilitated digitally. Platform workers are a subset of gig workers, distinguished by the platform-mediated nature of the engagement.
Core scheme and aggregator obligations: Sections 109–114 of the Code authorize the central and state governments to frame social security schemes for gig and platform workers addressing: (i) life and disability cover, (ii) accident insurance, (iii) health and maternity benefits, (iv) old-age protection, and other benefits. Funding for these schemes may include contributions from the government, aggregators, and workers, as specified in each scheme (Sections 109–111).
A key compliance obligation for businesses is the aggregator levy: Section 114 directs that notified aggregators—operators of digital on-demand services in sectors like ride-sharing, logistics, food delivery, e-commerce, health, content, and professional services—must contribute 1%–2% of their annual turnover (excluding taxes/levies), capped at 5% of the total amount paid to gig and platform workers. The exact contribution rate and the categories of covered services are to be set out in government notifications. The Code establishes a National Social Security Board for the Unorganised Sector to recommend and monitor these schemes, maintain a national register of gig and platform workers, and advise on benefit implementation (Section 6, Section 114).
Implementation status: Unable to confirm as of 2026-06-15.
Source: The Code on Social Security, 2020 — Ministry of Labour & Employment
Penalties for worker misclassification in India: labor inspectorate enforcement, back pay, and social-security liability
## Enforcement bodies and statutory framework
Misclassification of employees as independent contractors, gig workers, or contract labour in India is enforced primarily by statutory labor inspectorates and adjudicated by labour courts or tribunals. Under the Industrial Disputes Act, 1947 (IDA), powers of inspection and prosecution lie with the Labour Department (IDA Chapter II, Section 9). The Contract Labour (Regulation and Abolition) Act, 1970 (CLRA), Sections 28–30, empowers inspectors to demand records, enter premises, and initiate process for violations. The social security authorities (notably the Employees’ Provident Fund Organisation and ESIC) have parallel enforcement and recovery powers under their statutes (EPF Act, 1952 §§ 7A, 14, 14B; ESI Act, 1948 §§ 45A, 85, 85B).
## Consequences of misclassification
- Back pay and statutory benefits: If misclassification is found, the principal employer becomes liable for all statutory benefits retroactively. This includes back wages under IDA Section 17B, retrenchment compensation under Section 25F, gratuity (Payment of Gratuity Act, 1972), and bonus/leave as per other Codes. Labour tribunals routinely order reinstatement and full arrears (IDA § 17B) for illegally classified workers.
Source: Industrial Disputes Act, 1947
- Social security contributions (EPF, ESI): Employers must deposit unpaid provident fund and ESI contributions covering the period of misclassification, with interest (EPF Act § 7Q, ESI Act § 39(5)(a)) and penalty damages (EPF Act § 14B, ESI Act § 85B). Authorities may issue assessment orders; failure to pay can trigger coercive recovery and attachment proceedings.
Source: Employees’ Provident Funds and Miscellaneous Provisions Act, 1952
- Criminal and monetary penalties: Statutes impose fines and, for wilful or repeated non-compliance, criminal liability. Under the IDA, Section 25U imposes fines up to ₹1,000 per contravention; the CLRA, Section 25, sets fines up to ₹1,000 or imprisonment up to three months. EPF Act, Section 14, and ESI Act, Section 85, authorize imprisonment for repeat or deliberate evasion of contributions.
Source: Contract Labour (Regulation and Abolition) Act, 1970
- Inspectorate process and appeals: Inspectors may issue compliance or show-cause orders (CLRA § 28, ESI Act § 45A). Compliance failures escalate to prosecution in criminal courts or labor courts. Employers may appeal some orders to higher authority (e.g., EPF Act § 7I). IDA violation cases are adjudicated in labor courts constituted under Section 7.
## “Automatic” versus discretionary remedies
Remedies such as back pay, social security arrears, and employee status—once misclassification is proven—are generally mandatory by statute (IDA § 17B; EPF Act § 7Q). Criminal penalties and additional fines, however, often require proof of wilfulness or repeated violations and are subject to judicial discretion (IDA § 25U Explanation; EPF Act § 14AA).
## New Codes’ status
The Code on Social Security, 2020 and the Industrial Relations Code, 2020 were enacted but remain unnotified as of 2026-06-15; the above legacy statutes remain in force. Unable to confirm notification date as of 2026-06-15.
Editorial note: Only the citation URLs were updated in this section. The underlying enforcement content and statutory penalty provisions did not materially change based on current primary sources as of 2026-06-16.
Fixed-term employment in India: 2018 Amendment Rules, gratuity eligibility, and retrenchment exemption (updated for 2025–2026 Labour Codes)
The legal treatment of fixed-term employment in India underwent a fundamental change following the notification and enforcement of the Code on Social Security, 2020, effective 21 November 2025. While the Industrial Employment (Standing Orders) Central (Amendment) Rules, 2018 ("2018 Amendment Rules"), first established the fixed-term employment category and its regime of benefit parity and retrenchment exception, the unified Labour Codes—especially the Code on Social Security—now control key statutory entitlements, including gratuity eligibility.
Historical regime (2018–2025): The 2018 Amendment Rules, effective 16 March 2018, inserted a formal fixed-term employment category into the Standing Orders regime (Rule 3, Schedule I-B, para 3(1A)). This established (for central-sphere establishments, with subsequent state adoption) that fixed-term workmen must receive:
- "all benefits available to a permanent workman proportionately according to the period of service rendered by him" (3(1A)(i)),
- gratuity entitlement upon completion of one year of service (3(1A)(ii)), regardless of the standard five-year minimum in the Payment of Gratuity Act, and
- no retrenchment compensation or notice on natural expiry of the fixed-term contract (3(1A)(iii)), though Section 25F rights remained for premature termination.
Conversion of permanent posts into fixed-term posts was expressly barred for posts existing as of the commencement of the 2018 Rules.
Material change from 21 November 2025: With the Central Government’s notification of the Code on Social Security, 2020 and the repeal of the legacy Payment of Gratuity Act, 1972, gratuity entitlements for fixed-term employees are now governed by Section 53 of the Code and the Social Security (Central) Rules, 2026.
- Fixed-term employees are statutorily eligible for gratuity after completion of one year of continuous service—the five-year continuous service requirement is expressly waived for fixed-term employment. This aligns with and codifies the earlier rule introduced in the 2018 Amendment but is now rooted directly in the unified Labour Code, with updated enforcement and compliance provisions.
- The retrenchment exemption—no need for notice or retrenchment compensation on natural expiry—remains, now flowing from the Code on Industrial Relations, 2020, and supporting rules, once states notify their local adoption and effective dates.
Current compliance and risk pointers (as of June 2026):
- Employers must reference the Code on Social Security, 2020 (Section 53 and definitions) regarding gratuity for fixed-term workers, not the repealed Payment of Gratuity Act, 1972.
- All fixed-term employment contracts must remain genuinely time-bound and must not cover permanent roles in substance; repeated renewals may trigger judicial scrutiny and regularization risk, especially if engineered to avoid statutory protections.
- State-level implementation may vary; practitioners must confirm both central and relevant state notifications and rules.
Summary of 2025–2026 update: The principal regulatory base for fixed-term employment gratuity and retrenchment exceptions has transitioned from the 2018 Amendment Rules and Payment of Gratuity Act to the Code on Social Security, 2020 (from 21 November 2025). One year of continuous service now universally qualifies fixed-term employees for statutory gratuity under central law.
Source: Industrial Employment (Standing Orders) Central (Amendment) Rules, 2018 — Ministry of Labour & Employment Source: Code on Social Security, 2020 — Press Information Bureau Source: FAQs on Labour Codes — Ministry of Labour & Employment, January 2026 Source: PIB Gratuity Statement, Social Security Code 2020 Implementation
EPF and ESI coverage: statutory employee definitions, thresholds, and mandatory employer registration obligations
India’s Employees’ Provident Fund (EPF) and Employees’ State Insurance (ESI) regimes impose mandatory social security obligations on employers once statutory coverage thresholds are met, regardless of the label the employer applies to the working relationship.
EPF Act — Employee Definition and Coverage Threshold: The Employees’ Provident Funds and Miscellaneous Provisions Act, 1952 (EPF Act), applies to every establishment employing 20 or more persons, either currently or at any time in the past (Section 1(3)). "Employee" is defined in Section 2(f) as any person (other than an apprentice under the Apprentices Act, 1961) employed for wages in any kind of work, manual or otherwise, in or in connection with the work of an establishment, and who gets wages directly or indirectly from the employer, including those employed through a contractor. The Act requires covered employers to register with the Employees’ Provident Fund Organisation (EPFO), enroll all qualifying employees, and remit both employer and employee contributions as prescribed in Section 6. There is no statutory exclusion for persons styled as “consultants” or engaged through contractors if the facts show employment for wages in or in connection with the establishment’s work. This regime and its wage threshold for coverage continue under the Code on Social Security, 2020, as of June 2026 without material change to the trigger threshold.
ESI Act — Employee Definition, Threshold, and Wage Ceiling: The Employees’ State Insurance Act, 1948 (ESI Act), applies to non-seasonal factories and notified establishments employing 10 or more persons (Section 1(5)), with exceptions and higher thresholds possible under state notifications. “Employee” is defined in Section 2(9) as any person employed for wages in or in connection with the work of a factory or establishment, directly or through a contractor, but not including the classes of persons specified in the exclusions. Wage ceilings for ESI coverage (e.g., ₹21,000/month) are prescribed by separate government notification and are not set in the principal Act. As of June 2026, proposals exist to increase the wage cap, but these have not been notified; the ₹21,000/month level remains current.
In both regimes, principal employers are responsible for enrollment and contributions both for direct hires and workers engaged through contractors if those persons qualify as employees under the statutory definitions. Failure to register, enroll, or timely remit contributions triggers liability for arrears, statutory interest, damages, and penalties under the respective Acts.
Source: Employees' Provident Funds and Miscellaneous Provisions Act, 1952 Source: Employees’ State Insurance Act, 1948
Sham contractor arrangements under the OSH Code: Deemed direct employment of contract labour after the CLRA repeal
Effective 21 November 2025, the Contract Labour (Regulation and Abolition) Act, 1970 (CLRA) was formally repealed and replaced by the Occupational Safety, Health and Working Conditions Code, 2020 (OSH Code). The OSH Code serves as the new governing framework for contract labour in India, including treatment of sham contractor arrangements and deemed employment by principal employers. This represents a material change: all prior CLRA-based guidance must now be read as historical.
OSH Code—Statutory framework
- The OSH Code came into full force by Central Government notification on 21 November 2025, consolidating and repealing the CLRA along with several other central labour statutes (OSH Code, Section 143 "Repeal and saving").
- The OSH Code regulates contract labour under Chapter XI (Sections 45–61). Key changes include:
- Applicability threshold increased to 50 or more contract workers on any day in the preceding 12 months (Section 45), up from 20 under the CLRA.
- Principal employer and contractor registration/licensing requirements revised to a single license regime (Section 47, Section 48).
- Restrictions on engaging contract labour in "core activities" of an establishment, subject to Central Government notification (Section 57). Only specified exceptions allow contract labour in core functions.
- Welfare, wage, and statutory liability provisions updated; principal employer retains residual liability if the contractor defaults (Section 50).
Sham contractor arrangements and deemed employment
- OSH Code does not use the term “sham contractor” but continues the doctrine, as established in prior Supreme Court judgments, that if the contractor is a mere conduit and the principal employer exercises direct supervision and control, courts (and inspectorates) may reclassify the worker as directly employed by the principal.
- Section 61 ("Prohibition of contract labour") empowers the appropriate Government to prohibit use of contract labour in any process or operation of an establishment. Where contract labour is prohibited in a core activity, and a non-genuine (sham) contractor arrangement exists, workers may claim deemed direct employment with the principal employer for purposes of statutory rights and protections (wages, social security, retrenchment).
Transitional and litigation practice
- The OSH Code’s repeal and savings clause (Section 143) preserves actions and rights accrued under the CLRA prior to commencement. Ongoing litigation or claims under the CLRA as of 21 November 2025 will be adjudicated per the repealed statute, but all new arrangements and compliance must conform to the OSH Code.
- Core litigation evidence—pay slips, supervision records, contractor’s business independence—remains critical to establishing sham contractor status for deemed employment.
Practical impact for global and domestic employers
- Foreign and Indian companies using contract workers must now comply with the OSH Code’s higher thresholds and stricter rules on core activities and licensing.
- Engaging contract labour for core activities (absent a valid exception) exposes the principal employer to retroactive liability for deemed employment and statutory benefits under the OSH Code and related statutes.
Summary of material change
- CLRA has been repealed. All contract labour regulation after 21 November 2025 is under the OSH Code.
- Employers should review contract labour engagements for compliance with new thresholds, registration, and core activity prohibitions, and monitor Central/State notifications on core activities and contract labour exemptions.
Source: Occupational Safety, Health and Working Conditions Code, 2020 — Ministry of Labour & Employment Source: OSH Code, Section 143 — Repeal and saving Source: Ministry of Labour & Employment — Notifications (OSH Code)
Unorganised workers: statutory definition, registration, and social security coverage (Unorganised Workers’ Social Security Act, 2008 and Code on Social Security, 2020)
The definition and treatment of “unorganised workers” is a critical but often-overlooked dimension of worker classification in India, especially as the majority of the Indian workforce is outside the formal payroll sector.
## Statutory definition — Unorganised Workers’ Social Security Act, 2008 Section 2(m) of the Unorganised Workers’ Social Security Act, 2008 (UWSSA) defines an “unorganised worker” as a home-based worker, self-employed worker, or wage worker in the unorganised sector, but excludes regular government employees, employees of public sector undertakings, and workers covered by existing social security laws (e.g., the Employees’ Provident Funds and Miscellaneous Provisions Act, 1952, or the Employees’ State Insurance Act, 1948).
The “unorganised sector” (Section 2(l)) is defined as any enterprise (excluding government departments/establishments and PSUs) that employs less than ten workers, and includes self-employed persons. This captures the vast number of micro, home-based, agricultural, and small-scale enterprises not covered by the principal social-insurance statutes.
## Key compliance requirement — Registration and benefits Section 10 requires that every unorganised worker shall be eligible for social security benefits subject to registration as specified by the Central or State Government. Section 10(3) requires local self-government institutions to facilitate registration. Section 3 empowers the central government to formulate social security schemes for life and disability cover, health and maternity, old age protection, and other benefits; actual delivery is through central- or state-notified schemes, often with budget limitations.
Employers of unorganised workers are not subject to the extensive payroll, record-keeping, and contribution requirements of the EPF and ESI Acts, but may be responsible for compliance with state sectoral minimum wage notifications, certain safety requirements, and any industry-specific schemes. Misclassification risk remains if an employer intentionally splits workforces to avoid crossing the ten-worker threshold or mislabels covered wage workers as self-employed.
## Transition to the Code on Social Security, 2020 The Code on Social Security, 2020, not yet in force as of June 2026, repeals the Unorganised Workers’ Social Security Act, 2008, but retains the core definition and mandate for central and state social-security schemes. It expands coverage to gig and platform workers but preserves the framework for self-employed and home-based unorganised workers (Code, Sections 2(86), 109–114). Practitioners should monitor the notification date and subsidiary rules to confirm compliance triggers.
Source: Unorganised Workers' Social Security Act, 2008 (Ministry of Labour & Employment) Source: Code on Social Security, 2020 (Ministry of Labour & Employment)
Who is excluded as 'managerial or supervisory'? The Section 2(s) test and statutory wage cap under the Industrial Disputes Act, 1947
Section 2(s) of the Industrial Disputes Act, 1947 (IDA), defines "workman" for the purposes of unfair-dismissal, retrenchment, and other statutory protections—but carves out two distinct exclusion categories: (1) those employed mainly in a managerial or administrative capacity, and (2) those employed in a supervisory capacity who draw wages above a statutory threshold set by government notification.
1. Managerial or Administrative Exclusion Any person employed mainly in a managerial or administrative capacity is excluded from the IDA's protections. This is determined by the primary nature of the actual job duties (not the job title given by the employer). Courts examine whether the employee has substantial policy-making, disciplinary, or hiring/firing authority.
2. Supervisory Exclusion and Wage Cap For supervisory employees—those directing or overseeing junior staff—the exclusion depends both on job function and wages. Section 2(s) draws the line: supervisory staff are only excluded if their wages exceed the limit prescribed by notification under the Act. This wage cap was initially set at ₹1,600 per month, and later raised to ₹10,000 per month by S.O. 1440(E) (published in the Gazette of India on 17 May 2010). As of 2026-06-16, no further increase has been notified from a primary-authority source. Thus,
- A supervisor earning above ₹10,000/month is not a "workman"—IDA protections do not apply.
- A supervisor earning at or below ₹10,000/month remains a "workman" for IDA purposes, provided their duties are predominantly supervisory and not managerial/administrative.
Both the exclusion and the wage threshold focus on substance over title. Where a worker’s duties mix supervisory and clerical/manual functions, Indian courts emphasize the dominant nature of the job. An employee who mainly performs non-supervisory work may still qualify as a workman, regardless of a “supervisor” job title, unless the real role fits the statutory exclusion.
Practical impact: Employees falling within these exclusions do not receive IDA protections on retrenchment, closure, or unfair dismissal. They may be dismissed according to contract and general law, but not under the special remedies for “workmen” (e.g., reinstatement, statutory notice, and retrenchment compensation). Employers must factually document why an employee is managerial or supervisory and above the wage threshold to defend any exclusion.
Source: Industrial Disputes Act, 1947 – Section 2(s), as amended
When is a worker a genuine independent contractor? Statutory exclusions, Supreme Court multi-factor test, and practical indicators
Indian labour law does not expressly define "independent contractor"—the status is instead inferred from the absence of an employer-employee relationship under core labour statutes and clarified through Supreme Court case law. Practitioners must distinguish between an employee (protected by statutes like the Industrial Disputes Act, 1947 and the Employees' Provident Funds and Miscellaneous Provisions Act, 1952) and a worker who falls genuinely outside these regimes as a contractor.
Statutory exclusions:
- The Industrial Disputes Act, 1947 (IDA), Section 2(s) defines “workman” as a person employed in any industry to do work for hire or reward, under employment terms of manual, skilled, technical, clerical, or supervisory character. It excludes those in managerial/administrative roles and does not encompass persons contracted at arm's length for genuinely independent services. The Employees’ Provident Funds Act, 1952, Section 2(f) defines “employee” as anyone employed for wages in or in connection with the work of an establishment; a self-employed professional or business-to-business service provider typically falls outside this scope unless facts show employment in substance.
- The Contract Labour (Regulation and Abolition) Act, 1970 (CLRA) governs “contract labour”—workers hired and supplied to a principal employer by a contractor—but does not apply to genuinely independent businesses providing services under commercial terms outside day-to-day supervision or integration into the principal’s business. The distinction is not always clear from statutory text and is sharpened by case law.
Supreme Court multi-factor test: The Supreme Court, particularly in Workmen of Nilgiri Coop. Mktg. Society Ltd. v. State of Tamil Nadu (2004), synthesizes decades of jurisprudence into a practical, fact-driven test. The Court reaffirms that the true relationship depends on the full range of facts, looking for (see Nilgiri at paras 31, 36, 41):
- Degree of control and supervision: Does the principal control only the results, or also the manner of performance? A right of direct supervision, not just quality control, points to employment (Dharangadhara principle).
- Integration: Is the individual’s work an integral part of the business (suggesting employment), or ancillary? Para 36, Nilgiri.
- Economic dependence and business risk: Who supplies tools, sets working hours, and bears entrepreneurial risk? A contractor who controls their own hours, tools, and risk of loss (and can substitute workers) is less likely to be an employee. Nilgiri, para 41.
- Remuneration structure: Is payment made as wages/salary (periodic, regardless of results) or as project/lot-based fees against invoices? Salaried, regular payment with deductions for benefits signals employment; payment per assignment, without statutory deductions or benefits, favors contractor status (but is not conclusive).
- Exclusivity and substitution: Employees typically cannot substitute; genuine contractors can provide their own staff or substitute performance. Nilgiri, para 41.
The Court cautions that contracts and business registration are not definitive: "the substance of the relationship, not the nomenclature the parties give it, controls" (see Nilgiri, para 31).
Practical indicators
- Practical evidence favoring contractor status (not determinative in law): GST registration, invoices raised for services, income reported under "business/profession" in tax returns, work for multiple clients, no access to leave/pension, and ability to hire staff or subcontract work.
- If the relationship looks like ongoing, exclusive service managed by the principal, courts may find employment status even if titled "consultant" or "service provider."
Summary for practitioners: The most reliable defense against misclassification is substantive evidence that the principal does not control daily work, that the worker is not economically dependent, and that their work is not essential to the principal’s immediate business objectives. Courts will examine actual work practices, payment records, business risk, and operational independence. Indian law does not provide a checklist—each case turns on its facts.
Source: Industrial Disputes Act, 1947, Section 2(s) Source: Workmen of Nilgiri Coop. Mktg. Society Ltd. v. State of Tamil Nadu, 2004 (paras 31, 36, 41) Source: Employees’ Provident Funds and Miscellaneous Provisions Act, 1952, Section 2(f)
Who is a 'principal employer' under the Contract Labour Act? Statutory definition and group-entity coverage
The question of who qualifies as a “principal employer” is central to worker-classification analysis and statutory compliance when engaging contract labour or staffing arrangements in India. The definition governs who must register under the Contract Labour (Regulation and Abolition) Act, 1970 (CLRA), who is liable for wage and welfare obligations of contractor-supplied workers, and where statutory risk falls in group-company or site-owner scenarios.
Statutory definition—Section 2(1)(g) CLRA: The CLRA expressly defines “principal employer” in Section 2(1)(g):
- In the case of a government or local authority establishment, it is the head of the department or office.
- In a factory, it is the owner or occupier of the factory, and where a manager has been named under the Factories Act, 1948, that manager.
- In a mine, it is the owner or agent, and where a manager has been appointed under the Mines Act, 1952, that manager.
- In any other establishment, it is the person responsible for the supervision and control of the establishment.
The “principal employer” is always the end-user— the party for whom contract labour actually performs work on site— not the contractor or intermediary supplying the labour.
Implications for group entities and premises owners: Where multiple group companies occupy or operate within the same physical site (e.g., a multinational with Indian subsidiary, joint venture, or third-party service partners), the statutory principal employer for contract labour is the legal entity that exercises direct supervision and control over day-to-day operations at the establishment where the contract workers are deployed, not an unrelated group affiliate or a distant foreign parent. Courts and inspectorates regularly pierce formal corporate separateness for CLRA purposes, looking to the substantive reality of who directs the workers and benefits from their labor.
If a site owner (such as an IT park or factory landlord) merely leases space but does not directly control daily workplace activities, it is typically not the principal employer for contract workers engaged by tenant companies. The company directing and supervising the contract staff bears registration, wage, and welfare-board responsibility. However, if the owner provides core site services (security, sanitation, technical maintenance) using contractors, it becomes the principal employer for those service contractors’ staff.
Consequences—registration and liability:
- Registration and licensing: Every principal employer engaging 20 or more contract labour must register the establishment under Section 7, while each contractor supplying 20+ contract workers must hold a valid license (Section 12).
- Wages and welfare: Section 21 imposes direct wage-payment obligations on the principal employer: if the contractor fails to pay wages, or pays late or less than statutory minimums, the principal employer is required to pay and may recover the amount from the contractor. Welfare and canteen facilities must also be provided by the principal employer where applicable.
- Statutory liability attaches regardless of inter-corporate agreements. Attempting to allocate risk or payroll responsibility to a separate group entity via contract does not defeat the statutory regime. Inspectorates and labour courts focus on actual control and benefit.
Summary for practitioners: When engaging contract staff in India—whether via staffing agency or intra-group arrangement—the entity receiving services and exercising effective control on site is the “principal employer” for CLRA registration and statutory liability. Corporations must not assume a distant group company or vendor can shield them from wage, social security, or regularization claims by contract labour deployed on their premises.
Source: Contract Labour (Regulation and Abolition) Act, 1970, Section 2(1)(g) Source: Factories Act, 1948
Who qualifies as an employee under the Code on Wages, 2019? Statutory definition, scope, and exclusions
The Code on Wages, 2019 (Act No. 29 of 2019), enacted on 8 August 2019, consolidates India’s principal wage-related statutes—namely, the Minimum Wages Act, the Payment of Wages Act, the Payment of Bonus Act, and the Equal Remuneration Act—under a uniform legislative scheme for the first time. The Code’s key novelty is its broad, sector-agnostic statutory definition of "employee."
Statutory definition: Section 2(k) of the Code defines “employee” as any person—other than an apprentice engaged under the Apprentices Act, 1961—employed on wages by an establishment, either directly or through a contractor, to do any skilled, semi-skilled, unskilled, manual, operational, supervisory, managerial, administrative, technical or clerical work, whether the terms of employment are express or implied. This formulation deliberately covers all types of workers engaged for wages, regardless of job function, hierarchical status, or contractual channel. (Section 2(k))
Scope and application: Section 1(4) makes the Code applicable to all employees and establishments (including contractors), with the only express exclusions being (a) employees in the armed forces, (b) apprentices under the Apprentices Act, and (c) notified public-office holders. The intent is to extend core wage protections and minimum-wage and pay-period obligations to all establishments across sectors, replacing schedule- or sector-specific limitations in earlier law. Sections 3–5 establish a minimum-wage framework of universal application, subject to these exclusions. (Sections 1(4), 2(k), 3–5)
Employer status and contractor arrangements: The Code explicitly treats principal employers as "employers" for staff supplied through contractors (Section 2(l)). If the facts show wage employment in or in connection with the operations of the establishment, the worker comes within coverage, regardless of contractual label. (Section 2(l), 2(k))
Practical exclusions and interpretive cautions: The Code does not define or directly address emerging categories such as gig or platform workers; coverage will depend on whether the arrangement meets the “employed on wages” threshold. Genuine independent contractors, as delineated in case law (see, e.g., Workmen of Nilgiri Coop. Mktg. Society Ltd. v. State of Tamil Nadu, 2004), fall outside the statutory definition if not employed for wages or subject to the employer’s control. This is an inference based on the statutory text and existing Supreme Court principles, not explicit Code language.
Effective date: The Code’s text does not specify an effective date; implementation is by government notification in the Official Gazette. As of the date of the Code’s publication, prior statutes remain operative until such notification. Practitioners should verify commencement status via the Ministry of Labour & Employment.
Source: The Code on Wages, 2019 (Ministry of Labour & Employment)
Are apprentices 'employees'? Statutory exclusion under the Apprentices Act, 1961 and labour law coverage limits
The legal status of apprentices under Indian labour law is delineated primarily by the Apprentices Act, 1961. Section 18 of the Act provides an explicit carveout: “An apprentice engaged under this Act shall be a trainee and not a worker, and the provisions of any law with respect to labour (such as working conditions, wages, welfare, or social security) shall not apply… save as otherwise provided in this Act.” Apprentices engaged via a registered apprenticeship contract under this Act, therefore, do not qualify as "employees" or "workmen" under the core Indian employment statutes—including the Industrial Disputes Act, 1947 (IDA), the Employees’ Provident Funds and Miscellaneous Provisions Act, 1952 (EPF Act), and the Employees’ State Insurance Act, 1948 (ESI Act) (see IDA s.2(s) and EPF Act s.2(f), each excluding statutory apprentices from coverage).
Case law cements this status. The Supreme Court, in Mukesh K. Tripathi v. Senior Divisional Manager, LIC (Civil Appeal No. 6745 of 1997, 2004), affirmed that: “there does not exist a relationship of employer and employee between the apprentice engaged under the said Act and the management. The apprentice is not a 'workman' within the meaning of Section 2(s) of the Industrial Disputes Act, 1947.” Labour courts have no jurisdiction over termination or conditions-of-service claims by registered apprentices.
The two major new codes—the Code on Wages, 2019 (Section 2(k)) and the Code on Social Security, 2020 (Section 2(26), 2(80))—preserve this exclusion. Both define “employee” expressly to exclude those engaged as apprentices under the Apprentices Act, 1961. This means the minimum wage, statutory benefits, and retrenchment protections regimes (whether under the legacy or future code framework) do not reach covered apprentices.
Critical: The exclusion only applies to apprenticeships that meet the formal requirements of the Apprentices Act—including execution of a written contract, registration with the Apprenticeship Adviser, and engagement in a designated trade or occupation. Trainees, interns, or probationers outside the statutory framework may still be found to be employees—and attract full statutory protection—if their engagement evidences day-to-day control, wage payment, and integration into the establishment’s business.
Practical compliance for global employers: Ensure all apprenticeships with an Indian nexus are supported by a registered contract under the Act. Avoid labeling conventional trainees as “apprentices” outside the statute—such arrangements risk being reclassified as employment, triggering retroactive wage and benefits liability.
Source: The Apprentices Act, 1961 (Ministry of Skill Development and Entrepreneurship) Source: The Code on Wages, 2019 (Ministry of Labour & Employment) — see Section 2(k) Source: The Code on Social Security, 2020 (Ministry of Labour & Employment) — see Sections 2(26), 2(80) Source: Mukesh K. Tripathi v. Senior Divisional Manager, LIC, (2004) 8 SCC 387 (Supreme Court of India)
Commencement status of the Code on Social Security, 2020: Has it been notified and implemented as of June 2026?
The Code on Social Security, 2020 (Act No. 36 of 2020) was brought into force in stages by the Central Government through a series of official notifications, culminating in full national implementation by mid-2026. The principal notification (S.O. 5319(E)) was issued on 21 November 2025, initiating the commencement of most provisions of the Code.
Subsequently, the Social Security (Central) Rules, 2026 were formally notified and commenced by G.S.R. 344(E) dated 8 May 2026, setting the detailed framework for enforcement, coverage, and compliance. As of June 2026, further notifications, including G.S.R. 527(E) dated 29 June 2026, have operationalized key schemes under the Code, such as the Employees’ Pension Scheme, 2026.
Practical impact as of June 2026:
Material change: This section was updated to reflect the staged notifications and newly commenced Central Rules and Pension Scheme through mid-2026. Practitioners should regularly confirm subsidiary state-specific notifications and scheme updates published by the Ministry of Labour & Employment.
Source: Code on Social Security, 2020 – Ministry of Labour & Employment Source: Ministry of Labour & Employment — Notifications portal