A third-party logistics operator in Tamil Nadu ran a festive-season peak that needed roughly twice its normal floor headcount for about eight weeks, and its normal headcount the day after. The ramp was staffed as a dated surge under section 57(1)(c) of the OSH Code, sized from throughput rather than a headcount guess, run inside the overtime cap, and demobilised on the date in the work order. This is a representative composite of how such a ramp is done; no single client is described.
The situation
The site was a multi-client fulfilment hub in the Chennai belt, running pick, pack, sort and dock work through a single contractor on a licence covering about 200 contract labour [VERIFY: composite figure]. The customer's forecast for the festive quarter showed outbound volume rising in three steps over four weeks, holding for three, then falling off in one. The operations head's first request was the obvious one: "double the crew from the first of the month". The problem with that request was that it doubled the wage bill four weeks before the volume arrived, and it put 160 new people through the gate on one day, which is the pattern that produces the first-90-day exits described elsewhere on this site.
There were three compliance questions underneath the operational one. Pick and pack at a fulfilment hub is the establishment's core activity, so contract labour on it needed one of the section 57 exceptions, and the only one that fitted was (c): "any sudden increase of volume of work in the core activity which needs to be accomplished in a specified time". The contractor's licence covered 200, not 320, so it needed amending under section 47(3) before the first extra worker was deployed. And a 12-hour day for the existing crew, which was the other obvious answer, would have used four overtime hours per worker per day against a quarterly cap of 125 hours under the Tamil Nadu draft rules, which is exhausted in about eight weeks of such days [VERIFY: cap figure from draft r.30(4); final Tamil Nadu rules not notified].
What we did
We sized the ramp from the forecast, not from the request. The customer's volume steps translated into a headcount curve: about 200 on the floor in week one, 260 in week two, 320 from week four through week six, and back to 160 in week eight [VERIFY: composite figures]. Staffing to the curve rather than to the peak from day one took roughly 30% out of the surge wage bill compared with the "double it from the first" plan, before any overtime was counted [VERIFY: composite figure, arithmetic on the curve above]. It also meant the gate never took more than 60 new starters in a week, which the site's induction and the contractor's supervision could absorb.
| Week | Floor headcount | New starters | Notes |
|---|---|---|---|
| 1 | ~200 | ~40 | Bench called first; licence amendment filed before deployment |
| 2 | ~260 | ~60 | Second volume step; dock and sort added |
| 3 | ~290 | ~30 | Pack line at full; overtime block opened for pick only |
| 4 to 6 | ~320 | ~30 then 0 | Peak held; overtime hours tracked per worker against the cap |
| 7 | ~240 | 0 | First step down; surge crew released in reverse order of joining |
| 8 | ~160 | 0 | Work order closed; exit settlements and experience certificates issued |
Every figure in the table is a composite [VERIFY]. The exception relied on was documented before the first surge worker arrived: a one-page note in the contract file recording the forecast, the specified end date and the section 57(1)(c) basis, so that the deployment had an answer ready if an Inspector-cum-Facilitator or a union asked. The licence amendment to raise the headcount from 200 to 320 was filed on the Shram Suvidha portal in the week before the ramp and the acknowledgement kept with the note [VERIFY: amendment procedure and timing under the OSH (Central) Rules 2026].
- Bench first, then new hires. The contractor's bench of previously deployed workers, cleared on documents and inducted before, supplied the first 40; they were on the floor on day one with no induction lag and became the shift leads for the newcomers [VERIFY: composite figure].
- Overtime as a block, not a habit. A four-hour overtime block was opened for the pick function only, in weeks three to six, with written consent per worker and an hours tracker per worker against the quarterly cap; no worker crossed 60 overtime hours in the quarter [VERIFY: composite figure]. Section 30's twelve-hour gap was enforced through the contractor's attendance system, since some surge workers had come from another site's roster.
- ESIC and EPF from the first shift. Every surge worker was registered before day one, so that the monthly evidence pack for the peak month reconciled to the gate register; the site's exposure under section 42 of the Code on Social Security, where a worker is insured only after an accident, does not wait for the peak to end.
- Exit in reverse order, with paperwork. The work order carried the end date. Surge workers were released in reverse order of joining as the volume stepped down, each with a final settlement inside the wage period and the experience certificate section 56 of the OSH Code requires on demand, and the bench list was updated with the names to call first next year.
What changed
The peak was delivered without a missed outbound cut-off in the eight weeks, and the site ended the quarter with its normal headcount, a licence sized for the next peak, and a bench list of about 120 workers who had been through the induction once [VERIFY: composite figures]. The surge wage bill came in about 30% under the original "double from day one" plan, and the overtime spend under half of what a 12-hour roster for the existing crew would have cost, without the cap problem [VERIFY: composite arithmetic]. The compliance file for the quarter held four documents: the section 57(1)(c) note, the licence amendment acknowledgement, the per-worker overtime tracker and the monthly ECR and ESIC challans reconciled to the gate register.
Two things the site does differently now. The customer's forecast goes to the contractor as a headcount curve by week, six weeks before the first step, and the bench is called from that curve rather than from a phone call on the day. And the licence is kept at the peak number year-round, since the amendment is cheaper than the gap. Whether a particular site's peak falls within section 57(1)(c), and how its State's rules set the overtime cap, are questions on the facts for the site's own counsel; this composite describes a method, not a guarantee.
Sources
- Figures are a representative composite drawn from our own deployments; no single client is described. Founder to confirm or replace before publish.
- Occupational Safety, Health and Working Conditions Code, 2020 (Act 37 of 2020), Gazette text hosted by DGFASLI — s.27 (overtime and consent), s.30 (twelve-hour gap between employers), s.47(3) (licence headcount and amendment), s.56 (experience certificate), s.57(1)(c) (sudden increase of volume in core activity). Opened and read.
- Occupational Safety, Health and Working Conditions (Tamil Nadu) Rules, 2022 (draft), G.O. Ms. No. 38, 11 April 2022 — draft r.30(4) proviso, 125 overtime hours in any quarter. Draft only [VERIFY: whether final Tamil Nadu rules have been notified].
- Code on Social Security, 2020 (Act 36 of 2020), Gazette text hosted by the Ministry of Labour and Employment — s.31 (contributions for contractor employees), s.42 (Corporation's rights where a worker is insured late). Opened and read.
- Ministry of Labour and Employment, FAQs on the OSH Code, 2020 (January 2026) — Q2 (licensing threshold), Q3 (hours and overtime). Opened and read.