Skip to main content

The BUSKLAW July Newsletter: Horsing Around with Non-Compete Clauses

Non-compete provisions are part and parcel of many employment agreements. But these provisions must be carefully drafted to be enforceable. There are three sure-fire ways to have a court invalidate your non-compete clause without much judicial cogitation:
  1. Failure to provide a reasonable duration for the clause;
  2. Failure to restrict the operation of the clause to a reasonable geographic area; and
  3. Failure to establish a protectable business interest as the subject of the clause.
The first point is easy to grasp. In Michigan, you are on solid legal ground if the duration of your non-compete clause doesn't exceed one year. And you are probably okay if you add a year to that. But you're walking on quicksand if your non-compete provision lasts longer than two years. 

The second point is a bit more complicated. Courts don't like to enforce a non-compete clause if its geographical scope is too wide. For example, if I'm in the packaged ice business and sell my product mostly to retailers in West Michigan, a court probably won't enforce a non-compete agreement that covers the central or eastern side of the State.  

One drafter of a non-compete clause - by accident or design - tried to avoid this issue by not mentioning a geographical area at all. Perhaps they hoped that the clause wouldn't be litigated or if it was, that the court would helpfully insert a reasonable geographic area covered by the clause. That was the issue in a recent federal court case in Pennsylvania, Catalyst Outdoor Advertising, LLC v Jennifer Douglas. Ms. Douglas signed a non-compete agreement with Catalyst, a seller of billboard advertising, but the agreement didn't specify a geographical area for the restriction. She went to work for another billboard advertiser, City Outdoor, and Catalyst sued to enforce the non-compete. The Court found that the non-compete clause wasn't enforceable because not only did it fail to specify a geographic area, but also City Outdoor and Catalyst didn't operate in the same (or overlapping) territory so they weren't actually competitors. And the Court further noted (cue sad trombone) that it wasn't in the business of revising contracts to make them enforceable.  

The third point - the requirement for a protectable business interest - sounds complicated, but it isn't, as illustrated in a recent Tennessee Court of Appeals case: Sugar Creek Carriages v Hat Creek Carriages. (The quaint name arises from the fact that both parties offer horse-drawn carriage rides to customers in downtown Nashville.) Lester Blackwell signed a non-compete agreement with Sugar Creek that was okay from a duration and geographical area viewpoint. But what the agreement sought to protect was a problem - the carriage-driving expertise that Sugar Creek taught to Lester that he later used in driving for Hat Creek, Sugar Creek's competitor. But Sugar Creek didn't claim that Lester's specialized training involved its confidential information or disclosure of customers. And in fact, Sugar Creek offered the same training to anyone who could pay to attend its driving school. Further, Sugar Creek's offer declared that at the completion of the class, you will be prepared to start your own horse-drawn carriage business.

So the Court held that there was no protectable business interest for something that wasn't a trade secret, confidential business information, or a customer list, but freely available to all, with the clear message that "after this training, you can go into the horse carriage business - just like us!" 

Dare I say it? Don't horse around with your non-compete provisions. Have a competent attorney review them to see if they satisfy the three basic requirements, and if not, remedy the defects before you and your ex-employee wind up in court. 
If you find this post worthwhile, please consider sharing it with your colleagues. The link to this blog is and my website is And my email address is Thanks!


Popular posts from this blog

The BUSKLAW May Newsletter: Is There a Moral Imperative to Plain English? Part 1 - Examples

"The man in black fled across the desert, and the gunslinger followed." 

Thus begins Stephen King's epic story of the gunslinger, Roland Deschain, and the popular Dark Tower series of novels describing his adventures. But King didn't have to write this sentence that way; he could have consulted with the typical lawyer, politician, or company PR department first. Had he done so, the sentence may have appeared so:

"The bad hombre who was dressed mostly in dark clothing and running fast across an arid land was pursued by a multi-armed, extremely dangerous, and notorious vigilante."
The difference in these two sentences is clear. King's concise short sentence creates an image that grabs the reader's attention and raises provocative questions. Who is the man in black? Who is the gunslinger? Why is he after the man in black? But the Bizarro World Stephen King sentence - with its ethnic slur, passive voice, ambiguity, suppositions, and superfluous adjectives …

A BUSKLAW Newsletter Aside: Is Your Website Compliant with the European Union's GDPR?

Effective 25 May 2018, the EU's General Data Protection Regulation goes into effect. The GDPR is a big deal and quite complicated. There are 99 articles and 173 recitals defining the privacy rights of individuals and data controllers’ and data processors’ obligations. 

Are you a U.S.-baseddata controller or data processor subject to the GDPR? You are a “data controller” if you, alone or jointly with others, determine the purpose and means of “processing” personal data of EU individual customers or businesses. The threshold is that you offer goods or services to customers or businesses in the EU (including the UK, despite Brexit) and collect their personal data. But even if you don’t sell goods or services to EU customers but engage in marketing or monitoring activities involving EU individuals’ personal data, you are covered by the GDPR.

You are a data processorif you “process” personal data on behalf of a “data controller,” i.e., a data controller contracts with you to process pers…