Punjab Labour Code 2026: Ten Changes That Turn HR ...

Summary

• Appointment letters, job descriptions, salary structures, HR policies and actual working arrangements will need to speak the same language.
• HR, Procurement, Operations, Finance and Legal will all need visibility over who is working through third parties, what they are doing, for how long, and who is actually controlling their work.
• For HR and Legal, the impact is straightforward: restrictive covenants will need to be drafted around what genuinely requires protection rather than a standard prohibition on working for a competitor.

AI Generated Summary

By Harris Jamil Alam khan

For a long time, HR and Legal in many organisations have worked in sequence rather than together. HR recruits, manages, evaluates and disciplines employees. Legal usually enters the picture later, when a termination is challenged, a notice is received, a grievance escalates or management wants to know whether a decision already taken can be defended. The Punjab Labour Code 2026 begins to change that sequence. Enacted as Act IX of 2026 on 10 February 2026, it brings more than two dozen pieces of labour legislation into a single framework, but consolidation is only part of the story. The more important question for employers is what has actually changed underneath it.

Having spent a considerable part of my professional life in HR across education, the public sector and institutional environments in Pakistan, before moving further into legal and corporate governance work, I find many of the issues addressed by the Code immediately recognisable. Employment structures on the ground are rarely as neat as the documents describing them. A position can be temporary on paper and permanent in every practical sense. An outsourced worker can spend years inside an organisation and report to its managers. A consultant may gradually begin to look indistinguishable from an employee. Policies can be comprehensive while the reasons behind a promotion, increment, disciplinary action or termination are recorded far less carefully. These practices do not always arise from deliberate avoidance of the law. Often, they develop through operational convenience, budget constraints, historical practices or simply because “this is how we have always done it”. The Code now forces HR to look again at several of those arrangements.

Ten changes, in particular, stand out from an HR and legal perspective.

Traditional “workman” interpretation has changed. The Code applies across sectors and adopts a considerably broader conception of the workforce. Its definition of “worker” encompasses employees, contractors, subcontractors, agency workers, self-employed persons, apprentices, interns, casual and temporary workers and digital platform workers. Managerial, administrative and professional work is also expressly contemplated within the statutory framework, although individual Parts of the Code retain their own applicability rules. For HR, the impact is significant. The old assumption that seniority, professional status or the particular label attached to a person necessarily places them outside labour legislation becomes much less safe. Workforce mapping will have to go beyond the conventional employee headcount and consider who is actually working in and around the organisation.

The title of the agreement no longer dictates the relationship with the employer. Section 132 of the Code provides that employment status is to be determined primarily by the facts relating to the performance of work and remuneration, notwithstanding the way the parties may have characterised the arrangement. It looks towards matters such as control, whether the work falls within the ordinary course of the business and whether the person is genuinely operating an independently established trade or business. Section 133 goes further by addressing deliberate misclassification. This is one of the most important changes for both HR and Legal because changing the heading from “Employment Agreement” to “Consultancy Agreement” does not necessarily change what is happening underneath it. The practical exercise for employers will therefore be to review consultants, retainers, freelancers and other non-standard arrangements against the reality of how those people actually work.

An end to endlessly temporary contracts for permanent positions. Anyone who has spent sufficient time in HR in Pakistan will recognise the employee who has been “temporary” for four or five years. The contract expires, another one is issued, the dates change and perhaps the salary changes, but the role remains exactly where it was. The person is temporary; the job is not. The Code now makes permanent employment the default and requires an objective reason for fixed-term employment. It expressly provides that fixed-term agreements cannot be used for work of a permanent nature and can be deemed permanent where they are used on a lasting basis for positions connected with core operations. General fixed-term arrangements are limited to specified temporary circumstances, with a three-month maximum and a cumulative nine-month limit for successive general fixed-term agreements, while special-project contracts are separately regulated and subject to their own conditions. For HR, manpower planning and contracting can no longer be treated as separate exercises. If the organogram, annual budget and operational requirement all show that a position is permanent, the organisation should be able to explain why the employment is not.