Halse & Anor v Hamilton City Council

This case started with a workplace dispute that had already been settled. For many businesses, that sounds like the end of the story. But the Court’s decision shows that a settlement can keep operating long after the original employment relationship has ended.

In 2014, Mr Halse and Hamilton City Council resolved an employment relationship problem at mediation. The outcome was recorded in a formal record of settlement certified by an MBIE mediator. The settlement included confidentiality obligations and a mutual promise that neither side would make disparaging comments about the other party or Council employees.

Years later, Mr Halse had founded CultureSafe NZ Ltd and was providing advocacy services in employment matters. In 2020, CultureSafe began acting for a Council employee. Around that time, Mr Halse published a series of Facebook posts on CultureSafe’s page that were highly critical of the Council and its chief executive.

The Council said those posts breached the 2014 settlement. It wrote asking for the first post to be removed. It was not removed. Another post followed, then more posts in January 2021, making 13 in total. The Council then took enforcement action in the Employment Relations Authority.

That is what makes this case useful for business owners. It is not just about an old employment dispute. It is about what happens when a settlement is later tested by public commentary, especially on social media.

The legal fight was not really about whether the posts existed. Before the Authority, Mr Halse and CultureSafe did not deny their involvement in publishing them. The real questions were about whether the settlement could still be enforced, what the clauses actually covered, and whether public criticism changed the result.

Mr Halse argued that the settlement had become unenforceable after six years. He also argued that the alleged breaches had to relate to an employment relationship problem involving the parties, that there was no breach of the confidentiality clause, and that freedom of expression protected what he said.

The Court therefore had to work through several linked issues. First, when does time start running for enforcement of a mediated record of settlement: when the settlement is signed, or when the later breach happens? Secondly, did the posts go beyond the agreed confidentiality position? Thirdly, how broad was the non-disparagement clause when read in context?

That context point matters for ordinary businesses. A clause may look broad on paper, but courts still read settlement wording against the background in which it was agreed. So a business should not assume a non-disparagement clause is a blanket ban on every future criticism in every setting. At the same time, a person who signed the clause should not assume they can later revisit the settled dispute publicly just because they are speaking in another role or because time has passed.

The Court rejected the argument that the settlement had simply expired six years after it was signed. It said a mediated record of settlement is not just an ordinary contract. It has a statutory basis and is enforceable under the Employment Relations Act. The key timing point was that the cause of action arose when the alleged breach happened, not when the settlement was entered into.

That meant the Council’s proceedings about the 2020 and 2021 Facebook posts were filed in time. For business owners, that is an important practical point. A settlement may sit quietly for years, but if someone later acts in a way that breaches it, enforcement can still become live again.

The Court also rejected the argument that the alleged breaches somehow fell outside the original employment relationship problem. The settlement existed because of that employment dispute, and alleged breaches of the settlement still related back to it.

On confidentiality, the Court found that several posts breached the clause because the settlement said the only statement to be made outside mediation was that all matters had been resolved between the parties. Posts that referred to Mr Halse’s dismissal, the alleged reasons for it, or the settlement itself went beyond that agreed limit.

On non-disparagement, the Court found that all 13 posts were disparaging of the Council. But it did not accept the broadest possible reading of the clause. Instead, it interpreted the clause in context. The Court said comments on entirely different topics would not necessarily be caught. Even so, the actual posts before the Court were still tied closely enough to the settled employment dispute to fall within the clause.

For a small business, the practical lesson is not about councils in particular. It is about what happens after a workplace dispute has supposedly been put to bed. Many employers focus heavily on getting the settlement signed, paying the agreed amount and moving on. This case shows that the settlement can remain a live operational document long after the payment is made.

The first lesson is about time. A settlement does not become irrelevant just because years have passed. If someone later says or publishes something that breaches the settlement, the enforcement clock can start from that later conduct. That matters for businesses that keep old settlement files in storage and assume they will never matter again.

The second lesson is about communication channels. Social media is not informal in the eyes of the Court. A Facebook post can be treated as a serious public act, especially where it repeats allegations, refers to the settlement, or attacks the other party in a way the settlement was designed to stop. The same risk can arise with LinkedIn posts, business pages, online comments, newsletters or public statements by founders and managers.

The third lesson is about context. The Court did not read the non-disparagement clause as banning every possible criticism forever. That is useful because it shows courts will try to read these clauses sensibly. But that sensible reading did not help Mr Halse on the facts. The posts were still connected closely enough to the settled employment dispute to be caught.

In practice, businesses should read this case as a reminder that settlement obligations are not just legal drafting points. They affect day-to-day behaviour, especially when emotions are still running high and someone wants to respond publicly.

If your business settles an employment dispute, treat the settlement as part of your ongoing risk management. The people most likely to create problems later are often not lawyers. They are founders, directors, HR managers, line managers and anyone who handles public communications.

A practical starting point is to identify what the settlement actually says about confidentiality, public statements and non-disparagement. Then work out who inside the business needs to know. If the business has a communications lead, they should know that a former employee dispute may still be subject to restrictions. If the founder personally uses social media for business commentary, they should know where the boundaries are too.

It is also worth thinking about future scenarios before they happen. For example, what if a former employee posts criticism online? What if another worker raises related allegations? What if a manager wants to defend the business publicly? This case suggests the safest approach is to pause and check the settlement before responding.

A business may still be able to use proper internal, legal or regulatory channels where needed, but public commentary can create avoidable exposure if it strays into the territory the settlement was meant to close off. The Court’s reasoning shows that the line is not just about whether a statement is negative. It is also about whether the statement revives the dispute, refers to settlement-related matters, or publicly says the kind of thing the parties agreed not to say.

This decision also contains a useful drafting lesson. The Court found the non-disparagement clause enforceable, but it still interpreted the clause in context rather than giving it the widest imaginable reach. That is a reminder that broad wording alone does not solve every future problem.

If the wording is too blunt, parties may later argue about whether it covers unrelated criticism, ordinary customer complaints, civic participation or comments made in another role. The Court’s approach suggests that settlement wording will be read against the employment dispute it was designed to resolve.

For businesses, the better approach is to be clear at settlement stage about what the clause is trying to achieve. If the real concern is public commentary about the employment dispute, the wording should reflect that purpose. If the parties want a simple external line, such as confirming that matters have been resolved, that should be stated clearly and then followed in practice.

This case also shows why businesses should think beyond the legal team. A carefully drafted settlement can still fail in practice if the people speaking for the business do not know what it says. Drafting and implementation need to work together. The settlement should be understandable, realistic and capable of being followed in day-to-day communications, especially where a dispute may still attract attention later.