Gig Economy

The gig economy describes arrangements where work is allocated as discrete tasks or short engagements rather than as continuing employment, most visibly through digital platforms for delivery, transport, domestic services and freelance professional work.

Two features distinguish it from ordinary contracting. The allocation is usually mediated by an algorithm rather than negotiated, and the worker typically has no single counterparty relationship of the kind employment involves. Work is offered, accepted or declined, and paid for by the task.

The consequence that matters is legal rather than descriptive. Because the arrangement is not employment, the protections that attach to employment, being minimum wages, hours limits, leave, contributions, notice and severance, do not attach either.

That gap is the reason the category needed addressing in statute, and India addressed it in a specific way.

The Code on Social Security, 2020 recognises gig workers and platform workers as categories and provides for their welfare without deeming them employees.

The mechanism is a contribution by aggregators. Under section 114(4), the contribution is payable at a rate not exceeding two per cent and not less than one per cent of annual turnover, as notified, for aggregators in the categories listed in the Seventh Schedule. It is subject to a cap: the contribution shall not exceed five per cent of the amount paid or payable by the aggregator to gig and platform workers. Turnover for this purpose excludes tax, levy and cess payable to the Central Government.

One point is essential and frequently omitted. Section 114(5) provides that the date of commencement of the aggregator contribution is to be notified by the Central Government. The obligation therefore depends on that notification, and an organisation should establish the current position rather than assume the contribution is either in force or not.

The structure is worth understanding on its own terms. It funds welfare for a category of workers through a levy on the platforms that engage them, rather than by extending the employment relationship. That is a different policy choice from the one made in some other jurisdictions, and it means the classification question, whether someone is an employee, remains live and separate.

For most organisations the practical issue is not the gig economy in general but whether their own contractors are genuinely outside employment.

The label on the contract does not settle it. What matters is the substance of the arrangement, and the factors that point towards employment are familiar: control over how and when the work is done, integration into the organisation, exclusivity, provision of equipment, supervision, fixed hours, and leave approval.

The middle row is where organisations create exposure, usually to reduce cost or headcount. The consequence of getting it wrong is not limited to a reclassification: it means contributions that should have been made were not, and entitlements that should have accrued did not, for the whole period.

Because the exposure accumulates, the cost of discovering a misclassification rises with time, which argues for settling the question at the outset rather than when it is challenged.

Employers competing with platform work, particularly for early-career and shift-based roles, benefit from being clear about the actual comparison.

• Gig work offers control over when to work, low barriers to starting, and immediate payment, which are genuine advantages.
• It does not offer income stability, since earnings vary with demand, platform pricing and algorithmic allocation the worker does not control.
• It carries no employer contributions towards retirement or insurance, no paid leave, and no notice or severance.
• Costs sit with the worker: vehicle, fuel, device, data and maintenance are borne by them and are frequently underestimated when comparing gross earnings.
• There is no progression structure, so the work does not compound into a career in the way employment can.

An employer that cannot articulate this is competing badly. The comparison is now routinely made by candidates, and dismissing it as unrealistic concedes the argument rather than answering it.

The honest version of the answer is that employment trades some autonomy for stability, protection and accumulation, and that the trade is a good one for most people over time. That is a defensible position and it requires the employment on offer to actually deliver those things.

Two things are worth monitoring rather than assuming.

The first is the commencement and rate notifications under section 114, since the aggregator contribution's practical effect depends entirely on them. The rate is bounded by the Code and set by notification, and the commencement date is likewise notified.

The second is the rules made under the Code, which govern registration of gig and platform workers, the schemes funded by the contribution, and the mechanics of who is covered. The Code establishes the framework and leaves a substantial amount to be prescribed.

For an employer engaging gig workers directly rather than through a platform, the classification analysis above matters considerably more than the aggregator provisions, since those attach to aggregators in the Seventh Schedule categories rather than to every organisation using freelance labour.

The safe posture is to determine which of these applies to your arrangement specifically, since the answer differs sharply between engaging a freelancer, using a platform, and operating one.