Contract labour compliance has a well-known checklist: the principal employer registers, the contractor licences, both maintain registers, and returns go in half-yearly or annually depending on the state. Most establishments do that part. The exposure sits in the gaps between those items.
The first gap is scope creep in the registration certificate. Registration is granted for a stated number of workmen and a stated nature of work. When headcount at a site drifts above the number endorsed, or the contractor starts performing work outside the described activity, the registration no longer covers the deployment — and an inspection reads that as engaging contract labour without registration.
The second gap is wage verification. The principal employer is liable for wages if the contractor defaults, which makes monthly verification of the contractor's wage register, PF and ESI remittances a self-protective control rather than a courtesy. Ask for the ECR and the ESI contribution history against the deployed list, not just an invoice and a declaration.
The third gap is the boundary between contract labour and core activity. Under the OSH Code, engaging contract labour in core activities is restricted with limited exceptions. That is a design question about how work is packaged, and it needs answering before a contract is signed, not during an inspection.
The practical control set is short: reconcile deployed headcount to the registration monthly, verify contractor statutory remittances monthly against the deployed list, keep the licence and its conditions on the same calendar as your own registrations, and review any long-running deployment in a core activity annually with counsel.
Key takeaways
- Reconcile deployed headcount to your registration endorsement monthly.
- Verify contractor PF/ESI remittances against the deployed list.
- Test core-activity deployments before signing, not at inspection.