The most common ESIC question we get is not "what is ESIC", it's "is this specific worker covered or not", and the confusion almost always comes from mixing up gross wages, basic pay and the wage ceiling. Here's how it actually works.
The Ceiling, and What Counts Toward It
An employee is covered under the Employees' State Insurance scheme when their gross wages are at or below the notified ceiling, currently ₹21,000 per month (₹25,000 for employees with disabilities). Gross wages here means basic pay, dearness allowance, and most regular monthly allowances, added together. Under the wage definition used across the new Labour Codes, if allowances are structured so they exceed 50% of total remuneration, the excess gets added back into the wage calculation, which closes a common workaround where a higher-paid worker's basic was kept artificially low to dodge the ceiling.
The Two Conditions That Must Both Be True
- 1. The establishment must be coveredESIC registration is mandatory once a factory or establishment employs 10 or more people (20 in a few states) on any day in the preceding 12 months. This includes contract and fixed-term workers in the headcount, not just direct payroll staff.
- 2. The individual worker's wages must be within the ceilingOnce the establishment is covered, every worker earning at or below the ceiling is covered, regardless of how long they've worked there, from day one of insurable employment.
What Happens Mid-Period If Wages Cross the Ceiling
ESIC works in fixed contribution periods (April to September, and October to March). If a worker's wages cross the ceiling partway through a period due to a raise, coverage continues for the rest of that contribution period, contributions keep being deducted and paid as normal, and the question of continued coverage is only revisited at the next period.
Whether a worker is covered under ESIC isn't a judgement call. It's arithmetic, gross wages against a fixed ceiling, checked at the start of each contribution period.
Why This Matters for Contract Labour Specifically
Workers deployed through a manpower supplier are counted in the client establishment's headcount for the 10-employee threshold, and their coverage is assessed the same way as any direct employee. A supplier who tells you contract workers are "handled separately" from ESIC obligations is giving you an answer that doesn't match how the Act actually works.
Unsure which of your workers are ESIC-covered?
Send us your headcount and wage structure and we will walk through the coverage with you, no obligation.
Where Employers Actually Get This Wrong
In practice, ESIC coverage mistakes cluster around three specific situations. The first is a new establishment that crosses the 10-employee threshold mid-year, sometimes by adding a handful of contract workers for a short production run, and doesn't realise registration is now mandatory because nobody counted the contract headcount alongside direct staff. The threshold counts everyone working at the establishment on any day, not just permanent payroll.
The second is wage restructuring done for reasons that have nothing to do with ESIC, an incentive scheme, a temporary allowance, a festival bonus paid monthly instead of annually, that quietly pushes a worker's gross wages over the ceiling without anyone updating their coverage status. Since coverage is meant to continue for the rest of the contribution period once it starts, an increase that happens right at the start of a new period can genuinely remove a worker from coverage, and missing that update either way creates a compliance gap.
The third, and the one that causes the most friction with workers directly, is a misunderstanding about what ESIC actually pays for. Workers sometimes assume ESIC covers only hospitalisation, and are unaware it also covers sickness benefit (a wage-replacement payment during certified illness), maternity benefit, and disablement benefit for workplace injury. When a worker doesn't know these exist, they don't claim them, and an employer who doesn't proactively explain the scheme ends up with a workforce that feels like it's paying into something it never benefits from, even though the coverage was correctly administered the whole time.
What Good ESIC Administration Looks Like
A well-run ESIC process has three habits: wage structures reviewed against the ceiling whenever a raise or allowance changes, contribution period boundaries (April to September, October to March) tracked deliberately rather than left to payroll software defaults, and workers briefed at induction on what the scheme actually covers and how to use their ESIC card at an empanelled hospital or dispensary. None of this is complicated, but all three require someone to own it as an ongoing task rather than a one-time registration event.
One more detail worth knowing: the wage ceiling has stayed at ₹21,000 since January 2017, which means inflation alone has gradually pulled more workers above it over time even without a deliberate raise. If your workforce's average wage has crept up over the past few years, it's worth rechecking coverage status across the board rather than assuming nothing has changed just because you haven't actively revised anyone's pay structure.
This is also why we treat ESIC coverage review as a recurring item rather than a one-time setup task for every worker we place, checked whenever a wage change happens and reconfirmed at the start of each contribution period, so a client never discovers a coverage gap through an inspection instead of through their own monthly review.