Gig Worker Social Security in India: A Platform Playbook
Gig worker social security in India now has a notified National Social Security Board. Platform operators should prepare for data, protection and servicing requirements while monitoring scheme notifications.
Article brief
3 November 2026
12 min read
By Bharatsure Team

Category
Insurance infrastructure
Share
LinkedInQuick answer
The notified National Social Security Board provides a formal forum to recommend and monitor welfare schemes for gig and platform workers. Its constitution does not itself create an insurance benefit or appoint the Board as a scheme administrator, claims administrator or benefit-disbursing agency. Under [the Code on Social Security, 2020](https://www.labour.gov.in/static/uploads/2025/07/b0620548445580767b5c0d18c95c26f7.pdf), the Central Government frames schemes and a scheme may identify its own administrator and implementing agencies.
- The Board can recommend schemes, advise the Central Government, monitor centrally administered schemes and perform further functions assigned by the Central Government. The 30 October 2026 constitution announcement did not appoint it as a claims administrator, benefit-disbursing agency or scheme implementing agency. The Code and the constitution announcement set out this position.
- The Social Security (Central) Rules, 2026 require worker-data sharing and registration actions. They also require every aggregator to register on the designated portal or another portal specified by the Central Government. Rules 48 and 49 set out these requirements.
- Portal registration and a benefit are different stages. A notified scheme can impose its own eligibility and operating conditions, including its administration and implementing arrangements. Section 114 and Rule 48 provide the framework.
- Platforms can build modular protection, enrolment, support and claims workflows now while keeping platform-sponsored cover clearly separate from any future public scheme.
The direct answer: gig worker social security in India now has a formally constituted National Social Security Board that can recommend and monitor welfare schemes. Its formation does not automatically give every rider, driver or service partner a new insurance benefit. For product, operations and partnership teams, the immediate priorities are accurate worker data, compliance with applicable portal and data-sharing requirements, protection-gap assessment, and adaptable enrolment and servicing workflows. The Ministry of Labour and Employment announced the Board’s constitution on 30 October 2026.
What the National Social Security Board notification changes for gig platforms
The Ministry of Labour and Employment’s 30 October 2026 announcement confirms the constitution of the National Social Security Board for unorganised workers and for gig and platform workers. The Board includes government, aggregator, worker and other stakeholder representation, and it must meet at least three times each year.
Its statutory functions matter more than the announcement language. Under Section 6 of the Code on Social Security, 2020, the Board can recommend suitable schemes to the Central Government, advise it on administration of the Code, monitor centrally administered social-welfare schemes, review state-level record keeping and review expenditure from the relevant fund and account. The Central Government can also assign additional functions to a social security organisation by notification.
For a platform operator, this creates a standing policy forum with representation from aggregators and workers. Product and compliance teams should track Board recommendations, expert-committee work and government notifications that create or operationalise a scheme.
The notification does not replace obligations already set by the Social Security (Central) Rules, 2026. Effective from their publication in the Gazette on 8 May 2026, the Rules set out worker-registration, data-sharing and aggregator-registration processes. The Board adds an institution for policy development and oversight, rather than replacing platform data readiness. The final Rules are the primary reference for these processes.
Gig worker social security in India: the direct answer for platform operators
Platform leaders should separate the current position into three layers:
- Duties already in force: The Rules require aggregators to share details of existing gig and platform workers through an application programming interface, or API, or another electronic mode. New worker registrations and exits must be shared in real time or daily, and worker details must be updated monthly or at another frequency specified on the designated portal. Separately, every aggregator must register on the designated portal or another portal specified by the Central Government. Rules 48 and 49 set out these requirements.
- The Board’s current role: The Board can recommend, advise, monitor and review, and it may perform further functions that the Central Government assigns. The 30 October 2026 constitution announcement did not appoint the Board as an insurer, claims administrator, benefit-disbursing agency or implementing agency for a scheme. The Code defines the Board’s functions, while the announcement records its constitution.
- Benefits that require further action: Section 114 permits the Central Government to frame and notify schemes covering life and disability cover, accident insurance, health and maternity benefits, old-age protection, crèche support and other benefits it determines. A notified scheme may specify its administration, implementing agencies, aggregator role, funding sources and other operating rules. Section 114 provides this scheme-making framework.
A platform’s playbook should therefore run on two tracks: present-day compliance and voluntary protection, alongside readiness for future government programmes, scheme-specific eligibility conditions and, where applicable, contribution notifications.
What the Board can mean for future welfare schemes and insurance partnerships
The Board gives future platform worker social-security schemes a structured forum for considering worker needs, aggregator operations, implementation constraints and funding. The Rules also allow the Board to form an expert committee on worker welfare, workforce assessment, new types of aggregators and other gig-economy issues. Rule 9 describes the committee power and the Board’s gig-worker composition.
That structure can affect several parts of a platform’s operating model:
- Eligibility data: Schemes may depend on worker identity, engagement history, platform activity or other notified conditions.
- Funding and reconciliation: Section 114 allows schemes to use Central Government funding, state funding, aggregator contributions, beneficiary contributions, corporate social responsibility funds or other sources. The contribution in Section 114(4) applies to funding referred to in Section 141(1)(ii): it is set between 1% and 2% of annual turnover for covered Seventh Schedule aggregator categories, subject to a cap of 5% of amounts paid or payable to gig and platform workers. The Central Government must notify both the rate and the contribution commencement date. Section 114 sets out the funding models and contribution mechanism.
- Distribution: A scheme may require platforms to present information, verify eligibility, facilitate enrolment or connect workers to an implementing agency.
- Servicing: Workers may need support for identity corrections, eligibility questions, nominations, benefit explanations and escalations.
- Claims or benefit requests: Insurance-backed programmes may require policy-level claims workflows, while other welfare schemes may use a government benefit-disbursement process.
Platforms should avoid hard-coding one anticipated programme into their core application. Build configurable eligibility, contribution, consent and servicing components instead. BharatSure’s embedded and affinity insurance capabilities can support protection placed within worker onboarding, activation, subscription or milestone journeys, while its insurance infrastructure for gig platforms supports platform distribution use cases.
Why a notified Board does not by itself confirm a worker’s insurance benefit
A Board, a registration record and an insurance benefit are three different things.
The Board is a governance and recommendation body with the functions given under the Code and any additional functions assigned by the Central Government. Registration creates a worker record and can be a condition for access to an applicable scheme. An actual benefit requires an operative scheme, defined eligibility and an implementation process. Under Rule 48, the Central Government may notify conditions for eligibility in addition to registration on the designated portal. The Rules make this distinction explicit.
The Rules also set engagement thresholds for eligibility under schemes: at least 90 days with one aggregator, or 120 days across multiple aggregators, in the previous financial year. A day counts where the worker earns income through the relevant aggregator, irrespective of the amount. These thresholds sit alongside any other conditions notified by the Central Government for a particular scheme. Rule 48 contains the engagement and eligibility framework.
Worker communication should reflect these distinctions. Avoid messages such as “registration means you are insured”. Instead, show separate statuses for:
- registration on the portal designated by the Central Government;
- eligibility assessment for a named scheme;
- enrolment or policy issuance;
- cover start and end dates;
- worker or platform contribution status;
- nominations and dependants;
- claims or benefit-request status.
Platform-sponsored insurance should be labelled separately from government-backed protection. If a platform offers personal accident, hospital cash, health or income-related cover, the app should identify who pays, who underwrites the policy, when cover begins, principal exclusions and how a worker can seek assistance. Insurance remains subject to policy terms, conditions and exclusions.
A practical protection-gap audit for delivery and platform workforces
Do not wait for the first Board recommendation to understand the workforce’s exposure. Run a structured audit across worker segments, cities and operating models.
1. Map the workforce correctly
Create a reconciled view of active, inactive and multi-platform workers. Include workers engaged directly and through subsidiaries, associate companies, limited liability partnerships or third parties, because the 2026 Rules include these engagement structures.
Check whether identity, mobile number, address, engagement dates and exit status remain consistent across the platform ledger, designated-portal records and insurance records.
2. Identify events that stop work or create large expenses
Assess the financial effect of accidental injury, disability or death, hospitalisation, treatment expenses, temporary loss of income after a covered event, damage to essential work assets and household exposure after a worker’s death. The aim is not to bundle every possible product. It is to identify the few events that create the sharpest interruption to earnings and household cash flow.
3. Review existing cover line by line
For every programme, record the eligible cohort, insurer, policy period, sum insured, premium payer, exclusions, waiting periods, nomination process and claims route. Look for duplicate cover as well as unprotected groups.
The gig worker insurance design guide provides a broader framework for selecting relevant cover and placing enrolment inside journeys workers already use.
4. Test the claims experience
Review real worker journeys, not only policy documents. Test whether a worker can find the claims entry point in the app, understand document requirements, report an accident while unable to complete a normal shift, obtain family assistance, receive queries in an understandable language and distinguish an insurer decision from a platform-support response.
5. Record the unresolved gap
The audit output should show which risks are covered, partly covered, excluded or awaiting a policy decision. Assign an owner and review date to each gap. This gives the platform a baseline for assessing future gig platform worker welfare schemes.
How to build an adaptable insurance distribution and claims workflow
The safest architecture separates policy and scheme rules from the platform’s permanent worker experience.
Use a configurable eligibility layer
The eligibility service should accept inputs such as worker category, city, activity days, earnings event, vehicle type, age, platform status and contribution status. Each programme should use version-controlled rules without requiring changes to the core onboarding system.
Keep programme ledgers separate
Maintain distinct records for registration on the government-designated portal, government-scheme eligibility, platform-paid insurance, worker-paid or shared-cost insurance, policy issuance and renewal, contributions or deductions, and claims or non-insurance benefit requests. This separation reduces the risk that one programme’s status is presented as another programme’s entitlement.
Build consent and disclosure into the worker journey
Place short, plain-language disclosures at onboarding, activation or renewal. Record the version shown, language selected, consent timestamp and any worker contribution. Give the worker continuing access to the policy or programme summary.
Design one front door for support, with multiple back-end routes
A worker should not need to decide whether an event belongs with the platform, insurer, third-party administrator or government agency. The app can collect the basic incident information once and route it to the appropriate workflow.
BharatSure’s claims workflow infrastructure can support white-label intimation, document collection, status tracking and insurer or third-party administrator hand-offs. The same front-end pattern can route non-insurance requests to a separate government-programme queue without presenting them as insurance claims.
Create a regulatory change process
Assign a cross-functional owner across legal, public policy, product, finance, operations and insurance partnerships. For every new notification or Board recommendation, assess whether it creates a legal duty or is advisory; which workers and entities are covered; what data, portal or API changes are required; whether contributions change; whether a new benefit or insurance policy is involved; and how worker communications and support routing must change.
This approach lets platforms respond to future gig platform worker welfare schemes without rebuilding the entire worker app.
FAQ: What should gig platforms do while welfare-scheme details emerge?
Should platforms wait before offering their own protection programme?
No. Platforms can address current accident, hospitalisation, disability and income-interruption gaps while monitoring government developments. Platform-sponsored protection must be described separately from statutory benefits and remains subject to the relevant insurance policy terms.
Does registration on a portal designated by the Central Government mean that a worker is insured?
No. Registration and benefit eligibility are separate concepts under Rule 48. The Central Government may notify scheme-specific eligibility conditions in addition to registration, so a platform should not describe portal registration as confirmation of insurance cover. The rule sets out this additional-conditions framework.
What should the regulatory watchlist include?
Monitor Board recommendations and meeting outcomes, schemes notified under Section 114, any rate notification under Section 114(4), the notified contribution commencement date, designated authority appointments, portal specifications, scheme eligibility conditions and relevant state-level measures. The Code places scheme design, funding choices and contribution notifications with the Central Government.
Can an existing group insurance policy replace a future government scheme?
Platforms should not assume so. Whether an existing policy can support, supplement or interact with a notified scheme will depend on that scheme’s terms, implementing agency, funding structure and official operating instructions.
The practical response to the Board’s formation is not to promise benefits that have not been defined. It is to strengthen worker records, meet applicable registration duties, map current protection gaps and build distribution and servicing infrastructure that can accommodate both existing insurance and future public programmes.
Book a demo to map a white-label protection, enrolment and claims workflow for your platform workforce.
Frequently asked questions
Should gig platforms wait for the Board’s recommendations before offering insurance?
No. Platforms can assess accident, hospitalisation, disability and income-interruption gaps now. Any platform-sponsored cover should be clearly distinguished from a government scheme and remains subject to the relevant policy terms, conditions and exclusions.
Does registration on a portal designated by the Central Government automatically provide insurance?
No. Rule 48 treats registration as separate from eligibility for benefits under a scheme. The Central Government may prescribe additional eligibility conditions for a gig or platform worker scheme. The distinction appears in Rule 48.
What regulatory developments should platforms monitor next?
Monitor Board recommendations and meeting outcomes, schemes notified under Section 114, any contribution notification under Section 114(4), the notified contribution commencement date, portal specifications, eligibility conditions, implementing-agency appointments and relevant state measures. Section 114 sets out these scheme and contribution mechanisms.
Can existing platform insurance be presented as a statutory social-security benefit?
Not unless a relevant government scheme or official arrangement expressly provides for it. Platform-funded, worker-funded and government-backed protection should be described and administered separately.
Sources
- Press Release: Press Information Bureau — pib.gov.in
- Code on Social Security, 2020 — labour.gov.in
- The final Rules — labour.gov.in



