Labour Law
<p>Most employment contracts in South Africa contain some version of this line:</p><p>"The employee agrees to be bound by the company's policies, procedures and disciplinary code, which form part of this agreement."</p><p>It reads like standard boilerplate. Nobody thinks twice about it. But that single sentence can quietly change the legal status of every policy document in your business, and a string of recent Labour Court judgments shows exactly how that plays out when it goes wrong.</p><p>A quick note on scope: this isn't about whether your workplace rules are clear, reasonable or fairly enforced; we've covered that ground before in "Why Workplace Rules Matter: Building a Culture of Discipline and Fairness." This is specifically about what happens, legally, the moment those rules get written into the employment contract itself.</p><p>To be clear from the outset: this isn't an argument that policies can never form part of a contract. Sometimes an employer wants that: certain roles, certain sensitive procedures, certain regulatory requirements genuinely call for it. This is an argument that doing it by accident, through a throwaway clause nobody thought through, creates risk most employers never intended to take on.</p><h2><strong>The Legal Problem in One Sentence</strong></h2><p>An employment contract is a negotiated agreement. Once a term is contractual, it can only be changed with the other party's agreement, not unilaterally, no matter how reasonable the change seems to you as the employer.</p><p>Company policies, by contrast, are meant to be operational tools. You update your leave policy when the law changes. You tighten your IT policy when a new risk emerges. You revise your disciplinary code when a gap becomes obvious. None of that should require re-negotiating every employee's contract.</p><p>If your contract expressly says the disciplinary code (or any other policy) forms part of it, you've converted an operational document into a contractual one, and every future amendment to that policy is now, technically, a contractual amendment requiring the employee's agreement.</p><h2>What the Courts Have Actually Said</h2><h3>Sedumedi v Sefako Makgatho Health Sciences University (2025)</h3><p>This case turned on whether the university's HR policies were incorporated into a fixed-term contract. The Labour Court was clear that referring to a policy, or requiring compliance with it, isn't enough on its own. Incorporation has to be clear and unequivocal: vague references to "conditions of service" or similar language don't cut it. If an employer wants a document to be a binding contractual term, the contract has to say so, precisely.</p><p>The lesson: ambiguity doesn't protect you either way. If you didn't mean to make a policy contractual, a vague clause can still be argued into being one. Precision matters in both directions.</p><h3>Mpembe v University of Zululand (2025)</h3><p>Here the opposite scenario played out. The University's disciplinary code was clearly incorporated into the employee's contract. Partway through a serious misconduct hearing, the University tried to switch from a full hearing (oral evidence, cross-examination) to a "paper hearing": written submissions only, decided without a hearing.</p><p>The Labour Court intervened urgently. Because the disciplinary code was a contractual term, the employee had a contractual right to have the process run exactly as the code described. The University couldn't unilaterally streamline it, however sensible that seemed to management at the time. The Court treated this squarely as a contract dispute, not just a labour-law fairness question, which is a different, and in some ways less forgiving, legal lens.</p><p>The lesson: if you've made your disciplinary code contractual, you don't just have to run a fair process; you have to run the exact process the code describes, to the letter, or you're in breach of contract.</p><h3>NUMSA and Others v Denel SOC Ltd (2026)</h3><p>NUMSA, acting for two employees, brought an urgent application arguing that Denel's disciplinary code (again, incorporated into the employment contract) prohibited the employer from appointing an external chairperson and an external initiator to a disciplinary hearing.</p><p>The Labour Court disagreed. The code didn't actually contain any clause prohibiting external appointments, so there was no contractual term to breach. The application failed.</p><p>On the surface, Denel "won." But look at what it cost to get there: an urgent Labour Court application, legal representation on both sides, and a judgment turning on a fine-grained reading of clause wording, all because two employees believed, reasonably, that a contractual disciplinary code gave them standing to challenge a procedural decision in court rather than through the ordinary CCMA unfair-labour-practice route.</p><p>The lesson: even when the employer ultimately wins, a contractual disciplinary code hands employees a different, additional legal avenue (a breach-of-contract claim) on top of the usual unfair dismissal or unfair labour practice routes. That's added exposure, added cost, and added uncertainty, regardless of who wins any individual round.</p><h2>Putting the Three Together</h2><p>None of these cases says policies are dangerous. They say unclear intentions about policies are dangerous:</p><p>Sedumedi shows that half-hearted incorporation language creates fights over whether a policy is contractual at all.</p><p>Mpembe shows what happens once it clearly is contractual: you're locked into following it precisely, with no room for operational judgment calls.</p><p>Denel shows that even a technical win still means an urgent court application and legal spend that a non-contractual code would likely have avoided.</p><h2>The Practical Fix</h2><p>Instead of language like this:</p><p>"The disciplinary code, policies and procedures form part of this contract."</p><p>Consider this instead:</p><p>"The employee agrees to comply with the employer's policies, procedures, rules and disciplinary code, as amended from time to time. These policies regulate the employment relationship but do not form part of the employee's contract of employment unless expressly stated otherwise."</p><p>This version does two things at once. It still obliges the employee to follow your policies, so you retain a disciplinary basis to act if they don't. But it keeps the policies themselves outside the contract, meaning you can update, tighten, or restructure them as your business needs change, without needing every employee's individual sign-off.</p><p>If there's a specific policy you genuinely want to be contractually binding, such as a restraint of trade, a confidentiality undertaking, or a specific notice period, do that deliberately and explicitly for that one document. Don't let it happen by default because of a catch-all clause drafted years ago and never revisited.</p><h2>Conclusion</h2><p>Whether your policies belong inside or outside the employment contract isn't a question with one right answer. It is, however, a question every employer should be answering on purpose. If you're not sure what your current contracts say, that's the first thing to check, not the disciplinary code itself, but the one or two lines in your standard employment contract that describe how policies relate to it. It's a five-minute read that can save a great deal of legal exposure later.</p>