Gig & Platform Workers: An Employer's Compliance Guide

Gig & Platform Workers: An Employer's Compliance Guide

Gig and platform workers have moved from the edges of the Indian workforce to the centre of it. Delivery riders, drivers, freelance designers, on-demand technicians, content moderators, home-service professionals — every one of them works outside the traditional employer–employee mould, and every one of them is now firmly on the radar of India's labour law framework. If your company engages gig workers or platform workers in any form, gig worker compliance is no longer optional housekeeping. The Code on Social Security formally recognises gig and platform workers, several states have passed or proposed their own gig worker welfare laws, and enforcement attention on classification and social security is rising every quarter.

This guide explains, in practical terms, what founders, HR managers and payroll teams need to do: how to classify workers correctly, what obligations attach to aggregators and engagers, how to structure contracts and payments, and how to build a compliance runbook that survives an audit. It is written for SMBs and startups in India, but the principles travel well to any market that is formalising platform work.

One note before we start: this area of law is evolving quickly. Central rules, state rules and welfare board notifications are being issued in phases, and rates or thresholds may change. Treat this article as a working map, not legal advice, and verify current notifications on official government portals or with your labour law advisor before acting.

Who Is a Gig Worker? Definitions That Decide Everything

Getting definitions right is the foundation of gig worker compliance, because different categories attract different obligations.

The three key terms

• Gig worker: broadly, a person who performs work or participates in a work arrangement and earns from such activities outside a traditional employer–employee relationship. A freelance graphic designer paid per project is a gig worker even if no app is involved.
• Platform worker: a subset of gig workers whose work is organised through an online platform — ride-hailing drivers, food delivery partners, home-services professionals booked through an app.
• Aggregator: the digital intermediary or marketplace that connects buyers of services with workers who provide them. Ride-sharing services, food and grocery delivery apps, logistics platforms, e-marketplaces, professional services platforms and content platforms typically fall in this bucket.

Why the distinction matters

The obligations differ by category:

• Traditional employees get the full stack: PF, ESI (where applicable), gratuity, paid leave, statutory bonus and so on.
• Gig and platform workers are not "employees" for most of those statutes, but the Code on Social Security contemplates dedicated welfare schemes for them, funded partly by aggregator contributions.
• Independent contractors who genuinely run their own business remain governed mainly by contract law and tax law, but the label on the invoice does not decide the relationship — substance does.

If you remember one thing from this section: calling someone a "partner" or "freelancer" in a contract does not make them one in the eyes of a labour inspector or a court. Control, integration and economic dependence are what get examined.

Why Gig Worker Compliance Is Urgent Now

Three shifts have converged to make this a board-level topic.

1. The labour codes are operational

With the four labour codes notified and being implemented in phases, the Code on Social Security's provisions on gig and platform workers have moved from paper to practice. The code contemplates registration of gig and platform workers, a social security fund, and schemes covering life and disability cover, accident insurance, health and maternity benefits, old-age protection and more. Aggregators are expected to contribute a small percentage of their annual turnover towards these schemes, subject to caps linked to amounts paid to workers — the exact operative rates and mechanics depend on notifications, so verify the current position before budgeting.

2. States are legislating on their own

Several states have enacted or proposed dedicated gig worker welfare laws — Rajasthan and Karnataka moved early with platform-based gig worker statutes, and other states have bills or schemes in progress. These laws typically create a state welfare board, require aggregators to register and share worker data, and levy a welfare fee or cess on transactions. If you operate across states, you may face layered obligations: central code requirements plus state welfare board registrations, each with its own filings and timelines.

3. Misclassification risk has real teeth

Globally and in India, disputes about whether platform workers are actually employees keep multiplying. The financial exposure in a misclassification finding is not just prospective: it can include retrospective PF and ESI contributions, interest, damages and penalties, plus the operational shock of converting a contractor cost line into an employment cost line. For a funded startup heading into due diligence, an unresolved classification risk can directly affect valuation.

Classification: Employee, Contractor or Gig Worker?

Before you design any compliance process, classify every non-payroll worker honestly. Indian courts and authorities look past labels and apply substance-based tests.

The tests that matter

• Control test: Who decides how, when and where the work is done? Fixed shifts, mandatory login hours, supervisor approval of methods and disciplinary consequences for refusing tasks all point towards employment.
• Integration test: Is the person's work integral to the core business, or peripheral? A rider is integral to a delivery platform; a one-off logo designer is not integral to a fintech.
• Economic dependence: Does the worker earn all or most of their income from you? Exclusive arrangements and non-competes push towards employment.
• Provision of tools: Who supplies the vehicle, laptop, uniform, or software licences?
• Financial risk and opportunity: Genuine contractors can make a profit or loss, negotiate rates and substitute themselves; employees cannot.

A practical classification matrix

Score every engagement category against this matrix once a year and whenever the operating model changes. Document the assessment — a dated classification memo is one of the cheapest pieces of audit armour you can buy.

Grey zones to watch

• "Full-time freelancers" who work 9-to-6 on your tools with your team for months are the classic misclassification trap.
• Interns and trainees engaged through platforms need separate treatment; stipend-based apprenticeships have their own statutory framework.
• Moonlighting employees of others working gigs for you create conflict and confidentiality issues, though the classification analysis is unchanged.

What the Code on Social Security Expects

The Code on Social Security is the central pillar of gig worker compliance in India. The framework, at a high level, works like this — always verify the currently notified rules for specifics.

Registration and the national database

Gig and platform workers are expected to register, including on government portals created for unorganised and platform workers, with Aadhaar-seeded records. Aggregators are expected to help facilitate registration and share worker data with authorities. For HR teams this means your worker master data — names, IDs, bank details, engagement dates, categories of work — must be clean, current and exportable.

The social security fund and aggregator contributions

The code contemplates a social security fund for gig and platform workers, financed partly by aggregator contributions calculated as a percentage of annual turnover (with a cap linked to payments made to workers), plus government contributions. Key operational implications:

• Budget for the levy: build the contribution into unit economics now, even if your sector's notification is pending.
• Track payouts precisely: because caps reference amounts paid to workers, your payout ledgers must be reconcilable to the rupee.
• Watch sector notifications: schemes may be rolled out sector by sector (transport, delivery, e-commerce and so on) with different administrative arrangements.

Benefits contemplated for gig workers

Schemes under the code may cover:

• Life and disability cover
• Accident insurance
• Health and maternity benefits
• Old-age protection and pension-style benefits
• Creche and other welfare measures depending on scheme design

None of these convert a gig worker into an employee — they create a parallel welfare track. But they do create process obligations for the companies that engage these workers: registration support, data sharing, contribution payment and grievance handling.

State Welfare Boards and Layered Obligations

If the central code is the skeleton, state laws are fast-growing muscle. State platform-gig-worker statutes commonly include:

• Aggregator registration with a state welfare board within a defined window
• Worker database contributions: uploading and updating rosters of platform workers operating in the state
• A welfare fee or cess, often calculated per transaction or as a percentage of payouts within the state
• Transparency duties, sometimes extending to how automated systems allocate work or terminate access
• Grievance mechanisms with defined response timelines

What multi-state operators should do

1. Map every state where workers actually perform work — not just where your entity is registered.
2. Maintain a state-wise compliance register: applicable law, registration status, fee rates, filing cadence, responsible owner.
3. Build payout reports that can be sliced state-wise, since welfare fees are typically state-scoped.
4. Assign one owner (HR ops or compliance) for monitoring new bills — this space changes quarter to quarter.

Contracts for Gig and Platform Workers

A well-drafted engagement contract is your first line of defence. It cannot override reality, but it can document a genuinely independent relationship and allocate obligations cleanly.

Clauses your gig worker agreement should cover

• Nature of relationship: an explicit statement of independent engagement, with honest operational terms to match.
• Scope and acceptance: task- or project-based deliverables; the worker's right to accept or decline work.
• Fees and payment terms: per-task, per-hour or per-project rates; payment cycles; deductions, if any, spelled out transparently.
• Taxes: who bears what; TDS treatment (see below); the worker's obligation to file their own returns.
• Insurance and benefits: any accident or health cover you voluntarily provide, and clarity that statutory scheme benefits flow per applicable law.
• Equipment and expenses: who provides tools, vehicles, data plans; reimbursement rules.
• Confidentiality and data protection: handling of customer data, platform data and personal data, aligned to DPDP obligations.
• IP assignment: for creative and technical gig work, deliverable IP transfer on payment.
• Health & safety: safety norms, protective equipment where relevant, incident reporting.
• Suspension and deactivation: clear, fair criteria; notice where feasible; an appeal channel — increasingly a regulatory expectation, not just good practice.
• Dispute resolution and governing law.

What to avoid

• Non-competes and exclusivity for workers you claim are independent
• Disciplinary language borrowed from employment contracts
• Mandatory fixed shifts without operational justification
• "Deemed acceptance" of unilateral rate cuts buried in updates

Onboarding and Documentation Workflow

Treat gig onboarding with the same rigour as employee onboarding — just with a different checklist.

A step-by-step gig onboarding flow

1. Pre-engagement screening: identity verification (with consent), age check (18+), licence/permit checks for regulated work (driving, electrical, food handling).
2. Classification confirmation: tag the worker's category (gig / platform / contractor) in your HRMS against the classification matrix.
3. Contract execution: e-signed agreement, stored centrally with version history.
4. Tax data capture: PAN (mandatory for TDS), GST registration status if applicable, bank account verification via penny-drop.
5. Registration support: guide the worker through applicable government portal registration; record the acknowledgement.
6. Induction: safety briefing, code of conduct, grievance channel, data protection notice.
7. System provisioning: app access, ID badge if client-facing, communication channels.
8. Records: store all of the above with retention rules; you may need to produce them years later.

An HRMS that supports non-employee worker types is invaluable here. Running gig workers through spreadsheets while employees live in a proper system is how records get lost and audits get painful.

Payments, TDS and Invoicing

Paying gig workers correctly is half of gig worker compliance. The tax mechanics differ fundamentally from salary.

TDS on gig payments

Payments to gig workers are typically subject to TDS under the Income-tax law's provisions for contractual or professional payments, and e-commerce operators have their own TDS provisions for payments to e-commerce participants. Which section applies, at what rate, and with what thresholds depends on the nature of the work and the structure of the platform — and rates and thresholds change with Finance Acts. Practical rules of thumb:

• Collect and validate PAN before first payout; higher TDS applies where PAN is absent.
• Classify each payout stream (contractual work, professional services, platform-facilitated sale of services) and map it to the correct TDS section with your CA.
• Deposit TDS and file returns on the statutory cadence; issue TDS certificates to workers on time.
• Reconcile payout ledgers to TDS returns quarterly — mismatches trigger notices.

GST considerations

Some gig workers, especially higher-earning professionals, may be GST-registered and will invoice you with GST. Some platform sectors operate under reverse-charge or platform-liability mechanics. Confirm treatment sector-wise with your tax advisor; do not let individual operations teams improvise.

Payment hygiene that prevents disputes

• Publish a clear payout calendar and stick to it; delayed payouts are the top source of gig grievances.
• Itemise every payout: task fees, incentives, tips, deductions, TDS. An opaque payout statement is a dispute factory.
• Keep deduction categories minimal, contractual and explainable.
• Maintain a payout error SLA — wrong payouts corrected within a defined number of days.

Benefits and Welfare: Statutory and Voluntary

The statutory layer

As schemes under the central code and state laws go live, expect obligations like contribution payment, data sharing and facilitation of enrolment. Track notifications and budget for them.

The voluntary layer that pays for itself

Leading engagers of gig workers do not stop at the statutory floor, because attrition and churn among gig workers is expensive. High-ROI voluntary benefits include:

• Accident and hospitalisation cover beyond statutory schemes
• Vehicle and equipment support: maintenance tie-ups, financing facilitation
• Skilling pathways: certifications that raise worker earning capacity on your platform
• Earnings stability tools: minimum-engagement guarantees for high-performers, surge transparency
• Rest infrastructure for field workers: partnered rest stops, hydration points

Position these clearly as welfare measures under a structured program, documented separately from any employment-style benefits, so goodwill does not accidentally become evidence of employment.

Algorithmic Management and Fair Deactivation

Regulators and courts increasingly focus on how platforms use algorithms to allocate work, rate workers and deactivate accounts. Expectations you should build for now:

• Transparency: workers should be able to understand, at a usable level, how work allocation and ratings affect their earnings and standing.
• Human review of deactivation: a permanent loss of platform access should not be a black-box outcome; provide notice of reasons and an appeal path with human review.
• Bias checks: periodically test allocation and rating systems for discriminatory patterns.
• Records: log deactivation reasons and appeal outcomes; these records are your defence in disputes.

A one-page "fair deactivation policy" published to workers costs little and materially reduces both regulatory and reputational risk.

Data Protection for Gig Workforce Data

Gig operations run on data: identity documents, live location, earnings, ratings, sometimes health information. Under India's data protection law (DPDP), you are processing personal data of workers at scale, which means:

• Notice and consent: clear notices at onboarding covering what data you collect and why, in plain language.
• Purpose limitation: location tracking justified for active tasks is different from 24/7 tracking; design for the former.
• Security: worker KYC documents are a breach goldmine; encrypt, restrict access, and log access.
• Retention: define how long you keep data for departed workers, balancing statutory record needs against minimisation.
• Rights handling: a channel for workers to access and correct their data.

Fold gig worker data into your existing DPDP program rather than treating it as an afterthought — regulators will not distinguish between employee and gig data sloppiness.

Governance: Running a Blended Workforce Without Chaos

Most companies now run a blend: employees, fixed-term staff, contractors, agency workers and gig workers. Governance principles that keep the blend compliant:

Single system of record

Every worker of every type should exist in one system with a worker-type tag, engagement dates, documents and payment history. Fragmented records across ops tools, spreadsheets and vendor portals are the root cause of most compliance failures.

Quarterly workforce review

A standing HR–finance–legal review each quarter should cover: headcount by worker type, classification exceptions, contribution and levy payments made, state registrations status, grievance and deactivation statistics, and upcoming regulatory changes.

Metrics that matter

• Percentage of gig workers with complete documentation
• TDS reconciliation status
• Payout accuracy and timeliness
• Grievance resolution time
• Attrition/churn among gig workers by cohort

Comparison: your obligations at a glance

Common Mistakes and How to Avoid Them

1. Treating the contract as the compliance. The document matters, but inspectors look at rosters, app screenshots and payment patterns.
2. One national approach in a state-by-state world. Welfare fees and registrations are state-scoped; centralise monitoring, localise execution.
3. Ignoring PAN hygiene. Missing PANs mean higher TDS, unhappy workers and messy reconciliations.
4. Discipline-style deactivations. Punitive, unexplained cut-offs create both misclassification evidence and legal exposure.
5. Letting ops teams improvise payments. Every payout stream needs a tax and accounting design before it goes live.
6. No owner. Gig compliance falls between HR, finance and ops; someone senior must own the register.
7. Assuming small scale means exemption. Thresholds vary by statute and state; verify rather than assume.

A 90-Day Gig Compliance Runbook

Days 1–30: Discover and classify

• Inventory every non-payroll worker and payment stream
• Run the classification matrix; flag high-risk cohorts
• Map states of actual work performance
• Collect missing PANs and contracts

Days 31–60: Fix the foundations

• Standardise gig agreements with legal review
• Set up worker-type tagging in your HRMS
• Design TDS mapping per payout stream with your CA
• Register with applicable state boards; calendar the filings
• Draft the fair deactivation and grievance policy

Days 61–90: Operationalise

• Automate payout statements with itemisation
• Launch the grievance channel and train the team
• Run the first quarterly workforce review
• Build the state-wise compliance register with owners and due dates
• Brief leadership on levy budgeting and pending notifications

Worked Example: A Hyperlocal Delivery Startup Gets Compliant

Theory lands better with a concrete picture. Consider "SwiftKart", a fictional hyperlocal delivery startup operating in three cities across two states, with 40 employees and around 600 delivery partners engaged through its app.

Where SwiftKart started

• Delivery partners signed a two-page "partner agreement" copied from a template, silent on taxes and deactivation.
• Riders were tracked in one giant spreadsheet maintained by city ops leads; roughly one in five records lacked a PAN.
• Payouts went out weekly, but incentive calculations were manual and disputed constantly.
• A city manager had begun mandating minimum login hours and blocking riders who declined orders three times in a day — classic employment-style control creeping into a gig model.
• Nobody had checked whether either state had a gig worker welfare law in force.

What the 90-day cleanup looked like

Month 1 — Discovery. Finance pulled every payout stream into one ledger and matched it to worker records. The classification matrix flagged the minimum-login-hours practice as the top risk, and it was withdrawn in favour of incentive-based availability windows. Missing PANs were collected through an in-app campaign tied to the next payout cycle.

Month 2 — Foundations. Legal rewrote the partner agreement: task-level acceptance rights, transparent per-drop pricing, itemised deduction rules, a deactivation policy with a 48-hour appeal window and human review. HR moved all 600 partners into the HRMS as a distinct worker type with document vaults. The CA mapped payout streams to the correct TDS provisions and set up quarterly reconciliation.

Month 3 — Operations. Payout statements became itemised and automated. One state turned out to have a platform worker welfare law in force; SwiftKart registered with the welfare board, built a state-wise payout report for the levy, and calendared the filings. The COO now receives a monthly one-page dashboard: documentation completeness, payout accuracy, grievance ageing, deactivation appeals.

What changed commercially

Rider churn fell measurably within two quarters — partners stayed because payouts became predictable and disputes got answered. Diligence for the next funding round closed without a single workforce red flag. The total cost was one legal engagement, a few weeks of ops time and an HRMS configuration — a fraction of what a single retrospective PF demand would have cost.

The lesson: gig compliance done early is cheap, and it compounds. Done late, it is expensive, and it compounds the other way.

Preparing for Inspections and Audits

As schemes and state boards become operational, inspections and information requests will follow. You want to be the company whose response takes an afternoon, not a month.

Build an evidence pack that always stays current

Maintain a standing folder (digital, access-controlled) containing:

• Current template agreements for every worker type, plus the classification matrix and the latest annual classification memo
• Worker rosters by state with engagement dates and status
• Twelve months of payout summaries, TDS challans and return acknowledgements
• Welfare board registration certificates and levy payment receipts
• The deactivation policy, grievance SOP and their logs
• Data protection notices served to workers

How to handle an information request

1. Route every notice to the designated owner the day it arrives; log it in a compliance tracker with the response deadline.
2. Respond from records, not memory — this is where the single system of record pays off.
3. Keep responses factual and complete; partial or improvised answers invite escalation.
4. If a position is uncertain (for instance, an applicability question under a new state law), take written professional advice before responding, and preserve it.

Internal audit cadence

Run a light internal audit every six months: sample twenty gig worker files for completeness, re-run the classification matrix on any engagement model that changed, reconcile one quarter of TDS end-to-end, and test the grievance SLA with a dummy ticket. Findings go into the quarterly workforce review with owners and dates. This half-yearly rhythm is the difference between "audit-ready" as a slogan and as a fact.

Communicating With Your Gig Workforce

Compliance built in a back office fails at the last mile if workers do not understand it. A short communication layer multiplies the value of everything above:

• Onboarding in plain language: a one-page visual summary of pay structure, deductions, TDS and insurance — in the languages your workers actually read.
• Payout literacy: a standing explainer for every line item on the payout statement; most disputes are comprehension gaps, not calculation errors.
• Scheme awareness: when government schemes go live for gig workers, help workers enrol and claim; facilitation costs little and builds durable loyalty.
• Change notices: rate or policy changes announced with reasonable lead time, not discovered inside an app update.
• A named channel: workers should know exactly where to raise an issue and how long an answer takes.

Companies that treat gig workers as a communications afterthought pay for it in churn, disputes and — increasingly — regulatory complaints filed by workers who felt they had no other route.

Frequently Asked Questions

Are gig workers entitled to PF and ESI in India?

Genuine gig workers are outside the classical PF/ESI employee framework, but the Code on Social Security contemplates dedicated schemes for gig and platform workers funded partly by aggregator contributions. Misclassified employees, however, can be brought retrospectively into PF/ESI with interest and penalties — which is why classification is the first control.

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

All platform workers are gig workers, but not all gig workers are platform workers. A platform worker's work is organised through an online platform (apps, marketplaces). A freelance consultant sourced through referrals is a gig worker but not a platform worker.

Do small startups have to worry about aggregator contributions?

If your business model matches the aggregator definition — digitally intermediating between service seekers and workers — you should track the central scheme notifications and any state laws where your workers operate. Thresholds and mechanics vary; verify current notifications rather than assuming exemption by size.

Can we give gig workers benefits without making them employees?

Yes, if you structure benefits as a documented welfare program distinct from employment benefits and keep the operational relationship genuinely independent. Avoid mirroring employee-only benefits wholesale; that pattern, combined with control factors, strengthens a misclassification argument.

How should TDS be deducted on payments to gig workers?

It depends on the nature of the payment — contractual work, professional services and platform-facilitated transactions attract different provisions, rates and thresholds, which change with Finance Acts. Map each payout stream with your tax advisor, validate PANs before payout, and reconcile TDS filings to payout ledgers quarterly.

What records should we maintain for gig workers?

Identity and eligibility documents, executed agreements, classification assessments, payout statements, TDS records, registration acknowledgements, grievance logs and deactivation records. Keep them in one system with defined retention periods.

Do state gig worker laws apply if our company is registered elsewhere?

Generally, state welfare laws attach to where platform work is performed, not where your entity is registered. If your riders operate in a state with a gig worker law, expect registration and levy obligations there. Verify each statute's applicability tests.

What is the biggest single risk to get ahead of?

Misclassification. Every other obligation — levies, registrations, data sharing — is manageable operationally. A finding that your "gig workers" were employees rewrites your cost base retrospectively and can derail fundraising or M&A.

Conclusion: Build the Rails Before the Train Arrives

Gig and platform work is now a permanent, regulated layer of the Indian workforce. The direction of travel is unmistakable: registration, welfare funding, fair-treatment duties and data obligations will keep tightening, centrally and state by state. Companies that build clean classification, contracts, payment hygiene and a living compliance register today will absorb each new notification as a configuration change. Companies that improvise will face each one as a crisis.

You do not need a big compliance department to get this right — you need one system of record, one owner, and a quarterly rhythm. A modern HRMS like CozyHR helps you manage employees and gig workers side by side: worker-type tagging, document vaults, payout records, TDS-ready reports and compliance calendars in one place. If you are formalising your gig workforce this year, take a free trial of CozyHR and turn this runbook into your operating system.

This article provides general information for HR and payroll practitioners. Statutory schemes, rates and state laws in this area are being notified in phases and change frequently — verify current government notifications or consult a qualified professional before acting.