Gig Workers in India: Social Security & Employer Guide 2026

Gig Workers in India: Social Security & Employer Guide 2026

The way India works is changing. A decade ago, most organisations thought of their workforce in two simple buckets: permanent employees on payroll, and everyone else. Today, gig workers in India form a fast-growing third pillar of the labour market — delivery partners, drivers, designers, developers, content writers, trainers, beauticians, technicians, and consultants who work outside the traditional employer-employee relationship. Whether you run a startup that engages freelance developers, a logistics business that works with delivery partners, or a mid-sized company that mixes full-time staff with project-based contractors, you are already managing what HR professionals call a blended workforce.

This shift brings real advantages — flexibility, speed, access to specialised skills — but it also brings new obligations. The Code on Social Security, one of India's four consolidated labour codes, formally recognises gig workers and platform workers for the first time and introduces the concept of social security for people who do not have a conventional employer. At the same time, several Indian states have been moving ahead with their own gig worker welfare legislation and welfare boards. For employers and aggregators, the message is clear: the era of treating gig engagement as a compliance-free zone is ending.

This guide explains, in practical terms, who counts as a gig worker in India, how gig workers differ from platform workers, contract labour, and consultants, what the Code on Social Security broadly expects from aggregators, how to engage and pay gig workers correctly, and how to manage a blended workforce without drowning in spreadsheets. One important note before we begin: the rules in this area are still being operationalised, and implementation varies by state and evolves through government notifications. Treat this article as a practical orientation, not legal advice — always verify the current notifications applicable to your business and consult a qualified professional for specific decisions.

Who Counts as a Gig Worker in India? Definitions That Matter

Before you can comply with anything, you need to know which category each person in your extended workforce falls into. Indian labour law — and everyday business usage — uses several overlapping terms, and confusing them is the root cause of most compliance problems.

Employee

An employee works under a contract of employment. The organisation controls not just what work is done, but how, when, and where it is done. Employees receive a salary, are on the company's payroll, and are covered by the full stack of employment law obligations: provident fund and state insurance contributions where applicable, gratuity, statutory leave, bonus provisions, minimum wages, working hour limits, and protection against unfair termination. The employer deducts tax on salary under the salary TDS provisions and issues Form 16.

Gig Worker

The Code on Social Security describes a gig worker, in broad terms, as a person who performs work or participates in a work arrangement and earns from such activities outside of a traditional employer-employee relationship. Think of a freelance graphic designer who takes on projects from multiple clients, a wedding photographer, or an independent trainer who runs workshops for several companies. The defining feature is that they earn from work arrangements that are not employment. They choose their clients, often set their own rates, and are not subject to the day-to-day control that characterises employment.

Platform Worker

A platform worker is, broadly speaking, a specific type of gig worker: someone who accesses work through an online platform or app that connects them with customers — ride-hailing drivers, food and grocery delivery partners, home-services professionals booked through an app, and similar roles. The platform (called an "aggregator" in the Code's framework) does not employ them in the traditional sense, but it intermediates the work, often sets pricing and service standards, and controls access to the customer base. Because of this intermediary role, the Code places specific welfare-related expectations on aggregators, which we cover in detail below.

Contract Labour

Contract labour is different from both of the above. Here, workers are employed by a contractor (a manpower agency or service provider), and that contractor deploys them to work at your premises or on your projects. The workers are employees — just not your employees. Contract labour arrangements are governed by their own regulatory framework, which places obligations on both the contractor (the direct employer) and the principal employer (your organisation). If the contractor defaults on wages or statutory contributions, liability can travel up to the principal employer. Housekeeping staff, security guards, and factory workers supplied by an agency are classic examples.

Consultant / Independent Professional

A consultant is an independent professional or firm engaged for expertise — a chartered accountant on retainer, a fractional CFO, a legal advisor, a management consultant. Consultants typically operate through a professional practice or company, raise invoices, manage their own taxes and compliance, and serve multiple clients. In substance they are a subset of independent contractors, and much of what applies to gig workers on the contracting and tax side applies to them too.

Fixed-Term Employee

One more category worth knowing: a fixed-term employee is a regular employee hired for a defined period. Under the labour codes' framework, fixed-term employees are broadly entitled to the same wages and benefits as permanent employees doing similar work, on a pro-rata basis where relevant. A fixed-term employee is not a gig worker — this is a common and costly confusion. If you want someone on your premises, working your hours, under your supervision, for a defined project period, the honest classification is usually fixed-term employment, not a "consultant agreement."

Employee vs Contractor vs Gig/Platform Worker: Comparison Table

Keep this table handy. Almost every downstream decision — contracts, tax deduction, benefits, systems access — flows from getting this classification right.

Why the Distinction Matters: The Misclassification Risk

It is tempting to treat classification as paperwork. It is not. Misclassification — calling someone a contractor or gig worker when the reality of the relationship is employment — is one of the most significant hidden risks in Indian workforce management, and it is becoming more visible as regulators, workers, and courts pay closer attention to the gig economy worldwide.

What misclassification looks like

Misclassification rarely starts as a deliberate scheme. It usually creeps in through convenience:

• A "consultant" who has worked full-time, exclusively for your company, for three years, sits in your office, reports to a manager, attends daily stand-ups, and uses a company email ID.
• A "freelancer" who must seek approval for leave, works fixed hours, and is subject to your performance appraisal cycle.
• An intern-turned-"retainer" who does the same work as payroll employees sitting next to them, at a similar monthly amount, but without PF, ESI, or paid leave.
• A gig arrangement that includes a strict non-compete preventing the worker from serving any other client — which contradicts the very independence that justifies the classification.

In each case, the paper says "independent contractor," but the substance says "employee." Indian jurisprudence on employment status has long emphasised substance over form: what matters is the reality of control, supervision, integration into the organisation, economic dependence, and who bears business risk — not the label on the agreement.

What is at stake

If a worker you classified as a contractor is later found to be an employee in substance, the potential consequences can include:

• Retrospective statutory dues. Provident fund and insurance contributions that should have been made, potentially with interest and damages, for the entire period of the relationship.
• Employment law entitlements. Claims for gratuity, leave encashment, bonus, and notice pay or retrenchment compensation on termination.
• Wage-related claims. Minimum wage and overtime claims if the effective rate falls short once hours are counted.
• Tax complications. You deducted TDS as if paying a contractor when salary TDS provisions arguably applied, creating exposure on the tax side as well.
• Disputes and reputational damage. Misclassification disputes are slow, public, and corrosive to employer brand — particularly painful for companies that market themselves as good places to work.

The financial exposure compounds silently. One misclassified worker for one year is a manageable problem. Twenty misclassified workers across five years is a balance-sheet event.

A practical self-test

Ask these questions about any non-employee in your extended workforce. The more "yes" answers, the closer the relationship is to employment:

1. Does the person work only (or almost only) for your organisation?
2. Do you control their working hours, location, and methods?
3. Are they integrated into teams, reporting lines, and appraisal cycles like employees?
4. Do you provide the tools, equipment, and workspace?
5. Is their pay a fixed monthly amount regardless of output or milestones?
6. Has the arrangement continued indefinitely, rather than for a defined project?
7. Would an outsider observing their day be unable to tell them apart from an employee?

If you are answering yes to four or more, do not wait for a dispute. Either restructure the engagement to reflect genuine independence, or convert the person to employment (permanent or fixed-term) and absorb the cost consciously. The conversion cost is almost always smaller than the litigation cost.

The Code on Social Security: What It Means for Gig Workers in India

The Code on Social Security, 2020 consolidated a number of India's social security laws into a single framework. Its most talked-about innovation is the formal recognition of gig workers and platform workers as categories deserving of social protection — a significant conceptual shift, because Indian social security law had historically been built around the employer-employee relationship.

A word of caution up front: while the Code has been enacted, its implementation has been rolled out in stages, with rules framed at both central and state levels, and the operational details of gig-worker provisions continue to evolve through notifications and schemes. What follows is the general architecture. Before acting, verify the current status of notifications applicable to your state and sector on official government sources, and take professional advice.

Recognition without employment

The Code's approach is pragmatic. It does not convert gig or platform workers into employees. Instead, it creates a parallel welfare track:

• Gig and platform workers are defined as distinct categories, separate from employees and from unorganised workers in the traditional sense, though there is overlap in how schemes may reach them.
• The government is empowered to frame welfare schemes for gig and platform workers covering areas such as life and disability cover, accident insurance, health and maternity benefits, old-age protection, and other benefits the government may determine.
• Aggregators are brought into the funding picture. The Code contemplates that welfare schemes for platform workers may be funded partly through contributions from aggregators — the digital platforms that intermediate the work.

The aggregator contribution concept

For aggregators — platforms in ride-sharing, food and grocery delivery, logistics, e-commerce fulfilment, content and media services, professional services marketplaces, and similar categories — the Code introduces the concept of a mandatory contribution towards a social security fund for gig and platform workers.

The broad design, as contemplated in the Code, is that an aggregator's contribution would be a percentage of its annual turnover (with the Code indicating a band of roughly one to two per cent of turnover, subject to a cap linked to the amounts the aggregator pays its gig and platform workers). The precise rates, computation mechanics, payment processes, and effective dates depend on rules and notifications, which is why any aggregator should track official notifications closely rather than relying on secondary summaries — including this one.

What should aggregators be doing now, regardless of the final mechanics?

• Build clean payout data. Contribution formulas reference payments made to gig and platform workers. If your payout data is scattered across systems, reconstructing it later will be painful. Centralise and archive per-worker payout records now.
• Maintain a verified worker registry. Know exactly how many gig and platform workers you engage, with identity details, so that scheme enrolment and reporting are straightforward when required.
• Model the cost. A turnover-linked contribution is a real line item. Finance teams should model scenarios so pricing and unit economics are not blindsided.
• Assign ownership. Someone in your compliance or HR function should own "gig worker welfare compliance" as a standing responsibility, tracking central and state developments.

Registration and the national database concept

The Code and related government initiatives contemplate registration of unorganised workers, gig workers, and platform workers on a national database — the e-Shram portal being the flagship example of this approach for unorganised workers. The idea is a self-registration model where workers enrol with their identity details and receive a registration that enables access to welfare schemes.

For employers and aggregators, the practical implications are:

• Encourage and enable registration. Platforms can integrate registration prompts into partner onboarding. Even conventional businesses that engage many freelancers can share guidance on self-registration as a goodwill and welfare measure.
• Expect data-sharing obligations. Aggregators may be required to share worker and payout information with authorities to operationalise schemes. Design your data architecture with this in mind, including consent language in your partner terms.
• Do not conflate registration with employment. A gig worker registering on a government welfare database does not become your employee, and welfare scheme access does not create employment entitlements. Keep the categories clean in your documentation.

The state-level gig worker welfare board trend

While the central framework matures, several Indian states have moved ahead with their own legislation and schemes for gig and platform workers. Rajasthan was an early mover with a dedicated platform-based gig workers law, and Karnataka has pursued its own legislation; other states have announced boards, schemes, or draft bills. The common ingredients of this state-level trend include:

• A welfare board for platform-based gig workers, with government, aggregator, and worker representation.
• A welfare fund, typically financed through a fee or cess on aggregators — often structured as a small percentage of each transaction or payout routed through the platform.
• Worker registration, with unique IDs for gig workers operating in the state.
• Transparency obligations on aggregators, such as disclosure around automated work allocation and payment calculations, and sometimes grievance mechanisms or protections against arbitrary deactivation.

For a business operating across states, this creates a compliance matrix problem: the same delivery partner ecosystem may face different registration, cess, and reporting obligations in different states. Three practical responses:

1. Track state applicability. Maintain a simple register of which states you operate in, which have enacted or notified gig worker legislation, and what each requires. Review it quarterly — this space moves fast.
2. Build cess handling into finance systems. Transaction-linked welfare fees need to be computed at source in your payment systems, not manually after the fact.
3. Standardise upwards. If you operate in multiple states, it is often cheaper to build your processes to the strictest applicable standard than to maintain state-specific variants of everything.

The direction of travel is unmistakable: more registration, more aggregator funding responsibility, more transparency. Businesses that treat this as an operational design question now will spend far less than those that bolt on compliance after enforcement begins.

Engaging Gig Workers Correctly: Contracts, Scope, and Tax

Getting the engagement right at the start prevents most downstream problems. Here is what a well-run gig engagement looks like.

The independent contractor agreement

Every gig engagement deserves a written agreement, even for small projects. A strong agreement covers:

• Nature of relationship. State clearly that the engagement is a contract for services, that the worker is an independent contractor, and that nothing in the agreement creates employment. Remember, though: this clause is necessary but not sufficient. Courts look at substance, so the working reality must match the words.
• Scope of work and deliverables. Define outcomes, not hours. "Deliver a redesigned onboarding flow with clickable prototype by 30 September" is contractor language. "Work 9:30 to 6:30, Monday to Friday, reporting to the design manager" is employee language.
• Term and termination. A defined term or project duration, with notice provisions for early termination by either side, and clarity on payment for work completed up to termination.
• Fees and payment terms. Fixed fee, milestone-based, or rate-based (per hour/day/deliverable), with invoicing requirements, payment timelines, and what happens on late payment. Ambiguity here causes more freelancer disputes than anything else.
• Intellectual property. By default, be explicit: specify that IP in the deliverables is assigned to the company upon creation or upon payment, whichever your counsel recommends. Cover pre-existing IP the contractor brings (they license it, they do not assign it) and moral rights waivers where relevant. For creative and software work, this clause is the single most valuable paragraph in the contract.
• Confidentiality and data protection. A confidentiality clause covering business information, customer data, and materials shared during the engagement, surviving termination. If the contractor will handle personal data, add data-protection obligations aligned with India's data protection framework and your internal policies.
• Non-solicitation, not non-compete. Broad non-competes against independent contractors are both legally fragile and logically inconsistent with independence. A narrowly drawn non-solicitation clause (not poaching your employees or actively soliciting your clients using your confidential information) is the defensible middle ground. Take legal advice on enforceability.
• Warranties and liability. The contractor warrants the work is original and does not infringe third-party rights; liability caps are negotiated in proportion to fees.
• Compliance and taxes. The contractor is responsible for their own income tax filings and, where applicable, GST registration and invoicing. Your company is responsible for deducting tax at source as required by law.

TDS on contractor payments: the general picture

When an Indian business pays a contractor or professional, it is generally required to deduct tax at source before payment, once payments cross the thresholds prescribed under income tax law. In broad terms:

• Payments to contractors for work fall under the contractor-payment TDS provisions, at modest rates that differ for individuals and companies.
• Payments of professional or technical fees fall under the professional-fees TDS provisions, typically at a higher rate than contractor payments.
• Thresholds, rates, and categorisations change over time through Finance Acts, so verify the current rates with your tax advisor or the Income Tax Department's official resources before configuring your systems.

Practical hygiene for TDS on your gig workforce:

1. Collect PAN at onboarding. TDS at penal rates applies where PAN is not furnished; make PAN collection a hard gate before first payment.
2. Classify the payment type correctly. Is this a works contract, a professional fee, a commission? The classification drives the section and rate. Get your finance team to rule on ambiguous cases once, then apply consistently.
3. Deposit and file on time. Deducted tax must be deposited with the government within prescribed timelines, and quarterly TDS returns filed, with TDS certificates (Form 16A) issued to the contractor. Missed deposits attract interest and penalties.
4. Reconcile annually. Contractors will match your deductions against their Form 26AS/AIS. Discrepancies damage relationships and create rework.

Gig Worker Onboarding and Offboarding: A Step-by-Step Playbook

Gig worker onboarding is not employee onboarding minus the paperwork. It is a distinct process with its own logic: faster, lighter, but with sharper edges on documentation and access control.

Onboarding a gig worker: step by step

1. Confirm the classification. Before anything else, run the self-test from earlier in this guide. If the role you are filling looks like a job, hire an employee (permanent or fixed-term). Only proceed with a gig engagement if the substance genuinely supports it.
2. Collect KYC and tax documents. PAN (mandatory for TDS), bank account details, GST registration certificate if the worker is GST-registered, and address proof if your vendor process requires it. Store these in a structured system, not an email thread.
3. Execute the contract before work begins. No exceptions. Retrofitting a contract after deliverables have been exchanged weakens IP assignment and confidentiality protection. Digital signature workflows make this a same-day step.
4. Create a vendor/contractor record, not an employee record. In your HRMS and accounting systems, contractors should live in a clearly separate category. This single design decision prevents dozens of downstream errors — accidental PF enrolment, wrong TDS treatment, inclusion in headcount reports sent to authorities.
5. Provision minimal, time-bound access. Give access only to the tools, repositories, and data the project requires. Use contractor-specific email conventions (or no company email at all where feasible), set access expiry dates matching the contract term, and log what was granted.
6. Brief on ways of working. Share the project brief, points of contact, communication channels, invoicing instructions, and confidentiality expectations. A one-page contractor welcome note saves twenty clarification calls.
7. Set the review cadence. Agree how progress will be checked — milestone demos, weekly written updates — in ways that review outcomes rather than supervise methods. The distinction matters for classification hygiene.

Offboarding a gig worker: step by step

Offboarding is where most organisations are sloppy, and where most risk accumulates quietly.

1. Confirm deliverable acceptance. Formally accept final deliverables in writing. This triggers final payment terms and, in many contract structures, completes IP assignment.
2. Process the final invoice. Clear outstanding payments per contract terms. Slow final payments to departing contractors are a reputational tax you do not need to pay.
3. Revoke all access — the same day. Email, Slack, code repositories, cloud drives, CRM, VPN, building access. Access that lingers after engagement ends is a security incident waiting to happen. Automate this if your systems allow.
4. Recover assets and data. Company devices if any were issued, and written confirmation that company data has been deleted from personal devices per the contract's confidentiality clause.
5. Issue closure documentation. A completion note or engagement letter closing the contract, plus the TDS certificate cycle continuing per statutory timelines even after the engagement ends.
6. Capture the relationship. Record performance notes and rehire eligibility. Good gig workers are a talent pool; treating offboarding as relationship management pays off the next time you need the skill quickly.

Paying Gig Workers: Invoicing, Not Payroll

One of the clearest operational lines between employees and gig workers is how money moves.

Invoices in, payouts out

Employees are paid salaries through payroll, with payslips, statutory deductions, and salary TDS. Gig workers and contractors are paid against invoices (or, for platform workers, through per-task payout systems), through accounts payable. Blurring this line — for example, running a "consultant" through the payroll system for convenience — creates precisely the substance-over-form evidence that misclassification claims feed on.

A clean contractor payment process looks like this:

• The contractor raises an invoice referencing the contract or purchase order, with their PAN and GST details where applicable.
• Finance verifies the invoice against the contract and milestone acceptance.
• TDS is deducted at the applicable rate and the net amount is paid within agreed timelines.
• The transaction is recorded as a professional/contractor expense, not as salary cost.

GST at a high level

Goods and Services Tax adds a second dimension to gig payments, and it works completely differently from anything in payroll:

• Services by an employee to an employer in the course of employment are not a GST supply. Salaries carry no GST. This is one more reason the classification line matters.
• Services by an independent contractor are a supply of services. If the contractor's aggregate turnover exceeds the registration threshold, they must register for GST and charge it on their invoices. Your business can generally claim input tax credit on that GST, subject to the usual conditions.
• Many individual freelancers are below the threshold and legitimately invoice without GST. Your accounts payable process should be able to handle both registered and unregistered contractors correctly.
• Reverse charge and special cases exist in specific service categories, and the treatment of cross-border freelance services (imports and exports of services) has its own rules. These are firmly in "ask your tax advisor" territory — the point for HR and operations leaders is simply to know that GST questions attach to contractor payments and to route them to finance early.

Payment discipline as a competitive advantage

The Indian freelance market runs on reputation in both directions. Companies known for slow, disputed, or arbitrarily reduced payments find that the best independent talent quietly stops responding. Concrete practices that cost little and return much:

• Publish your standard payment terms (for example, within a defined number of days of invoice acceptance) and honour them.
• Never make contractors chase TDS certificates.
• Pay kill fees when you cancel scoped work, as the contract provides.
• Use structured systems so payments do not depend on one manager remembering to forward an invoice.

Managing a Blended Workforce: The Operating System

Once gig workers, contractors, consultants, and employees all contribute to the same business outcomes, workforce management stops being a payroll problem and becomes an operating-system problem. Here is how to run it deliberately.

Headcount planning for a blended workforce

Traditional headcount planning counts employees. Blended workforce planning counts capacity. Practical shifts to make:

• Plan by work, not by roles. Break annual plans into streams of work, then decide the sourcing mix for each: core, ongoing, and strategically sensitive work goes to employees; spiky, specialised, or experimental work is a candidate for gig engagement.
• Track total workforce cost, not just salary cost. Contractor fees often sit in different budget lines than salaries, which lets blended costs grow invisibly. Report employees, contractors, and gig spend in one consolidated workforce view.
• Set conversion triggers. Decide in advance the conditions under which a recurring gig engagement should convert to employment — for example, when the same individual has been engaged near-continuously beyond a defined period, or when the work has become core and permanent. This turns classification hygiene into a routine planning decision instead of a legal emergency.
• Watch dependency risk. If a single freelancer holds critical knowledge with no documentation, you have a key-person risk without the retention tools employment provides. Insist on documentation as a deliverable.

Access control and information security

Every non-employee with system access expands your attack surface and your data-protection obligations. Principles that scale:

• Default to least privilege; grant per-project, time-bound access.
• Tag contractor accounts distinctly in every system so audits can filter them instantly.
• Align access expiry to contract end dates automatically.
• Include data handling and deletion obligations in every contract, and verify them at offboarding.

Culture and inclusion without blurring lines

A blended team still has to feel like a team. The art is including gig workers in the work while not absorbing them into the employment relationship:

• Include them in project communications, kick-offs, demos, and the credit for shipped work.
• Be cautious about extending employee-only rituals — appraisal cycles, mandatory all-hands, leave approval workflows — to contractors. These are exactly the integration signals that misclassification analysis looks for.
• Train managers. Most misclassification risk is created by well-meaning line managers who start treating a long-running contractor like a team member with a different badge. A one-hour briefing for managers on "how to work with contractors" is one of the highest-ROI compliance investments available.

Performance management for gig workers

You cannot appraise a contractor, but you can and should manage quality:

• Evaluate deliverables against the contract's acceptance criteria, not the person against competencies.
• Give feedback per milestone; course-correct through scope conversations, not performance improvement plans.
• Keep a structured vendor scorecard (quality, timeliness, communication, rework rates) to inform future engagement decisions.

Blended workforce compliance checklist

The Risks of Treating Contractors Like Employees (and Vice Versa)

It is worth naming the two failure modes explicitly, because they are mirror images.

Failure mode one: contractors treated like employees

This is the classic misclassification pattern described earlier — control, integration, exclusivity, and indefinite duration wrapped in a consultant agreement. The exposure is retrospective statutory contributions, employment entitlements, tax complications, and disputes. The remedy is honest classification at the design stage and conversion triggers in workforce planning.

Failure mode two: employees treated like contractors in spirit

The reverse also happens: organisations engage genuine gig workers but then manage them so loosely that the business suffers — no contracts, no IP assignment, payments from personal UPI accounts, no TDS, no record of who has access to what. Nothing here creates employment liability, but it creates tax non-compliance, IP that legally belongs to the freelancer rather than the company (a genuine deal-killer in fundraising and acquisition due diligence), and security gaps. The remedy is process: the onboarding, contracting, and payment discipline described in this guide.

A healthy blended workforce avoids both: crisp classification, and professional-grade process on both sides of the line.

How HR Software Helps You Manage a Mixed Workforce

Spreadsheets can track ten contractors. They cannot track sixty gig workers across four states, three business units, and two financial years — at least not without someone burning weekends on reconciliation. This is where a modern HRMS built for Indian compliance earns its keep in blended workforce management.

• One system, separate categories. A good HRMS lets you maintain employees, fixed-term staff, contract labour, and gig workers/consultants in one platform with clearly separated record types — so reporting sees everyone, but payroll, PF/ESI, and leave logic apply only to those they should.
• Document vault with expiry tracking. Contracts, PAN, GST certificates, NDAs, and IP assignments stored against each worker record, with alerts when a contract term is about to lapse — the moment when classification drift usually begins.
• Contractor payment workflows. Invoice capture, milestone acceptance, TDS computation support, and payment status visibility, distinct from the payroll run.
• Access and asset registers. Who has which system access and which assets, with offboarding checklists that force same-day revocation.
• Compliance calendars. TDS deposit dates, return filings, statutory registers, and — as gig worker welfare rules are notified — state-wise obligations, tracked in one place instead of one person's memory.
• Unified workforce analytics. Total workforce cost, contractor dependency ratios, engagement durations flagging conversion candidates, and audit-ready reports for due diligence.

The strategic point is simple: regulation is moving toward more visibility into non-employee work arrangements. Companies whose data is already structured will find each new notification a configuration change. Companies running on scattered spreadsheets will find each one a fire drill.

Frequently Asked Questions

1. Are gig workers in India entitled to PF and ESI?

Not in the traditional sense. Provident fund and state insurance are built around the employer-employee relationship, and genuine gig workers fall outside it. The Code on Social Security instead contemplates dedicated welfare schemes for gig and platform workers — covering areas like accident insurance, health benefits, and old-age protection — funded partly by aggregator contributions. The operational details are being rolled out through central and state notifications, so check current government sources for what is in force for your sector and state.

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

A gig worker is anyone earning from work arrangements outside traditional employment — the broad category. A platform worker is a gig worker who gets work through an online platform or app (an aggregator), such as ride-hailing or delivery apps. All platform workers are gig workers in this framing, but not all gig workers are platform workers: a freelance designer with direct clients is a gig worker but not a platform worker.

3. Do I have to deduct TDS when paying a freelancer?

Generally yes, once payments cross the thresholds prescribed under income tax law. Contractor payments and professional fees are covered by different TDS provisions with different rates. Collect the freelancer's PAN before the first payment, deduct at the applicable rate, deposit on time, and issue TDS certificates. Rates and thresholds change through Finance Acts, so confirm current figures with your tax advisor.

4. Can a long-term consultant claim to be an employee?

If the substance of the relationship resembles employment — exclusive work, employer control over hours and methods, integration into teams and appraisals, indefinite duration — a consultant may have grounds to claim employment status regardless of what the contract says. Indian courts look at the reality of the relationship, not the label. Long-running consultancies should be reviewed periodically and either restructured for genuine independence or converted to employment.

5. What are aggregators required to contribute under the Code on Social Security?

The Code contemplates that aggregators — platforms intermediating work — will contribute to a social security fund for gig and platform workers, with contributions linked to a percentage of annual turnover, subject to a cap referencing amounts paid to workers. The exact rates, mechanics, and effective dates depend on rules and notifications that are still being operationalised, and some states have separate transaction-linked welfare fees. Aggregators should track official notifications closely and model the cost now.

6. Should gig workers register on e-Shram or state gig worker portals?

Registration on government worker databases is designed to give gig and unorganised workers access to welfare schemes and, in states with gig worker legislation, to state welfare board benefits. Registration is the worker's own act and does not make them anyone's employee. Employers and platforms can support workers by sharing accurate guidance on how to register — it costs nothing and builds goodwill.

7. Is GST payable on payments to gig workers?

It depends on the worker. Salaries to employees carry no GST, but services from independent contractors are a taxable supply — a GST-registered freelancer will charge GST on invoices, which your business can generally claim as input tax credit subject to conditions. Freelancers below the registration threshold legitimately invoice without GST. Specific categories and cross-border services have special rules, so route non-standard cases to your tax advisor.

8. How do I decide whether to hire an employee or engage a gig worker for a role?

Look at the nature of the work, not the cost line. Choose employment when the work is core, continuous, and requires control over how it is done, or involves sensitive strategy and data best protected by an employment relationship. Choose a gig engagement when the work is project-shaped, specialised, or variable in volume, and can be defined by deliverables. If you need a full-time person for a defined period, use fixed-term employment rather than dressing the role up as a consultancy.

Conclusion: Build the Blended Workforce Deliberately

Gig workers in India are no longer an informal fringe — they are a structural part of how work gets done, and the law is catching up. The Code on Social Security's recognition of gig and platform workers, the aggregator contribution concept, and the wave of state welfare boards all point the same way: businesses that engage non-employee talent will be expected to know exactly who they engage, what they pay them, and how those workers are protected.

The good news is that the playbook is not complicated. Classify honestly. Contract properly, with IP and confidentiality nailed down. Pay through invoices with clean TDS and GST handling. Onboard with minimal access and offboard with same-day revocation. Plan headcount as capacity, set conversion triggers, and keep your records in a system that can answer an auditor's question in minutes rather than weeks.

That last part is where tooling matters. CozyHR is built for Indian SMBs managing exactly this kind of blended workforce — employees, fixed-term staff, and contractors in one platform, with payroll, compliance calendars, document management, and workforce analytics designed around Indian statutory requirements. If your gig workforce is currently living in spreadsheets and email threads, it may be time to give it a proper home. Explore CozyHR and see how much simpler a mixed workforce becomes when the system does the remembering for you.

Disclaimer: This article is for general informational purposes only and does not constitute legal, tax, or professional advice. Labour code implementation, TDS rates, GST rules, and state gig worker legislation evolve through official notifications — always verify current requirements on government sources and consult qualified professionals for your specific situation.