There is one assumption in contract labour compliance that costs Indian employers more than any other: that engaging a contractor moves the obligation to the contractor. Under the Contract Labour (Regulation and Abolition) Act, a great deal of it stays exactly where it was.
This matters because contract labour is how most Indian plants, warehouses and multi-site operations actually staff themselves. If you engage contract workers above the applicable threshold, you are a principal employer, and that is a defined role with defined duties, not a commercial description.
The principle in one line
The contractor employs the worker. The principal employer remains answerable for whether the law was followed on their premises.
Everything below follows from that. An inspection does not arrive at your gate and ask to see your contractor. It asks to see your records.
Registration and licensing come first
Two separate things have to exist before contract workers are deployed, and they are held by two different parties:
- Your registration as principal employer, covering each establishment where contract labour is engaged, listing the contractors you engage. Adding a contractor generally means amending it.
- The contractor's licence, which is theirs to hold, and yours to verify. Engaging an unlicensed contractor is a problem for you as well as for them.
The most common finding at inspection is not an absent registration. It is a registration that no longer matches reality: a contractor who is on site but not on the certificate, or a headcount well past what was declared.
What you have to maintain yourself
These are the principal employer's own records. They are not the contractor's to keep on your behalf:
- Register of contractors engaged, per establishment
- Records of the work each contractor performs and the period of engagement
- Notice of commencement and completion of contract work
- Statutory abstracts and notices displayed where the workforce can read them
- Evidence that you verified the contractor's compliance, month by month
What you have to verify, every month
This is where the real risk sits, because it is the part that quietly stops happening once an engagement settles into routine. The contractor maintains the muster roll, the wage register, the wage slips and the deduction registers. You have to see them.
- Wages paid to contract workers at or above the applicable minimum wage for that state and scheduled employment
- Wages paid within the wage period, through bank transfer, with proof
- PF and ESI contributions actually remitted, not merely deducted
- Challans and returns filed, and retrievable by period
- The register of workmen matching the people who are physically on site
Registers reconcile on paper far more often than they reconcile with the gate. A headcount that does not match the muster roll is the finding that leads an inspector to look at everything else.
Wages: the liability that surprises people
If a contractor fails to pay contract workers, the obligation does not simply lapse. The principal employer can be required to make the payment and recover it from the contractor afterwards. In practice that means a contractor's cash flow problem can become your payment problem, in the same month, with no notice.
This is the strongest practical argument for collecting compliance evidence every month. By the time an annual review finds a problem, several months of exposure have already accrued.
What to put in the contract
- An obligation to hold and maintain a valid licence, with a copy provided
- Monthly submission of wage registers, attendance, challans and returns as a condition of invoice payment
- The right to inspect records and to audit the site
- Indemnity for statutory dues, and a clear position on who bears a penalty arising from the contractor's default
- A defined exit process, including handover of records you are required to keep
Tying evidence to invoice payment is the single most effective clause in that list. It moves compliance from a request to a condition.
Making it a system
Compliance fails on cadence, not on knowledge. Almost every employer knows what is required. What separates a clean inspection from a bad one is whether the records can be produced on the day, at the site, for the period being asked about.
A workable system has four parts: a named owner per site, a fixed monthly date for collecting contractor evidence, one place where registers and challans are stored by period, and a review that closes previous observations rather than repeating them.
The HR compliance checklist lists the registrations, registers, returns and displays an inspection asks for, with nothing to fill in first. Or read how compliance management runs as a standing service.
