Gig Worker Policy: What Indian Companies Using Freelancers and Platform Workers Must Know in 2026

India’s gig economy does not look like it did five years ago. Back then, the legal question was mostly theoretical: are these workers employees or not? Today, the question has a regulatory framework attached to it, and companies that have not updated their internal policies to reflect that reality are carrying quiet but meaningful risk.

This post is for HR and legal teams at companies that engage freelancers, independent contractors, or platform-based workers in any significant way. It covers what the law now requires, what your policies need to say, and where the gaps tend to appear. For the broader picture of what the new Codes change, see our overview: How India’s new Labour Codes are forcing companies to rewrite their HR policies.

The Legal Shift That Changed Everything

The Code on Social Security, 2020 is the piece of central legislation that brought gig and platform workers into India’s formal policy vocabulary for the first time. Before this Code, there was no statutory definition of a gig worker. Contracts were whatever companies wrote them to be, and social protection for this segment was essentially nonexistent.

Under the Code, a gig worker is defined as a person who performs work or participates in a work arrangement and earns from such activities outside of a traditional employer-employee relationship. A platform worker is a subset of this: someone who accesses organisations or individuals using an online platform to provide specific services.

This definitional separation matters because platform workers have clearer entitlements under the Code, and state governments are empowered to build social security schemes specifically for them. Several states including Rajasthan have already moved ahead with state-level gig worker welfare legislation. Others are drafting. The regulatory floor is rising.

What the Code on Social Security Actually Requires

The Code mandates that the central and state governments establish social security funds for gig and platform workers. Aggregators (the companies and platforms engaging these workers) are required to contribute a percentage of their annual turnover to these funds, subject to a ceiling. The exact percentages are yet to be universally notified, but the framework is operational in principle.

Beyond the fund contribution, the Code requires aggregators to register gig and platform workers. This is not optional once the relevant state rules are notified. If your company operates a platform or regularly engages gig workers through one, the registration obligation falls on you.

The Code also gives gig workers the right to receive a summary of the terms and conditions of their engagement, the right to grievance redressal, and the right to seek information about how their earnings are calculated. None of these are extraordinary rights. But they require your policy framework to exist, be documented, and be accessible to the workers it covers.

Five Policies Every Company Engaging Gig Workers Needs

A Gig Worker Engagement Policy

This is the foundational document. It should define, in plain language, what categories of work your company engages gig workers for, how that engagement is structured (platform-mediated, direct contract, or both), and what the company’s obligations are under the Code on Social Security.

The policy should state clearly that gig workers are not employees of the company, explain what that means in practical terms (no PF, no Employee State Insurance, no gratuity in the traditional sense), and simultaneously acknowledge the company’s obligations under the evolving social security framework.

Where many companies go wrong: they write a policy that is really just a contract template dressed up as a policy. A policy governs how your organisation operates. A contract governs a specific engagement. You need both, and they need to be consistent with each other.

Terms of Engagement Document

Every gig worker your company engages should receive a written terms of engagement document before they start work. This is not just good practice. Under the Code, gig workers have the right to a summary of the terms under which they work.

The document should cover the nature of the work, the basis of payment (per task, per hour, per project), the payment timeline, how disputes about payment are raised and resolved, the conditions under which the engagement can be ended by either party, and any intellectual property assignment relevant to the work.

This document is also your primary evidence if a misclassification dispute ever arises. A well-drafted terms of engagement that genuinely reflects an independent contractor relationship is far stronger than a one-line clause buried in an onboarding form.

Grievance Redressal Procedure

The Code gives gig workers the right to grievance redressal. Your policy needs to specify how this works in practice: who they contact, through what channel, within what timeframe they can expect a response, and what escalation looks like if the first level does not resolve it.

For companies with enterprise-wide policy infrastructure, this procedure should be consistent across engagements in different states, while accommodating any state-specific requirements. A gig worker in Karnataka and a gig worker in Maharashtra should not be receiving materially different grievance processes from the same company.

Payment and Deduction Policy

Algorithmic payment systems are one of the most legally sensitive aspects of platform-based gig work. If your platform deducts amounts from worker earnings for cancellations, quality flags, or penalties, the basis for those deductions needs to be disclosed and documented.

The Code specifically includes transparency in earnings calculation as a right. This means your payment policy cannot be a black box. Workers should be able to understand, in practical terms, how their pay is computed and what can reduce it. Documenting this in a formal policy also protects the company: undocumented deductions that workers cannot explain are the most common trigger for disputes and regulatory complaints.

Data and Surveillance Policy

This one is underappreciated. Many companies that engage platform workers collect significant amounts of data from them: location data, productivity metrics, communication logs, ratings data. In the absence of a clear policy, this creates both a legal exposure and a trust problem.

Your data policy for gig workers should specify what data is collected, why, how long it is retained, who has access to it, and how it is used in decisions about the engagement. Where AI or algorithmic systems make decisions about worker assignments, ratings, or deactivations, the policy should explain the general logic even if not the specific code.

This is not a compliance nicety. With India’s Digital Personal Data Protection Act now in force, any company collecting personal data from workers (gig or otherwise) needs a documented lawful basis for doing so and must be able to demonstrate it.

The Misclassification Question

No discussion of gig worker policy is complete without addressing misclassification, because it is the risk that keeps labour lawyers busy.

Misclassification happens when a company treats a worker as an independent contractor when, in substance, the relationship looks a lot more like employment. Courts and labour authorities in India look at several factors: whether the company controls how the work is done (not just the output), whether the worker works exclusively for one company, whether the worker uses their own tools and equipment, and whether the engagement is continuous or project-based.

There is no single test, and the line is genuinely blurry in some cases. But the companies that face misclassification challenges almost always have one thing in common: their contracts say “independent contractor” while their operational reality says otherwise. If your gig workers work exclusively for you, follow detailed daily instructions, cannot set their own rates, and have been doing the same thing for three years, the label in the contract is not going to save you.

The policy fix here is not to make your contracts sound more like contractor agreements while nothing else changes. It is to audit the actual working relationship and make sure what your policy says matches how work actually happens. AI-assisted policy review that flags inconsistencies between policy language and operational descriptors is one practical way to catch this before a regulator does. Companion read on direct-employment side: fixed-term employee policies under the new Labour Codes.

State-Level Complexity in 2026

By 2026, the patchwork of state-level gig worker regulations has grown more complex. Rajasthan’s Platform Based Gig Workers (Registration and Welfare) Act was the first of its kind in India. Other states have introduced or are actively drafting similar legislation, each with its own registration requirements, contribution schedules, and grievance frameworks.

A national gig worker engagement policy is necessary but not sufficient. It needs state-specific addenda wherever your company operates and engages gig workers.

Jurisdiction-aware policy distribution ensures that a gig worker in Rajasthan receives the version of the policy that includes the state-specific registration and welfare board information relevant to them, not the generic national version that may leave them uninformed about their actual entitlements.

The Documentation Burden Is Operational, Not Just Legal

Here is the practical reality that HR teams often find difficult: the compliance burden for gig workers is not a one-time documentation exercise. It is ongoing.

Every new gig worker needs their terms of engagement before starting. Registration obligations need to be tracked against state notification timelines. Contribution records need to be maintained. Grievances need to be logged, tracked, and closed within defined windows. When the regulatory landscape changes, existing policies need to be updated and re-distributed.

Real-time compliance tracking tied to your gig worker database makes this manageable. When a new worker is onboarded, the documentation checklist triggers automatically. When a state notifies new rules, the affected worker policies are flagged for review. When a grievance is raised, the clock starts and the system tracks it to closure.

For gig workers who have questions about their terms, payment, or entitlements, self-service policy interaction reduces the volume of queries landing on HR and gives workers faster, more consistent answers in plain language.

A Practical Checklist for 2026

Before engaging any gig worker, you should have:

• Gig worker engagement policy approved and accessible
• Terms of engagement template reviewed against current Code requirements
• State-specific registration obligations checked and fulfilled where applicable
• Payment and deduction methodology documented and explainable
• Grievance contact and process communicated to the worker

On an ongoing basis, you should be tracking:

• State-level regulatory notifications and their impact on existing policies
• Social security fund contribution obligations as they become operational
• Worker data collection practices against Digital Personal Data Protection Act compliance requirements
• Any patterns in grievances that suggest a policy gap

When a gig engagement ends, you should have:

• Final payment reconciliation documented
• Any outstanding grievances resolved or formally escalated
• Engagement records retained for the period required under applicable law

Frequently Asked Questions