Can a Company Introduce Automation Without Giving Workers Advance Notice in India?
What Section 40 Actually Says (and What It Doesn't)
Section 40 contains two separate prohibitions. First, no employer may effect a change in any Third Schedule service condition without giving affected workers notice "in such manner as may be prescribed" of the nature of the proposed change. Second, no employer may effect that change within 21 days of giving the notice. The notice goes out on day zero; the earliest the change can take effect is day 21.
Critically, Section 40 does not say “automation requires notice.” It says “changes to these eleven matters require notice.” The distinction matters enormously for HR and operations teams planning technology rollouts.
The Third Schedule lists eleven conditions of service:
- Wages, including period and mode of payment
- Employer contributions to provident fund, pension, or similar funds
- Compensatory and other allowances
- Hours of work and rest intervals
- Leave with wages and holidays
- Starting, altering, or discontinuing shift working (otherwise than per standing orders)
- Classification by grades
- Withdrawal of any customary concession or privilege, or change in usage
- Introduction or alteration of discipline rules
- Rationalisation, standardisation, or improvement of plant or technique likely to lead to retrenchment
- Increase or reduction in the number of persons employed in any occupation, process, department, or shift
Item 10 is the automation-specific provision. If introducing technology is “rationalisation, standardisation or improvement of plant or technique” and it is “likely to lead to retrenchment of workers,” the notice obligation is engaged. But the word “likely” does the heavy lifting. A company that installs collaborative robots to assist existing workers, with no headcount reduction planned, may argue item 10 does not apply. A company that deploys automated sorting equipment and eliminates twelve manual sorting positions almost certainly cannot.
Item 6 captures another common automation side-effect: changing shift patterns. If automation reduces the number of shifts needed, or changes their start and end times, that is a Third Schedule matter independent of item 10. Item 4 (hours of work) and item 11 (headcount changes) may also apply simultaneously.
The Four Exceptions — and Why "Emergency" Is Narrower Than It Sounds
The proviso to Section 40 carves out four situations where no notice is required:
| Exception | What it covers |
|---|---|
| Settlement or award | Change made in pursuance of a settlement or award |
| Government service rules | Workers governed by specified public-service rules |
| Emergent shift change | Shift change required by an emergency, made in consultation with the Grievance Redressal Committee |
| Government order | Change effected in accordance with an appropriate Government order |
The third exception is the one employers most often try to invoke for urgent automation deployments. It has three elements: an emergent situation, a shift change, and consultation with the Grievance Redressal Committee. All three must be present. “We needed the system live by quarter-end” is not an emergent situation in the statutory sense. And if the Grievance Redressal Committee was not consulted — or does not exist — the exception fails regardless of how urgent the business case was.
The fourth exception is broader than it first appears: it covers changes made “in accordance with the orders of the appropriate Government,” which can include government directions during disruptions. But it does not cover a private employer’s internal automation timeline.
The Practical Trap: Whose Rules Apply to You
Section 40 is statute and binds every employer covered by the Code, which commenced on 21 November 2025. But the “prescribed manner” of giving notice depends on whether the Central Government or a State Government is the appropriate Government for your establishment.
For central-sphere establishments — railways, mines, oil fields, major ports, air transport, telecommunications, banking, insurance, central public sector undertakings, and their contractors — the Industrial Relations (Central) Rules prescribe Form IV as the notice format.
For most other establishments, the State Government is the appropriate Government, and the prescribed manner is whatever that state’s Industrial Relations rules say. As of late 2026, most states had not notified final rules under all four labour codes. Gujarat was the only state with final rules across all four; Karnataka had notified wages and industrial relations rules, while most others remained in draft.
The practical consequence: even where your state has not prescribed a form, you still owe the notice and the 21-day wait. Using Form IV is the safest approach — it is the Central Government’s own template, and no employer has been penalised for giving more detail than required.
What Counts as "Retrenchment" for Item 10
The Third Schedule does not define “retrenchment” for item 10 purposes. The Industrial Relations Code’s definition provisions, and the case law that will develop around them, will matter here. But the ordinary meaning is instructive: retrenchment means termination of employment for reasons other than disciplinary action, retirement, or voluntary resignation. Automation that eliminates positions is the clearest case.
The harder question is automation that changes the content of jobs without eliminating headcount. A warehouse that introduces automated guided vehicles may keep the same number of workers but reassign them from picking to monitoring roles. Does that constitute “rationalisation likely to lead to retrenchment”? If the reassignment involves a change in classification by grades (item 7) or a change in customary privileges (item 8), a separate Third Schedule trigger may apply even if item 10 does not.
The safest compliance posture is to screen every automation proposal against all eleven items before drafting the notice, not just item 10. An automation project that changes reporting structures, performance metrics, or shift rotations may trigger obligations through items that have nothing to do with the technology itself.
What Happens If You Skip the Notice
Section 40 is not a criminal provision in the way some labour law obligations are. The penalty chapter of the Code does not make a breach of Section 40 an offence. But that does not mean the risk is low.
A change made without the required notice is a change made in breach of statute. That gives affected workers a strong opening in conciliation and before a tribunal. The change may be challenged as invalid. And once an industrial dispute is pending, Section 90(1) freezes the position: the employer cannot alter conditions of service connected with the dispute to the prejudice of the workers concerned without express permission of the authority before which the proceeding is pending.
There is also the litigation cost of defending a procedural challenge that could have been avoided with a three-week wait and a written notice. For a mid-sized establishment, the legal fees alone will exceed whatever operational urgency justified the shortcut.
The Compliance Checklist for Automation Rollouts
Before announcing any automation-driven change, HR and operations teams should document the following:
- 1. Map the change against the Third Schedule. Which of the eleven items does this automation affect? Be specific. “It changes how work is done” is not a Third Schedule item. “It eliminates the night shift” is item 6. “It reduces the packaging department from 20 to 14 workers” is item 11.
- 2. Identify affected workers. Section 40 requires notice to “the workers likely to be affected by such change”. That may include workers whose roles are not directly automated but whose shifts, reporting lines, or work allocation change as a consequence.
- 3. Draft the notice. State the nature of the proposed change. If your establishment falls under central rules, use Form IV. If state rules are not yet notified, use Form IV anyway.
- 4. Serve the notice and document the date. The 21 days run from the giving of the notice. A notice you cannot date is a notice you cannot count from. Keep proof of service.
- 5. Wait 21 days before implementation. No exceptions short of the four statutory carve-outs. If you believe an exception applies, document the specific facts that satisfy every element — particularly for the emergent-shift exception, where the Grievance Redressal Committee consultation must actually have happened.
- 6. If in doubt, give notice anyway. The cost of a 21-day wait is measurable. The cost of a successful procedural challenge to an automation rollout is not.
Frequently Asked Questions
No. Introducing technology does not by itself trigger Section 40. The obligation depends on whether the change affects a Third Schedule service condition — such as shifts, hours, duties, classification, concessions, or rationalisation likely to lead to retrenchment. A software upgrade that changes nothing about how, when, or for how long workers work may fall outside the provision entirely.
No. Hours of work and rest intervals are item 4 of the Third Schedule, and starting, altering, or discontinuing shift working is item 6. If automation changes when workers start or end their shifts, the notice requirement applies regardless of the technology that caused the change. The only shift-related exception is an emergent situation, and that requires consultation with the Grievance Redressal Committee.
The Code’s penalty chapter does not make a breach of Section 40 a criminal offence. However, a change made without notice is a change made in breach of statute, which strengthens any worker challenge before a tribunal. Once a dispute is pending, Section 90(1) restricts further changes connected with the dispute. The practical penalty is litigation risk and potential invalidation of the change, not a fine.
Section 40 applies to “workers” as defined in the Code. The definition excludes persons employed mainly in a managerial or administrative capacity, and persons in supervisory roles drawing wages above the prescribed threshold (₹18,000 per month at the time of writing). For employees outside the definition, a unilateral change to material terms of employment is a contract question, not a Section 40 question.
Give the notice anyway. Use Form IV — the Central Government’s template — and serve it on affected workers. The 21-day wait applies regardless of whether the state has prescribed a specific form, and using Form IV ensures the content covers what a notice should contain.
The Bottom Line
Automation is not exempt from India’s industrial relations framework. Section 40 creates a procedural gate: if the change touches a Third Schedule condition, the employer must notify and wait 21 days. The gate is not onerous — three weeks is a manageable lead time for most technology rollouts — but it is mandatory. The companies that plan automation with the Third Schedule open beside the project plan will avoid the trap of discovering, after the fact, that the change they implemented was procedurally invalid from day one.
Reference: Industrial Relations Code, 2020 · Section 40, Third Schedule, Section 90(1)
