assureOfficeCompliance Made Simple
Employment & Benefits

Do Contractors, Trainees and Remote Staff Count Toward Labour-Law Thresholds?

They can, but the answer changes with the obligation. Indian employment law does not use one universal company headcount. An employee, worker, contract labourer and statutory apprentice are different legal categories. An establishment may be covered by one chapter while another duty has a different threshold, counting unit or look-back period.

Factory architectural illustration
Architectural illustration by assureOffice; not a photograph of a particular government office.

They can, but the answer changes with the obligation. Indian employment law does not use one universal company headcount. An employee, worker, contract labourer and statutory apprentice are different legal categories. An establishment may be covered by one chapter while another duty has a different threshold, counting unit or look-back period.

In 2026, use the commenced Labour Codes, operative schemes and surviving state laws. A historical chart copied from the repealed enactments can be wrong even where some familiar numbers remain. The safest practical method is a workforce register detailed enough to apply each legal test, followed by a separate applicability decision for each obligation.

Begin with the population, not the payroll total

List everyone performing work for the business: permanent staff, fixed-term staff, part-time staff, ordinary trainees, statutory apprentices, agency workers, managers, remote staff and people described as consultants. Record the actual employer, work, location, service dates and contract basis. Remove duplicates without removing genuine simultaneous employment or deployment facts.

Payroll contains only part of that population. A staffing agency may pay workers who still count for a relevant establishment obligation. A worker on unpaid leave may remain employed although receiving no current salary. A manager can fall within an employee definition even when excluded from a narrower worker definition.

A consultancy invoice does not settle whether the person is really independent. Where classification is uncertain, collect the engagement terms, supervision, working arrangements, integration and payment facts for legal assessment. Do not use a headcount exclusion to decide the employment question backwards merely because the business prefers to stay below a threshold.

Understand the legal categories

The Social Security Code’s employee definition includes people employed directly or through a contractor for a broad range of work, including managerial and administrative duties. It excludes apprentices engaged under the Apprentices Act. It also contains chapter-specific provisions, including the rule that employees above the wage ceiling count for establishment coverage under EPF and ESI chapters.

The OSH Code distinguishes employee from worker and contract labour. The worker definition has exclusions for particular functions and supervisory wages. A manager’s exclusion from a worker-based benefit does not establish exclusion from an employee-based registration test. Read the particular provision rather than selecting the definition which gives the smallest count.

Contract labour has its own definition and an exclusion for specified regularly employed contractor workers meeting the statutory employment conditions. Do not assume every vendor employee automatically falls outside it, or that every person employed by a service provider must be classified identically. Preserve the actual facts and assess the relevant provision.

Use a duty-specific threshold table

The following are starting points from the Codes, not a complete list of exemptions or special notifications:

Obligation Starting test requiring further application
EPF chapter coverage Establishment employing twenty or more employees
ESI chapter coverage Establishment employing ten or more persons, with statutory exceptions and special cases
Gratuity at a shop or establishment Ten or more employees now or on any day in preceding twelve months
Maternity chapter at a shop or establishment Ten or more employees now or on any day in preceding twelve months
OSH contract-labour Part Fifty or more contract labour at establishment on any day in preceding twelve months; separate contractor test
OSH migrant-worker Part Ten or more qualifying inter-State migrant workers on any day in preceding twelve months

A factory, mine or other named establishment can be covered on a basis different from the shop-and-establishment row. ESI also has benefit-area commencement and specially notified hazardous-occupation considerations. State Shops legislation and other surviving laws require their own tables. A quick comparison is useful only when its limitations remain visible.

Separate establishment coverage from individual entitlement

An establishment can cross an EPF or ESI threshold using employees who do not all become contributing members on identical terms. The Social Security Code specifically includes above-ceiling employees when counting for those chapters. Individual membership, existing membership history and the operative wage ceiling are the next questions.

For example, a business should not omit its highly paid staff from the establishment count merely because payroll proposes no contribution for some first-time higher-paid joiners. Nor should it assume that reaching twenty means every individual’s pension eligibility is the same. Coverage, membership and contribution amount need separate columns.

This distinction is important after 2026 scheme changes. The current EPF Scheme and later ceiling notifications must be applied by date. A legacy exclusion declaration based on an old ceiling does not establish treatment for a current joining event. Avoid embedding a historical monetary threshold in the general workforce ledger; retain a dated legal parameter alongside the classification.

Count branches using the relevant legal unit

For EPF chapter purposes, the Social Security Code expressly treats departments and branches of an establishment, whether in the same or different places, as parts of the same establishment. Two offices with twelve people each cannot simply assume they remain outside the twenty-person test because each location is small.

Separate legal entities raise an additional factual question. Common ownership alone should not be treated as a universal aggregation formula, but separate registration numbers do not conclusively prevent aggregation where the true relationship establishes an integrated establishment. Management, financial links, control, workforce and functional dependence can matter.

Preserve an organisation chart, cost allocation, employee transfers, shared services and operating arrangements where this is a real issue. Earlier judicial aggregation decisions must be used in their statutory context. Do not copy an EPF conclusion into a branch-closure or state registration analysis without examining that law’s establishment test.

Treat trainees and apprentices carefully

A statutory apprentice is not simply anyone whose appointment letter says trainee. Retain the apprenticeship arrangement and evidence that the engagement is genuinely under the Apprentices Act. An ordinary trainee performing employment work for wages needs assessment under the relevant employee or worker definition.

A probationer is ordinarily a person whose employment is being assessed, not a person automatically absent from all labour counts. A fixed-term employee also does not disappear from the workforce because the contract has an expiry date. Keep the engagement category but do not confuse it with a blanket threshold exemption.

Different surviving laws can use broader definitions. The workplace sexual-harassment law expressly includes trainees and apprentices in its employee definition, alongside contract and temporary workers. Thus even a valid exclusion under a Labour Code employee definition cannot safely be exported to every other employment-law obligation.

Remote work is not absence from employment

A remote employee remains part of the employer’s workforce. Record the employing entity, assigned establishment, reporting line and work arrangement. The daily office-attendance figure is a facilities planning measure; it is not automatically the statutory establishment headcount.

Consider a hybrid office with thirty employees but only eight attending on a given day. A duty based on employees employed should not be tested solely using eight occupied desks. Likewise, splitting attendance across alternate weekdays does not itself divide one establishment into several independent workplaces.

The precise territorial consequences of a permanent remote arrangement need their own assessment. A worker’s home location may raise state-law questions, but it does not justify either ignoring the person or assuming every home is independently registered for all laws. Document the basis used and review it when a remote cohort becomes a functioning branch.

Preserve peak counts and look-back history

An any-day-in-twelve-months test can be triggered by a short peak. Keep dated joiners, exits, transfers and contractor overlaps rather than only month-end totals. A business with forty-eight contract workers which temporarily deploys another crew needs to examine whether the fifty-person threshold was crossed during the relevant period.

Use the actual statutory period. Some duties use the preceding twelve months; others use a current count, average, ordinary employment or a separately prescribed period. There is no general rule that every threshold must be exceeded for a full month or for 240 days. The familiar service-day figures used for particular benefits should not be imported into establishment coverage.

When evidence is incomplete, reconstruct it from attendance, bank payroll, access records, invoices, work orders and contribution records. Identify assumptions and gaps. A retrospectively invented attendance sheet is not a lawful solution. Preserve original records and explain any correction rather than overwriting them silently.

Do not switch off coverage after downsizing

Section 1(8) of the Social Security Code preserves chapter application after the establishment first becomes covered, even if employee numbers later fall below the First Schedule threshold. A current count below twenty or ten therefore does not, by itself, permit stopping compliance.

The Code contains distinct procedures concerning voluntarily covered establishments, with conditions and competent decisions. Those should not be confused with ordinary mandatory coverage followed by downsizing. Nor does a closure application resolve unpaid contributions or employee benefits automatically.

Maintain a coverage-history field showing the first trigger date and legal basis. When the business reorganises, review continuation, transfer, closure and historical liabilities before changing payroll configuration. An inactive portal account or lack of a recent demand is not evidence that statutory coverage ended.

Create a reviewable headcount register

Useful fields are person identifier, employer, branch, deployment site, function, engagement type, apprenticeship basis, wage category, start and end dates, transfers and documentary source. Add obligation-specific inclusion flags only after the legal mapping is approved. Keep the underlying population separate from the calculated result.

Reconcile the register monthly with HR, payroll, procurement and site operations. Procurement should report new agency deployments; HR should report transfers and remote changes; finance should identify labour-like vendor payments. Assign uncertain cases to a named reviewer with a resolution date and interim compliance decision.

assureOffice can sit within the practice’s surrounding financial and client workflow, but a universal headcount calculator should not be assumed. Information at assureoffice.in does not replace the relevant definition or determine a contested establishment boundary. The useful deliverable is a dated applicability sheet which another reviewer can reproduce from the records.

Frequently asked questions

1. Can two small branches always be counted separately?

No. EPF chapter provisions expressly aggregate an establishment’s departments and branches. Other duties need their own establishment test. Record the legal unit and factual relationship instead of treating separate addresses, payroll codes or registration numbers as universal proof of independent coverage.

2. Do managers count when benefits apply only to workers?

They may count for employee-based obligations while being outside a narrower worker definition. The result depends on the provision. Separate the coverage count from individual entitlement and retain job-function evidence where a managerial or supervisory classification affects the answer.

3. Are ordinary trainees the same as statutory apprentices?

No. A valid Apprentices Act engagement has a specific legal basis. A trainee label alone does not establish it. Obtain the relevant agreement and statutory records, and separately assess ordinary trainees performing employment work under the applicable employee or worker definition.

4. Does crossing a threshold for one day matter?

It can where the provision uses any day in the preceding twelve months. Preserve peak counts and deployment overlaps. Do not assume a full month of excess staffing is required or use a month-end payroll snapshot as the complete historical test.

5. Can a covered employer stop after downsizing?

Not merely because current numbers fall. The Social Security Code preserves chapter coverage after the first trigger. Examine the specific legal route for any proposed cessation, transfer or closure and settle historical obligations rather than disabling contributions based on a smaller current roster.

6. Do employees above the contribution ceiling count?

For EPF and ESI establishment coverage, the Social Security Code expressly includes employees above the wage ceiling. Their individual membership and contribution treatment are separate. Excluding all highly paid employees from the threshold count can wrongly conceal establishment coverage.

7. Should agency workers appear in our workforce register?

Yes, with the actual employer and deployment clearly recorded. They can be relevant to several coverage tests and direct establishment duties. Keeping them out because another entity runs payroll makes it harder to assess contract-labour thresholds, welfare and social-security responsibilities.

8. Does every service-provider employee count as contract labour?

Apply the statutory definition, including its specific exclusion conditions. Examine actual employment and work facts. A vendor contract or permanent appointment label does not establish the answer for every purpose; neither should all provider staff be classified without considering the provision concerned.

9. Are probationers excluded until confirmation?

Probation does not create a general exclusion from employment-law counts. Record the actual employment start and relevant terms. Apply any genuine statutory exception, but do not postpone coverage simply because HR has not yet issued a confirmation letter.

10. Do fixed-term employees count?

A fixed expiry date is not a blanket threshold exemption. Apply the employee or worker definition and the relevant count period. Keep fixed-term status for benefit and service analysis while including the person wherever the legal counting test requires it.

11. Should hybrid staff count only on office days?

Not where the duty concerns employees employed by the establishment. Daily attendance and employment headcount are different measures. Record the assigned establishment and actual employment, then examine any specific provision that genuinely uses a different counting basis.

12. Does every remote home become a separate establishment?

No universal conclusion follows. Assess employing entity, assigned establishment and territorial facts for the particular law. A permanent operating branch and an individual home-working arrangement may raise different issues. Document the basis rather than either ignoring remote staff or multiplying registrations automatically.

13. Can a consultant invoice prove non-employee status?

No. The actual relationship matters where classification is disputed. Review terms, control, integration and work arrangements with appropriate advice. Do not decide the relationship solely to obtain a preferred headcount result or rely on a tax invoice as conclusive employment evidence.

14. Should everyone be counted using the same twelve-month period?

No. Use the period stated for the duty: current employment, any day, average or another prescribed basis. The preceding-twelve-month test is important for several provisions but is not universal. Keep dated source data so different tests can be calculated accurately.

15. Can payroll totals be used as the only source?

No. Payroll may omit agency staff, some absent employees and disputed engagements. Reconcile HR records with procurement, attendance and contribution evidence. The underlying population should be broader than a single payment run before legal inclusions and exclusions are applied.

16. Do apprentices count under workplace sexual-harassment law?

Its employee definition expressly includes apprentices and trainees. This illustrates why a Code-specific exclusion cannot be exported to every surviving statute. Maintain a separate applicability assessment for the Internal Committee and other workplace obligations under that law.

17. Can separate group companies always avoid aggregation?

Separate personality is relevant but not necessarily conclusive. Examine the true operational relationship where integration is alleged. Common management, finance, workforce and functional links can matter under the relevant legal test. Avoid both automatic group-wide aggregation and automatic separation.

18. What should happen when old records are missing?

Reconstruct the history from reliable contemporaneous sources and disclose gaps. Preserve originals, methodology and reviewer decisions. Do not invent attendance or service records. A transparent reconstruction is more defensible than an unexplained retrospective spreadsheet presented as the original register.

19. When should headcount mapping be reviewed?

Review it after new branches, acquisitions, contractor deployments, remote-work changes or substantial hiring and exits. Reconcile routinely with payroll and procurement. Keep the first coverage date and earlier versions so future reviewers can understand why obligations continued after numbers fell.

20. Can assureOffice give one universal threshold number?

No such universal legal number exists. assureOffice can be considered within the wider practice workflow, while the headcount assessment remains obligation-specific. The useful record identifies the definition, counting unit, period, evidence and conclusion for each statutory duty.