Licences and compliance

Contract Labour Licence: When Businesses Need It

Contract labour law explained — CLRA registration for principal employers, contractor licences, thresholds, compliance duties and the risks of ignoring it.

Licences and compliance · 4 min read · Updated 2026-01-22

Housekeeping through an agency, security guards from a vendor, loading labour via a thekedar, a canteen run by a caterer — the moment workers on your premises are employed by someone else, the Contract Labour (Regulation & Abolition) Act enters the room. It obligates two parties at once: you (the principal employer) to register, and your contractor to hold a licence. Most SMEs discover the Act from an inspector's notice; here is how to discover it in advance.

When the Act applies

  • Threshold: 20 or more contract workers on any day of the preceding 12 months (central sphere) — several states have raised it (20→50 in some, e.g., for their establishments); check your state's amendment
  • Counts across contractors: 8 security guards + 7 housekeeping + 6 canteen staff = 21 — you're in
  • Applies to establishments and to every contractor supplying that many workers to one establishment
  • Excluded: work of an intermittent/casual nature (formally determined, not self-declared)

New labour codes (the OSH Code) reframe these provisions with higher thresholds, but until state-wise enforcement fully switches, the CLRA machinery is what inspectors apply — comply with the regime actually enforced in your state.

Your side: principal employer registration

Cross the threshold and the establishment must register (Form I) with the registering officer — state portals now handle this online in most places — declaring the nature of work, contractor details and worker counts. The certificate hangs with your other licences. Registration is not a formality you can skip while the contractor holds his licence: an unregistered principal employer cannot lawfully engage contract labour at all, and the Act's penalties (fines and imprisonment provisions) attach personally to the employer and manager.

The contractor's licence — verify it like a bank verifies collateral

  • Every in-scope contractor needs a licence (Form IV application) per establishment served, with security deposit and validity/renewal cycles
  • Before onboarding any manpower vendor: take the licence copy, verify worker counts within its limit, and calendar its expiry
  • Your agreement should oblige the contractor to maintain licences, registers, and statutory payments — with an indemnity
  • An unlicensed contractor's workers can be deemed your direct employees in disputes — the single largest hidden risk in casual outsourcing
The liability ladder

Under the Act, if the contractor fails to pay wages or provide amenities, the principal employer must pay and recover from the contractor. PF and ESI follow the same pattern. Outsourcing transfers work — it never transfers ultimate liability. Choose manpower vendors like you choose auditors.

Running compliance month to month

The rhythm that keeps both sides clean: contractors pay wages in your representative's presence (and certify it — Form-wise registers exist for exactly this); collect monthly proof of the contractor's PF/ESI challans for deployed workers before releasing their invoice; maintain the principal employer's registers (contractors, employment cards' oversight) and display notices as prescribed; ensure amenities the Act promises — canteen/restrooms/first-aid at applicable scales, drinking water always; and file annual returns where prescribed. Ten minutes of monthly verification beats one deemed-employment judgment.

Structuring to stay sane

Legitimate structuring helps: consolidating vendors (three licensed contractors are easier to police than nine informal ones), genuine service contracts for outcome-based work (a pest-control AMC is a service, not contract labour — but disguising manpower supply as 'services' fails the substance test), and automating threshold tracking so you register before an inspector counts for you. What never works: splitting one contractor into paper entities to stay under 20, or ignoring the Act because 'sab aise hi karte hain' — labour inspections increasingly start from PF/ESI data where your contractors' workers already appear against your premises.

How Aidwish helps

Aidwish maps contract-labour exposure for clients — threshold audits, principal-employer registration, contractor verification kits and the monthly compliance checklist — as part of its staffing and norms stage, so outsourced manpower stays an efficiency, not a liability.

FAQ

Questions, answered

We use 12 security guards and 10 housekeeping staff through agencies. Are we covered?

Yes — 22 contract workers across contractors crosses the standard threshold; the establishment needs registration and each in-scope contractor a licence (verify your state's current threshold — some raised it to 50).

What happens if our contractor never took a licence?

You face prosecution exposure for engaging contract labour irregularly, and in disputes those workers can claim to be your direct employees — with back wages and benefits. Verify licences before onboarding, not after notices.

Are we responsible for the contractor's PF and ESI?

Ultimately yes — as principal employer you must ensure coverage and can be made to pay defaults (then recover from the contractor). Collect monthly challan proofs as an invoice-release condition.

Does the Act apply to one-time construction work at our site?

Construction typically routes through BOCW and CLRA depending on scale — a 20+ worker contractor project triggers the machinery. For renovations and projects, make CLRA/BOCW compliance the contractor's documented obligation with verification.

Ready to move forward?

Book a free consultation and get a clear, step-by-step plan for your business.