Connecticut Employment Law Blog Insight on Labor & Employment Developments for Connecticut Businesses

Another Look at “Moral Turpitude” and Why Drafting Isn’t Always Easy

Posted in Highlight, Human Resources (HR) Compliance, Wage & Hour

Last week, Ken Adams was kind enough to provide us with a great guest post on using the clause “moral turpitude” in employment contracts.  If you haven’t read it yet, take a minute to do so.

I agree with Ken that the phrase “moral turpitude” has some issues and should be used sparingly in employment contracts.

But what is good in theory may not work as well in practice.

Take a company that has used such a phrase in their contracts for years.  It now wants to abandon that phrase for all contracts going forward; all very well and good but how will that change affect interpretations of existing contracts?  And if it has dozens of contracts, how does it keep track of the changes?

Moreover, while the clause may be vague, the company may not have had any disputes about the scope of the clause before. Why rock the boat?

Or take an executive who is the recipient of a company’s version of a contract that has the clause in there. Is the executive going to go to battle over a phrase that will likely never come into play?

Thus as a result, companies and executives do not have a significant incentive to remove that clause from the contract. A search of publicly-available executive contracts shows plenty of examples of that phrase still being used repeatedly.

What is an employer to do? Employment agreements need not be static creatures.  Indeed, the best contracts are the result of years of revising to improve upon language when issues develop.   And when your existing contracts are up for renewal, use it as a time to clean up language that could use some additional clarity.  The use of “moral turpitude” is not so risky as to merit wholesale revisions but if you are starting from scratch, use it as an opportunity to find language that is simpler and easier to interpret.

There is no simple path to contract drafting. But by paying attention to the words that you use, there’s nothing that prevents you from simplifying your contracts.

 

  • http://www.adamsdrafting.com/ Ken Adams

    Dan: At the risk of engaging in control-freakery, I thought I’d wade in.

    Regarding “how will that change affect interpretations of existing contracts,” what’s there to worry about? You’d be replacing a hopeless usage with a clear and specific standard, and that change won’t affect the meaning of “moral turpitude,” or rather lack of meaning.

    And if the need to keep track of changes is a problem, nothing will ever change. It’s not that hard: a company can just note in its collective memory that after X date references to “moral turpitude” were eliminated in favor of a clearer standard.

    As regards the why-rock-the-boat argument, what wait until a dispute occurs? The whole point of this sort of change is to reduce the odds of dispute. That applies from the perspective of the company and the perspective of the executive. If I were asked to sign a contract that uses the term “moral turpitude,” I’d ask for it to be changed. If the company were to refuse, that would speak volumes, in a bad way, about the company.

    So I don’t agree that there’s insufficient incentive to make the change. The fact that one can find innumerable contracts that use the phrase “moral turpitude” has nothing to do with the value of the phrase, and it shouldn’t be taken as suggesting that the phrase is innocuous: there’s no end to the crap on display in traditional drafting.

    And I’m not sure why you say that the time to eliminate “moral turpitude” is when you’re “starting from scratch.” As you note, companies tend to revise templates on an ongoing basis. I don’t see anything scary about taking the opportunity, during a round of revisions, to get rid of “moral turpitude.”

    If anyone feels compelled to tolerate a usage a problematic as “moral turpitude,” it’s almost certain that their templates are chock full of other suboptimal usages.

    Ken