<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" version="2.0">

<channel>
	<title>Current Employment</title>
	
	<link>http://currentemployment.net</link>
	<description />
	<lastBuildDate>Thu, 12 Jan 2012 17:38:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/currentemployment/aaa" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="currentemployment/aaa" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>How NOT to Go Out of Business</title>
		<link>http://currentemployment.net/2012/01/how-not-to-go-out-of-business/</link>
		<comments>http://currentemployment.net/2012/01/how-not-to-go-out-of-business/#comments</comments>
		<pubDate>Thu, 12 Jan 2012 17:38:35 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[HR Issues]]></category>
		<category><![CDATA[Labor Law]]></category>
		<category><![CDATA[Wage & Hour]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1768</guid>
		<description><![CDATA[So, apparently it&#8217;s not a great time to be in the baked goods industry. Hostess has filed for Chapter 11 for a second time in 10 years. And last month [...]]]></description>
			<content:encoded><![CDATA[<h3>So, apparently it&#8217;s not a great time to be in the baked goods industry.</h3>
<p><img class="alignleft" style="margin: 10px;" src="http://farm3.staticflickr.com/2678/5701078956_64e8470b65_m.jpg" alt="Twinkie" width="240" height="190" /></p>
<p>Hostess has filed for Chapter 11 for a second time in 10 years. And last month the locally-renowned bakery Rolf&#8217;s Patisserie shuttered its doors permanently.</p>
<p>It&#8217;s obviously not fair to compare a multinational food product manufacturer with a micro-regional fancy-cake-maker, but I&#8217;m going to do it anyway, because it&#8217;s an easy way to make a point.</p>
<p>Both of the news stories surrounding these companies center on employment issues. Almost immediately after it filed for bankruptcy, Hostess cited its pension liability and rigid work rules as the principal issue in restructuring the company; it needs to get out of its current collective bargaining agreements and start over, it says. The Teamsters disagreed, of course, but the correlation was there. Even though <a href="http://www.thestreet.com/story/11372755/1/twinkie-maker-hostess-files-for-bankruptcy.html" target="_blank">the unions are going to take it on the chin</a>, the message turned out all collaborative and warm. The company that brought us Twinkies and other delicacies was fighting for its life, and it just needs the union&#8217;s help to stay afloat. The union obviously held a press conference of its own, but the tone was already set. Hostess, for PR purposes, at least, was playing nice.</p>
<p><img class="alignright" style="border-image: initial; margin: 10px;" title="Rolf's Logo" src="http://rolfspatisserie.com/uploads/shop/rolfspatisserie.com/912.jpg" alt="Rolf's Logo" width="102" height="140" /></p>
<div>
<p>Contrast that with Rolf&#8217;s. First of all, for you non-Chicago readers, <a href="http://rolfspatisserie.com/" target="_blank">Rolf&#8217;s Patisserie</a> made some really really good cakes. The fancy kind that they make reality shows about. They were a north shore staple. In mid-December, though, the company abruptly closed its doors. Abrupt to its regulars, its upcoming wedding orders, and, most unsettling, abrupt to its employees.</p>
<p>The workforce was told the company would be closed on December 11 for cleaning. Not unusual &#8211; the same thing had happened the year before &#8211; except this time, instead of reopening, the company altered its website to tell the world (including the part of the world employed by Rolf&#8217;s) that it was permanently closed.</p>
<div>
<div>
<p>That&#8217;s bad. It makes the company look bad, obviously. But the employees all got final checks in the mail. No one&#8217;s getting sued over it, right?</p>
<p>Well&#8230;</p>
<div>
<p>The news reported this week that <a href="http://articles.chicagotribune.com/2012-01-11/news/ct-met-bakery-protest-20120111_1_final-paychecks-bakery-employees-claim" target="_blank">Rolf&#8217;s former employees were protesting outside its facility</a>, on the day their class action filing hit the Northern District Clerk&#8217;s Office. Apparently, those final checks&#8230; wait for it&#8230; bounced. Plus, the state and federal governments have this requirement &#8211; called the WARN Act &#8211; that requires businesses to give their employees advance notice of a mass layoff or closure. When you don&#8217;t, you get sued. Even if you go under. You still get sued.</p>
<p>Am I saying that Rolf&#8217;s could&#8217;ve avoided being sued if they had notified their employees of their financial troubles? No. What I&#8217;m saying is that when you&#8217;re facing financial peril, no matter what size company you are, no matter what your chances of survival are or aren&#8217;t, how you manage employee expectations will dictate everything, from legal liability to public perception. It is absolutely imperative.</p>
<p>There is a point at which you must be honest with your employees. Not only because it&#8217;s the right thing to do, but because it&#8217;s the law. It&#8217;s okay if you don&#8217;t know what that point is &#8211; it&#8217;s going to be different for everybody. But you have to find out. Hostess looks like a smart corporation telling it&#8217;s employees to eat their peas, to borrow a Presidential phrase. Rolf&#8217;s, on the other hand, looks like a company that kept everyone in the dark, and now is going to have to pay for it. In both treasure and goodwill.</p>
</div>
</div>
</div>
</div>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=jr29Ifr-bf0:p4r8iVWuXcU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=jr29Ifr-bf0:p4r8iVWuXcU:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=jr29Ifr-bf0:p4r8iVWuXcU:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/jr29Ifr-bf0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2012/01/how-not-to-go-out-of-business/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dear Everyone In Charge: Get to #@$ Work</title>
		<link>http://currentemployment.net/2012/01/dear-everyone-in-charge-get-to-work/</link>
		<comments>http://currentemployment.net/2012/01/dear-everyone-in-charge-get-to-work/#comments</comments>
		<pubDate>Mon, 09 Jan 2012 06:01:15 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[Labor Law]]></category>
		<category><![CDATA[Politics]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1766</guid>
		<description><![CDATA[So, President Obama used the (possible) Senate recess to fill the necessary positions at the NLRB again. (Hi, everybody. I&#8217;m back) Yes, I said again. Because he did this last [...]]]></description>
			<content:encoded><![CDATA[<h3>So, President Obama used the (possible) Senate recess to <a href="http://www.politico.com/news/stories/0112/71086.html" target="_blank">fill the necessary positions at the NLRB</a> again.</h3>
<p>(Hi, everybody. I&#8217;m back)</p>
<p>Yes, I said again. Because <a href="http://www.cnn.com/2010/POLITICS/03/27/obama.appointment.controversy/" target="_blank">he did this last time, too</a>. Craig Becker, whose appointment just expired, was a recess appointment as well. Both times, incensed Republicans have unloaded a magazine of PR soundbites about the President circumventing the Constitutional role of the Senate, and creating some kind of rogue bureaucracy that&#8217;s equal parts fascist dictatorship and Marxist, wealth-sharing, Soviet state.</p>
<p>Meanwhile, a couple of news stories later, the Indiana Democratic minority is <a href="http://www.news-sentinel.com/apps/pbcs.dll/article?AID=/20120108/NEWS/120109698" target="_blank">walking out of session again</a> because the Republican majority is insisting on introducing legislation that would make Indiana the 23rd right-to-work state in the nation. That&#8217;s right, I said again. Again. Indiana Dems spent several weeks in a motel in Urbana-Champaign to keep the bill off the floor in 2010. Ground the whole legislative session to a halt.</p>
<p>Two labor issues, two stalemates among legislatures. Look, I know the ideology behind organized labor is deeply-rooted and not going anywhere any time soon. But that actually speaks to my point here. These are not new issues. The political lines between unions and company owners were drawn before the ones separating the modern parties. And still, Presidents appointed NRLB members who actually got confirmed, and minorities showed up on the first day of session.</p>
<p>The obvious question is why, all of the sudden, these historical fissures are causing such caustic stalemates. But, to be honest, I don&#8217;t really care what the question is. And whether you&#8217;re a unionized worker or a business owner, Republican or Democrat, neither do you.</p>
<p>Every day I wake up with items from yesterday&#8217;s to-do list. Every day I work too much, fight harder, and every night go to sleep too late with half a to-do list still to be done. We all are. Welcome to <em>The Recovery</em>. And that&#8217;s fine. That&#8217;s how we do it here in America. We work hard.</p>
<p>What we don&#8217;t need &#8211; worker and business owner alike &#8211; is for the entire legislative session or regulatory schema to get rutted by the pissing contest that has replaced political discourse, wondering if Hot-Button-Issue A is going to kill our company&#8217;s profit for the year. And (not to wax too grandiose) I&#8217;m not working this hard to live in a country that can&#8217;t suck it up and cooperate with people they don&#8217;t like. Even if it means taking the uppercut to the chin, voting &#8220;no&#8221; for the bill or the person you don&#8217;t like, and fighting to get a majority the next time around so you can win some fights.</p>
<p>Honestly, for three years now the economy&#8217;s been slowly clawing its way out of the toilet, and every economic pundit I&#8217;ve heard during that time has said the #1 thing holding us back is fear. Uncertainty. Employers need to know what&#8217;s going to happen a year from now to know whether it makes sense to hire someone. Employees can&#8217;t spend any money until they know they&#8217;re going to have a job in 6 months. We can&#8217;t know what the markets will do tomorrow, but we&#8217;re supposed to be able to forecast what the political climate will look like a year from now.</p>
<p>I don&#8217;t think the whole country is looking for a single answer to the economic problem. What we&#8217;d like, if anyone elected to anything is listening, is <strong>any movement at all</strong>. Just one time, for someone to say &#8220;well, they got us this time, we&#8217;ll get &#8216;em next time&#8221; and let us move on.</p>
<p>And yet, with approval ratings further down the crapper than their economy, Congresspeople and Senators from every seat on the political seesaw still pull this &#8220;I&#8217;m-taking-my-ball-and-going-home&#8221; garbage. It&#8217;s petty and weak. Learn how to lose, folks. The rest of us need to get some work done.</p>
<p>You know, if I&#8217;d hired a team that produced results this bad, I&#8217;d fire them all and start over. Man, if only I&#8217;d hired them. If only&#8230;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=GpRsktEFUzQ:a_uCiQDviTU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=GpRsktEFUzQ:a_uCiQDviTU:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=GpRsktEFUzQ:a_uCiQDviTU:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/GpRsktEFUzQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2012/01/dear-everyone-in-charge-get-to-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NLRB Postpones Poster Requirement</title>
		<link>http://currentemployment.net/2011/10/nlrb-postpones-poster-requirement/</link>
		<comments>http://currentemployment.net/2011/10/nlrb-postpones-poster-requirement/#comments</comments>
		<pubDate>Fri, 07 Oct 2011 15:01:23 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[HR Issues]]></category>
		<category><![CDATA[Labor Law]]></category>
		<category><![CDATA[Politics]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1731</guid>
		<description><![CDATA[The National Labor Relations Board has moved the date its new posters must be up in most businesses to January 31, 2012. According to the official press release, the NLRB&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>The National Labor Relations Board has moved the date its new posters must be up in most businesses to January 31, 2012.</p>
<p>According to the official press release, the NLRB&#8217;s reason is that there&#8217;s confusion from business owners about which companies are under the Board&#8217;s jurisdiction, and they want to spend some time educating the business community about the issue.</p>
<p><a href="http://www.theemployerhandbook.com/2011/10/nlrb-puts-the-temporary-kibosh.html" target="_blank">Eric Meyer over at the Employer Handbook calls bulls&#8212;</a> on the PR explanation for the delay, and I completely agree. Eric notes that the Board made quite a big deal out of the FAQ they released with the final regulations, so there&#8217;s not that much educating left to do. Also, figuring out if you&#8217;re covered by the NLRB&#8217;s jurisdiction is not that hard. Seriously, we do hard things here; this is not one of them&#8230;.</p>
<p>I think most employer-side attorneys would tell you the real reason for the postponement has something to do with the stream of lawsuits that have been filed challenging not just the poster requirement, but the NLRB&#8217;s ability to enact regulations at all.</p>
<p>The new date will pose some logistical problems, though. Many employers buy new laminated breakroom posters around the new year, and the companies that make them have been busy redesigning the 2012 models to fit the NLRB info in. Now that the Board&#8217;s regulation is up-in-the-air, poster companies (and the employers that buy those posters) are going to have to decide whether to print them with the info or not.</p>
<p>At any rate, no need to hang the new poster next month like we expected.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=sUW47ng-Xeo:cHYk530Gyj4:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=sUW47ng-Xeo:cHYk530Gyj4:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=sUW47ng-Xeo:cHYk530Gyj4:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/sUW47ng-Xeo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2011/10/nlrb-postpones-poster-requirement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Friday Diversion #8: The HP Retirement Fund</title>
		<link>http://currentemployment.net/2011/09/friday-diversion-8-the-hp-retirement-fund/</link>
		<comments>http://currentemployment.net/2011/09/friday-diversion-8-the-hp-retirement-fund/#comments</comments>
		<pubDate>Fri, 30 Sep 2011 17:24:54 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[Friday Diversions]]></category>
		<category><![CDATA[HR Issues]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1732</guid>
		<description><![CDATA[One of my favorite employment-related ways to waste time is to read about the golden parachutes ousted CEOs receive after they (or their companies) royally muck things up. No, seriously. [...]]]></description>
			<content:encoded><![CDATA[<p>One of my favorite employment-related ways to waste time is to read about the golden parachutes ousted CEOs receive after they (or their companies) royally muck things up.</p>
<p>No, seriously. That&#8217;s what passes as fun for me.</p>
<p>This week, HP disclosed what it&#8217;s departing leader, Léo Apotheker, is getting as a reward for killing the company&#8217;s market share and stock price over the past 11 months or so. I won&#8217;t bore you with the details &#8211; <a href="http://www.forbes.com/2011/09/30/hp-discloses-ousted-ceos-pay-day-marketnewsvideo.html" target="_blank">that&#8217;s what Forbes is for</a> &#8211; but here&#8217;s a snippet:</p>
<ul>
<li>$7.2 million in severance</li>
<li>$3.56 million in accelerated-vesting stock</li>
<li>Only 424,000 of the restricted stock units that he was eligible for for, you know, doing a good job (he could&#8217;ve gotten over 700,000 shares, if only he&#8217;d, you know, done a good job)</li>
<li>a $2.4 million bonus (?!)</li>
<li>and relocation expenses back to France or Belgium.</li>
</ul>
<p>All this is more awesome when you put it in perspective, though. <a title="Mark Hurd, HP &amp; Oracle: Adventures in Employment Law" href="http://currentemployment.net/2010/09/mark-hurd-hp-oracle-adventures-in-employment-law/" target="_blank">If you remember,</a> before Mr. Apotheker there was Mark Hurd, who also left the company under not-the-best circumstances. And he actually <em>made</em> HP some money.</p>
<p>HP may be wisening up, though. Their incoming CEO, Meg Whitman, is <a href="http://blogs.ft.com/fttechhub/2011/09/hp-shareholders-can-now-count-the-cost-of-their-last-ceo/#axzz1ZSONGbLk" target="_blank">taking a $1.00 salary, with an annual bonus of $2-6 million</a>, depending on how badly she screws things up over there.  And, apparently, Meg&#8217;s payout will be considerably less <del>if</del> when they let her go some time in 2012.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=bPhfx4McCG4:xx7qOYH-G0w:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=bPhfx4McCG4:xx7qOYH-G0w:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=bPhfx4McCG4:xx7qOYH-G0w:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/bPhfx4McCG4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2011/09/friday-diversion-8-the-hp-retirement-fund/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Employment Documents in Plain English – A Primer</title>
		<link>http://currentemployment.net/2011/09/employment-documents-in-plain-english-a-primer/</link>
		<comments>http://currentemployment.net/2011/09/employment-documents-in-plain-english-a-primer/#comments</comments>
		<pubDate>Tue, 27 Sep 2011 13:15:58 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[HR Issues]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1676</guid>
		<description><![CDATA[The other day I made my case for why employment documents should all be written in Plain English, omitting the legalese and other stuff employees don&#8217;t really read. In part [...]]]></description>
			<content:encoded><![CDATA[<p>The other day I <a title="Thanks for the Contract. Can You Tell Me What it Says?" href="http://currentemployment.net/2011/09/thanks-for-the-contract-can-you-tell-me-what-it-says/">made my case for why employment documents should all be written in Plain English</a>, omitting the legalese and other stuff employees don&#8217;t really read.</p>
<p>In part 2 of this 2-part series, we&#8217;re going to talk a little about what a Plain English document is, mostly by talking about what it&#8217;s not.</p>
<h2>1. &#8220;Plain English&#8221; Is Not Code for &#8220;Short&#8221;. Or &#8220;Cute&#8221;.</h2>
<p>What most people think of when I mention &#8220;plain English&#8221; and &#8220;employment document&#8221; in the same sentence is the now-famous Nordstrom Employee Handbook, which consisted entirely of a single card handed out to an employee on their first day. The card read:</p>
<blockquote><p><strong>Welcome to Nordstrom</strong></p>
<p>We’re glad to have you with our Company. Our number one goal is to provide outstanding customer service. Set both your personal and professional goals high. We have great confidence in your ability to achieve them.</p>
<p><strong>Nordstrom Rules: Rule #1: Use best judgment in all situations. There will be no additional rules.</strong></p>
<p>Please feel free to ask your department manager, store manager, or division general manager any question at any time.</p></blockquote>
<p>That was it. Sounds good, right? Yeeaah, not going to cut it.</p>
<p>The card is great &#8211; a little gimmicky maybe &#8211; but definitely written in plain English. Still, it&#8217;s not what I have in mind when I recommend an employer&#8217;s documents be revised. 99% of employers will need all the regular EEO, wage-and-hour and leave policies in place in order to securely protect their businesses.</p>
<p>Nor does writing in plain English mean your handbook has to read or look like the Ropes at Disney&#8217;s. While that document is super-fun (albeit very, very outdated), your documents don&#8217;t have to be. They do have to be legible to your workforce.</p>
<p>For some reason, everyone seems to think that you either get all the gobbledygook in the standard form versions of employment documents, or you get the Nordstrom treatment. Not true. The concept behind the plain English movement is that the documents <em>out there right now</em> &#8211; the ones you are currently using &#8211; can keep all the information they currently contain, but be more understandable and more specific at the same time. You don&#8217;t have to talk in vague generalities in order to be understood. You just have to use modern words and sentence structure.</p>
<h2>2. Plain English is Not An Excuse to Do It Yourself</h2>
<p>A lot of employers hear &#8220;no legalese&#8221; and think</p>
<blockquote><p>Great! This lawyer is telling me I can write this stuff myself! I just saved myself <strong>a ton</strong> in legal fees! What an idiot! Haha! Sucker!</p></blockquote>
<p>Please don&#8217;t do this. Number one, it&#8217;s mean. Number two, it&#8217;s wrong.</p>
<p>On second thought, go for it. Write them all yourself! You can do it! Just remember: we said that Plain English takes all the information in the documents you currently have and makes it easier to understand. So, analyze what it is your agreement or handbook actually guarantees, protects, explains, etc., and rewrite the document clause-by-clause in a way that makes sense. Have at it. Just make sure your language doesn&#8217;t water down the original purpose. Oh, and avoid any terms of art that might get you in trouble if the contract has to be interpreted.</p>
<p>And how, exactly, does &#8220;Upon termination of this Agreement, pursuant to the terms of section 4(e), neither party shall have any further obligations under this Agreement, except for the obligations which by their terms survive this termination as noted in Section 16 hereof &#8221; sound when you write it in your native tongue? Well, don&#8217;t worry about it. Just delete that part, then. And when you get sued and your contract gets thrown out, you can pay me to tell you you&#8217;re going to lose your case.</p>
<p>You get that I&#8217;m being sarcastic, right? Believe it or not, your policies or contracts are <em>harder</em> to write in conversational language than in legalese. Legalese is easy. Talking is hard. <a href="/contact-tim-eavenson">Call a lawyer.</a></p>
<p>Ok, so if that&#8217;s what plainly-written employment documents <em>aren&#8217;t</em>, what <em>are</em> they?</p>
<h2>3. Plain English Employment Documents Are. . . Whatever You Want Them to Be.</h2>
<p>The point I&#8217;m trying to make is that writing something in Plain English is the means, not the end. You can have good or bad policies written in either legalese or conversational English. What plain writing opens you up to is thinking about your HR documents as more than just legal cover-your-behind paperwork. These are the papers that will communicate who you are as an organization to your employees. That is not something to take so lightly.</p>
<p>Think about the Disney handbook from the 40&#8242;s. Obviously, you don&#8217;t want to replicate the actual policies in there, but the way it&#8217;s written? Phenomenal. And &#8211; like I said before &#8211; it&#8217;s <em>not</em> because of the novelty. It&#8217;s because that style is perfect <em>for Disney</em>. If you&#8217;re running a 15-person storefront CPA, you probably won&#8217;t have pictures of guys sliding down stairway railings. You may want something more cut-and-dry, like a two-column &#8220;If&#8230;then&#8221; sheet for common problems, or to draft your employee handbook as an FAQ with bullet points. A lot of forward-thinking tech-based companies are creating wiki pages or other intranet sections to store their employment documents as searchable files. The idea is to write in a way that makes it click with your workforce.</p>
<p>If you&#8217;re looking for a place to start &#8211; sort-of a test balloon to see if this is worth the time and money &#8211; I would suggest redoing (or doing-in-the-first-place, <a href="http://www.ohioemployerlawblog.com/2011/09/dear-congress-can-you-fix-economy.html" target="_blank">as the case may be</a>) your social media policy. More than any other HR policy, the SM guidelines should really bear the stamp of your particular organization. Most employment attorneys will tell you that a good social media document will not only tell the employee what the rules are, but tell them why, and why it matters to both your company and them. That&#8217;s a perfect diving board for practicing some plain writing.</p>
<p>But don&#8217;t stop there. Look at that handbook, or, if you&#8217;re really feeling frisky, your contracts. How can the language in those documents convey the same attitude as your new SM policy?</p>
<p>Oh &#8211; I told you I&#8217;d reveal what all that ridiculous legalese from the confidentiality agreement in the first post turned into:</p>
<p>NOTHING.</p>
<p>We deleted it &#8211; all of it. No recitals at all. No introductory sentence full of fill-in-the-blanks. We replaced the whole first page with a highly personalized &#8220;Introduction&#8221; that explained why it was vital to the Company to protect its secrets from competitors, and why it was equally vital to the protection of the employee&#8217;s new job. By writing it this way, we completely turned the tone of the agreement around; now, instead of having to drop &#8220;grounds for termination&#8221; on every new hire, the document reads like a collaborative effort to turn the company in the market leader in its industry. All by changing the document into something the employees might actually read before signing.</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=jcGmYZT_zTc:FbNSShROVyQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=jcGmYZT_zTc:FbNSShROVyQ:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=jcGmYZT_zTc:FbNSShROVyQ:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/jcGmYZT_zTc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2011/09/employment-documents-in-plain-english-a-primer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My, How Times Have Changed</title>
		<link>http://currentemployment.net/2011/09/my-how-times-have-changed/</link>
		<comments>http://currentemployment.net/2011/09/my-how-times-have-changed/#comments</comments>
		<pubDate>Tue, 20 Sep 2011 13:45:05 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[HR Issues]]></category>
		<category><![CDATA[Other]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1696</guid>
		<description><![CDATA[My son is 3. While he watches waaaaay less television than I did growing up, he does catch an episode of Mickey Mouse Clubhouse most mornings. It&#8217;s nice that he [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft" style="margin: 10px;" title="The Ropes at Disney" src="http://wdfmuseum.squarespace.com/storage/post-images/laborday2011_ropesatdisney.jpg?__SQUARESPACE_CACHEVERSION=1314903911414" alt="" width="350" height="262" />My son is 3.</p>
<p>While he watches waaaaay less television than I did growing up, he does catch an episode of <a href="http://en.wikipedia.org/wiki/Mickey_Mouse_Clubhouse" target="_blank">Mickey Mouse Clubhouse</a> most mornings.</p>
<p>It&#8217;s nice that he is getting to know the same characters I knew as a kid, but when I finally sat down and watched the show the other day, I noticed an unusual change in the attitude of a couple of the characters. The Clubhouse was visited at separate points in the episode by the old <a href="http://en.wikipedia.org/wiki/Willie_the_Giant#Willie_the_Giant" target="_blank">Mickey-and-the-Beanstalk Giant</a> and by <a href="http://en.wikipedia.org/wiki/Pete_(Disney_character)" target="_blank">Pete</a>, Mickey Mouse&#8217;s foil from the old cartoons. Unlike the dastardly or dopey bad guys of my youth, though, the characters were both generally helpful and nice, if unwittingly causing a problem or two.</p>
<p>Things change.</p>
<p>And, just like the differences between the cartoons I grew up with and those my son is watching, Disney offers a great example of how things change in HR, as well. Over labor day, the <a href="http://wdfmuseum.squarespace.com/posts/2011/9/5/the-ropes-at-disneys.html" target="_blank">Walt Disney Family Museum</a> posted a link to &#8220;<a href="http://wdfmuseum.squarespace.com/storage/LaborDay2011_theropesatdisneys_wdfmuseum.pdf" target="_blank">The Ropes at Disney&#8217;s</a>&#8221; &#8211; a superbly-detailed employee handbook for the men and women (but mostly men) at Disney&#8217;s animation studio in 1943. It doesn&#8217;t take many pages of drawings to realize there&#8217;s not going to be any sexual harassment section to this doc.</p>
<p>I can only imagine the current handbook is even more unrecognizable to its predecessor than those bad guys I grew up with are to my boy.</p>
<p>Still, it would be great to see more handbooks as tailored to their audience as Disney&#8217;s was back then.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=IW9FFv4olmg:BnbEdZNF1lc:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=IW9FFv4olmg:BnbEdZNF1lc:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=IW9FFv4olmg:BnbEdZNF1lc:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/IW9FFv4olmg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2011/09/my-how-times-have-changed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Friday Diversion #7 – And You Thought Your Job Was Dangerous</title>
		<link>http://currentemployment.net/2011/09/friday-diversion-7-and-you-thought-your-job-was-dangerous/</link>
		<comments>http://currentemployment.net/2011/09/friday-diversion-7-and-you-thought-your-job-was-dangerous/#comments</comments>
		<pubDate>Fri, 16 Sep 2011 19:18:26 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[Friday Diversions]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1685</guid>
		<description><![CDATA[Note: Today&#8217;s Friday Diversion is not funny. It&#8217;s not dire or anything &#8211; then it wouldn&#8217;t be a diversion, really &#8211; but I didn&#8217;t want to get your hopes up [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Note:</strong> Today&#8217;s Friday Diversion is not funny. It&#8217;s not dire or anything &#8211; then it wouldn&#8217;t be a diversion, really &#8211; but I didn&#8217;t want to get your hopes up for comedy and then drop a public radio story on you.</p>
<p><a href="http://en.wikipedia.org/wiki/Bacillus_cereus"><img class=" alignright" style="margin: 10px;" title="Bacillus cereus. Gross." src="http://upload.wikimedia.org/wikipedia/commons/0/02/Bacillus_cereus_01.png" alt="" width="259" height="194" /></a></p>
<p>I am always drawn to stories of how people work. Maybe its <a href="http://en.wikipedia.org/wiki/Working_%28book%29" target="_blank">a Chicago thing</a>, I don&#8217;t know. Well, here in Chicago, the local NPR affiliate has a little mini-show about science called Clever Apes, and the other day, they ran <a href="http://www.wbez.org/blog/clever-apes/2011-09-13/clever-apes-18-biological-weapons-91950" target="_blank">this story </a>that I found fascinating, where the host got to see &#8220;how people work with deadly bugs like anthrax, plague, MRSA and others&#8221; in a Federally-chartered research laboratory set up after the 2001 Anthrax scare.</p>
<p>The story spends a lot of time discussing the intricacies of donning and doffing workwear and other precautionary measures that the researchers take before and after they handle things like the plague. In one of those bizarre life-twists,<a href="http://www.wbez.org/blog/clever-apes/2011-09-15/lab-mishap-shows-risks-working-dangerous-bugs-92043" target="_blank"> another story broke this week</a> that a researcher at the facility&#8217;s sister-lab was infected with <a href="http://en.wikipedia.org/wiki/Bacillus_cereus" target="_blank">Bacillus cereus</a>, the same pathogen the researchers are working on in the story. Clever Apes&#8217;s host, Gabriel Spitzer, interviewed the lab&#8217;s director about the infection.</p>
<p>The two stories paint a fascinating picture of what these scientists go through every day just to get to work. Definitely worth a listen.</p>
<p>Personally, I don&#8217;t think I&#8217;ll ever say my job&#8217;s making me sick ever again.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=n9vnnL0Cwqw:kezMHOjsmsg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=n9vnnL0Cwqw:kezMHOjsmsg:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=n9vnnL0Cwqw:kezMHOjsmsg:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/n9vnnL0Cwqw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2011/09/friday-diversion-7-and-you-thought-your-job-was-dangerous/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NLRB Poster Now Available</title>
		<link>http://currentemployment.net/2011/09/nlrb-poster-now-available/</link>
		<comments>http://currentemployment.net/2011/09/nlrb-poster-now-available/#comments</comments>
		<pubDate>Thu, 15 Sep 2011 16:51:34 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[HR Issues]]></category>
		<category><![CDATA[Labor Law]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1672</guid>
		<description><![CDATA[Hey, remember that additional poster you&#8217;re going to have to put in your break room? It&#8217;s ready for download from the NRLB website.  The Board is giving you the option [...]]]></description>
			<content:encoded><![CDATA[<p>Hey, remember that <a title="NLRB Makes It Official: One More Labor Poster on the Wall" href="http://currentemployment.net/2011/08/nlrb-makes-it-official-one-more-labor-poster-on-the-wall/">additional poster you&#8217;re going to have to put in your break room</a>?</p>
<p>It&#8217;s ready for download <a href="https://www.nlrb.gov/poster" target="_blank">from the NRLB website</a>.  The Board is giving you the option of downloading one 11 x 17 poster, or two 8.5 x 11&#8242;s, if you&#8217;re rocking the standard office printer.</p>
<p>The poster doesn&#8217;t have to be put up until November 14, so if you want to be stingy, you can wait until then. While there&#8217;s certainly no need to spend money on it, I would suggest just printing the thing out and hanging it now, so you don&#8217;t forget about it. When you buy next year&#8217;s commercial workplace poster, the NLRB language should be included in it.</p>
<p>Or you could just <a href="http://online.wsj.com/article/SB10001424053111904836104576561222186231848.html" target="_blank">sue the Federal Government</a>. That&#8217;s also an option.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=3OsBHO75qYk:HvQJpkYPpdw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=3OsBHO75qYk:HvQJpkYPpdw:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=3OsBHO75qYk:HvQJpkYPpdw:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/3OsBHO75qYk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2011/09/nlrb-poster-now-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Current Employment is a LexisNexis Top 25 Blog!</title>
		<link>http://currentemployment.net/2011/09/current-employment-is-a-lexisnexis-top-25-blog/</link>
		<comments>http://currentemployment.net/2011/09/current-employment-is-a-lexisnexis-top-25-blog/#comments</comments>
		<pubDate>Wed, 14 Sep 2011 13:01:04 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[Housekeeping]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1673</guid>
		<description><![CDATA[I received word from the powers-that-be over at Lexis Nexis that Current Employment has been selected as one of the top 25 Labor &#38; Employment Blogs of 2011 by the LexisNexis [...]]]></description>
			<content:encoded><![CDATA[<p>I received word from the powers-that-be over at Lexis Nexis that <a href="http://www.lexisnexis.com/community/labor-employment-law/blogs/labor-employment-top-blogs/archive/2011/09/13/the-lexisnexis-top-25-labor-and-employment-law-blogs-of-2011.aspx" target="_blank">Current Employment has been selected </a>as one of the top 25 Labor &amp; Employment Blogs of 2011 by the <a href="http://www.lexisnexis.com/community/labor-employment-law/" target="_blank">LexisNexis L&amp;E Community</a>!</p>
<p>I&#8217;m honored by the selection, particularly to be mentioned next to the blogs that I go to for <em>my</em> L&amp;E news, like the <a href="http://www.ctemploymentlawblog.com/" target="_blank">Connecticut Employment Law blog</a>, the <a href="http://www.delawareemploymentlawblog.com/" target="_blank">Delaware Employment Law blog</a>, the <a href="http://www.ohioemployerlawblog.com/" target="_blank">Ohio Employer&#8217;s Law blog</a>, <a href="http://www.lawfficespace.com/" target="_blank">Lawffice Space</a>, and <a href="http://texaslawyer.typepad.com/work_matters/" target="_blank">WorkMatters</a>.</p>
<p>There are two other blogs that I am astonished are not on the list, both of which are better than this little site, IMHO. So when you&#8217;ve exhausted all the news here, and up there, you should check out the <a href="http://theemployerhandbook.com" target="_blank">Employer Handbook </a> by Eric Meyer, and the <a href="http://www.laborrelationstoday.com/" target="_blank">Labor Relations Today </a>by Seth Borden.</p>
<p>Thanks so much for reading Current Employment, and a special thank-you to all those who voted.</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=2REGNthEyhE:0TBOQjtxFQ4:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=2REGNthEyhE:0TBOQjtxFQ4:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=2REGNthEyhE:0TBOQjtxFQ4:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/2REGNthEyhE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2011/09/current-employment-is-a-lexisnexis-top-25-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Thanks for the Contract. Can You Tell Me What it Says?</title>
		<link>http://currentemployment.net/2011/09/thanks-for-the-contract-can-you-tell-me-what-it-says/</link>
		<comments>http://currentemployment.net/2011/09/thanks-for-the-contract-can-you-tell-me-what-it-says/#comments</comments>
		<pubDate>Tue, 13 Sep 2011 16:47:26 +0000</pubDate>
		<dc:creator>Tim Eavenson</dc:creator>
				<category><![CDATA[HR Issues]]></category>
		<category><![CDATA[The Profession]]></category>

		<guid isPermaLink="false">http://currentemployment.net/?p=1538</guid>
		<description><![CDATA[Not long after you start law school, someone you know will say the following to you: I bet you&#8217;re going to start using phrases like &#8220;party of the first part&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>Not long after you start law school, someone you know will say the following to you:</p>
<blockquote><p>I bet you&#8217;re going to start using phrases like &#8220;party of the first part&#8221; and writing in fine print now.</p></blockquote>
<p><a title="365 Days - Day 64 by SMercury98, on Flickr" href="http://www.flickr.com/photos/smercury98/2573529568/"><img class="     alignright" style="margin: 15px 10px;" title="Sarah Fleming - from Flickr" src="http://farm4.static.flickr.com/3280/2573529568_f5125cb3fd.jpg" alt="365 Days - Day 64" width="210" height="127" /></a></p>
<p>And then they will laugh at you. It happened to me, and I was an English major, so I wrote pretentiously already.</p>
<p>Lawyers complain about the stereotype &#8211; that we all just make things more confusing &#8211; but we&#8217;re not doing much to change this conventional wisdom. Case in point: I just finished revising a client&#8217;s documents as part of an HR audit. The company needed a Noncompete/Nondisclosure Agreement, so I opened a Sample Noncompete Agreement to tweak, and read the following:</p>
<blockquote>
<p align="center"><span style="font-size: small;"><strong><span style="text-decoration: underline;">W I T N E S E T H</span></strong>:</span></p>
<p><span style="font-size: small;"><strong>WHEREAS</strong>, the Company is principally engaged in the business of <strong>making widgets</strong> (hereinafter referred to as the “Business”); and</span></p>
<p><span style="font-size: small;"><strong>WHEREAS</strong>, Employee in his or her capacity as an employee of the Company may acquire extensive knowledge of the operations of the Business and certain confidential and proprietary information relating to the operation of the Business, as well as strong contacts and relationships with the Company&#8217;s customers, suppliers, and employees; and</span></p>
<p><span style="font-size: small;"><strong>WHEREAS</strong>, the Company is unwilling to employ the Employee unless Employee agrees to be bound by the terms of this Agreement; and</span></p>
<p><span style="font-size: small;"><strong>WHEREAS</strong>, to induce the Company to employ the Employee the Employee desires to execute this Agreement and be bound by the terms hereof.</span></p>
<p><span style="font-size: small;"><strong>NOW, THEREFORE</strong>, in consideration of the covenants and mutual agreements set forth herein and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties do hereby agree as follows:</span></p>
<p style="padding-left: 30px;"><span style="font-size: small;">1. <strong>Recitals</strong>.  The recitals set forth above are incorporated herein by this reference.</span></p>
<p style="padding-left: 30px;"><span style="font-size: small;">2. <strong>Consideration</strong>.  On the date hereof, as consideration for the Employee&#8217;s agreement to be bound by the terms of this Agreement, the Company agrees to hire Employee.</span></p>
</blockquote>
<p>And on and on and on it went. As I edited the document, I started to wonder:  <em>why am I not trying to make this more clear?</em></p>
<p>So I asked some of my non-lawyer friends what they thought of contracts that read like the one above. Not surprisingly, they universally hated them. But my followup question was a lot more interesting: Why, if they all hated contracts like this, did they accept them, sign them, let their lawyers write them in the first place? Why not ask for it in plain English?</p>
<p>To a man, they all said basically the same thing: Legal documents are different. Right? All those redundant phrases and grammatical gymnastics are what protect us from liability, right?</p>
<p>Right?</p>
<p>Well, no. Not right. There are some areas of the law that still require a lot of antiquated English, like Real Estate. And practices may lend themselves to confusion. Like patents. Patents are confusing to, like, 90% of lawyers even.</p>
<p>But in labor and employment law, there is absolutely no reason that a document has to be grammatically confusing. In fact, confusion is the #1 reason that your employment documents <em>should</em> be written in plain English. For some reason, though, most of them read like the last page of an auto loan application.</p>
<h2>Why Employment Docs Sound So Dumb</h2>
<p>Employers and lay people rightly blame attorneys for the legalese, but every attorney you talk to will have an equally-bad tale about reviewing a set of documents a business owner has pieced together from various free online sample documents, creating a Franken-contract that creates more liability than it eliminates.</p>
<p>There&#8217;s a million reasons legalese is tougher to kill than <a href="http://en.wikipedia.org/wiki/Kudzu" target="_blank">kudzu</a>. After my informal poll, though, I&#8217;ve figured out two central problems:</p>
<ol>
<li>Everyone &#8211; lawyers and clients and employees alike &#8211; <em>expects</em> legal documents to be difficult to read; and</li>
<li>Lawyers can&#8217;t bill for re-writing something from scratch if they have a version of it on file (so the old language just gets reused).</li>
</ol>
<p>Neither of these are good enough reasons to keep writing that stuff up there.</p>
<h2>Why They Shouldn&#8217;t</h2>
<p>I&#8217;m here to tell you, folks: If you hire a lawyer to write a contract for you, it doesn&#8217;t have to sound like that quote above. It <em>can</em> &#8211; that language is perfectly legible to attorneys and judges, and it&#8217;s just as legal as anything &#8211; but I don&#8217;t think it <em>should</em>. If you haven&#8217;t already, I think it&#8217;s time to rewrite your employment documents in Plain English. Here&#8217;s why:</p>
<h3>1. Everyone Likes It Better.</h3>
<p>It sucks to read legalese. Sucks for your employees, too. What you may not know is that it also sucks for lawyers and, more importantly, judges. An <a href="http://www.journallegalwritinginstitute.org/archives/2010/183.pdf" target="_blank">actual empirical study proved</a> that 2/3 of judges found plainly-written filings more persuasive than their more traditional counterparts, and that even judges &#8220;skim&#8221; documents &#8220;for their essence&#8221; when faced with legalese.</p>
<h3>2. Your Employees Will Read It.</h3>
<p>When I was clerking in Chancery Court, we handled a lot of noncompete disputes. In every single case, the employee&#8217;s attorney argued that the Employee didn&#8217;t read the document, or didn&#8217;t know what he was signing even if he had read it. In 90% of the cases, this argument failed. But you know what? The employer still had to pay their attorneys to write briefs and appear in court to defend against it. By just eliminating this single argument, you could probably save yourself $1,000 to $2,000 in litigation costs.</p>
<p>And if he decided that an agreement <em>was</em> confusing &#8211; to a lay person, not a lawyer &#8211; my judge was not above tossing the case on those grounds, alone.</p>
<p>All your documents, from the Handbook to the CEO&#8217;s bonus structure, should be tailored to the person who&#8217;s name is in ink at the bottom.</p>
<h3>3. After They Read It, Your Employees Will Still Like You.</h3>
<p>Check out &#8220;WHEREAS&#8221;-es numbers 3 and 4 up there.</p>
<blockquote><p>&#8220;Company is unwilling to employ the Employee unless&#8230;&#8221; ?</p>
<p>&#8220;to induce the Company to employ the Employee&#8230;&#8221; ?</p></blockquote>
<p>&#8220;Welcome to the Company! We&#8217;ll fire you if you don&#8217;t agree to this stuff!&#8221; Is that really the image you want to convey on your new hire&#8217;s first day at the job? I didn&#8217;t think so.</p>
<p>I know that change is hard, and the thought of redesigning all of your employment documents to make them sound more conversational is sort-of scary. But, I promise you, more confusing ≠ more protection. It means less.</p>
<h2>I&#8217;m In! What Now?</h2>
<p>So hopefully I&#8217;ve convinced you of the &#8220;why&#8221; &#8211; that reviewing those old employment documents is worth it. In a future post, I&#8217;ll go over the &#8220;how&#8221;. We&#8217;ll talk about some common misconceptions about Plain English documents and how to work with your attorney to get usable, solid docs in language that people actually understand. I&#8217;ll also show you what that gobbledygook up there became when we were all done with it.</p>
<p>In the meantime, if you have questions about your employment documents, <a title="Contact" href="http://currentemployment.net/contact-us/">drop me a line</a>.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=y8h_yZ0J9aw:Gg-swOJLZsM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=y8h_yZ0J9aw:Gg-swOJLZsM:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/currentemployment/aaa?a=y8h_yZ0J9aw:Gg-swOJLZsM:I9og5sOYxJI"><img src="http://feeds.feedburner.com/~ff/currentemployment/aaa?d=I9og5sOYxJI" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/currentemployment/aaa/~4/y8h_yZ0J9aw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://currentemployment.net/2011/09/thanks-for-the-contract-can-you-tell-me-what-it-says/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

