Why gig and platform work need a separate explanation

Gig and platform work can involve short assignments, multiple clients, variable earnings and digital intermediaries. A delivery worker, an app-based driver and an independent professional may face similar income uncertainty while having different contractual and legal arrangements. The Social Security Code recognises new categories, but a careful answer must distinguish recognition, scheme eligibility, funding and the separate question of an employment relationship.

This guide explains the Code’s framework and points to the notified Social Security (Central) Rules, 2026 and the Ministry’s 2026 implementation material. It does not assume that every benefit listed as a possible scheme subject is automatically payable to every registered worker. For a current scheme claim, identify the actual notification, eligibility and administrative procedure in force on the relevant date.

The core definitions

Definitions overlap in practical discussion but should not be merged in legal revision. Read the statutory wording and context. A worker may use several platforms, work offline as well and have changing arrangements over time. The classification depends on the relevant facts and provision rather than on the marketing label chosen by a business.

Recognition does not settle every employment question

The Code’s recognition of gig and platform workers creates an express social-security framework for them. It does not follow that every person using an app is automatically an employee of that app for every law. Nor should the category be used to dismiss a genuine employment relationship without examining the facts and governing legal tests.

For examination purposes, distinguish two questions: what social-security scheme can cover the category, and whether a particular relationship attracts employee protections under another provision. A multiple-choice question may deliberately combine the two. The safest method is to identify the exact definition or chapter being tested before deciding whether an assertion is correct.

An original example helps: a salaried employee who occasionally uses the employer’s internal task app is not necessarily a platform worker merely because tasks arrive digitally. By contrast, an independent service provider obtaining assignments through a marketplace may fall within the relevant platform-work concept. The digital tool alone does not answer the classification question.

Section 114: possible social-security schemes

Section 114 empowers the Central Government to frame and notify suitable schemes for gig and platform workers. The specified subjects include life and disability cover, accident insurance, health and maternity benefits, old-age protection, crèche facilities and other benefits determined under the provision. Learn these as the statutory scope for scheme design.

A notified scheme can specify administration, implementing agencies, the role of aggregators, funding and other operational matters. This means the benefit architecture can be tailored rather than copied automatically from an existing employee scheme. It also explains why a question asking “which benefit can a scheme cover?” differs from one asking “what amount is currently payable to this worker?”

For a descriptive answer, explain the risk being addressed. Accident cover protects against a sudden event, health protection concerns treatment costs and related needs, and old-age protection addresses income insecurity after working life. A credible system may need several instruments because one contribution account cannot automatically solve every kind of risk.

Aggregator contributions: two different percentage bases

The Code provides for a notified aggregator contribution within a range of one to two per cent of annual turnover, subject to a cap of five per cent of the amounts paid or payable to gig and platform workers. The rate and commencement of contribution depend on the Central Government’s notification. The statutory explanation also addresses exclusion of taxes, levies and cesses paid or payable to the Central Government from turnover.

These percentages have different denominators. The 1–2% range relates to turnover; the 5% cap relates to payments to workers. A common wrong answer applies 5% to turnover or treats 2% as the automatically operative rate in every case. Revision notes should always write the base beside the percentage.

A worked hypothetical calculation

Assume relevant annual turnover is ₹100 crore, amounts paid or payable to workers are ₹20 crore, and a valid notification for the hypothetical situation sets the rate at 2%. The turnover-based amount would be ₹2 crore. The cap would be 5% of ₹20 crore, or ₹1 crore. The contribution would therefore be limited to ₹1 crore under those assumptions.

This calculation illustrates the statutory ceiling. It does not assert that 2% is the actual currently notified rate for every aggregator. If a question changes worker payments to ₹60 crore, the cap becomes ₹3 crore and the turnover-based ₹2 crore would fall below it. Understanding both bases is more reliable than memorising one numerical answer.

Registration, identification and facilitation

Section 113 provides for registration of unorganised, gig and platform workers within the statutory conditions. Registration supports identification and scheme administration. The Code refers to the prescribed age and self-declaration framework, with Aadhaar-related provisions in the relevant legal setting. Exact operational requirements should be read with the current rules and portal instructions.

The e-Shram portal is a national database covering unorganised workers, including gig and platform workers. A record can help connect workers with social-security schemes, but enrolment and benefit sanction are different stages. Avoid telling a candidate or worker that an e-Shram number guarantees every insurance, pension or cash benefit regardless of eligibility.

Facilitation matters because workers can have variable work schedules, different languages, limited documentation or difficulty resolving mismatched records. A well-designed registration process needs assistance, correction channels and clear information about scheme conditions. In Mains, these administrative details show how a legal entitlement can become accessible in practice.

What changed in the 2026 implementation framework?

The official Gazette notification dated 8 May 2026 contains the Social Security (Central) Rules, 2026. These are distinct from the earlier draft proposals. The rules provide an operational framework across the subjects they cover, including provisions relevant to the gig and platform-worker system. Check the English portion and the exact rule rather than assuming that a circulating summary reproduces it completely.

The Ministry also issued an aggregator-onboarding communication for e-Shram dated 1 June 2026. Its existence is a useful current-affairs point because it connects statutory design with the administrative work of identifying aggregators and workers. For detailed thresholds or operational duties, read the actual communication and rule together. An onboarding instruction is not, by itself, a substitute for every benefit-scheme notification.

For exam revision, maintain a three-line update card: Code provision, final rule and implementation communication. This makes it easier to answer whether a statement concerns legislative authority, procedural detail or a particular administrative action. It also helps distinguish old notes that describe final rules as still draft.

National Social Security Board and funding

The Code assigns a role to the National Social Security Board in the welfare framework for gig and platform workers, with the relevant representation arrangements. Study its role alongside scheme formulation and administration. Do not confuse it with the Central Board administering provident-fund arrangements or with ESIC merely because all are social-security institutions.

Funding can involve sources identified in the statutory scheme, including government support, aggregator contributions and other specified arrangements. A sustainable scheme must connect expected benefits with reliable funding and administration. An ambitious list of benefits without an operational financing mechanism does not establish actual coverage.

For a Mains answer, discuss accountability as well as funding. Workers need clear information on enrolment, contribution records where relevant, benefit applications, rejections and grievance routes. Administrators need data quality and auditability. These are practical requirements for turning a legal framework into dependable social protection.

Central framework and state initiatives

State-level initiatives can address platform-worker welfare through their own legal and administrative arrangements. Do not assume that one state’s scheme applies throughout India. Likewise, do not assume that any state levy and the central aggregator contribution have identical legal bases, beneficiaries or collection methods.

When comparing initiatives, use a table with jurisdiction, legal source, worker definition, funding, benefits, institution and grievance system. If a question asks whether a particular contribution is due, identify the operative law and notification. A general discussion of national policy is not enough to determine a state-specific obligation.

This distinction is especially useful in current affairs. An announcement, a bill, an enacted state law, notified rules and a functioning benefit process are different stages. Record the stage and date rather than copying a headline that says a scheme has been “introduced” without explaining what that means.

Implementation challenges and practical reforms

Portability is a major issue because workers can move between platforms and states. A worker may also use more than one platform during the same period. Accurate identification should reduce duplication while avoiding exclusion. A sound system needs to recognise work across platforms without forcing a person to lose protection whenever an app account changes.

Variable income creates difficulty in contribution design and benefit continuity. Platform data can improve records, but workers need understandable correction and appeal mechanisms. Access to a smartphone does not automatically mean the person can resolve a complex rejected claim. Assisted service and multilingual guidance remain important.

Other concerns include awareness, grievance resolution, representation, privacy and the relationship between contributions and benefits. In an examination answer, pair each problem with a practical response: portable records, transparent statements, simple registration, clear eligibility communication, timely claim decisions and meaningful worker participation in the administrative framework.

Practice questions and a short-answer framework

Question 1: Does section 114 automatically place every gig worker in EPS? Answer: No. It enables notified schemes for the category; EPS membership has its own framework. Recognition and automatic enrolment in every employee scheme are different propositions.

Question 2: Is the 5% cap calculated on aggregator turnover? Answer: No. It is linked to amounts paid or payable to gig and platform workers. The turnover-based rate and the cap must be calculated separately.

Question 3: Does a platform-worker definition depend only on owning a mobile phone? Answer: No. The nature of the work arrangement and the statutory definition matter. A device is not a legal classification.

For a short descriptive answer, define the categories, identify section 114, explain registration and funding, then discuss portability and implementation. Conclude with practical institutional measures. Use the current rules and notifications for operational details, and clearly label any hypothetical example or editorial recommendation.