• rradar

Restrictive Covenants (Prophet plc v Christopher Huggett [2014])


Ensuring that an employee doesn’t leave your company and take valuable information straight to a competitor has often been the reason behind restrictive covenants. Have you got the expertise to accurately draft one? Check out our article on what happened to one company who made a mistake in the wording.


If an employee leaves a business and goes to work for a competitor, they may be able to use information that they have acquired in the course of their job to assist their new employer and damage the business of their former employer.


Employers have sought to protect themselves against such eventualities by employing what are known as restrictive covenants. These are clauses in a contract which prohibit an employee from taking part in activity that competes with the former employer for a defined period after the employee has left the business. Such clauses are also used to stop former employees from using privileged knowledge of customers or clients against the interests of their former employer.


These clauses are often included in the contracts of senior or highly skilled staff at the commencement of their employment. Employers may hope that by doing so, they will deter employees from joining competitors or prevent approaches to their employees from other companies.


Such post-termination restrictions are often viewed as void on the grounds that they are unreasonable and a restraint of trade. However, if the former employer can make a good case that the covenant is:


  • designed to protect legitimate business interests; and

  • that it goes only as far as is reasonably necessary to protect those interests then it is likely that it will be upheld.


However, one thing that employers need to be aware of is the wording of the restrictive covenant itself. They may find that, regardless of their intention, the way that the covenant is phrased renders it to all intents and purposes meaningless. This is what happened in the case of Prophet plc v Christopher Huggett [2014]


Prophet plc was a company that developed computer software for the fresh produce industry. Mr Huggett had been taken on as a sales manager for Prophet and his contract included post-termination restrictions. Clause 19 of his contract contained the following:

‘The Employee shall not…for a period of twelve months …without the consent in writing of the Board of Directors of the Company…carry on or be engaged, concerned or interested in any business which is similar to, or competes with, any business of the Company in which the Employee shall have worked…within the geographical area (namely the United Kingdom)…Provided that this restriction shall only operate to prevent the Employee from being so engaged, employed, concerned or interested in any area and in connection with any products in, or on, which he/she was involved whilst employed hereunder.’

Had the first sentence been left as it was, it would have been deemed unenforceable as an unreasonable restraint of trade. To qualify it and avoid this, the second sentence was added.

In December 2013, when Huggett gave notice that he was leaving Prophet and it was discovered that his new employer was a competitor, Prophet wheeled out the restrictive covenant. It was at this point that they discovered the covenant had been worded in such a way that, if taken literally, it would have had no effect. The clause only applied to ‘any products in, or on, which he/she was involved whilst employed hereunder’, namely products developed and sold by Prophet.


Whilst Huggett’s new employer, K3 Business Solutions, was involved in developing software for use in the same sector as Prophet, that software was its own, not Prophet’s and would therefore not be covered by Clause 19’s second sentence. Even Prophet’s own Counsel was forced to admit this.


The judge said that since taking the clause literally would render it meaningless, “something had gone wrong in the drafting”. Based on this conclusion, he sought the input of Counsel for both parties to determine what the wording should have said, and then carried out a correction by adding the words “or similar thereto” to the end of the clause. Subject to this correction, he was prepared to grant Prophet’s injunction application. Huggett took his case to the Court of Appeal.


The Court of Appeal considered that the judge’s actions in the first instance were incorrect.


The courts should not take it upon themselves to re-write a covenant between two parties.


Prophet should have looked more closely at the wording of its clause to consider whether it would be likely to prove useful if Huggett were to join a competitor.


Although generally speaking, a court should, when presented with ambiguous clauses, seek to provide a commercially sensible solution, the Court of Appeal did not consider that this was an ambiguous clause. To quote Lord Justice Rimer:

“If the parties’ chosen words result in a restriction of limited, or even no, effect, the explanation may be that…the employer has simply made a bad bargain. The court should be wary about mending such a bargain so as to improve it.” He went on to say “It was not for the judge nor is it for this court to re-make the parties’ Clause 19 bargain. Prophet made its Clause 19 bed and it must now lie upon it.”

How does this affect employers? Since it is clear that courts will not alter the wording of a restrictive covenant where the meaning of the words used is clear, even if it does not make logical sense, employers should carefully consider the phrasing of such restrictive covenants to ensure that they make sense and achieve what they are intended to achieve. If in doubt, they should obtain legal advice.


How rradar can help:


For more information about our legal services and how rradar can help your business, please visit our website and speak to our professionals today for free.


To keep up to date with current legal news and rradar services, please follow us on Twitter and Linkedin.