.png)
How Do Gig Worker Rules Apply to Contractors in India?
- Saransh Garg
- 3 days ago
- 8 min read
India runs its gig and platform worker protections through a national statute, the Code on Social Security, 2020, and at least four states have added their own overlapping laws on top of it. If your company engages IT contractors in India through a staffing partner, gig worker rules apply to contractors in India more often than most HR teams outside the country realise, because the legal definitions are broad enough to catch a backend developer on a fixed term contract, not just a delivery rider on an app. We work with contract engineers placed across Bengaluru, Hyderabad, and Delhi NCR, and this is the exact breakdown we give clients before they sign a new contractor agreement.
What Are Gig Worker Rules and Why Do They Matter for IT Contractors in India?
A gig worker, under the Code on Social Security, is defined as someone who earns from a work arrangement outside a traditional employer employee relationship. A platform worker is someone connected to that work through a digital platform. Neither definition mentions job function, so a QA engineer paid on invoice through a contractor management portal can technically read the same way as a food delivery rider on paper, even though the actual working relationship is nothing alike.
This is precisely where gig worker rules apply to contractors in India in ways that catch foreign companies off guard. The trigger is not the type of work. It is how the payment flows, whether a digital platform sits between the company and the worker, and how much control the company exercises over hours and output. Get those three details wrong and a straightforward six month contract can end up looking, on paper, like a platform gig arrangement.
How Is a Contractor Different From a Gig Worker Under Indian Law?
This is where contract hiring and full time hiring start to diverge in practice. A full time employee in India is covered by the Industrial Relations Code and standard payroll obligations such as provident fund and gratuity once tenure thresholds are met. An independent contractor sits outside that framework entirely and is governed instead by the Indian Contract Act, 1872, through the terms of a service agreement.
A gig or platform worker is a third category the law created only recently. The difference from a contractor usually comes down to structure rather than title. A contractor engaged on a defined scope of work, billed against deliverables, and paid directly or through an employer of record, generally sits outside gig worker classification. A worker sourced through an app style platform and paid per completed task looks statutorily closer to a gig worker, even if the underlying skill is identical.
Where Does India's Best Contract Talent for This Work Actually Sit?
Bengaluru carries the deepest bench for backend, cloud, and DevOps contractors serving foreign clients on fixed term or project based agreements. Hyderabad is strong for SAP, data engineering, and QA contracting. Pune and Chennai carry solid contract talent in embedded systems and enterprise Java, and Delhi NCR, where our own recruiting base sits, is strongest for platform engineering contractors working directly with European and North American clients.
Indian contract engineers are generally comfortable with non standard engagement because most have already worked under fixed term contracts or milestone based agreements for overseas clients. What they often lack is documentation discipline. Engineers coming out of smaller freelance platforms are used to loosely worded arrangements built around per task payment, which is exactly the pattern that looks closest to platform gig work on paper.
We test for this during vetting by reviewing every candidate's prior statements of work, and we flag anyone whose engagement history was purely task based through an intermediary app, because that pattern can complicate how a new contract gets classified later.
What Does the Law Actually Say About Gig Worker Rules for Contractors in India?
The Code on Social Security defines gig worker and platform worker in its worker definitions chapter, and establishes a dedicated Social Security Fund for both categories, funded partly by an aggregator contribution of one to two percent of annual turnover, capped at five percent of what the aggregator pays its workers. Draft central rules propose that gig worker welfare eligibility triggers after ninety days of engagement with a single aggregator, or a hundred and twenty days across multiple aggregators in a financial year, thresholds that most six month or twelve month IT contracts will clear easily on duration alone.
Karnataka, home to the largest concentration of India's contract IT workforce, went further with its own Platform Based Gig Workers Act. It defines a gig worker as someone in a contractual, piece rate arrangement sourced through a platform, and requires the aggregator to register every such worker with a state Welfare Board within thirty days, backed by a welfare fee of one to five percent per transaction. The Act is currently being challenged in the Karnataka High Court by platform operators, but the court has so far declined to pause it, so the compliance obligation still stands.
The most common mistake we see is a company assuming the word "contractor" in an agreement is protection enough. It is not. What matters is the substance of the relationship: control over hours, exclusivity, how payment is routed, and whether a digital platform connects the two parties. That is the real test behind whether gig worker rules apply to contractors in India in any specific case, not the label on the contract.
Talk to our compliance team before your next contractor agreement is signed: Get your contractor structure reviewed.
Contractor vs Platform Gig Worker vs Contract Labour: Quick Comparison
Feature | Independent IT Contractor | Platform Gig Worker | Contract Labour (CLRA) |
Governing law | Indian Contract Act, 1872 | Code on Social Security, Ch. IX plus state Acts | Contract Labour (Regulation and Abolition) Act, 1970 |
How work is sourced | Direct agency placement or EOR contract | Digital platform connects worker to task | Licensed contractor supplies labour to principal employer |
Payment structure | Invoice or retainer tied to deliverables | Per task or per transaction via app | Wages tracked against the principal establishment |
Registration required | None specific to gig status | Mandatory with Welfare Board or e-Shram | Contractor must hold a labour licence |
Welfare fund contribution | Not applicable | One to two percent turnover, up to five percent per transaction in Karnataka | Not applicable directly |
Best fit for | Remote software, DevOps, and QA contractors | Delivery, ride hailing, home services workers | On site or facility staff via licensed vendor |
Any engagement paid per completed task through a shared portal, with no fixed scope of deliverables, is the profile most likely to attract scrutiny under the new rules, regardless of whether the person is writing code or delivering groceries.
How AnjuSmriti Global Structures Contractor Hiring to Stay Compliant
Our standard timeline for placing a vetted contract developer runs twelve to eighteen working days from mandate to signed offer. For contract roles specifically, we now run an added compliance pass before any contract is signed: reviewing the payment routing method, the scope of work language, and whether the engagement could be read as platform mediated.
We added that step after a real scare. A mid sized US fintech client with around 300 employees globally had forty contract QA and backend engineers in Bengaluru and Hyderabad, engaged through a third party payments platform that batched invoices on a fixed schedule. When Karnataka's Act came into force, their counsel flagged that the payment platform's structure looked uncomfortably close to the statute's definition of platform work. Registering forty contractors as gig workers would have meant a welfare fee and a Welfare Board registration nobody had budgeted for.
We worked with the client's legal team over three weeks to restructure the engagement: contractors moved to milestone based invoicing tied to deliverables instead of logged hours, the third party payments platform was replaced with a straightforward Employer of Record (EOR) arrangement for payroll, and every contract was rewritten to remove per task pricing language. The result was zero contractors requiring Welfare Board registration, an estimated eighteen to twenty two lakh rupees in avoided first year welfare fee exposure, and a restructuring completed in under a month.
What Does Contract Hiring Cost Compared to Full Time Hiring in India?
Contract IT rates in India, per month, run roughly as follows for the roles we place most often:
Mid level backend or QA contractor, three to five years experience: ninety thousand to one lakh forty thousand rupees
Senior contractor, six to nine years, cloud or DevOps or full stack: one lakh sixty thousand to two lakh fifty thousand rupees
Lead or architect level contractor, ten plus years: two lakh eighty thousand to four lakh twenty thousand rupees
On top of the base rate, clients using our remote contract hiring model typically add an EOR or payroll processing fee of eight to twelve percent of monthly billing. A full time hire, by comparison, carries provident fund, gratuity, and statutory benefit obligations that contract engagements avoid, which is exactly why founders and finance heads default to contract hiring for project based work and reserve full time offers for core, long term roles.
None of this changes because of the new gig laws. What changes is the compliance layer underneath it: a properly structured contract keeps you outside the welfare fee and Board registration requirements entirely, while a badly structured one adds an unbudgeted one to five percent fee on top of every payment cycle.
Conclusion
Contract hiring in India is shifting fast alongside broader shifts in outsourcing, cloud adoption, and AI assisted engineering. More global companies are running smaller, senior heavy contract teams instead of large offshore benches, and pairing that with AI powered code review and testing tools that let a lean contract team cover more ground than before. At the same time, state governments are moving quicker than the central government on gig worker rules, which means the compliance picture keeps shifting state by state rather than settling into one national standard.
If your contractor agreements were drafted before your team had visibility into these state laws, a review now is far cheaper than a compliance notice later.
Ready to get your contractor agreements reviewed? Talk to our team here.
Interesting Reads:
FAQs
1.Does the Code on Social Security automatically classify my Indian IT contractor as a gig worker?
No. Classification depends on the substance of the arrangement, not the job title. A contractor paid against fixed deliverables, with a written scope of work and no digital platform connecting the parties, generally sits outside gig worker classification under current rules.
2.Does Karnataka's gig worker law apply if my contractor works from Hyderabad instead of Bengaluru?
Karnataka's Act applies to aggregators and platform workers operating within Karnataka. A contractor based in Hyderabad or Pune would fall under the central Code instead, unless the payment platform itself is registered or headquartered in Karnataka.
3.Do I need to register as an aggregator if I use a contractor payments platform?
Possibly, if that platform connects you to individual workers for task based payment. A milestone based contract combined with employer of record payroll avoids aggregator obligations under both the central Code and the state Acts.
4.What welfare fee would apply if my contractors were reclassified as gig workers in Karnataka?
The Karnataka Act permits a fee of one to five percent per transaction, depending on aggregator category. For a contractor billing one lakh fifty thousand rupees monthly, that could mean an added fifteen hundred to seventy five hundred rupees per month, per contractor.
5.Can Indian contractors claim gig worker benefits even if my company never registered them?
Benefits generally flow through registration with a Welfare Board or the central fund. A contractor who believes the arrangement meets the statutory definition can still raise a grievance independently, which is why correct contract structure matters more than avoiding registration.
6.Does a ninety day contract duration threshold apply to a standard six month IT contract?
Yes, on current draft rules. Most six month or twelve month contracts clear that threshold easily, which means duration alone offers no protection. The payment and platform structure is what actually determines classification.
7.How does the Contract Labour Act interact with these gig worker rules?
CLRA governs labour supplied through a licensed contractor to work on site at a principal employer's premises, a different pattern from remote IT contracting. Direct control over a contractor's daily hours can still create CLRA adjacent risk alongside gig worker risk.
8.Should offer letters state explicitly that a contractor is not a gig worker?
A disclaimer alone will not hold up if the underlying arrangement resembles platform work, since Indian adjudication looks at substance over wording. Structuring the payment and scope terms correctly first is what actually protects the engagement.
Comments