Gig Workers and the Employment Law Gap

Most Indian labour protections — minimum wage, provident fund contributions, protection against arbitrary termination — attach to an 'employer-employee' relationship as traditionally understood: a fixed workplace, defined hours, direct supervision. Platform-based gig work is often structured, deliberately, to avoid meeting that test, with workers formally engaged as independent contractors even where the platform exercises substantial control over how the work is done.

Abstract

This piece traces how Indian courts have historically tested for an employment relationship, argues that platform work is structured specifically to fail that test while replicating much of its practical control, and evaluates whether the Code on Social Security's new 'gig worker' category closes the resulting protection gap or merely names it.

The traditional test, and why platforms don't trip it

Indian courts have generally used a 'control test' or a broader 'integration test' to determine whether someone is an employee: does the principal control not just what work is done but how it's done, and is the worker integrated into the organisation's operations. A platform that sets delivery time windows, controls pricing, and can deactivate a worker's account for performance metrics is exercising a great deal of control by any functional measure — while carefully avoiding the specific formal markers, like fixed hours or a designated workplace, that older case law used as proxies for control.

What the Code on Social Security actually does

The Code on Social Security, 2020, introduces statutory definitions of 'gig worker' and 'platform worker' for the first time, and empowers the government to frame welfare schemes for them covering areas like life and disability insurance, health and maternity benefits, and old age protection. This is a meaningful acknowledgment that platform work doesn't fit the old employee/contractor binary. It does not, however, extend the full suite of employee protections — minimum wage guarantees, protection against arbitrary deactivation, collective bargaining rights — that apply to traditional employees.

• Welfare schemes under the Code depend on rules and funding mechanisms that, as of this writing, remain substantially unimplemented in most states.
• The Code creates the category without importing the procedural protections — like a right to be heard before termination — that traditional labour law attaches to employment.
• Platform workers still generally cannot unionise or bargain collectively in the way the Industrial Disputes framework allows for recognised employees.

Naming a category of worker is not the same as protecting them. The Code took the first step. The second step is the one that actually costs something.

Where the gap concretely bites

The clearest illustration is account deactivation. A traditional employee facing dismissal has, at minimum, procedural protections under industrial law. A platform worker whose account is deactivated — often by an algorithm, for a metric the worker can't fully see or contest — currently has little equivalent recourse, because they were never classified as an employee for those protections to attach to in the first place. Closing this specific gap, rather than the broader classification question, may be the more tractable near-term reform.