Worker or Employee: What Actually Changes in Your Week?

Industrial Relations Code protections for workers apply in addition to the protections applicable to employees. Grievance redressal under section 4 of that Code, and retrenchment notice and compensation under section 70, apply to workers. The employee protections apply to everyone employed for wages. Section 2(k) of the Code on Wages, 2019 defines an employee as a person, other than an apprentice engaged under the Apprentices Act, 1961, employed on wages by an establishment to do skilled, semi-skilled, unskilled, manual, operational, supervisory, managerial, administrative, technical or clerical work, and it excludes members of the Armed Forces. Supervisory, managerial and administrative work is included in the employee definition and excluded from the worker definition. Payment on time, equal pay for equal work, and the applicable social-security protections therefore apply to the whole payroll. Those employee protections apply whether the person manages a shift or a business unit. The worker protections apply in addition and have a narrower scope because they protect people whose terms are set for them rather than negotiated. For an employer, the main difference between a worker and an employee is which duties apply to that person under the relevant definition.

Every listed duty applies to a worker. Employers get that column wrong, because a table built on the statutory noun looks as though a duty applicable to "employees" excludes workers. It does not. Within each Code the worker's work-list is contained within the employee's: section 2(z) of the Code on Wages covers manual, unskilled, skilled, technical, operational, clerical and supervisory work, and section 2(k) covers all of those plus managerial and administrative work. So a clerk is a worker and an employee at once, and the minimum rate, the wage slip and equal pay are owed to them on the employee footing.

The second column identifies the differences. A duty applicable to employees applies to a manager; a worker-specific duty does not. Employee rights and obligations therefore apply first, and the additional rights and obligations attached to worker status apply concurrently.

The table contains one easily missed distinction. Annual leave and overtime under the OSH Code apply to workers, which surprises employers who assume leave is universal. A manager's leave comes from the contract and company policy, not from section 32, and that difference determines entitlement to encashment on exit.

For apprentices under the OSH Code, the worker definition is broader than the employee definition. Section 2(1)(t) of the OSH Code defines an employee as a person "other than an apprentice engaged under the Apprentices Act, 1961". Section 2(1)(zzl) defines a worker with no apprentice exclusion at all. So an apprentice on your site is a worker and not an employee under that Code: annual leave and overtime apply to them, and the appointment-letter duty in section 6 does not. The Code on Wages and the Industrial Relations Code exclude an apprentice from both definitions, so the asymmetry is the OSH Code's alone.

The re-skilling fund contribution has a separate deadline. Section 83(2)(a) makes the employer's contribution an amount equal to fifteen days' wages last drawn by the worker, for every retrenched worker and in the case of retrenchment only, and section 83(3) has it credited to that worker's account within forty-five days.

Rule 37 of the Industrial Relations (Central) Rules, 2026 prescribes the employer’s transfer deadline. Under rule 37(1) an employer who has retrenched a worker must, within ten days from the date of the retrenchment, electronically transfer fifteen days of the worker's last drawn wages into the fund, whose account name is displayed on the websites of the Ministry of Labour and Employment and the Chief Labour Commissioner (Central). Rule 37(3) prescribes a second obligation: submit a list naming the retrenched worker, the amount and the worker's bank account details to the Chief Labour Commissioner (Central) or the Deputy, Regional or Assistant Labour Commissioner. Rule 37(2) then has that office credit the worker within forty-five days.

Ten days is the shortest of the deadlines set out above, and it runs from the retrenchment rather than from the final settlement. An employer who treats the re-skilling contribution as an annual levy, or as a duty still pending a scheme, misses it on the first retrenchment. The four Codes have been in force since 21 November 2025, and a State may notify its own rules on any of this, so check the sphere before you apply a Central figure. The wording differs Code by Code, so the definition you apply is the one inside the Code that contains the provision. The applicable definition determines the resulting duties.

Why worker status matters is easiest to see in one row. A person recorded as a manager has no access to the Grievance Redressal Committee, is excluded from the twenty-worker count that requires it, and is not protected by section 70 if you later end their employment. All three consequences result from one classification.

Most Labour Code thresholds count workers, not total employees, so worker classification determines the number. The four types of workers a threshold might count are not interchangeable. Section 4 of the Industrial Relations Code requires an industrial establishment employing twenty or more workers to constitute one or more Grievance Redressal Committees, and the twenty is a worker count. Your HR system counts people. The Code counts workers in the establishment, and that count excludes staff employed mainly in managerial or administrative work, and supervisors paid above the notified figure. Those two numbers change differently when someone is promoted.

Ritu manages HR at a 140-person software firm in Pune. Her system shows 140 employees, and she had assumed the worker count was around 18, because she was thinking of facilities and support staff. The reconciliation produces a much larger worker count.

Her worker count is 119, not 18, and her establishment had exceeded the twenty-worker threshold for six years without a Grievance Redressal Committee. The figures are illustrative, but the pattern is the point: a clerical or technical majority means the worker count is usually close to the payroll total rather than the supervisor count.

Two habits keep that number defensible. Store it as its own dated field in the HR system, separate from the headcount the payroll module reports, with the reason recorded against each exclusion. A number you cannot reconstruct cannot support the decision that followed it, and a committee formed or not formed on an unreconstructable number is the decision most likely to be questioned.

Recount at four moments: after every promotion round, after every restructure, when a wage crosses a supervisory figure, and when a notification changes one of the figures. For each recount, record a dated entry with the count, the exclusions applied and the person who applied them. The recount itself takes an hour; reconstructing a count from two years ago takes a week, and usually ends in an estimate. Keep contractor-supplied people in a separate count. How they are treated is settled by the contract-labour rules, which limit what you may outsource, and folding them into your own worker count corrupts both numbers at once: it inflates the count that makes your committees mandatory, and it obscures the count that determines the contractor's licence requirement.

The difference between the employee count and worker count also depends on the proportion of managers. A firm whose staff are mostly technical, clerical or operational finds that nearly everyone counts, which is why Ritu's count was 119 rather than 18. A firm with many managers has a wider gap. Neither pattern is unusual, and neither can be guessed: the count must be calculated group by group, which is why it belongs in the system rather than in someone's head. The other threshold values, including the Works Committee and standing-orders numbers, are fixed by the Industrial Relations Code, 2020, Chapter IX governs lay-off, retrenchment and closure, and Chapter X contains the special provisions that begin at section 77 and start at three hundred workers; apply the relevant lay-off, retrenchment and closure requirements according to the worker count.

A promotion changes status only when both parts of the supervisory test are satisfied: the person is employed in a supervisory capacity, and the wages cross the figure. Section 2(zr)(iv) of the Industrial Relations Code and section 2(1)(zzl)(iv) of the OSH Code both use eighteen thousand rupees a month; section 2(z)(d) of the Code on Wages uses fifteen thousand. Nothing has been notified under any of the three, so all three figures stand as enacted, and each power is worded to notify an amount rather than only to raise one.

Naveen leads a four-person shift on ₹24,000 a month in wages, an illustrative figure. His wages exceed the threshold of the Industrial Relations Code test. Whether he is employed mainly in a supervisory capacity is the open question, and both parts have to be true before the worker definition excludes him. If he still spends most of his day on operational work, the supervisor label will not survive a challenge.

"Mainly" is a question about time and substance rather than about title, and it is answered from the same evidence in both directions. A shift lead who runs the line for six hours and allocates work for two is not mainly supervising. A person who allocates, approves and reviews for most of the day is, whatever the designation says. Rosters, approval logs and system permissions answer that question better than a job description written at the point of hiring, because they record what happened rather than what was intended.

The supervisory test applies only to work performed in a supervisory capacity. It removes a person employed in a supervisory capacity who draws wages above the figure. It says nothing about a person who is not employed in a supervisory capacity at all, whatever they earn, which is why a senior technician on a high wage who supervises nobody remains a worker.

Status changes when the duties change, not when the letter is signed. Accordingly, you cannot backdate a status change to the letter, and you cannot postpone one because the paperwork lagged.

The wage figure to test against is the statutory one, and CTC, gross pay and take-home appear nowhere in any of the four Codes. Each Code measures against its own wage definition, so a computation made for one Code cannot automatically be used for another. The same analysis applies to the reverse case: a demotion, or a return to operational work, brings the person within the worker definition, and the same evidence is required even though the change favours the employee. To know whether a given role is a worker, classify it role by role against each Code's own definition.

How you classify employees is tested only when something goes wrong. Misclassification surfaces as a dispute or an inspection question, months after a designation changed and the duties record did not. The cost is rarely a single fine. Skip a notice period for someone who was in fact a worker and the retrenchment is defective, because section 70 of the Industrial Relations Code sets conditions precedent that have to be met before a worker in continuous service for not less than one year is retrenched.

Section 70 sets three conditions, and most summaries give two. First, one month's notice in writing indicating the reasons for retrenchment, with the notice period expired, or wages for the notice period paid in lieu. Second, compensation at the time of retrenchment equal to fifteen days' average pay, or the average pay of such days as the appropriate Government notifies, for every completed year of continuous service or any part of a year in excess of six months. Third, notice served on the appropriate Government, or on the authority it specifies, in the prescribed manner. The third is the one that disappears from checklists.

Kavita is titled "Assistant Manager, Warehouse Operations" on ₹32,000 a month, with no hiring, disciplinary or spending authority: a manager in the HR system, a worker in practice. The incorrect record excluded her from grievance-committee access, the worker count and section 70 protection. The reverse error is cheaper. A manager treated as a worker costs avoidable process and an internal precedent, not a defective termination. It is still worth correcting, because the next person may rely on that internal precedent, and because a count inflated by people who do not belong in it will eventually make a duty applicable that you did not owe.

The pattern under all seven rows is the same: the designation changed without corresponding evidence of changed duties. That is why the first check in every row is a data question rather than a legal one. You are not looking for a wrong opinion about the law. You are looking for a gap between what a record says a person does and what the rosters, approvals and permissions show they did.

Start with the people the HR system retitled in the last year, and check each one's duties against the designation. The claim procedure and employer liability are governed by the Code on Wages, 2019, separately from the section 70 entitlement.

Remediation starts before the next payroll run or notice: fix the duties entry, repeat the affected Code tests, then act. Do not begin with a re-labelling exercise across the whole company. Begin with the decision actually in front of you, because a grievance, a notice, a threshold count and a benefit each have their own test and their own date. Write down what the person did during the period in question, using evidence you could hand to someone else. Then apply the test, note the date you applied it, and correct the current record.

Obtain legal review in three situations before reversing an earlier decision.

A live industrial dispute, because a classification changed while a dispute is running becomes evidence in it, and the change will be read as an admission whether or not it was meant as one.

An adverse action already taken on the wrong basis, such as a notice served on someone who was in fact a worker. Section 70 sets conditions precedent, so the question is not whether the notice period was generous but whether the three conditions were met before the retrenchment took effect.

Review any threshold that may have been crossed in an earlier period, because the resulting duty, such as constituting a Grievance Redressal Committee, applied from that earlier date rather than from the date it was identified. Maintaining the existing compliance position while that review remains pending is usually safer than a unilateral correction that changes a served notice.

Where contract labour is involved, the principal employer's position is decided separately again, on who supervises the work day to day and who actually pays, and not on the classification in your own HR system.

Limitation periods and penalties depend on the applicable claim procedure, not classification alone. For unpaid wages, apply the wage-claim procedure and the rules of the appropriate Government.

Four common engagements require separate analysis from the worker-or-employee question as per the new Labour Code, and each has an answer of its own. A fixed-term employee is entitled to gratuity on a pro-rata basis when the fixed term expires after one year of continuous service under that contract, and the trigger is expiry of the term rather than resignation. Contract labour comes through a contractor, so duties may apply to both of you, and licensing requirements determine what may be outsourced. An apprentice engaged under the Apprentices Act, 1961 is outside the employee definition in the Code on Wages and outside the worker definition in the Industrial Relations Code. Gig and platform workers are separate statutory categories rather than industrial-relations workers.

The apprentice exclusion differs between Codes. The exclusion appears in the Code on Wages and the Industrial Relations Code. No apprentice exclusion appears in the OSH Code's worker definition at section 2(1)(zzl), though its employee definition at section 2(1)(t) has one. So an apprentice excluded from two definitions is not thereby excluded from the third, and the four categories require four separate engagement analyses.

The Code on Social Security defines its own categories rather than borrowing the industrial-relations one. Section 2(26) sets its own employee definition with chapter-specific provisos, and sections 2(35), 2(61) and 2(86) separately define a gig worker, a platform worker and an unorganised worker. Provident-fund and state-insurance coverage is determined under those definitions and their notified ceilings, which is why a manager outside the worker definition can still be covered by provident fund and State insurance and by the Social Security Code's own chapters. Before the next contract renewal, check which of the four you are actually engaging, because the label on the contract does not determine the duty. The same employer is bound by all four Labour Codes, and each Code applies according to the nature of the engagement rather than its label.