If you run a growing enterprise in India, you have likely heard about the major threshold shift introduced by the Industrial Relations (IR) Code, 2020. The headline news across corporate compliance networks was clear: the employee headcount threshold above which a company must seek prior government permission for layoffs, retrenchments, or plant closures was officially raised from 100 to 300 or more workers.
For many Tech Founders, Chief Human Resources Officers (CHROs), and IT Directors, this update brought a sense of relief. However, it also sparked a persistent compliance misconception.
A commonly asked question in corporate legal clinics highlights this confusion: “We are an IT company in Bangalore with 350 employees. Since we are over the 300-worker threshold, do we need to secure formal permission from the Karnataka state government just to fire a single underperforming software engineer?”
The short answer is absolutely not. But the legal reasoning behind that answer reveals a sharp structural division in Indian labour jurisprudence between a factory floor and a commercial office. If your HR operations team cannot distinguish between these frameworks, your company is exposed to unexpected regulatory risks. Let’s break down the rules, map the statutory boundaries, and review the exact operational steps required for a compliant performance-based exit.
The Executive Context: Dismantling the “Industrial Establishment” Misconception
The primary error made by corporate leadership teams lies in a fundamental misinterpretation of where the 300+ worker rule applies. Chapter X of the modern IR Code, 2020 (which replaces Chapter V‑B of the legacy Industrial Disputes Act, 1947) states that prior government permission for layoffs, retrenchment, or closure is mandatory only for an Industrial Establishment or Undertaking.
Under Section 2(r) of the IR Code, 2020, an “industrial establishment or undertaking” means an establishment or undertaking in which any “industry” is carried on. The term “industry” under Section 2(p) is defined broadly as “any systematic activity carried on by co‑operation between an employer and worker”; a definition that can encompass many service sector operations.
Therefore, there is no blanket “commercial exclusion” under the IR Code. The applicability of the 300‑worker permission requirement depends on whether an establishment falls within the broad definition of “industrial establishment or undertaking” under the IR Code, not merely on its classification under a state Shops and Establishments Act. The two statutory frameworks operate independently.
Consequently, an IT company with 350, 3,500, or even 35,000 employees based in Bangalore should not assume it is automatically exempt from prior permission requirements. The correct approach is to seek legal advice to determine whether the specific nature of its operations brings it within the ambit of the IR Code‘s provisions.
For the avoidance of doubt, individual performance‑based terminations; even in covered industrial establishments do not require prior government permission. The 300+ worker rule applies specifically to mass workforce adjustments: a layoff (temporary inability to give employment), a mass retrenchment (permanent downscaling of surplus staff), or a complete closure. Terminating a single employee due to documented, persistent underperformance is an individual separation event that does not require state government panel approval.
The True Operational Risk: The “Worker” vs. “Non‑Worker” Trap
While you may not need government permission to proceed with an individual performance-based termination, your primary compliance vulnerability involves how that termination is executed. This depends on whether the underperforming employee is classified as a “Worker” or a “Non‑Worker” under the law.
1. The Executive/Managerial Class (Non‑Worker)
If the employee is a genuine manager, director, or team lead with administrative authority (e.g., they possess the power to approve leaves, execute appraisals, or supervise other employees) or a supervisor drawing gross monthly wages exceeding ₹18,000, they fall outside the protection of the IR Code‘s retrenchment provisions.
Their exit is governed strictly by their employment contract and state-specific Shops and Commercial Establishments Acts. Under Section 39 of the Karnataka Shops and Commercial Establishments Act, 1961, you can dispense with their services for a “reasonable cause” (such as documented non‑performance following a failed Performance Improvement Plan) by providing one month‘s written notice or matching pay in lieu of notice.
2. The Technical/Clerical Class (The Hidden Worker)
This is where IT employers frequently face legal challenges. Many software enterprises assume that because an employee holds a high‑end title like “Senior Systems Engineer,” “Data Analyst,” or “Full‑Stack Developer” and earns a substantial tech salary, they are automatically an executive.
Indian courts look strictly at the nature of the work, not the designation. If the employee’s daily duties are purely technical, execution‑oriented, and coding‑heavy, with zero managerial or supervisory control over other human resources, they may be legally classified as a “Worker” under Section 2(zr) of the IR Code, 2020. The Code clarifies that individuals employed in a supervisory capacity earning less than ₹18,000 per month will be considered “workers”.
For a technical employee deemed a statutory worker, a termination for poor performance is legally viewed as an individual retrenchment. While you do not need government permission for a single such event, you must satisfy clear statutory obligations, including paying retrenchment compensation (15 days‘ last drawn wages per completed year of service or more) and contributing to the Worker Re‑Skilling Fund.
Dual‑Regime Compliance Matrix: Shops Act vs. IR Code
To help your legal and HR operations teams distinguish between shifting statutory baselines, use this comparative guide:
| Compliance Matrix | IT/Commercial Office (Example: Bangalore) | Industrial Establishment (Factory/Manufacturing) |
| Primary Governing Statute | Karnataka Shops and Commercial Establishments Act, 1961 (or applicable state Shops Act) | IR Code, 2020 (formerly ID Act, 1947) |
| Individual Performance Exit Protocol | Governed by Section 39 of the Shops Act (requires documented reasonable cause + 1 month’s notice) | For workers: governed by individual retrenchment rules under IR Code. For non‑workers: as per contract/Shops Act. |
| Worker Re‑Skilling Fund Levy | Not triggered for genuine managerial separations; applies if an operational tech worker undergoes individual retrenchment under the IR Code. | Mandatory deposit of 15 days‘ wages last drawn per worker retrenched due to structural alignment. |
| Prior Permission for Mass Retrenchment | Do not assume exemption. Applicability depends on whether the establishment falls within “industrial establishment or undertaking” under the IR Code. Seek legal advice. | Required under Chapter X of the IR Code for establishments with 300 or more workers for mass layoffs, retrenchments, or closure. |
Critical 2026 Core Impact Filters for IT Payroll & Separation
When managing a performance-linked separation this year, your payroll and HR delivery desks must account for three strict financial filters introduced by the consolidated codes:
1. The Strict 48‑Hour Wage Exit Rule
Section 17(2) of the Code on Wages, 2019 eliminates the traditional corporate practice of wrapping up full‑and‑final clearances within a standard 30‑day corporate payroll cycle. The mandate requires that all wages (Basic Pay + Dearness Allowance + Retaining Allowance) payable to an employee upon separation must be paid within two working days of the date of termination, whether due to resignation, dismissal, retrenchment, or closure.
2. The 50% Wage Rule Cost Expansion
Under the Code on Wages, 2019, an employee‘s core Basic Pay plus Dearness Allowance (DA) must constitute at least 50% of their total gross Cost to Company (CTC) structure. Because notice‑period pay, retrenchment packages, and other statutory calculations are tied to this expanded definition of “wages,” the cash outlay for a performance separation will be significantly higher than historical calculations under legacy frameworks.
3. Fixed‑Term Employment (FTE) Guardrails
If your IT firm utilizes fixed‑term contractors for specialized development cycles, remember that the modern code framework enforces absolute benefit parity. FTE personnel are entitled to pro‑rata statutory gratuity payouts after completing just 1 year of continuous service, meaning you cannot utilize an early performance‑linked contract termination to erase accrued end‑of‑service statutory dues.
The Defensible Performance Exit Sequence – FREE
To protect your enterprise against claims of wrongful dismissal or arbitrary termination under Section 39 of the applicable state Shops Act, your HR business partners must execute a clean, data‑driven separation sequence.
Phase 1: Establish Documented Performance Gaps (Metric Logging)
Collate clear, objective data points showing where the employee missed their deliverables (e.g., missed coding sprints, bug‑fix delays, or low code‑quality scores). Avoid subjective feedback such as “poor fit” or “lack of enthusiasm.”
Phase 2: Deploy a Bona Fide Support Plan (Structured PIP)
Place the employee on a formal Performance Improvement Plan (typically 30 to 60 days). Document the specific tools, training courses, and senior mentorship sessions provided by the company to help them succeed. Courts reject PIPs that provide no real organizational support.
Phase 3: Review Worker Status and Core Payroll Dues (Legal Re-Verification)
If the employee fails the PIP, analyze their daily functional role to determine if they qualify as a worker or a manager. Calculate their final settlement components using the 50% Wage Rule baseline to ensure perfect alignment with code definitions.
Phase 4: Execute Separation and the 48‑Hour Wage Payout (Compliant Offboarding)
Issue the formal separation letter citing documented non‑performance as a reasonable cause. Ensure your finance desk processes the full wage settlement transfer directly to the employee‘s bank account within the mandatory 48‑hour window to satisfy Section 17(2) of the Code on Wages, 2019.
Financial and Operational Risk Analysis
The risks of mismanaging an individual performance exit in India‘s technology hubs can quickly lead to costly operational challenges.
Additionally, if your internal HR operations fail to clear an underperforming worker‘s terminal wages within the mandatory two‑day limit, it can trigger automated exceptions in your unified digital compliance returns. This can lead to unexpected labour inspections and create unnecessary administrative hurdles for your leadership team during standard corporate compliance audits. It is important to note that the 48‑hour mandate does not statutorily apply to non‑wage benefits such as gratuity, which follow their own timelines; however, best practice remains to settle all dues promptly to avoid any adverse judicial inference of bad faith.
Conclusion
The 300‑worker myth is largely a misdirection for India‘s technology and service sectors. For individual performance exits, you do not need state government permission. Your real compliance vulnerabilities lie elsewhere: correctly distinguishing between a “worker” and a “non‑worker” under the IR Code, 2020; adhering to the 48‑hour wage settlement rule under the Code on Wages, 2019; and respecting the “reasonable cause” requirement under state Shops and Commercial Establishments Acts.
For mass layoffs or retrenchments, the situation is more complex. There is no blanket “commercial exclusion” from the IR Code‘s provisions, and many service sector companies may find themselves within the broad definition of “industrial establishment or undertaking.” The correct approach is to seek legal advice before undertaking any mass workforce reduction, rather than assuming exemption based on classification under a state Shops Act.
Smart enterprises will:
- Audit job descriptions to correctly classify “workers” vs. “non‑workers” at the time of hiring,
- Implement genuine, well‑documented PIPs with objective metrics and support,
- Maintain impeccable 50% wage rule compliance for all payroll calculations,
- Ensure the finance desk can execute a 48‑hour wage settlement for every separation,
- Seek legal counsel before any mass layoff or retrenchment to confirm applicability of the 300‑worker permission requirement.
Disclaimer – This blog is provided for general informational and educational purposes only and does not constitute legal advice. The information contained herein may not reflect the most current legal developments and is not guaranteed to be complete, accurate, or up‑to‑date. Nothing in this publication creates an attorney‑client relationship between the reader and the author or publisher. Laws, regulations, and judicial interpretations vary by jurisdiction and may change over time. Readers should not act or refrain from acting on the basis of any information contained in this publication without first seeking independent legal counsel from a qualified lawyer licensed to practice in the relevant jurisdiction. The author and publisher expressly disclaim all liability in respect of any actions taken or not taken based on any or all of the contents of this publication. Case citations and statutory references are provided for illustrative purposes only and do not constitute a guarantee of any particular outcome. Always consult a qualified legal professional for advice tailored to your specific circumstances.