Factory licensing across three states: what actually differs
Same product, same process, same machinery — and three completely different licensing experiences. A close read of what genuinely differs between Maharashtra, Gujarat and Tamil Nadu factory rules, and what does not.
A manufacturer opening an identical plant in three states expects three licence applications and one shared checklist. What they get is three licence applications and three different checklists, because the Factories Act, 1948 sets the floor and each state's factory rules build on it differently.
We compared the current rules in Maharashtra, Gujarat and Tamil Nadu against a single hypothetical unit — 220 workers, one hazardous process, standard machinery — to see exactly where they diverge.
Where they are genuinely the same
The Central Act does the heavy lifting on substance. Definition of a factory, occupier and manager nomination, working hours, overtime limits, annual leave entitlement, and the core safety obligations for hazardous processes are all Central law and do not vary. A worker's statutory leave entitlement in Coimbatore is the same as in Pune.
Where they diverge, and by how much
Licence application format and fee structure. Maharashtra uses a capacity-and-horsepower-linked fee slab revised periodically by notification. Gujarat's fee schedule is linked to the number of workers in bands of 50. Tamil Nadu uses a flat structure by factory category with a separate renewal fee. None of the three fee calculations are transferable to another state's form.
Renewal cycle. Maharashtra factory licences are typically annual with an option for multi-year renewal at a higher combined fee. Gujarat has moved toward a longer default validity for lower-risk categories. Tamil Nadu retains an annual cycle for most categories. A compliance calendar built for one state's cadence will not fire correctly for the other two.
Online filing maturity. All three states now require online licence applications, but the portals differ enough in document format requirements, file size limits and workflow steps that a checklist written for one portal routinely fails on another — missing a mandatory field that simply does not exist on the first portal.
Welfare facility thresholds. Canteen, crèche and welfare officer thresholds are set by the Central Act as a floor, but several states have historically applied stricter local thresholds for specific facilities through state rules or standing instructions. This is the single most common gap we find in first-pass compliance audits: a plant meeting the Central threshold but not the state's stricter local one.
Inspection approach. Maharashtra and Tamil Nadu have both moved toward risk-based, web-allocated inspection scheduling for most categories, reducing (but not eliminating) inspector discretion on visit timing. Gujarat retains more inspector-initiated scheduling for higher-risk categories. This affects how much notice a plant realistically gets before a visit.
The table that should exist and usually does not
| Item | Maharashtra | Gujarat | Tamil Nadu |
|---|---|---|---|
| Fee basis | Capacity/HP-linked | Worker-count bands | Category-flat |
| Default renewal cycle | Annual (multi-year option) | Extended for low-risk | Annual |
| Welfare officer threshold | Central + local instruction | Central | Central + local instruction |
| Inspection allocation | Risk-based, web-allocated | Mixed | Risk-based, web-allocated |
This is the table a multi-state manufacturer needs and, in our experience building obligation registers for plant networks, almost never has in one place. It usually exists as institutional memory split across three plant managers who have each dealt with only their own state.
What this means for a group compliance function
Three practical consequences follow from this, none of them exotic:
- A single "factory licensing" line item on a group compliance calendar is meaningless. It needs to be three line items, each with the correct fee basis, renewal cycle and application lead time for that state.
- New-plant playbooks do not transfer. A checklist built from the Maharashtra experience will miss steps when applied to a Gujarat site, and vice versa. Each new state needs its own first-pass build, ideally informed by someone who has done it before in that specific state.
- Welfare facility thresholds need a state-specific check, not a Central Act check. This is where audits most often find a genuine, correctable gap — not a paperwork issue but an actual missing facility below the locally expected threshold.
None of this is a criticism of any individual state's approach — each has reasonable administrative logic behind its choices. It is simply a reminder that "the Factories Act" is a floor, not a specification, and the specification is set locally, state by state, by rules that a group compliance function has to hold separately rather than assume are interchangeable.
Written by Kavita Iyer, Director of Solution Architecture
Part of the team that builds and maintains the Regulens obligation library and platform. If you disagree with something here, we would genuinely like to hear it — get in touch.