Contract Labour Headcount: Are You Paying for Workers Who Are Not on the Line?

Almost certainly yes — the open question is how much. Most Indian plants count contract labour at the gate and pay per attendance day, but the gate is not the line. On a 300-worker plant billing 120 contract heads at roughly Rs 700 a day all-in, every one percent of gap is about Rs 2.6 lakh a year.

You run a 200–1000 worker plant somewhere between Hosur, Pune, Rajkot and Manesar. You have a manpower contractor — maybe three. Each month a bill arrives with a head-day count on it, and you have almost no independent way to check that number. This article is about building one, what it is legitimately worth in rupees, and where the whole idea can backfire on you.

Key points

• The gate is the wrong counting point. A gate reading tells you who entered the premises. Your bill is for productive presence on a line, in a shift, for the hours claimed. Those are different numbers, and only one of them is what you bought.
• The law changed under your feet. The Occupational Safety, Health and Working Conditions Code, 2020 consolidates 13 labour laws — including the Factories Act, 1948 — and now carries the contract-labour provisions that used to sit in the Contract Labour (Regulation and Abolition) Act, 1970 (PRS legislative tracker). The major provisions of the labour codes took effect on 21 November 2025 (KPMG flash alert). If your contract templates still cite "the CLRA Act, 1970" as the governing statute, they are stale.
• The threshold moved from 20 to 50. The Code's contract-labour chapter applies to establishments that employed 50 or more contract workers on any day in the preceding 12 months, and to manpower contractors at the same threshold (India Briefing, OSH Code primer). Under the OSHWC Central Rules, 2026, such a contractor needs a single licence valid for five years (Obhan & Associates on the Central Rules, 2026). The 20–49 band is now a soft zone, and that shapes how contractors split and report headcount.
• The rules assume contractor wage default is a live risk. Rule 90 of the Central Rules, 2026 requires a security deposit of Rs 1,000 per contract worker, which the Chief Labour Commissioner (Central) may draw on directly if minimum wages go unpaid (Obhan & Associates, above). Ask your own counsel what residual liability sits with you as principal employer — the Code defines the principal employer as the person responsible for supervision and control of the establishment where contract labour is engaged.
• The rupee base is real and rising. Central-sphere minimum wages were revised again by a notification of 30 March 2026 with effect from 1 April 2026 — for sweeping and cleaning, Rs 827/day in Area A, Rs 693 in Area B and Rs 556 in Area C (SCC Online). Every percentage point of phantom headcount costs more this year than last.
• A camera count is evidence, not a verdict. Used well it opens a conversation with your contractor. Used badly it creates an industrial-relations incident and a legal argument you do not want.

The three numbers that never agree

Every plant that engages contract labour is quietly carrying three different headcounts:

1. The muster / bill count. What the contractor says was deployed. This is what you pay.
2. The gate count. Biometric, card, or register at the entry. Closer to reality, but it says nothing about where the person went after the turnstile.
3. The line count. How many bodies were actually at the packing table, the loading bay, the housekeeping round, during the shift hours billed.

The gap between (1) and (2) is the classic phantom-worker problem, and it is the one everyone talks about. In practice it is often the smaller gap, because gate systems have been common in Indian plants for years.

The gap between (2) and (3) is where the money usually is, and almost nobody measures it. Twelve people badge in for the second shift; nine are on the line at 15:40; two are on a tea break that started at 15:05; one is doing a favour for another department. Nothing here is necessarily fraud. It is drift, and you are funding it.

What actually causes the gap

Be precise about the mechanism before you accuse anyone. In Indian plants the gap usually comes from one of five things, and only two of them are the contractor's fault.

The percentages below are a planning heuristic for structuring your own measurement — not published data. Use them to decide what to look at, then replace them with your numbers.

That last row matters most. If your contract heads are physically present but idle because the previous operation starved them, the leak is in your planning, not the contractor's bill — and cutting heads will cost you output. This is exactly the distinction production line monitoring cameras are for: presence and activity are two separate measurements, and confusing them is how owners make the wrong decision confidently.

A rupee model for a 300-worker plant

Assumptions, stated openly so you can substitute your own:

• 300 total workers on site; 120 engaged through contractors
• Billed all-in rate Rs 700 per head-day — wage plus PF/ESI plus contractor service fee. For scale: the central-sphere unskilled sweeping-and-cleaning rate from 1 April 2026 runs Rs 556–827/day basic-plus-VDA depending on area. Your state schedule (Maharashtra Zone I, Tamil Nadu, Haryana) will differ — substitute it.
• 26 billed days per month

Baseline: 120 × 26 × Rs 700 = Rs 21.84 lakh per month, about Rs 2.62 crore a year.

Against that, a retrofit analytics layer over existing CCTV — no new cabling, no new NVR — typically lands in the low lakhs a year for a plant this size, so even the conservative 3% case pays back inside a year. The full cost side is in does camera AI pay for itself in India.

One caution on the model: do not book the whole gap as savings. Some of it converts into output rather than a lower bill, and some of it you will hand back in a renegotiated day rate once the contractor's margin assumption is corrected.

The OSH Code paperwork angle nobody uses

Here is the part that is specific to India after November 2025.

Under the Code, employers must issue letters of appointment, issue wage slips (electronically or otherwise), and maintain registers containing worker particulars including wages paid and receipts given (India Briefing primer). Records that used to be a dusty muster book are now expected to exist in electronic form.

That matters commercially, not just legally: it means the per-worker wage record you want from your contractor is a record they are already obliged to keep. Ask for it as a contractual deliverable in the work order — the Code does not hand it to you automatically, but it makes "we don't keep that" an implausible answer.

So the reconciliation becomes a three-way one — the contractor's wage/attendance record, your gate log, and your line count. Any two agreeing and the third disagreeing tells you which of the five causes above you are dealing with. You do not need to accuse anyone; you present the three columns.

One structural point worth knowing before you read a contractor's numbers: because the licensing regime now bites at 50 contract workers, a contractor has an obvious incentive to report strength at 49 rather than 50, including by splitting a deployment across entities. If a contractor's reported strength sits suspiciously just under the threshold while your line count says otherwise, that is a compliance question that reaches you as principal employer, not only a billing question.

What the cameras do NOT do — read this before you buy

They do not identify individuals, and you should not want them to. A count of bodies at a workstation is a count. The moment you add face recognition to match names on a contractor's muster, you are processing biometric personal data about people who are not your employees, with all the consent and notice questions that follow under India's DPDP framework — see DPDP and worker CCTV. For headcount reconciliation you need a number, not a name. Buy the number.

They do not prove fraud. A low line count is consistent with a phantom worker, a stores errand, a machine breakdown, and a camera whose view got blocked by a stacked pallet. Treat every count as a prompt to ask, never as a finding. Anyone selling you "automatic contractor billing deduction" is selling you a dispute.

They can feed a sham-contract argument against you. The Code prohibits contract labour in core activities of an establishment, with narrow exceptions — where the activity is ordinarily done through a contractor, where it does not need full-time workers for the major part of the day, or where there is a sudden spike in volume (PRS tracker). Indian tribunals look hard at supervision and control when deciding whether an arrangement is genuine. If you build a dashboard where your manager tracks individual contract workers shift by shift and directs them, you are creating a record of your own control. Keep the measurement at the aggregate, per-line, per-shift level, route every consequence through the contractor, and have your labour counsel review the reporting design, not just the contract.

Counting is genuinely hard in some places. Dense assembly benches with heavy occlusion, dark dyeing sections, dusty grinding bays, and anywhere workers cluster shoulder to shoulder will give you a soft number. Loading bays, packing halls, canteen approaches, line entries and housekeeping rounds count well. Place cameras for counting deliberately rather than reusing whatever happens to point at the aisle.

They do not survive being sprung on people. Introducing counting as a surprise audit of a specific contractor, mid-contract, in a plant with an active union, is how you get a shutdown instead of a saving.

How to run this without a fight

1. Tell the contractor first, in writing, before any camera is pointed anywhere. Frame it as reconciliation, not surveillance. Most contractors with clean books welcome it, because it protects them from your suspicion too.
2. Put it in the next work order. A clause stating that billing is reconciled against line-presence sampling, with a defined tolerance band (say 5%) and a joint review before any adjustment, converts a future argument into an agreed procedure.
3. Measure for one full month before you say anything. Include a festival week and a peak week. One bad Monday proves nothing.
4. Present line and shift aggregates, never individuals. "Line 3, second shift, billed 22, average present 18.4" is a business conversation. A named worker's timeline is an IR case.
5. Separate presence from output. Fix the material-starvation rows in the table above yourself before demanding money back for them.
6. Retain the footage no longer than you need it, and align retention with whatever else you already store.

The realistic outcome is not that you catch a fraudster. It is that within two months your contractor's bill and your line reality converge, your supervisors stop guessing about shift-edge drift, and a sum that on this model runs somewhere between Rs 8 lakh and Rs 39 lakh a year stops leaving quietly. It is also that you sometimes discover the gap was yours.

FAQ

Is it legal to count contract workers with cameras in an Indian factory? Counting bodies at a workstation is ordinarily lawful in a workplace you control, with proper signage and notice. It becomes legally sensitive when you identify individuals — biometrics or face matching against a contractor's muster pulls in DPDP obligations and, because these are not your employees, consent and notice questions you cannot answer alone. Aggregate counts avoid most of it.

Does the Factories Act, 1948 still govern this? No. The Factories Act, 1948 is one of the 13 laws consolidated into the OSH Code, 2020, whose major provisions took effect on 21 November 2025, with the OSHWC Central Rules notified in 2026. The Code also carries the contract-labour regime that previously sat in the Contract Labour (Regulation and Abolition) Act, 1970. Contracts, standing orders and vendor templates still citing the 1970 Act by name should be refreshed at the next renewal.

Can I deduct from the contractor's bill based on camera counts? Not unilaterally, and not safely. Camera counts are one input, alongside the gate log and the contractor's own wage and attendance records. Any deduction needs a pre-agreed clause, a tolerance band, and a joint review of the disputed shifts. Deducting on camera data alone invites a dispute you will probably lose on process.

How many cameras do I need just for headcount? Far fewer than for full coverage. You need clean views of line entries, the packing and dispatch areas, and the main circulation routes. Start with existing cameras that already see those points, and add only where the view is genuinely blocked. See how many cameras a factory floor needs.

What if my contractor refuses to accept camera-based reconciliation? That refusal is itself information, but do not over-read it. Many contractors object because they fear the numbers will be used punitively rather than diagnostically. Offer them the same monthly report you see, agree the tolerance band in advance, and give one cycle as a no-consequence baseline. Genuine refusal after that is worth a hard look at the next tender.

Will this help with attendance for my own permanent workers too? Yes, but the value is different. For permanent staff you already have payroll-grade attendance; what cameras add is shift-edge and break discipline, not headcount verification. That is a supervision question rather than a billing one.