Research
State of Contract Labour Compliance in Indian Manufacturing 2026
12 min read
Data source: Anonymized InOps platform data from 163+ manufacturing sites across India, covering automotive, electronics, FMCG, steel, cement, and logistics sectors. Data period: January 2025 – May 2026.
Key finding: The majority of Indian manufacturing sites operating contract labour carry at least one unresolved statutory compliance gap at any given time. PF reconciliation errors, incomplete Form V/XIII documentation, and untracked overtime are the three most common failure modes — each of which can result in penalties under the Contract Labour (Regulation & Abolition) Act, 1970.
This report draws on anonymized InOps platform data from 163+ manufacturing sites across India spanning automotive, electronics, FMCG, steel, cement, and logistics. It is the first dataset of this scale to be published on contract labour compliance outcomes in Indian industry.
Most common compliance violations by category
PF/ESI reconciliation gaps are the most prevalent violation type across the dataset. The root cause in most cases is not intent but process: statutory deductions are calculated on one system, verified on another, and filed from a spreadsheet — with deltas accumulating silently across monthly cycles.
The second-most common violation class is overtime documentation. Under the Factories Act and most state-level standing orders, overtime must be pre-authorised, capped, and tracked per worker. Manual systems cannot enforce these rules in real time, so violations surface only during inspections.
Form V and Form XIII (CLRA documentation for contractor establishments) are missing or incomplete at a significant share of sites. This is the highest-risk gap during a labour department inspection because it implicates the principal employer directly.
Multi-site complexity multiplies risk
Sites operating three or more contractor agencies simultaneously show materially higher compliance incident rates than single-contractor sites. The breakdown is not operational — it is informational: each contractor runs its own documentation process, and principal employer HR teams lack a unified view.
Top-quartile performers in the dataset use a single platform for onboarding, attendance, and statutory filing across all contractors and gates. Bottom-quartile sites still reconcile contractor invoices manually against Excel attendance exports at month-end.
Contractor onboarding: the first failure point
A significant share of compliance incidents traced back to incomplete onboarding at day zero — workers cleared for gate entry before background verification, Aadhaar linking, or Form V filing was complete. The risk: a principal employer is liable under CLRA for any contractor worker on site, regardless of the contractor's documentation status.
Digital onboarding that gates physical access on document completion eliminates this class of violation entirely. Among InOps sites with gate-linked onboarding workflows, pre-day-one compliance incidents are effectively zero.
What top-quartile sites do differently
The plants with the cleanest compliance records share three characteristics: biometric attendance feeds payroll directly (no manual timesheets), statutory deductions are calculated and verified in the same system, and contractor documentation is stored digitally with expiry alerts. None of these are technology breakthroughs — they are process discipline enforced by software.
The payoff is measurable: plants in the top compliance quartile report fewer inspector-initiated disputes, lower penalty exposure, and faster finance closes. Compliance is not a cost centre when the process is automated.
Implications for principal employers
The CLRA places joint liability on the principal employer for any contractor compliance failure on their premises. This means the legal and financial consequences of contractor non-compliance — PF arrears, ESI disputes, overtime claims — fall on the factory operator, not the staffing agency.
The practical response is not more auditing. It is replacing the audit cycle with real-time visibility: live headcount, per-worker deduction tracking, and automated challan generation. InOps CLMS was built to make this the default, not an exception.
