Gig & Platform Workers Under the Social Security Code

Gig and Platform Workers Under the Social Security Code: What Indian Employers Need to Know

India's labour market no longer fits the neat picture of full-time employees on a company payroll. Delivery partners, ride drivers, freelance designers, home-service professionals, warehouse helpers hired by the shift, and independent experts on digital marketplaces now form a visible part of the workforce. For years they sat in a legal grey zone: not quite employees, not quite traditional contractors, and mostly outside the social security net.

The Code on Social Security brought gig workers and platform workers into the statute for the first time, with definitions, a framework for contributions by aggregators and schemes for benefits. States have also moved on their own with platform worker legislation and welfare boards. For businesses, this raises practical questions. Are we an aggregator? Which of our freelancers count as gig workers? What do we owe, and where do we register? How should payroll and accounts treat these payments, and how do we avoid misclassifying employees as gig workers?

This guide explains the key concepts in plain language, helps you work out whether the framework touches your business, and lays out a practical compliance approach. It is written for founders, HR managers and finance teams at SMBs and startups that work with non-traditional workers.

Important: The Code on Social Security, its rules, schemes, contribution rates and state-level laws are evolving. Details such as the aggregator contribution percentage, registration portals, thresholds and timelines depend on notifications. Treat this article as general guidance, verify the latest position with official sources and consult a labour law professional before acting.

Why This Topic Matters Now

Several trends are converging.

1. Growth of platform-based work. More businesses use apps and marketplaces to match workers and customers.
2. Policy attention. Governments want social protection for workers who fall outside traditional employment.
3. Litigation and classification disputes. Workers and unions have challenged how platforms characterise their relationships.
4. State-level action. Some states have introduced or proposed laws creating welfare boards, registration and contribution mechanisms for platform workers.
5. Compliance expectations. Aggregators may need to register workers, make contributions and share data with authorities.

Even if you are not a large delivery or mobility platform, you may use gig-style arrangements for events, field work, content, logistics, installation or customer support. Understanding the framework helps you structure these arrangements properly.

Key Definitions in Plain Language

The Code on Social Security introduces several categories. The following explanations are simplified. Always check the exact statutory wording.

Gig worker

A person who performs work or participates in a work arrangement and earns from such activities outside of the traditional employer-employee relationship. A freelancer who takes assignments through different clients and is not on a client's payroll may fit here.

Platform worker

A person engaged in or undertaking platform work, which is work arranged through an online platform, outside the traditional employer-employee relationship, where the worker accesses organisations or individuals and earns by providing services. Delivery partners and app-based drivers are common examples.

Aggregator

A digital intermediary or marketplace for a buyer or user of a service to connect with the provider of that service. Aggregators are listed in a schedule to the code in specific sectors such as ride sharing, food and grocery delivery, e-marketplace, professional services, healthcare, travel, hospitality and content and media services. The schedule is a defined list that the government can amend.

Unorganised worker

A home-based worker, self-employed worker or wage worker in the unorganised sector, including some who work in the organised sector but are not covered by certain laws. Gig and platform workers are separate categories but may overlap with unorganised workers in practice.

Employee and worker

The traditional categories continue to apply for people employed under a contract of service. The gig label does not apply simply because a contract says so; the real nature of the relationship matters.

Is Your Business an Aggregator?

This is the first question to ask. Consider:

1. Do you operate a digital platform or app? If you connect customers with independent service providers, you may be an aggregator.
2. Is your sector within the list of aggregator categories? The code names categories, and the government may notify additions.
3. Do you control the service? If you set prices, assign tasks, rate and discipline the workers, the relationship may look more like employment, which brings different obligations.
4. Do you hire freelancers directly without a platform? Then you might simply be a business engaging independent contractors, not an aggregator. Your obligations are mainly under contract, tax and any applicable laws, but you should watch classification risk.

If you operate a marketplace-style business, seek legal advice on whether you fall under the aggregator definition and what registration or contribution duties apply.

Aggregator Obligations: A Summary

Under the framework, aggregators are expected to contribute to a social security fund for gig and platform workers. The code specifies that the contribution is a percentage of the aggregator's annual turnover, within a stated range, with a cap tied to the amount paid or payable to gig and platform workers. The precise percentage and the process are determined by notification. Do not rely on numbers you read in news articles; confirm from the official notification applicable to you.

Other expected obligations typically include:

1. Registration. Workers and aggregators may need to register on a government portal. Workers receive an identifier that supports portability of benefits.
2. Sharing data. Aggregators may be required to share information on workers engaged and payments made.
3. Contribution payments. On a periodic basis as notified.
4. Information to workers. Transparent communication about terms, payments and benefits.
5. Grievance mechanisms. Particularly where state laws require them.
6. Record keeping. Maintaining records of engagement, payments, ratings and deactivation decisions.

Penalties for non-compliance can apply, so build processes before the deadline, not after.

Benefits Contemplated for Gig and Platform Workers

The code provides for schemes for gig and platform workers that can include:

• Life and disability cover.
• Accident insurance.
• Health and maternity benefits.
• Old age protection.
• Provident fund-like benefits, creche facilities or skill upgradation, depending on the scheme.

Eligibility conditions can involve age, registration and a minimum number of days of engagement with aggregators in a year. The details are specified in schemes. Employers and platforms should understand these conditions because they affect how engagement data is recorded.

State-Level Developments

Some states have enacted or proposed platform worker laws that create welfare boards, registration systems and contribution mechanisms, such as a small fee on each transaction. These can differ from the central framework and from each other. If your workers or customers are in more than one state, track each state's rules. Key questions:

1. Does the state law apply to your sector?
2. Do you have to register the platform in the state?
3. Is there a transaction-based welfare fee?
4. What are the grievance and transparency requirements?
5. How do state and central obligations fit together?

Keep a simple register of applicable laws by state and review it quarterly.

The Classification Question: Gig Worker or Employee?

The biggest risk for many SMBs is not the aggregator contribution. It is misclassification: treating people who are in substance employees as independent gig workers.

Why it matters

If a person is an employee, you may owe minimum wages, provident fund, ESI, bonus, gratuity, leave, notice and other benefits. Back-liability, interest and penalties can accumulate. A contract that merely labels someone a freelancer or partner will not protect you if the actual working relationship shows control and integration.

Factors that point to employment

Indian courts and authorities look at the real nature of the relationship, often using tests such as control, integration, economic dependence and mutuality of obligation. Typical indicators include:

1. Control over how work is done. Fixed schedules, mandated methods, supervision.
2. Integration into the business. The person performs core functions as part of the organisation.
3. Exclusivity. The person is not allowed to work for others.
4. Tools and equipment. The company provides them and requires their use.
5. Fixed, regular pay. Monthly payment unrelated to deliverables.
6. Long, continuous engagement. Years of work under the same arrangement.
7. Disciplinary powers. The company can discipline or terminate like an employer.
8. Branding. The person is presented to customers as part of the company.

Factors that point to independence

1. Freedom to accept or reject assignments.
2. Ability to work for competitors or multiple clients.
3. Own tools and methods.
4. Payment by task, project or outcome.
5. Right to send a substitute, where appropriate.
6. Bears business risk and invests in their own business.
7. Short, defined assignments.

No single factor decides the matter. Review the whole picture. Our guide on employee versus contractor classification explains the risk in more depth.

A quick self-assessment

Score each engagement with a simple checklist: who decides schedule, who decides method, who provides tools, whether the person can work for others, how pay is determined, and how long the engagement has lasted. If most answers point to company control, treat the person as an employee or take legal advice to restructure the arrangement honestly.

Typical Gig-Style Arrangements in SMBs

Freelance professionals

Designers, writers, developers, consultants and analysts engaged project by project. Usually straightforward independent contractors, with a written agreement, deliverables and invoices.

Delivery and logistics partners

Local delivery partners engaged through an app. Aggregator rules may apply if you operate the platform. If you hire delivery staff directly with set shifts, they may be employees.

Event and promotional staff

Short-term staff for events, campaigns, exhibitions or retail promotions. Often engaged through staffing agencies, which brings contract labour rules into play.

Field executives and survey agents

People paid per visit, per lead or per survey. Check the degree of control, targets and exclusivity before classifying them as independent.

Customer support and back office on shift basis

Where agents work set shifts using company systems, the relationship tends toward employment.

Home-service professionals

Technicians and beauticians who accept jobs through a marketplace app. Platform worker rules are most relevant here.

Contract Design for Gig Engagements

Even when the classification is sound, a well-drafted agreement reduces disputes.

Clauses to include

1. Nature of relationship. Independent contractor or platform participant, with the practical reality matching the label.
2. Scope of work or tasks. Clear deliverables or task types.
3. Payment terms. Rate, unit of payment, schedule and any incentives.
4. Deductions. What is deducted (taxes, platform fee, penalties) and why. Be transparent.
5. Ratings and deactivation. Criteria, notice, review and appeal process.
6. Insurance and safety. What cover is provided and who bears which risks.
7. Data and privacy. How personal data is used and protected.
8. Confidentiality and IP. Especially for professional services.
9. Termination. Notice, reasons and settlement of dues.
10. Dispute resolution. A simple grievance channel and escalation.
11. Compliance with laws. Registration with the social security portal and sharing of details where required.

Avoid employment-like controls in a contractor agreement

Fixed working hours, mandatory attendance, restrictions on working for others and disciplinary clauses similar to a code of conduct for employees can undermine an independent status. If you need these controls, hire the person as an employee.

Payment, Tax and Accounting

TDS on payments to gig workers and freelancers

Payments to independent contractors and professionals may attract TDS under the relevant sections of the Income Tax Act depending on nature and amount. For platform payouts, specific provisions on e-commerce operators and payments to certain resident sellers or service providers have existed, with thresholds. Because the rules and thresholds change, confirm the current position with your tax adviser and set up your payables process to deduct and deposit TDS accurately.

GST

Independent service providers above the registration threshold may need GST registration. Aggregators may have specific liabilities for certain services. Check how GST applies to your platform and workers.

Invoicing and records

Collect invoices from freelancers where required. For platform payouts, generate payout statements that list tasks, amounts, fees and deductions. Keep these for audit.

Do not run gig payments through salary payroll

Mixing contractors into the employee payroll creates confusion about statutory deductions and misclassification evidence. Maintain a separate payables process, but ensure your HR and finance data link so that you can detect patterns such as a "freelancer" working full time for years.

Provident fund and ESI

These apply to employees as defined by their laws. If someone is correctly an independent contractor, they are generally outside employee-based PF and ESI, but they may be covered by gig worker schemes when notified. Do not assume that a contractor label automatically removes obligations.

Minimum Earnings and Fair Pay Considerations

The minimum wages framework is designed for employees. Gig and platform workers are typically paid per task. Still, think about fairness:

1. Transparent rate cards. Workers should know what they will earn per task and how bonuses work.
2. Waiting time and idle periods. Consider whether tasks are priced to make work sustainable.
3. Fuel, data and equipment costs. Workers often bear them. Reflect this when setting rates.
4. Timely payment. Weekly or fortnightly payouts are common; delays create distress and reputational risk.
5. Surge and incentive rules. Publish clear terms.

Fair pay is not only an ethical choice. It reduces churn and dispute risk.

Safety, Insurance and Wellbeing

Gig work can involve road travel, late hours, heat, and customer interaction. Responsible businesses consider:

1. Accident cover. Insurance for on-duty accidents.
2. Health benefits. Access to health cover or wellness programmes.
3. Safety training. Road safety, customer handling and emergency response.
4. Protective equipment. Helmets, high-visibility gear and rain protection where relevant.
5. Rest provisions. Limits or alerts to avoid fatigue.
6. Harassment prevention. Clear channels for complaints, especially for women workers.
7. Grievance redress. A responsive helpline.

Coverage under the national schemes, once available, should complement rather than replace any insurance you provide.

Data, Algorithmic Management and Transparency

Platforms often use algorithms to assign tasks, rate performance and set pay. This raises fairness and privacy concerns, and authorities are paying attention.

Good practice includes:

1. Explain how ratings work. Share the criteria in simple language.
2. Offer human review. Provide an appeal for deactivation or penalties.
3. Limit data collection. Collect only what you need, such as location during active tasks.
4. Protect personal data. Follow the data protection law as applicable, including purpose limitation, security and consent where required. Our guide on the DPDP Act for HR teams explains the basics.
5. Check for bias. Make sure rules do not unfairly disadvantage particular groups.
6. Document changes. Notify workers when pay or assignment rules change.

A Compliance Roadmap for SMBs

Step 1: Inventory your non-employee workforce

List every freelancer, platform participant, agency worker and consultant. For each, record the nature of work, duration, payment method, control level and whether they work for others.

Step 2: Classify each engagement

Use the factors above. Mark each as employee, independent contractor, gig or platform worker, agency or contract labour worker. Escalate doubtful cases.

Step 3: Determine whether you are an aggregator

If you operate a digital intermediary in a listed sector, plan for registration, contribution and data-sharing obligations.

Step 4: Fix contracts

Update agreements to reflect real relationships, include transparent payment and deactivation terms, and remove employment-like controls where the person is meant to be independent.

Step 5: Set up payments properly

Build a separate payables workflow with invoices or payout statements, TDS, GST where applicable and timely payment.

Step 6: Prepare for registration and data sharing

Identify which data you will need: worker identity, engagement days, payments, location of work. Make sure you collect it lawfully and store it securely.

Step 7: Provide safety and insurance

Evaluate risk and set up basic cover and safety training.

Step 8: Build grievance and transparency mechanisms

Create a channel for questions and complaints, an appeal route for deactivation and clear communication on changes.

Step 9: Train managers

Teach managers not to treat contractors as employees in practice, for example by assigning fixed hours or disciplinary action.

Step 10: Monitor law changes

Subscribe to updates from labour ministry notifications and state labour departments. Review quarterly.

Agency and Contract Labour: A Different Route

Many companies obtain flexible workers through staffing agencies or contractors. These workers are not gig workers; they are employees of the contractor or agency, and the principal employer may carry responsibilities under the contract labour framework. If you use such an arrangement:

1. Verify that the contractor holds the required licence and registrations.
2. Ensure wages and statutory contributions are paid on time.
3. Retain evidence such as challans and registers.
4. Avoid direct control that blurs the employer relationship.
5. Review principal employer liabilities.

Our guide on contract labour compliance for principal employers explains the obligations.

Fixed-Term Employment as an Alternative

If your need is for temporary but dedicated workers who follow your schedules and work under your supervision, fixed-term employment may be the honest and compliant option. The labour codes recognise fixed-term employees, with benefits proportionate to permanent employees and gratuity eligibility after a shorter service period in the relevant context. This route offers flexibility without misclassification risk. See our guide on gratuity for fixed-term employees.

Managing Risk: Red Flags to Watch

1. A "freelancer" who has worked full time for you for years with a fixed monthly payment.
2. Contractors who use company email IDs, attend daily stand-ups and follow set hours.
3. Contractor agreements that prohibit working for anyone else.
4. Penalties for absence or lateness.
5. Disciplinary language in contractor communications.
6. Sudden deactivations without explanation.
7. Delayed payments.
8. No written agreement.
9. Tax deducted inconsistently.
10. Workers unaware of the terms that apply to them.

Address red flags early. Switching a worker to employee status proactively is better than facing a claim.

Reporting and Analytics for Non-Employee Workforce

Track the following to stay in control:

Review these with HR, finance and legal each quarter.

Worker Communication: Keep It Plain and Respectful

Gig and platform workers often come from varied backgrounds and may not read long legal documents. Communication that is clear and local builds trust and reduces disputes.

1. Use simple language. Summarise key terms on one page: how pay is calculated, when payouts happen, what can lead to deactivation and how to raise a concern.
2. Offer local language versions. Provide translations for the main languages of your workforce.
3. Use the channel workers actually use. In-app notices, messaging apps and short voice notes may work better than email.
4. Announce changes in advance. Give notice before changing rates, incentives or rules, and explain the reason.
5. Provide a human contact. A helpline or support person who can resolve issues makes a large difference.
6. Share payout breakdowns. Show gross earnings, deductions and net payment for each cycle.

Practical Example: A Small Home-Services Marketplace

Imagine a startup with a mobile app connecting households with electricians, plumbers and cleaners. It has eight employees and about 300 service professionals who accept jobs through the app.

• Aggregator check. The startup operates a digital intermediary in a service category, so it should review aggregator obligations, registration and data-sharing requirements, and prepare for contributions as notified.
• Classification. Service professionals choose jobs, use their own tools and can work on competing apps, which supports independent status. The startup avoids fixed shifts and attendance rules.
• Contracts. A short platform agreement explains fees, payouts, ratings, deactivation review and insurance.
• Payments. Weekly payouts with a statement. TDS and GST handled as the law requires.
• Safety. Basic accident cover and a short onboarding on customer conduct and safe practices.
• Grievances. An in-app support channel and a review panel for deactivation disputes.
• Records. The startup keeps job logs, payout records and communication history for audits.

The company still hires its eight core staff as employees on payroll with PF, ESI and other benefits where applicable. The line between the two groups is clear and based on the real nature of the work.

Frequently Asked Questions

1. What is the difference between a gig worker and a platform worker?

A gig worker earns from work arrangements outside the traditional employer-employee relationship, which can include freelance work for various clients. A platform worker's work is arranged through an online platform. Many people are both, such as a delivery partner or a freelance professional on a marketplace.

2. Does the Code on Social Security make gig workers employees?

No. The code recognises gig and platform workers as separate categories and provides for social security schemes, rather than converting them into employees. However, if the actual relationship is employment, the person may still be treated as an employee regardless of the label.

3. Who is an aggregator under the code?

An aggregator is a digital intermediary or marketplace that connects buyers of a service with providers of it. The code lists sectors where aggregators are recognised and allows the government to add more. Check whether your business fits.

4. How much must aggregators contribute?

The code sets a range as a percentage of annual turnover, capped by a share of the amount payable to gig and platform workers. The exact rate and procedure come through notification, so confirm the latest figures from official sources before budgeting.

5. Do freelancers need provident fund or ESI?

If a person is genuinely an independent contractor, employee-based PF and ESI generally do not apply. If the person is in substance an employee, these obligations can arise. Gig worker schemes may offer separate benefits once notified.

6. How do I know if my freelancer could be treated as an employee?

Look at control over how and when work is done, exclusivity, integration into your business, fixed monthly pay, tools provided and length of engagement. If most factors point to control and dependence, seek legal advice and consider converting the person to an employee.

7. Should we deduct TDS from freelancers?

In many cases yes, depending on the nature of payment, status of the payee and thresholds. Rules change, so confirm the applicable section and rate with your tax adviser and apply them consistently.

8. Do state platform worker laws apply in addition to the central code?

Several states have introduced their own frameworks. They can apply alongside the central code, with differences in registration, fees and grievance mechanisms. Check the laws of each state in which you operate.

9. Can we use gig workers instead of hiring employees to reduce costs?

You can engage independent workers for genuinely independent work. But using gig labels to avoid obligations for people who function as employees is risky and may lead to liability. Choose the arrangement that matches reality.

10. How can CozyHR help with a mixed workforce?

CozyHR helps you maintain a clear register of employees and contractors, track engagement duration and categories, and keep HR and payroll data organised so classification reviews and compliance reporting are easier.

Conclusion

The arrival of gig and platform workers in the Code on Social Security is a sign that the definition of work is widening. For most SMBs the practical agenda is simple: know who works for you and on what basis, classify each engagement honestly, write fair contracts, pay on time with correct tax treatment, and stay ready for aggregator obligations if you operate a platform.

Start with an inventory of every non-employee worker, test each engagement against the control and independence factors, and fix the ones that fail. Verify current contribution rates, registration processes and state laws with official sources and a qualified adviser.

If you want a cleaner record of your workforce across employees, contractors and agency staff, you can try CozyHR. It helps Indian SMBs and startups keep people data organised and compliance-ready as the world of work keeps changing.