Gig Economy & Platform Workers

The Code on Social Security, 2020 introduces two new worker categories into Indian labour law for the first time. Section 2(35) defines a "gig worker" as a person who performs work or participates in work arrangements and earns from such activities, outside of a traditional employer-employee relationship. Section 2(55) defines a "platform worker" as a gig worker who accesses other organisations or individuals through an online platform and provides services or solves specific problems in exchange for payment.

The distinction matters because platform workers are a subset of gig workers, but gig workers need not operate through a digital platform. A freelance electrician hired through word-of-mouth is a gig worker but not a platform worker. A delivery executive working through Zomato or Swiggy is both a gig worker and a platform worker. A ride-hailing driver on Uber or Ola is similarly a platform worker.

Critically, gig and platform workers are distinct from contract labour under the Contract Labour (Regulation and Abolition) Act, 1970 (which will be subsumed by the OSH Code). Contract labour involves a tripartite relationship where workers are employed by a contractor and deployed to a principal employer. Gig workers, by contrast, operate outside the employer-employee framework entirely. They are also distinct from employees under the Shops and Establishments Acts or the Factories Act. The practical categories include ride-hailing drivers, food and grocery delivery personnel, freelance technology workers, cloud-based workers on platforms like Upwork or Fiverr, and home service providers on platforms like Urban Company.

Chapter IX of the Code on Social Security, 2020 (Sections 113-114) establishes the framework for gig and platform worker social security. The Central Government is empowered to frame schemes covering life and disability cover, health and maternity benefits, old age protection, and any other benefit as determined by the government. These schemes will be administered through a National Social Security Board for unorganised workers, gig workers, and platform workers.

The funding mechanism is set out in Section 114: aggregators must contribute to the social security fund at a rate between 1% and 2% of their annual turnover, as notified by the Central Government. Additionally, there is a cap: contributions shall not exceed 5% of the total amount paid or payable by the aggregator to gig and platform workers. The Central Government may also contribute from the Consolidated Fund of India, and state governments may contribute from their respective funds.

Section 2(1) defines an "aggregator" as a digital intermediary or marketplace that connects buyers of a service with the seller/provider of the service. This definition is broad enough to cover food delivery apps, ride-hailing platforms, home service marketplaces, and potentially even e-commerce platforms that facilitate third-party service delivery. Aggregators must register with the relevant authority and maintain databases of their gig and platform workers, including Aadhaar numbers, for the purpose of administering social security schemes.

Karnataka enacted the Platform-Based Gig Workers (Social Security and Welfare) Act in 2024, making it India's first comprehensive state-level legislation specifically addressing gig worker rights and platform obligations. The Act goes significantly beyond the Social Security Code's framework by establishing detailed operational requirements for aggregators operating in Karnataka.

Key provisions include mandatory registration of all aggregators with the Karnataka state government within 60 days of the Act's commencement, and registration of all gig workers on a state database with unique identification numbers. The Act establishes a Karnataka Platform-Based Gig Workers Welfare Board comprising government representatives, aggregator nominees, gig worker representatives, and independent experts. A dedicated Social Security Fund is financed through a "welfare fee" of 1-2% of each booking value (not annual turnover, a key distinction from the central Code) deposited by aggregators.

The Act introduces path-breaking provisions on algorithmic transparency: aggregators must disclose the basis on which work is allocated, pricing is determined, and performance is assessed. Gig workers have the right to access their personal data held by the platform, and aggregators cannot terminate or deactivate a gig worker without providing reasons and a 14-day notice. A grievance redressal mechanism with defined timelines is mandatory, with an appellate authority above it.

For aggregators operating in Karnataka, compliance is immediate upon notification of rules. The welfare fee on booking value represents a direct cost impact on unit economics, particularly for high-volume, low-margin delivery and ride-hailing platforms.

Rajasthan followed Karnataka with its own Platform-Based Gig Workers (Registration and Welfare) Act, creating the second state-level framework for gig worker protection. While sharing the broad objectives of the Karnataka Act, the Rajasthan legislation has distinct features and a slightly different emphasis that enterprises must understand.

The Rajasthan Act establishes a Welfare Board with a tripartite composition: government officials, aggregator representatives, and gig worker representatives, along with subject-matter experts. The Board is responsible for registering gig workers and aggregators, administering the welfare fund, and recommending social security schemes to the state government. The social security fund is financed through a welfare cess, with the rate structure similar to Karnataka's model of a percentage of transaction or booking value.

Aggregators must register with the Rajasthan Welfare Board and share comprehensive data including the number of gig workers, payment details, work duration, and other operational metrics on a quarterly basis. The data sharing obligations are more prescriptive than Karnataka, requiring aggregators to provide aggregated and de-identified data sets that enable the Board to monitor working conditions and earnings patterns.

The Rajasthan Act also includes provisions for a grievance redressal mechanism and an appellate process. Compared to Karnataka, the Rajasthan framework places relatively greater emphasis on data transparency and the Welfare Board's monitoring role, while Karnataka's Act is more detailed on algorithmic transparency and individual worker rights. Enterprises operating in both states need to maintain separate compliance processes, as the registration, contribution, and reporting requirements differ in specifics even where the overall framework is similar.

The distinction between an employee and an independent contractor remains the most litigated question in Indian labour law, and the gig economy has intensified this debate. Indian courts have historically applied multiple tests to determine the existence of an employment relationship, and a misclassification finding can retrospectively create employer obligations for PF, ESI, gratuity, bonus, and leave.

The dominant test remains the "control test" articulated by the Supreme Court in Dhrangadhra Chemical Works Ltd v State of Saurashtra (1957): the key question is whether the employer has the right to control not just what work is done but how it is done. In Silver Jubilee Tailoring House v Chief Inspector of Shops (1973), the Court refined this with the "integration test": is the worker integrated into the employer's business, or is the worker in business on their own account? The "economic reality test" examines the degree of economic dependence on a single engager.

For gig platforms, the classification challenge is acute. Platforms exercise significant control through algorithmic assignment, pricing, rating systems, and deactivation policies, which argue for employment status. However, workers typically set their own hours, use their own equipment, and can work for multiple platforms simultaneously, which argues for independent contractor status. Recent trends in Indian courts show increasing willingness to look beyond contract labels to economic substance.

The consequences of misclassification are severe: retrospective PF and ESI contributions with interest and penalties (often 7-10 years), gratuity liability for all qualifying workers, applicability of minimum wage and bonus laws, coverage under the Shops and Establishments Acts, and potential prosecution under multiple statutes. The IT sector is particularly vulnerable, where large-scale use of "consultants" and "contractors" for core business functions faces growing regulatory and judicial scrutiny.

Aggregators must implement a structured compliance programme addressing both central and state-level obligations. At the central level under the Social Security Code: register as an aggregator with the Central Government or designated authority upon notification of the relevant rules; establish a system to calculate and deposit social security contributions (1-2% of annual turnover, capped at 5% of payments to gig workers); maintain a complete database of all gig and platform workers including Aadhaar numbers, contact details, nature of work, and payment history; file quarterly data returns with the National Social Security Board showing the number of workers engaged, total payments made, average earnings, and duration of engagement; set up an internal grievance mechanism with defined response timelines; ensure all contracts with gig workers clearly define the nature of the relationship, payment terms, insurance coverage, and dispute resolution process.

For Karnataka-specific compliance: register with the Karnataka Welfare Board within 60 days of notification; calculate welfare fee at 1-2% of booking value (not turnover) and deposit to the state welfare fund; report booking value data monthly; disclose algorithmic work allocation criteria; ensure no termination without 14-day notice and stated reasons; provide data access to workers on request; establish a Karnataka-compliant grievance mechanism with specified escalation timelines.

For Rajasthan-specific compliance: register with the Rajasthan Welfare Board; deposit welfare cess as notified; share quarterly operational data (worker counts, payments, duration); cooperate with Board inspections and data requests.

Documentation best practices: maintain standardised engagement contracts (not employment contracts), keep auditable records of all payments, retain communication logs related to deactivation decisions, and conduct annual classification risk assessments.

India's approach to gig worker regulation sits between two global poles, and understanding the international landscape helps predict where Indian law is heading. The European Union's Platform Workers Directive (2024) establishes a rebuttable presumption of employment for platform workers, meaning platforms must prove that workers are genuinely self-employed rather than workers proving they are employees. This reversal of burden of proof is the most aggressive regulatory stance globally and has forced platforms to restructure operations across EU member states.

The United Kingdom's Supreme Court in Uber BV v Aslam (2021) held that Uber drivers are "workers" (a UK-specific intermediate category between employee and independent contractor) entitled to minimum wage, paid holidays, and pension contributions. The ruling emphasised substance over contractual form, finding that Uber's control over pricing, terms, and driver behaviour was incompatible with genuine self-employment. Australia's Fair Work Commission has similarly found certain gig workers to be employees despite contractual labels.

In the United States, California's ABC test (codified in AB5, 2019) presumes all workers are employees unless the hiring entity proves three conditions: the worker is free from control, performs work outside the usual course of business, and is an independently established trade. Several other US states have adopted or are considering similar tests.

India's approach under the Social Security Code takes a middle path: it does not create an employment relationship but mandates social security contributions from aggregators. This preserves platform flexibility while extending a safety net. However, the Karnataka and Rajasthan Acts move closer to the EU model by imposing operational obligations (algorithmic transparency, termination protections) that mirror employment-like protections without formally creating employment status. The trajectory suggests India will progressively layer more protections onto the gig worker framework, and enterprises should plan for a regulatory environment that becomes stricter over time.