Contract Labour vs Employment: Compliance Risks for Startups

As startups scale, hiring rarely happens through a single clean channel. Some people join as full-time employees, some come in through staffing agencies or contractors for specific functions, and some are engaged as consultants or freelancers. Each of these categories carries a different compliance profile, and the line between them is not just paperwork; it determines who owes PF, ESI, gratuity, and other statutory dues, and to whom.

What the CLRA Actually Regulates

The Contract Labour (Regulation and Abolition) Act, 1970 governs the use of contract labour, workers supplied by a contractor to work at another business's establishment, rather than being directly employed by that business. It applies to every establishment where contract labour is used and every contractor who supplies that labour, once the applicable threshold is crossed, and it imposes separate registration and licensing obligations on the two sides of that relationship.

The Act does not ban contract labour outright; it regulates how it can be used, requires baseline welfare facilities for contract workers, and gives the appropriate government the power to prohibit contract labour in specific categories of work where it decides direct employment is more appropriate.

The 20-Workmen Threshold

The registration and licensing requirements apply once 20 or more workmen are engaged as contract labour, on any day in the preceding 12 months, for both the principal employer and the contractor:

Both obligations run in parallel and neither substitutes for the other. A startup that has itself registered as a principal employer is not automatically compliant if the contractors it uses have not obtained their own licences, and vice versa. For a growing business that engages multiple staffing vendors, security agencies, or housekeeping contractors, it is worth checking each vendor's licensing status rather than assuming compliance is handled purely on the vendor's side.

Note that this 20-workmen count is specific to workers engaged through contractors; it is a separate count from, and often overlaps in practice with, the 20-employee EPF threshold and the lower ESI applicability threshold, both of which count the full workforce including contract staff.

Principal Employer Obligations Beyond Registration

Registration is the starting point, not the end, of a principal employer's obligations. Under the CLRA framework and related labour law, a principal employer is generally expected to:

• Ensure welfare facilities for contract workers at the workplace, including canteen, restrooms, and first-aid facilities where applicable, even though the contractor is the immediate employer.
• Monitor wage payment by the contractor and step in to pay wages directly, recoverable from the contractor, if the contractor defaults. This is a genuine financial exposure, not a theoretical one; a principal employer cannot simply point to the contractor and disclaim responsibility when workers go unpaid.
• Maintain records of contract labour engaged, including attendance and the licences held by each contractor supplying workers.

This shared-liability structure is precisely why a principal employer benefits from actively verifying contractor compliance, checking licence validity, reviewing whether the contractor is depositing PF and ESI for its workers, rather than treating the contractor relationship as fully outsourced and risk-free.

The Real Risk: Misclassification, Not Just Registration

The more common exposure for startups is not failing to register under CLRA; it is misclassifying what is actually an employment relationship as a contractor, consultant, or gig-worker arrangement to avoid statutory obligations altogether. Authorities and courts look past the label on the engagement letter to the substance of the relationship. Factors that push a relationship toward being treated as employment, regardless of what the contract calls it, include:

• Fixed working hours and a requirement to be present at the employer's premises or log in during set hours.
• Direct supervision and control over how the work is performed, not just what output is delivered.
• Exclusivity, being barred from working for other clients or taking on other engagements.
• Use of the company's equipment, email domain, and systems in the same way as regular employees.
• Ongoing, indefinite engagement rather than a defined project or deliverable with a clear end date.
• Integration into the core team structure, reporting lines, appraisals, and internal communications as if a regular employee.

If a relationship structured as a "contractor" or "consultant" arrangement is later found to function as employment, the consequences are retrospective: PF and ESI contributions for the full period the relationship existed, potential gratuity liability if the tenure crosses the threshold, and penalties for the underlying non-compliance. Because these liabilities can span years of an engagement rather than a single missed filing, misclassification risk tends to be underestimated relative to how much it can eventually cost.

Getting the Classification Right From the Start

The practical safeguard for a startup is to make the engagement structure match the label used. Genuine consultants and freelancers should have real project-based deliverables, control over their own working hours and methods, freedom to take other clients, and their own tools and equipment. Where a business genuinely needs supervised, ongoing labour at scale, contract labour through a licensed contractor, with the principal employer registration and contractor licensing properly in place, is the compliant route; treating the same workforce as informal "freelancers" to sidestep both routes is where the real exposure sits.