Gig Worker Aggregator Liability Insurance in India: What Platforms Owe, What IRDAI Expects, and How to Structure Cover

Indian gig worker aggregators operate a business model that Indian insurance law was never designed to address. The foundational assumption of workers' compensation under the Employees' Compensation Act, 1923 is a clear employer-employee relationship. The ESI Act, 1948 similarly presupposes a defined establishment with identifiable employees. Gig aggregators disrupt both assumptions. The worker is classified as an independent partner, the platform disclaims the employer label, and the service is delivered outside any premises controlled by the aggregator. Yet the platform sets the terms of engagement, controls pricing, assigns work through algorithms, and enforces quality standards that functionally resemble employment.

This structural ambiguity creates a liability exposure that standard insurance products do not address. A conventional commercial general liability (CGL) policy covers the insured's premises-based operations and products. An employer's liability policy covers claims from employees. Neither responds cleanly when a Swiggy delivery rider is injured during an order, or when a customer is harmed by a service provider dispatched through Urban Company, and the injured party sues the platform rather than (or in addition to) the service provider.

The problem is not theoretical. Indian courts, consumer forums, and labour tribunals have been hearing an increasing volume of cases where gig workers or their families seek compensation from the platform, not the individual customer or service recipient. The Consumer Protection Act, 2019 makes platforms potentially liable as service providers. The Motor Vehicles (Amendment) Act, 2019 introduced aggregator licensing with implicit insurance responsibilities. And the Social Security Code, 2020 created, for the first time, a statutory framework imposing financial obligations on aggregators toward gig and platform workers. For any platform with more than a few hundred active workers, the cumulative liability exposure from these converging legal developments is substantial enough that operating without a purpose-built insurance programme is a material business risk.

The Code on Social Security, 2020 is the most consequential piece of Indian legislation for gig worker aggregator liability. Its provisions, once fully notified and operationalised, will transform what was previously a voluntary and uneven sector into a mandatory compliance framework.

Section 2(35) defines a gig worker as a person who performs work or participates in a work arrangement and earns from such activities outside of a traditional employer-employee relationship. Section 2(61) defines a platform worker as a gig worker whose work or service is dependent on a digital platform. Section 2(2) defines an aggregator as a digital intermediary or marketplace that connects buyers and sellers of goods or services through a platform. These three definitions, read together, capture the vast majority of Indian gig economy participants and the platforms that facilitate their work.

Chapter IX of the Code empowers the Central Government to frame social security schemes for gig and platform workers. The benefits envisaged under Section 109(1) include life and disability cover, accident insurance, health and maternity benefits, old age protection, creche benefits, and any other benefit as the Central Government may determine. Section 114 imposes the financial obligation: every aggregator must contribute to the social security fund at a rate between 1% and 2% of its annual turnover, as specified by the Central Government.

For a platform with annual turnover of INR 1,000 crore, this translates to a mandatory contribution of INR 10 crore to INR 20 crore per year. This is a direct statutory cost, not a discretionary insurance purchase. It sits alongside, and does not replace, any commercial insurance the platform may carry for its own liability protection.

The implementation timeline has been staggered. While the Code received Presidential assent in September 2020, the notification of specific schemes and state-level rules has progressed unevenly. Rajasthan enacted the Platform Based Gig Workers (Registration and Welfare) Act, 2023, which mandates a welfare fee from aggregators, creates a gig worker welfare board, and establishes a registration framework. Karnataka, Maharashtra, and Telangana have signalled similar state-level legislation. Platforms cannot afford to wait for uniform national implementation. The direction of travel is clear, and compliance infrastructure built now will be far less disruptive than a last-minute scramble when notifications are issued.

The single most important legal concept for aggregator liability insurance is vicarious liability: the principle that one party can be held liable for the acts of another based on the nature of their relationship. For gig aggregators, the question is whether the platform is vicariously liable for injuries or damage caused by workers it classifies as independent contractors.

Indian courts apply a multi-factor test to determine whether vicarious liability attaches. The Supreme Court in Dharangadhara Chemical Works v. State of Saurashtra (1957) established that the decisive criterion is the right to control the manner of work, not merely the right to direct the result. In the gig economy context, platforms exercise extensive control: algorithmic work allocation, mandatory acceptance rates, prescribed service protocols, required uniforms and equipment, GPS-tracked routes, customer rating systems that determine continued access to the platform, and penalty mechanisms for non-compliance. Each of these control elements strengthens the argument for vicarious liability.

The Karnataka High Court in the Ola Financial Services case (2020) examined driver-platform relationships and found sufficient indicia of control to create employer-like obligations. While the ruling did not definitively classify all gig workers as employees, it established that the independent contractor label, standing alone, does not insulate a platform from liability.

For insurance purposes, vicarious liability is the exposure that demands the most careful programme design. If a delivery rider causes a road accident while completing an order, the rider's personal motor insurance (if any) covers the rider's liability. But if the injured third party, or the rider's own family in case of the rider's injury, sues the platform on the theory that the platform controlled the conditions of work and is vicariously liable, the platform needs its own liability insurance to respond.

The practical implication is that platforms must insure on a dual-track basis. Track one covers the platform's own direct negligence: failure to vet workers adequately, failure to implement safety standards, algorithmic decisions that create unsafe conditions (such as assigning deliveries with unrealistic time pressures). Track two covers vicarious liability for the acts of workers, regardless of whether the platform was itself negligent. A well-structured aggregator liability policy covers both tracks, and does not condition coverage on the resolution of the employee-versus-contractor classification question, which may take years to settle definitively in Indian jurisprudence.

IRDAI has recognised that the gig economy requires insurance product innovation that the existing regulatory framework does not easily accommodate. Several initiatives over the past three years have begun to address this gap.

The IRDAI Regulatory Sandbox, established under the Sandbox Regulations of 2019 and expanded under the 2023 framework, has been the primary mechanism for testing gig economy insurance products. Insurers including ICICI Lombard, HDFC Ergo, Bajaj Allianz, and Go Digit have used the sandbox to pilot products such as per-trip accident covers for delivery riders, usage-based health insurance with premiums tied to active working hours, and parametric injury covers that pay a fixed benefit within 48 hours of a verified accident without requiring conventional claims documentation.

The Bima Sugam initiative, IRDAI's planned unified insurance marketplace, is expected to simplify policy issuance and claims for gig workers who may lack the documentation and financial literacy to work through traditional insurance processes. The platform is designed to support API-based policy issuance, vernacular language interfaces, and paperless claims processing, all of which are essential for a workforce that conducts most of its financial transactions through mobile phones.

IRDAI's micro-insurance regulations permit policies with sum insured up to INR 2 lakh and simplified terms, making them suitable for low-cost covers for gig workers. However, the micro-insurance framework has limitations for aggregator liability purposes. The sum insured cap is too low for serious injury or death claims, and the simplified terms may not accommodate the subtle coverage requirements of platform-mediated service delivery. For aggregator liability, the product needs to be a full commercial policy with appropriate limits, not a micro-insurance product.

IRDAI's 2024 master circular on general insurance products also introduced provisions for group insurance policies with flexible member entry and exit, which directly addresses the high-churn nature of gig workforces. Platforms can now structure group policies where workers are automatically enrolled when they begin accepting assignments and automatically removed when they become inactive, with premium calculated on a per-active-worker basis rather than a fixed annual headcount. This structure aligns the insurance cost with the platform's actual operating workforce and avoids the problem of paying premium for inactive or departed workers.

Despite these developments, significant gaps remain. There is no IRDAI-standardised product specifically designed for aggregator vicarious liability. Policies must be structured as bespoke commercial liability programmes, typically negotiated between the platform's broker and the insurer's specialty lines team. The absence of standardised terms means that coverage quality varies significantly across platforms, and smaller aggregators without experienced brokers may end up with policies that contain exclusions rendering them ineffective for the most likely claim scenarios.

A properly structured liability insurance programme for an Indian gig worker aggregator should consist of multiple coordinated layers, each addressing a distinct risk.

The first layer is a commercial general liability (CGL) policy, customised with endorsements to cover the platform's liability for bodily injury and property damage arising from services delivered through the platform. The standard CGL wording must be amended to remove the premises-only limitation and to extend coverage to services performed at customer locations or on public roads by platform-associated workers. The policy should include vicarious liability coverage, explicitly stating that the insurer will respond to claims against the platform arising from the acts or omissions of service providers engaged through the platform. Limits for a mid-sized platform (10,000 to 50,000 daily active workers) should be in the range of INR 10 crore to INR 50 crore per occurrence, with an annual aggregate of INR 50 crore to INR 100 crore.

The second layer is a group personal accident (GPA) policy covering platform workers for accidental death, permanent total disability, permanent partial disability, and temporary total disability while engaged in platform work. The sum insured should reflect actual economic loss, not an arbitrary round number. For a delivery rider earning INR 20,000 per month, an accidental death benefit of INR 5 lakh is inadequate by any actuarial measure. A benefit of INR 15 lakh to INR 25 lakh, calculated as a multiple of annual earnings, is more appropriate. The GPA policy should cover both on-duty and commuting periods, as many worker injuries occur while travelling to and from assignment locations.

The third layer is a group health insurance policy providing hospitalisation cover to workers. In metro cities where a single hospitalisation for fractures sustained in a road accident can cost INR 2 lakh to INR 5 lakh, the sum insured per worker should be at least INR 3 lakh. Cashless hospitalisation through a wide network of hospitals is essential because gig workers rarely have the financial capacity to pay upfront and seek reimbursement later.

The fourth layer is professional indemnity (PI) or technology errors and omissions (E&O) insurance, covering the platform for claims arising from algorithmic errors, service mismatches, data processing failures, or technology glitches that result in financial loss or injury. If the platform's algorithm assigns a delivery to an inappropriate rider (for example, dispatching someone without a valid licence for a two-wheeler delivery), the resulting claim may be characterised as a technology failure rather than a bodily injury claim, and the CGL policy may not respond.

The fifth layer, for platforms handling customer data (which includes virtually all aggregators), is cyber insurance covering data breaches, regulatory penalties under the Digital Personal Data Protection Act, 2023, and first-party costs of breach response.

Each layer should be coordinated to avoid gaps and overlaps. The broker must ensure that the CGL deductible does not create an uninsured gap between the GPA benefit and the CGL coverage trigger, and that the PI policy does not exclude claims that could alternatively be characterised as bodily injury claims under the CGL.

Pricing aggregator liability insurance in India is an actuarial challenge because the risk is new, the claims data is thin, and the exposure characteristics differ fundamentally from traditional employer or premises liability.

For the GPA component, insurers price based on the occupational risk class of the workers. Delivery riders on two-wheelers fall into one of the highest-risk categories, with claim frequencies significantly exceeding those of office workers or even factory employees. Road accident data from the Ministry of Road Transport and Highways shows that two-wheeler riders account for roughly 30% of all road fatalities in India, and delivery riders, who spend 8 to 12 hours daily on congested urban roads, face elevated exposure even within this high-risk category. GPA premiums for delivery riders typically range from INR 400 to INR 1,200 per worker per annum for a sum insured of INR 10 lakh to INR 20 lakh, though platforms with poor claims experience may see rates at the higher end.

For the CGL component, pricing depends on the platform's service category, daily transaction volume, geographic concentration, claims history, and the quality of its risk management practices. A ride-hailing platform in metro cities faces higher bodily injury claim severity than a home services platform, but the home services platform may face higher property damage frequency. Insurers use proxies from international gig economy claims data (particularly from the US, UK, and Australia where platform liability litigation is more advanced) to supplement the limited Indian actuarial base.

The fundamental data challenge is that most Indian aggregators have not historically tracked claims in a format useful for insurance actuarial analysis. Worker injuries may have been settled informally through ex-gratia payments without insurer involvement. Customer complaints about service quality may have been resolved through refunds or credits without generating a claims record. This informal resolution approach, while operationally convenient, deprives both the platform and its insurer of the structured data needed for accurate pricing and coverage design.

Platforms that want to negotiate better insurance terms should invest in a claims information system that records every incident (whether or not it results in a formal claim), categorises incidents by type and severity, tracks resolution costs, and maintains this data in a format that can be shared with insurers and their actuaries. A platform that presents three years of clean, structured incident data will receive meaningfully better terms than one that cannot quantify its own loss experience. Several insurers in the Indian market now offer premium discounts of 10% to 20% for platforms that share real-time telematics data, incident data through API feeds, and worker safety training completion rates.

Aggregator platforms at different stages of maturity need a phased compliance roadmap that prepares them for the full operationalisation of the Social Security Code while addressing immediate liability exposures.

Phase one, which should be completed immediately if not already done, involves a workforce classification audit. Every individual providing services through the platform must be classified under the SS Code definitions: employee, gig worker, or platform worker. The classification must be based on the actual nature of the engagement, not the contractual label. Platforms that have relied on contractor agreements to avoid employer obligations should have these agreements reviewed by employment law counsel against the SS Code definitions and recent court rulings. The cost of retrospective reclassification, including back-dated ESI contributions, PF contributions with interest and penalties, and potential litigation, can be devastating for a growth-stage platform.

Phase two involves establishing baseline insurance coverage. Platforms that currently provide no insurance to workers should immediately procure a group personal accident policy and a basic group health cover. Platforms with existing voluntary covers should benchmark their terms against the likely statutory floor once SS Code schemes are notified. The benchmarking should assess sum insured adequacy (is INR 2 lakh sufficient when a single hospitalisation for a road accident can exceed that amount?), coverage hours (is the worker only covered during active orders, or also during commuting and waiting periods?), waiting periods and exclusions (do pre-existing conditions exclude the workers most likely to need care?), and claims accessibility (can a gig worker with limited documentation and digital literacy actually file and collect on a claim?).

Phase three involves building the technology infrastructure for scalable insurance administration. The platform's tech stack should support real-time worker enrolment and de-enrolment via API integration with the insurer, automated premium calculation based on active worker counts, digital claims filing with photograph and document upload, claims status tracking visible to the worker through the platform app, and premium reconciliation tied to the platform's payment cycle. Building this infrastructure before the SS Code schemes are notified gives the platform a compliance head start and avoids the scramble that will inevitably follow notification.

Phase four involves engaging with IRDAI-authorised insurers to design a full liability programme as outlined in the previous section. This should be done through an experienced broker who understands gig economy risks and can negotiate terms that reflect the platform's actual exposure rather than generic industry rates. The broker should conduct a comparative market exercise across at least three to four insurers, negotiate bespoke policy wordings that address the platform's specific service categories, and ensure that the programme is designed to scale with the platform's growth without requiring fundamental restructuring at each renewal.

The value of aggregator liability insurance is tested not in the policy document but at the point of claim. Three scenarios from the Indian market illustrate the gaps that catch platforms unprepared.

Scenario one: a delivery rider for a quick-commerce platform in Hyderabad was struck by a bus while completing a delivery during evening rush hour. The rider suffered a fractured femur and was hospitalised for 18 days. Medical expenses totalled INR 3.8 lakh. The platform's GPA policy provided an accidental death benefit of INR 5 lakh and temporary total disability benefit of INR 500 per day, but the medical expense reimbursement sub-limit was INR 50,000. The rider's family was left with INR 3.3 lakh in unreimbursed medical bills. The family filed a complaint with the district consumer forum, naming both the bus operator and the platform. The consumer forum held the platform liable for the medical expense gap, reasoning that the platform had a duty of care to provide adequate insurance and that the INR 50,000 medical sub-limit was manifestly inadequate for a worker engaged in high-risk road-based work. The platform settled for INR 4.5 lakh, which its own CGL policy covered minus the deductible.

Scenario two: a home services platform in Mumbai faced a claim after a plumber engaged through the platform caused water damage to a customer's apartment during a bathroom fitting. The damage to flooring, electrical wiring, and personal belongings was assessed at INR 6.2 lakh. The platform's CGL policy had a property damage sub-limit of INR 10 lakh per occurrence, which was sufficient. However, the policy contained an exclusion for damage arising from work performed by contractors not directly employed by the insured. The insurer denied the claim on this basis. The platform had to engage legal counsel, who successfully argued that the policy's vicarious liability endorsement (which had been added at the broker's insistence during placement) overrode the contractor exclusion. The claim was eventually paid after four months of dispute. The lesson: policy wordings must be reviewed for internal contradictions between standard exclusions and bespoke endorsements, and the endorsement should explicitly state that it takes precedence over conflicting standard terms.

Scenario three: a ride-hailing platform's driver in Delhi was involved in a fatal accident where a pedestrian was killed. The pedestrian's family filed claims against both the driver and the platform. The driver's mandatory third-party motor insurance (unlimited liability under the Motor Vehicles Act) covered the claim against the driver. However, the family also pursued a separate claim against the platform under the Consumer Protection Act, alleging that the platform's surge pricing and delivery time targets created unsafe driving incentives. The platform's CGL policy responded to the claim, but the insurer appointed counsel raised the question of whether the platform's algorithmic design constituted wilful misconduct, which would be excluded. The case was settled before this question was judicially determined, but it highlighted a growing risk: as regulators and courts scrutinise platform algorithms, the boundary between insurable negligence and uninsurable wilful conduct will become a significant coverage question.