Free Webinar on Restrictive Covenants and What Employers Need to Know Now

Have you taken steps to prevent your business from walking out the door? That issue -- and the overall use of restrictive covenants will be the subject of today's free webinar at noon. You can sign up here

Our monthly webinar series (after taking the holiday period off) runs on the second Wednesday of each month. 

In our past webinars, attendees have asked if we could post the presentation materials ahead of time.  You can view those materials here.

Enforcing Restrictive Covenants - What Employers Need to Know

There were signs this morning that the economy is starting to pick up again. If that continues to happen, there is no doubt that we'll start to see many more employees changing jobs to take advantage of new opportunities.

But as that happens, some of those employees' employers will be left scratching their head and asking: How can I protect my clients, customers and confidential data from walking out the door?

What's one possible solution? Restrictive Covenants are typically contract provisions that restrict an employee from competing with your business, soliciting clients or employees, or using trade secrets in their new business.  They take many shapes and sizes but overall, courts will give them serious consideration if they are reasonable in time and scope.

Our monthly webinar series returns in February (after a holiday absence) to discuss this very issue and how employers can draft restrictive covenants that will hold up in court.  My fellow partners, Jon Orleans and Rick Robinson have agreed to spearhead this production and should be both educational and entertaining.

It will be held on February 10, 2010 at 12 noon EST.  Sign up through this link (and, as always, it's free). 

The monthly webinars will continue on the second Wednesday of each month at noon. If you have any suggestions on topics that you'd like to hear, please feel free to drop me a line. 

Quick Takes: Firing Via E-mail, COBRA, EFCA, Facebook, Last-Chance Agreements & Restrictive Covenants

Employment law is quite the hot topic among various blogs. So much so that it's time for the next installment of Quick Takes -- a quick summary of what's new and noteworthy.

And on the lighter side, don't miss this fun post by the Delaware Employment Law Blog recapping the top 10 excuses for being late to work.

Non-Compete Agreements: A Warning For Connecticut Employers with California Employees

I'm not sure where I heard it first, but I was once told that there federal employment laws to worry about, and then there are California'screative commons licensed by Dan Schwartz employment laws to worry about.  Indeed, California acts like a country of its own when it comes to several laws.

For employers in Connecticut with California-based employees (whether in sales, manufacturing or otherwise) an important decision released earlier this month reinforces that notion.  In striking down a non-compete law, the California courts have re-emphasized that restrictive covenants in California are unlikely to be upheld.

Several blogs have the details including Wage Law, Employer Law Report and Labor & Employment Law Blog.   L&ELB has the concise summary:

In Edwards v. Arthur Andersen LLP, the California Supreme Court reaffirmed California's strong public policy against covenants not to compete.  The primary issue in the case was whether the Ninth Circuit's "narrow restraint" exception was a proper interpretation of California law.  Under the narrow restraint exception, employers could enforce non-competition agreements that did not "entirely preclude" an employee from practicing his or her trade.  The Supreme Court summarily rejected this exception.  The lesson for employers is that unless a covenant not to compete falls squarely within one of the statutory exceptions, it is not likely to be upheld by a California court.

Connecticut employers with California employees would be wise to review their restrictive covenants again in light of this decision.

New Connecticut Laws effective October 1, 2007

Pumpkin - Morgue FileOctober.  Here in New England, it brings to mind pumpkins.  Besides being carved up (made into pumpkin pie), pumpkins also hold a place in story lore -- you'll recall from Cinderella that a pumpkin could be magically transformed into a beautiful carriage (which of course, you can buy on Amazon.) 

In Connecticut, October also brings about new laws, which go into effect on this date.  Which laws will blossom into beautiful carriages, with meaning and true purpose, and which ones will remain pumpkins?  It remains to be seen.  But here are some of my early contenders on the employment side of things:

Carriages (Laws that should run smoothly -- relatively easy to interpret, apply and understand):

  • The laws regarding discrimination on the basis of sexual orientation and civil union status have been evolving this year.  Before this year, Connecticut just prohibited discrimination on the basis of sexual orientation.  In July 2007, Connecticut prohibited employment discrimination based on a person's civil union status.  Now, effective today, however, the laws are broadened even further on sexual orientation grounds. 

It will now be "discriminatory practice for any person to subject any other person to the deprivation of any rights, privileges or immunities secured by the Constitution or laws of this state on account of sexual orientation."  This is clear and gives some greater consistency to the application of sexual orientation discrimination laws in the state.  A full background on these new laws is discussed during an earlier post. 

Pumpkins (Laws with limited application or may lead to unintended consequences):

  • A new law prohibiting the use of non-compete agreements, in some circumstances, for security guards.  I've discussed this new law's background at length previously, but suffice to say that its an inartfully drafted statute.  At its core, the new law prohibits employers from requiring security officers to "enter into an agreement prohibiting such person from engaging in the same or a similar job, at the same location at which the employer employs such person, for another employer or as a self-employed person". (If the employer can "prove" that the employee received trade secrets, then a non-compete can be used.)
  • Incidentally, this same new law also prohibits the use of non-compete agreements for broadcast employees (also known as television anchors).  Jonathan O'Connell, of the Hartford Business Journal, had this to say about the case over the summer and recalled the influence that WFSB Channel 3 anchor Al Terzi had on its passage. 

One can argue about whether non-compete agreements are a useful tool for business or harm an employee's right to work; when the legislature carves out exceptions for certain industries however, it passes up on the opportunity to set real boundaries for restrictive covenants. Instead, this statute would appear to affect just a handful of employees every year, if even that.

(Speaking of deadlines and new laws, yesterday was the deadline for filing new updated EEO-1 forms to comply with federal laws. The guidance from the DOL is publicly available.  Employers that haven't yet submitted the information should do so ASAP.)   

Non-Compete Agreements for Security Guards

With apologies to Alex Trebek, it's time for a game of legal Jeopardy

First, the answer: "As a result of a new Connecticut law (effective October 1, 2007), employees in this arcane type of job classification can now bring suit if their employer requires them to sign a certain type of non-compete agreement."

The question: What is "classification 339032 of the standard occupational classification system of the Bureau of Labor Statistics of the United States Department of Labor"?

Are you confused yet? If so, let's back up.  

About a year ago, Guardsmark, a security company, lost its contract to provide services to ESPN. When employees from the old security company tried to work for the new company, Guardsmark invoked the non-compete agreements that these employees signed.  As Connecticut readers know, there are not many state laws that restrict the use of non-compete agreements, compared with other states.

Attorney General Richard Blumenthal picked up the cause and testified in support a new bill that would prohibit employers from using non-compete agreements on security personnel in limited circumstances. 

The bill, which was subsequently modified then passed by the general assembly, prohibits employers from requiring security officers to "enter into an agreement prohibiting such person from engaging in the same or a similar job, at the same location at which the employer employs such person, for another employer or as a self-employed person".   (If the employer can "prove" that the employee received trade secrets, then a non-compete can be used.)

The general assembly, however, did not use the term "security officer" or define it, which, I would argue would have been the more logical approach to take. Rather, it relied on standard occupational classifications that have been created by the U.S. Department of Labor "for the purpose of collecting, calculating, or disseminating data."

A look at the online SOC codes, however, are far from enlightening: Under 33-9062 (which is how the DOL actually lists its classification), it has the following description:

33-9032 Security Guards -- Guard, patrol, or monitor premises to prevent theft, violence, or infractions of
Far from an eloquent description, since many employers are not even aware that the DOL uses these types of classification.

So, how will this be interpreted? We're unlikely to find out given the narrow nature of the law. For employers of security guards, however, one answer is simple: Do not use broad non-compete agreements to prevent employees from working for new employers at the same location. 

And stay tuned for a sequel; the DOL website posts this informational note: "The 2000 SOC Manual is currently under revision.