<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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"
	>

<channel>
	<title>Texas HR Law Update</title>
	<atom:link href="http://texashrlaw.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://texashrlaw.com</link>
	<description>Resources and Perspectives for Today's Marketplace</description>
	<pubDate>Thu, 19 Nov 2009 17:15:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
	<language>en</language>
			<item>
		<title>Are you wearing the white hat?  Eight ways to lose a non-compete case.</title>
		<link>http://texashrlaw.com/?p=500</link>
		<comments>http://texashrlaw.com/?p=500#comments</comments>
		<pubDate>Thu, 19 Nov 2009 17:15:56 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=500</guid>
		<description><![CDATA[About once a month I get a call from an attorney or a client asking me to get my scorched earth battle gear on because they want to go after an employee/former employee who is competing against them in business after having signed a non-compete agreement.
Sometimes, their stories are compelling and the facts are clear [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://texashrlaw.com/wp-content/uploads/2009/11/gallopingcowboytb.jpg"><img class="alignleft size-medium wp-image-501" title="gallopingcowboytb" src="http://texashrlaw.com/wp-content/uploads/2009/11/gallopingcowboytb.jpg" alt="" width="180" height="121" /></a>About once a month I get a call from an attorney or a client asking me to get my scorched earth battle gear on because they want to go after an employee/former employee who is competing against them in business after having signed a non-compete agreement.</p>
<p>Sometimes, their stories are compelling and the facts are clear that action must be taken.  Sometimes, however, the battle is one of principle that, ultimately, will cost the business owner more in heartache, time away from their own business, and legal warfare fees than the fight is worth.</p>
<p>Whenever the situation is such that the fight is one of pride and principle rather than of solid legal merit, I point my client or colleague to Jay Shepherd&#8217;s (<a href="http://www.shepherdlawgroup.com/" target="_blank">Shepherd Law Group</a>) excellent blog post <a href="http://bit.ly/NGVEn" target="_blank">&#8220;Eight Ways to Lose a Non-Compete Case.&#8221;</a></p>
<p>His bottom line advice: If you&#8217;re truly wearing the white hat (i.e., are the &#8220;good guy&#8221;), and your agreement is narrowly drafted, and your secrets or customer relationships are indeed  in imminent peril, then you&#8217;ve got a fighting chance of winning. Otherwise, wave goodbye to the former employee and get back to work.</p>
<p>Take a look at his 8 excellent tips and then ask yourself if you really want to saddle up that horse:</p>
<p><span id="more-500"></span></p>
<p>Gruntled Employees: Eight ways to lose a noncompete case http://bit.ly/NGVEn</p>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=500</wfw:commentRss>
		</item>
		<item>
		<title>New FMLA Amendments - family military leave entitlements</title>
		<link>http://texashrlaw.com/?p=490</link>
		<comments>http://texashrlaw.com/?p=490#comments</comments>
		<pubDate>Wed, 18 Nov 2009 18:47:09 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=490</guid>
		<description><![CDATA[
Last year, at just about this time, we were telling you about the new FMLA regs.
Nearly one year ago, the regulations implementing the Family and Medical Leave Act (FMLA) were substantially revised. Those revisions imposed certain new obligations on employers and created military leave entitlements for family members of military servicemembers who were injured in [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 9]><xml> Normal   0               false   false   false      EN-US   X-NONE   X-NONE                                                     MicrosoftInternetExplorer4 </xml><![endif]--><!--[if gte mso 9]><xml> </xml><![endif]--><!--  --></p>
<p><!--[if gte mso 10]> <mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	text-align:justify; 	line-height:200%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} --><!--[endif]--><a href="http://texashrlaw.com/wp-content/uploads/2009/11/fmla-compliance-is-difficult-in-manual-system1.jpg"><img class="alignleft size-thumbnail wp-image-496" title="fmla-compliance-is-difficult-in-manual-system1" src="http://texashrlaw.com/wp-content/uploads/2009/11/fmla-compliance-is-difficult-in-manual-system1-150x150.jpg" alt="" width="150" height="150" /></a>Last year, at just about this time, we were telling you about the <a href="http://texashrlaw.com/?p=158" target="_blank">new FMLA regs</a>.</p>
<p>Nearly one year ago, the regulations implementing the <a href="http://www.dol.gov/whd/fmla/index.htm" target="_blank">Family and Medical Leave Act (FMLA) </a>were substantially revised. Those revisions imposed certain new obligations on employers and created military leave entitlements for family members of military servicemembers who were injured in the line of active duty and for &#8220;qualifying exigencies&#8221; arising from a call to active duty.</p>
<p align="left">Guess what, there&#8217;s now even more newness to catch up on!</p>
<h2>Read more to find out what employers should do to ensure compliance&#8230;</h2>
<p align="left"><span id="more-490"></span></p>
<p>On October 28, 2009, President Obama signed the <a href="http://www.govtrack.us/congress/bill.xpd?bill=h111-2647" target="_blank">Defense Department authorization bill for fiscal year 2010</a>, which included new amendments to these provisions of the FMLA. These amendments expand the scope of the FMLA&#8217;s military leave entitlements and employers will need to revise any existing FMLA policy to ensure compliance with the amended FMLA provisions.</p>
<p align="left"><strong>Changes Affecting &#8220;Qualifying Exigency&#8221; Leave</strong></p>
<p>The military leave entitlement for a &#8220;qualifying exigency&#8221; previously applied to the spouse, son, daughter, or parent of an employee <em>on active duty (or who has been notified of an impending call to active duty) in the National Guard or Reserves &#8220;in support of a contingency operation.&#8221; </em></p>
<p><em></em>Under the amended statute, this FMLA leave entitlement has been expanded to cover the spouse, son, daughter, or parent of a servicemember who is a member of the regular Armed Forces. In addition, the entitlement no longer applies to a call to duty &#8220;in support of a contingency operation.&#8221; Instead, it applies to a call to &#8220;covered active duty,&#8221; which is defined as deployment to a foreign country under certain statutory provisions.</p>
<p align="left"><strong>Changes Affecting &#8220;Military Caregiver&#8221; Leave</strong></p>
<p>Under the pre-amendment statute, an employee could take up to 26 weeks of unpaid leave to care for a parent, spouse, child, or next of kin, who was a member of the Armed Forces (including National Guard and Reserves) and who was injured while on active duty. This provision has been expanded to allow for leave to care for a servicemember whose pre-existing injury or illness was &#8220;aggravated by service in the line of duty on active duty in the Armed Forces.&#8221;</p>
<p>Additionally, the amendments create a new leave to care for &#8220;a veteran who is undergoing medical treatment, recuperation, or therapy, for a serious injury or illness and who was a member of the Armed Forces (including a member of the National Guard or Reserves) at any time during the period of 5 years preceding the date on which the veteran undergoes that medical treatment, recuperation, or therapy.&#8221; The definition of a &#8220;serious illness or injury&#8221; has similarly been revised to cover a veteran&#8217;s &#8220;qualifying (as defined by the Secretary of Labor) illness or injury.&#8221; Because the Secretary of Labor has not issued regulations defining what constitutes a veteran&#8217;s qualifying injury or illness, this new leave entitlement is not yet effective but conservatism is recommended - employers should update policies now to ensure compliance with the law.</p>
<p align="left"><strong>What Should Employers Do?</strong></p>
<ul>
<li>Review your existing FMLA policies to determine if revisions are necessary for compliance with the amended statute&#8217;s military leave provisions.</li>
</ul>
<ul>
<li>If you haven&#8217;t yet revised your FMLA policy and forms to reflect the January 2009 regulations, get with your favorite labor and employment attorney and make sure you correct that asap!</li>
</ul>
<ul>
<li>Post the new FMLA poster when it becomes available from the <a href="http://webapps.dol.gov/libraryforms/" target="_blank">Department of Labor</a>.</li>
</ul>
<ul>
<li>Make sure that you are using the appropriate FMLA forms issued by the DOL after the January 2009 revisions to the regulations (click <a href="http://texashrlaw.com/?p=178" target="_blank">here</a> for the forms). Since the new forms aren&#8217;t yet available from the DOL wrt an employee requesting Qualifying Exigency or Military Caregiver leave, check back here often to see if the DOL has issued new forms reflecting the October 2009 amendments.</li>
</ul>
<p><!--[endif]--></p>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=490</wfw:commentRss>
		</item>
		<item>
		<title>EEOC Approves Proposed ADA Regulations for Public Comment</title>
		<link>http://texashrlaw.com/?p=473</link>
		<comments>http://texashrlaw.com/?p=473#comments</comments>
		<pubDate>Tue, 22 Sep 2009 21:53:58 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=473</guid>
		<description><![CDATA[


The Equal Employment Opportunity Commission (EEOC) recently approved a notice of proposed rulemaking regarding its regulations interpreting the Americans with Disabilities Act (ADA). A copy of the proposed regs can be found here (hat tip to @HR Hero).

Among other things, the proposed changes would:

Expand the list of major life activities to include things like bending, [...]]]></description>
			<content:encoded><![CDATA[<p><!--[endif]--></p>
<p class="MsoNormal"><a href="http://texashrlaw.com/wp-content/uploads/2009/09/disabilities1.jpeg"><img class="size-medium wp-image-475 alignleft" title="disabilities1" src="http://texashrlaw.com/wp-content/uploads/2009/09/disabilities1.jpeg" alt="" width="135" height="113" /></a></p>
<p class="MsoNormal">
<p class="MsoNormal">The Equal Employment Opportunity Commission (<a href="http://www.eeoc.gov/" target="_blank">EEOC</a>) recently approved a <a href="http://www.eeoc.gov/press/9-16-09f.html" target="_blank">notice of proposed rulemaking</a> regarding its regulations interpreting the Americans with Disabilities Act (ADA). A copy of the proposed regs can be found <a href="http://www.hrhero.com/eeoc/eeoc_proposedregulations.pdf" target="_blank">here</a> (hat tip to <a href="http://twitter.com/hrhero" target="_blank">@HR Hero</a>).</p>
<p class="MsoNormal">
<h1 class="MsoNormal" style="text-align: left;">Among other things, the proposed changes would:</h1>
<ul>
<li>Expand the list of major life activities to include things like bending, reading, reaching, sitting, interacting with others and communicating. The expansion enables individuals to more readily meet the threshold requirement of demonstrating that they are substantially limited in a &#8220;major life activity.&#8221;</li>
</ul>
<ul>
<li>Direct courts to apply a “common sense” comparison of the impaired employee&#8217;s limitations to those of the average person in the population, applying the standard that a condition need not significantly or severely restrict performance of any major life activity to be substantially limiting. Many courts (5th Circuit included) require a plaintiff to prove a substantial limitation in working by establishing statistics on the number of jobs the plaintiff could not perform due to impairment. Under the proposed regs, it appears that a statistical analysis as to the extent of a person’s limitation is not necessary to establish a substantial limitation in a major life activity.</li>
</ul>
<ul>
<li>Establish that specific medical conditions (autism, cancer, cerebral palsy, diabetes, epilepsy, HIV or AIDS, multiple sclerosis and muscular dystrophy, and individuals with depression, bipolar disorder, obsessive compulsive disorder, post-traumatic stress disorder, or schizophrenia) <strong><em>per se </em></strong><strong><em>disabilities</em></strong><strong><em> under the ADA</em></strong> — even if they are in remission or treated with medication — so long as they would &#8220;substantially limit&#8221; a major life activity when active.</li>
</ul>
<ul>
<li>Add “surgical intervention” to the list of mitigating measures (such as medication and assistive devices) that can no longer be taken into account when determining whether an individual’s medical condition rises to the level of disability.</li>
</ul>
<ul>
<li>Add “work” to the list of what is now identified as a major life activity.</li>
</ul>
<p style="text-align: left;" align="left">These proposed changes are big and if unchanged after the public comment period will likely lead to litigation as employers sort this out and employees seek reasonable accommodation.</p>
<p class="MsoNormal" style="text-align: left;" align="left">The public has 60 days to comment on these proposed regulations (pages 1-2 of the download provide instructions on how/where to comment).  Final regulations will likely be issued in the first quarter of 2010.</p>
<p><strong><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><span style="color: #800000;">When the 60-day period for public comment ends, the EEOC may revise its proposal in response to the comments it receives or adopt the regulations as issued. Meanwhile, because the ADA Amendments Act went into effect in January 2009, employers should exercise caution and take into account the proposed regulations when deciding whether someone is disabled under the ADA. </span></span></strong></p>
<p>A helpful Q&amp;A may be found <a href="http://www.eeoc.gov/policy/docs/qanda_adaaa_nprm.html" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=473</wfw:commentRss>
		</item>
		<item>
		<title>4 Tips to Ensure Compensation Record Retention Compliance after Ledbetter</title>
		<link>http://texashrlaw.com/?p=451</link>
		<comments>http://texashrlaw.com/?p=451#comments</comments>
		<pubDate>Fri, 18 Sep 2009 17:49:21 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Compliance]]></category>

		<category><![CDATA[Documents]]></category>

		<category><![CDATA[Employment]]></category>

		<category><![CDATA[General Management]]></category>

		<category><![CDATA[Small business]]></category>

		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[compensation]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[Fair pay]]></category>

		<category><![CDATA[Lilly Ledbetter]]></category>

		<category><![CDATA[record retention]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=451</guid>
		<description><![CDATA[
 Since its passage in January, the Lilly Ledbetter Fair Pay Act has caused concern for employers and we&#8217;re routinely asked - &#8220;how long do I need to keep compensation records on file?&#8221;








The Act resulted from Ledbetter’s claim against Goodyear Tire Company. She sued and claimed that her salary increases over a 20-year period had [...]]]></description>
			<content:encoded><![CDATA[<blockquote>
<p style="margin: 0in 0in 0.0001pt; text-align: left;" align="left"><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val=" " /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-margin-top-alt:auto; 	margin-right:0in; 	mso-margin-bottom-alt:auto; 	margin-left:0in; 	text-align:justify; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoPapDefault 	{mso-style-type:export-only; 	mso-margin-top-alt:auto; 	mso-margin-bottom-alt:auto; 	text-align:justify;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --><!--[if gte mso 10]> <mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin-top:auto; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:auto; 	mso-para-margin-left:0in; 	text-align:justify; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} --> <!--[endif]--><a href="http://texashrlaw.com/wp-content/uploads/2009/09/paycheck.jpg"><img class="alignleft size-medium wp-image-454" title="paycheck" src="http://texashrlaw.com/wp-content/uploads/2009/09/paycheck.jpg" alt="" width="170" height="170" /></a><span style="font-size: 12pt;">Since its passage in January, the Lilly Ledbetter Fair Pay Act has caused concern for employers and we&#8217;re routinely asked - <strong><em>&#8220;how long do I need to keep compensation records on file?&#8221;</em></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
</blockquote>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
<p style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">The Act resulted from Ledbetter’s claim against Goodyear Tire Company. She sued and claimed that her salary increases over a 20-year period had been based more on her gender than her work performance, in violation of federal law.</p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; text-align: left;" align="left">
<p style="text-align: left;" align="left">She was victorious in her jury trial, but the 11th Circuit Court of Appeals reversed. Ultimately, the US <a href="http://www.law.cornell.edu/supct/pdf/05-1074P.ZO" target="_blank">Supreme Court agreed</a> after finding that the discrimination had happened too long ago to be the basis for a claim.</p>
<p style="text-align: left;" align="left">Because their finding was based on the statutory 180-day time limit after the discrimination occurred, the Court issued a challenge to Congress to rectify the wording of Title VII, asking Congress to reconsider which events could trigger the time limit.</p>
<p style="text-align: left;" align="left"><a href="http://www.whitehouse.gov/briefing_room/LillyLedbetterFairPayActPublicReview/" target="_blank">The Ledbetter Act</a> solidifies the position that discrimination actually recurs with each discriminatory paycheck.  Thus, the period of time during which an employee or other affected person can file a lawsuit begins when the discriminatory practice is adopted; when the individual becomes subject to the decision or practice; or when the individual is affected by the application of the decision or practice.  As a result, the issuance of each paycheck falls within the new definition, so the statute of limitations begins anew with each subsequent discriminatory paycheck.</p>
<p style="text-align: left;" align="left"><strong><em>So what does this mean for your records retention policies?</em></strong></p>
<p style="text-align: left;" align="left">Under Ledbetter, decisions you make today can be reviewed well into the future, even after the people making policy and reviewing decisions are long gone. As a result, you need practices in place that help you defend how decisions are made and compensation levels are set.</p>
<h1 style="text-align: left;"><span style="color: #800000;">4 Tips to Ensure Compensation Record Retention Compliance</span></h1>
<p><span id="more-451"></span></p>
<p class="MsoNormal" style="text-align: left;" align="left"><span style="color: #800000;"><strong>Tip 1: Assess Your Compensation Practices</strong></span></p>
<p style="text-align: left;" align="left">Take time to make good decisions about pay and maintain records that document the consideration given to such decisions. Do you have enough documentation supporting how and why your people are paid what they’re paid?  Is the documentation maintained in such a way that someone representing the company 10 or 20 years down the line can easily access and then utilize the material for a successful defense of those decisions?</p>
<p class="MsoNormal" style="text-align: left;" align="left"><span style="color: #800000;"><strong>Tip 2: Maintain Those Records</strong></span></p>
<p style="text-align: left;" align="left">Indefinitely? Well, with the technology available today and the discovery rules currently in effect, electronic archiving is the way to go and it ensures that, yes, documents can be maintained indefinitely, if necessary. Make sure you’ve got an IT department to help set things up appropriately.</p>
<p class="MsoNormal" style="text-align: left;" align="left"><strong><span style="color: #800000;">Tip 3: Review Past Decisions</span></strong></p>
<p style="text-align: left;" align="left">Like Tip 1, careful review of compensation decisions helps ensure compliance. If the practice of your company is to have one manager or supervisor make decisions on pay, review that practice to determine whether it is defensible. Consider adopting a compensation review system that allows decisions to be reviewed with the same kind of scrutiny used in a termination or disciplinary scenario. Committee oversight, or at the very least, an additional set of eyes reviewing those decisions may be critical.</p>
<p style="text-align: left;" align="left"><strong><span style="color: #800000;">Tip 4: Train Decision Makers</span></strong></p>
<p style="text-align: left;" align="left">Ensure that whoever is making pay decisions for your company understands the implications of their actions – the decisions made on compensation today can now be challenged years down the line. Appropriate decisions and proper documentation supporting those decisions are vital when it comes to the future defense of same so it’s important that your compensation decision makers understand this and are trained appropriately.</p>
<p class="MsoNormal" style="text-align: left;" align="left"><strong><span style="color: #800000;">More than anything, the Ledbetter Act serves as a reminder of the importance of thinking ahead. Whether it’s a termination decision, a disciplinary decision, or a compensation decision, always keep in mind how you (or a future management team) will support and defend those decisions later.</span></strong><span style="font-size: 12pt;"><span style="color: #800000;"><strong> </strong> </span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=451</wfw:commentRss>
		</item>
		<item>
		<title>Management, Employee Retention, and&#8230;Fantasy Sports?</title>
		<link>http://texashrlaw.com/?p=430</link>
		<comments>http://texashrlaw.com/?p=430#comments</comments>
		<pubDate>Thu, 17 Sep 2009 16:23:39 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Employment]]></category>

		<category><![CDATA[General Management]]></category>

		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[employee evaluations]]></category>

		<category><![CDATA[employee retention]]></category>

		<category><![CDATA[human resources]]></category>

		<category><![CDATA[management]]></category>

		<category><![CDATA[profit]]></category>

		<category><![CDATA[turnover]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=430</guid>
		<description><![CDATA[I asked my brother to a Dallas Cowboys pre-season game last month in the new stadium.  50(ish)-yard line seats.  Right behind the squad.  Had to crane your neck at a 45-degree angle to see that gargantu-tron.  His response?  Can&#8217;t make it - I have Fantasy Football.
Since I know he&#8217;s a life-long Cowboys fan, I was [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://texashrlaw.com/wp-content/uploads/2009/09/football.jpeg"><img class="alignleft size-medium wp-image-431" title="football" src="http://texashrlaw.com/wp-content/uploads/2009/09/football.jpeg" alt="" width="150" height="98" /></a>I asked my brother to a Dallas Cowboys pre-season game last month in the <a href="http://stadium.dallascowboys.com/" target="_blank">new stadium</a>.  50(ish)-yard line seats.  Right behind the squad.  Had to crane your neck at a 45-degree angle to see that <a href="http://bit.ly/Am1Qa" target="_blank">gargantu-tron</a>.  His response?  Can&#8217;t make it - I have Fantasy Football.</p>
<p>Since I know he&#8217;s a life-long Cowboys fan, I was shocked.  Aghast.  Even a little miffed.  So I did some reading&#8230;what is this <a href="http://games.espn.go.com/frontpage" target="_blank">fantasy league</a> that has consumed the lives of professional colleagues, friends and family alike?</p>
<p>Here&#8217;s what I <a href="http://msn.foxsports.com/fantasy/story/6886008" target="_blank">learned</a>:</p>
<p><script type="text/javascript"><!--
          //document.getElementById('number_of_comments').innerHTML = commentCount+" Comments";</p>
<p>// --></script></p>
<p><!-- // Story Content // --><script type="text/javascript"><!--
   if(fanid.length &gt; 0 &amp;&amp; typeof(nflDefaultLeague)!= "undefined") {
       leagueId = nflDefaultLeague;
    //find teamId of default league (if exists)
    for(var i=0; i &lt; teamsInfo.length; i++){
      if(teamsInfo[i][4] == leagueId){
        defaultTeamId = teamsInfo[i][0];
      }
    }
    var fantasyLeaguePlayerJsPath = 'http://msn.foxsports.com' + '/nugget/200002_' + leagueId + '|||' + fanid;</p>
<p>  }</p>
<p>// --></script></p>
<p style="text-align: justify; padding-left: 30px;">Fantasy football is a game that allows fans to take an active role in professional football by creating their own team and competing with teams built by others.  Fans create their own roster of players by drafting talent from actual NFL teams and compete based on those players&#8217; real-life performances in NFL games.  Fantasy owners assume roles similar to that of NFL personnel — a combination of a scout, general manager and owner - drafting players and competing against friends and co-workers in a fantasy league for bragging rights as the best team.</p>
<p>The more I learned, the more I realized there are aspects of the game employers might incorporate into the workplace.</p>
<h2><strong><span style="color: #800000;">For example:</span></strong></h2>
<p><span id="more-430"></span></p>
<ul>
<li><span style="color: #800000;"><strong>Scout, General Manager, Owner</strong><span style="text-decoration: underline;"><strong><br />
</strong></span></span></li>
</ul>
<p style="padding-left: 30px;">This is, pure and simple, cross-training.  Could allowing, where appropriate, an employee to assume for a specific time period the role of a supervisor or counterpart in another department be an impetus for innovation and increased profit?  It would certainly lead to new levels of understanding between people and departments.</p>
<ul>
<li><span style="color: #800000;"><strong>Play Calling</strong><span style="text-decoration: underline;"><strong><br />
</strong></span></span></li>
</ul>
<p style="padding-left: 30px;">Are there departments in your organization where friendly competition could spur productivity?  A sales team comes to mind whereby each team creates &#8220;rosters of talent&#8221; from current staff and &#8220;game plans&#8221; for reaching specific company goals (to win!) at the end of a quarter.  To be successful, each individual on the team would certainly need to be engaged, know and understand the company goals, and know and understand all aspects of your business.  Expectations you probably have now.</p>
<ul>
<li><span style="color: #800000;"><strong>Win/Loss Record</strong></span></li>
</ul>
<p style="padding-left: 30px;">At the end of a season, there&#8217;s a record of Ws and Ls.  Same for a company with its year end balance sheet.  What mechanism(s) do you have in place that illustrates for employees what their role is within the organization and how their performance impacts their &#8220;teammates&#8221; and the company&#8217;s bottom line?  Is that once a year evaluation plan really doing the trick?</p>
<p>Sound out of bounds?  In sports terms, it&#8217;s really a question of whether you want your team missing the playoffs year after year or leading their division.</p>
<p>If nothing else, know your team and what&#8217;s important to them.  Maybe the salary cap is worrying your rainmaker.  Maybe a key player, like the Red Sox&#8217;s Dustin Pedroia, is anxious about a <a href="http://www.boston.com/sports/baseball/redsox/articles/2009/07/08/red_sox_pedroia_benefits_from_embrace_of_hardball8217s_softer_side/" target="_blank">family priority</a>.</p>
<p>Under the management style Pedroia experienced, it&#8217;s probably no coincidence that &#8220;the Red Sox are the only team to have won the World Series twice this decade&#8221; and have led the American League much of this season   - thanks to <a href="http://www.gruntledemployees.com/gruntled_employees/2009/07/divisionleading-employee-management.html" target="_blank">Jay Shepherd</a> for the Red Sox edification and an excellent post on &#8220;division-leading employee management&#8221;.</p>
<p>Whether it&#8217;s sport or commercial commerce, teams strive to win.  If that&#8217;s what you want from your team, remember what&#8217;s important to your players - higher company profits and lowered employee turnover will be the likely result.</p>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=430</wfw:commentRss>
		</item>
		<item>
		<title>Top Ten HR Documentation Blunders</title>
		<link>http://texashrlaw.com/?p=416</link>
		<comments>http://texashrlaw.com/?p=416#comments</comments>
		<pubDate>Wed, 16 Sep 2009 18:35:52 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Affirmative Action]]></category>

		<category><![CDATA[Compliance]]></category>

		<category><![CDATA[Documents]]></category>

		<category><![CDATA[Employment]]></category>

		<category><![CDATA[General Management]]></category>

		<category><![CDATA[IRS]]></category>

		<category><![CDATA[Immigration]]></category>

		<category><![CDATA[Small business]]></category>

		<category><![CDATA[Supreme Court]]></category>

		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[Employee]]></category>

		<category><![CDATA[evaluation]]></category>

		<category><![CDATA[human resources]]></category>

		<category><![CDATA[litigation]]></category>

		<category><![CDATA[top ten]]></category>

		<category><![CDATA[trial]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=416</guid>
		<description><![CDATA[
I was asked to speak to a group of up and coming business owners recently through a great San Antonio organization, the South Texas Women&#8217;s Business Center, on HR Essentials for employers.  It was encouraging to see the turnout and the desire the group exhibited for wanting to &#8220;do the right thing&#8221; when it comes [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://texashrlaw.com/wp-content/uploads/2009/09/women-logo1.jpg"><img class="alignleft size-medium wp-image-419" title="women-logo1" src="http://texashrlaw.com/wp-content/uploads/2009/09/women-logo1.jpg" alt="" width="123" height="170" /></a></p>
<p>I was asked to speak to a group of up and coming business owners recently through a great San Antonio organization, the <a href="http://www.stwbc.com/webpages.asp?wpid=1" target="_blank">South Texas Women&#8217;s Business Center</a>, on HR Essentials for employers.  It was encouraging to see the turnout and the desire the group exhibited for wanting to &#8220;do the right thing&#8221; when it comes to managing employees.</p>
<p>We covered routine issues, such as &#8220;<a href="http://www.twc.state.tx.us/ui/lablaw/posters.html" target="_blank">what types of posters am I required to maintain in the workplace</a>,&#8221; and discussed the problems inherent in misclassifying an <a href="http://texashrlaw.com/?p=149" target="_blank">employee as an independent contractor</a> or a <a href="http://texashrlaw.com/?p=404" target="_blank">non-exempt employee as exempt</a>.</p>
<p>One take-away that I wanted to share here are the Top Ten Blunders employers want to avoid when it comes to documenting employment issues.  It&#8217;s been my experience that if employers can avoid the following, they&#8217;re on the right track:</p>
<h1><span style="color: #800000;"><strong>Top Ten HR Documentation Blunders</strong></span></h1>
<p><span id="more-416"></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>1.  <span style="text-decoration: underline;">Unsigned or undated documents</span></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>This is the No. 1 blunder. Sign and date everything and have the employee do the same.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>2.  <span style="text-decoration: underline;">Illegibility</span></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>In court, neatness counts; and, in some cases-saves you!</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>3.  <span style="text-decoration: underline;">Late documentation</span></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>Judges and juries look doubtfully at disciplinary or other reports written weeks or months after the incident they describe.<span> </span>Timeliness is key.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>4.  <span style="text-decoration: underline;">Inaccuracy<span> </span></span></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>Facts need to be correct in all documents. Even one error makes the entire document suspect. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>5.  <span style="text-decoration: underline;">Unsupported conclusions</span></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>Fact specific statements by objective witnesses support your decisions.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>6.  <span style="text-decoration: underline;">Waffling</span></strong> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>Vagueness without objective, quantifiable measures hurts more than helps.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>7.  <span style="text-decoration: underline;">Don’t make excuses</span></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>Don’t make excuses in order to be nice. Be factual.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>8.  <span style="text-decoration: underline;">Don’t lie…even to be nice!</span></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>Credibility is everything.<span> </span>A fabricated statement becomes Exhibit “A” at trial.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>9.  <span style="text-decoration: underline;">Be consistent</span></strong></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>Treat all employees the same. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.25in;"><span><strong>10.  <span style="text-decoration: underline;">Don&#8217;t miss the forest for the trees</span></strong> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;"><span>Writing every small infraction may sound insignificant; however, documentation tells the story that either supports your defense or sinks your ship.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in;">
<h2 class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.75in; text-align: justify;"><span style="color: #800000;"><strong>What story does your documentation tell?</strong></span></h2>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 1in;"><span> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;">
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=416</wfw:commentRss>
		</item>
		<item>
		<title>New EEOC Commissioner Nominated</title>
		<link>http://texashrlaw.com/?p=412</link>
		<comments>http://texashrlaw.com/?p=412#comments</comments>
		<pubDate>Tue, 15 Sep 2009 14:32:18 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Compliance]]></category>

		<category><![CDATA[EEOC]]></category>

		<category><![CDATA[Legislation]]></category>

		<category><![CDATA[Obama Administration]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=412</guid>
		<description><![CDATA[ On Monday, President Obama announced his intent to nominate disability and gay-rights expert, Chai R. Feldblum, for one of the five Commissioner spots on the Equal Employment Opportunity Commission.  Feldblum is a Professor of Law at the Georgetown University Law Center where she has taught since 1991.  Feldblum previously served as Legislative Counsel to [...]]]></description>
			<content:encoded><![CDATA[<p><img class="setimage" src="http://www.tips-q.com/files/u1/feldblum.jpg" alt="Chai Feldblum" width="98" height="120" /> On Monday, President Obama <a href="http://www.whitehouse.gov/the_press_office/President-Obama-Announces-More-Key-Administration-Posts-9/14/09/" target="_blank">announced</a> his intent to nominate disability and gay-rights expert, Chai R. Feldblum, for one of the five Commissioner spots on the Equal Employment Opportunity Commission.  Feldblum is a Professor of Law at the Georgetown University Law Center where she has taught since 1991.  Feldblum previously served as Legislative Counsel to the AIDS Project of the American Civil Liberties Union.  In this role, she developed legislation, analyzed policy on various AIDS-related issues, and played a leading role in the drafting of the Americans with Disabilities Act of 1990 and, later as a law professor, in the passage of the ADA Amendments Act of 2008.  Feldblum has also worked on advancing lesbian, gay, bisexual and transgender rights and has been a leading expert on the Employment Nondiscrimination Act.  Feldblum clerked for Judge Frank Coffin and for Supreme Court Justice Harry A. Blackmun.  She received her J.D. from Harvard Law School and B.A. from Barnard College.</p>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=412</wfw:commentRss>
		</item>
		<item>
		<title>Department of Labor Targeting Wage and Hour Violators</title>
		<link>http://texashrlaw.com/?p=404</link>
		<comments>http://texashrlaw.com/?p=404#comments</comments>
		<pubDate>Wed, 09 Sep 2009 17:22:34 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Compliance]]></category>

		<category><![CDATA[Department of Labor]]></category>

		<category><![CDATA[Employment]]></category>

		<category><![CDATA[General Management]]></category>

		<category><![CDATA[Small business]]></category>

		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[blackberry]]></category>

		<category><![CDATA[business owner]]></category>

		<category><![CDATA[comp time]]></category>

		<category><![CDATA[DOL]]></category>

		<category><![CDATA[Employee]]></category>

		<category><![CDATA[employer]]></category>

		<category><![CDATA[Fair Labor Standards Act]]></category>

		<category><![CDATA[FLSA]]></category>

		<category><![CDATA[litigation]]></category>

		<category><![CDATA[manager]]></category>

		<category><![CDATA[off the clock]]></category>

		<category><![CDATA[overtime]]></category>

		<category><![CDATA[salary]]></category>

		<category><![CDATA[Solis]]></category>

		<category><![CDATA[Wage and Hour]]></category>

		<category><![CDATA[wages]]></category>

		<category><![CDATA[workweek]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=404</guid>
		<description><![CDATA[
The National Law Journal reports today that the Department of Labor is stepping up its enforcement of wage and hour violations by hiring 250 additional wage and hour investigators.  To drive the point home, Labor Secretary, Hilda L. Solis, has vowed to &#8220;make use of the full weight of [her] authority to find and prosecute [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://texashrlaw.com/wp-content/uploads/2009/09/lawsuits3.jpg"><img class="alignnone size-thumbnail wp-image-409" title="lawsuits3" src="http://texashrlaw.com/wp-content/uploads/2009/09/lawsuits3-150x150.jpg" alt="" width="150" height="150" /></a></p>
<p>The <a href="http://www.law.com/jsp/nlj/index.jsp" target="_blank">National Law Journal</a> reports today that the Department of Labor is stepping up its enforcement of wage and hour violations by <a href="http://www.law.com/newswire/cache/1202433665519.html" target="_blank">hiring 250 additional wage and hour investigators</a>.  To drive the point home, Labor Secretary, Hilda L. Solis, has <a href="http://news.prnewswire.com/ViewContent.aspx?ACCT=109&amp;STORY=/www/story/09-02-2009/0005087188&amp;EDATE=" target="_blank">vowed</a> to &#8220;make use of the full weight of [her] authority to find and prosecute violators.&#8221;</p>
<p>The article reports that in a study of 4,000 low-wage workers,  76% had worked overtime for which they were not paid time-and-a-half, 26% were paid less than minimum wage, and front-line workers in low-wage industries lose more than $56.4 million per week as a result of employment and labor law violations.</p>
<p><strong>The Law<br />
</strong></p>
<p>The coverage of the Fair Labor Standards Act (FLSA) is very broad and almost every employee is covered.  The Act requires that covered employees in the US be paid at least the federal minimum wage for each hour they work and overtime pay at one and one-half the employee&#8217;s regular rate of pay for all hours worked over 40 in a workweek.</p>
<p>If an employee complains or participates in a legal proceeding under the FLSA, it is a violation for the employer to fire or in any other manner discriminate against        the employee for engaging in such activity and, under certain facts, doing so can result in criminal prosecution and a fine up to $10,000.  A second conviction may result in imprisonment.</p>
<p>Employers who willfully or repeatedly violate the minimum wage or overtime        pay requirements are subject to a civil money penalty of up to $1,100 for        each such violation.</p>
<p>Such claims are popular with attorneys because the FLSA includes a provision for liquidated (or double) damages.  Thus, if an employee claims $5,000 of unpaid overtime compensation, the statute&#8217;s liquidated damages provision brings an employer&#8217;s potential liability to $10,000.  In addition, the Act provides for attorney&#8217;s fees and costs - regardless of the amount recovered!  In other words - while the employee may recover $5,000, the attorney&#8217;s fees may be in excess of that amount; and, under the FLSA he or she is entitled to that amount and any costs associated with the litigation.</p>
<p><strong>Common Pitfalls<br />
</strong></p>
<p>With the DOL&#8217;s pledge to increase enforcement, employers must internally examine their pay practices to avoid the panic that a knock on the door from the DOL can bring!</p>
<p>The law can be confusing.  Here are some pitfalls to avoid:</p>
<ul>
<li><strong>Calculate overtime correctly.</strong> The rate of overtime is one-and-a-half times the employee&#8217;s regular rate of pay.  It must be paid for hours worked beyond 40 in a workweek.  It must be paid in wages and not in equivalent time off or goods.</li>
<li><strong>&#8220;Off the clock&#8221; does not necessarily mean off payroll. </strong>The law requires that non-exempt employees be paid for <em>work</em> completed off the clock - even if it&#8217;s done voluntarily.</li>
<li><strong>Salaried Managers Don&#8217;t Get Overtime. </strong>Giving an employee a salary or high-sounding job title such as &#8220;director of production&#8221; or &#8220;development manager&#8221; makes no difference, if the employee&#8217;s job duties do not satisfy the criteria found in the DOL&#8217;s &#8220;duties&#8221; test for an exemption category.  A DOL investigator looks right past titles and focuses instead on the nature of the job and how the employee does the job.</li>
<li><strong>But we give Comp Time!</strong> Private employers may use an informal variety of compensatory time by adjusting the schedule within the same workweek to ensure that total hours worked do not exceed 40. However, overtime hours in most cases may not be averaged out over a longer period of time. Otherwise, any overtime worked within a workweek must be paid for that workweek.</li>
<li><strong>The Ubiquitous Blackberry </strong>The jury is still out on whether employers are required to pay hourly workers for responding to calls, e-mails, and messages at night and after hours.  Case law is revving up on this issue, though.  As a result, employers should set policy about the use of such technology to avoid the claims that are sure to come.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=404</wfw:commentRss>
		</item>
		<item>
		<title>E-Verify Effective Today</title>
		<link>http://texashrlaw.com/?p=398</link>
		<comments>http://texashrlaw.com/?p=398#comments</comments>
		<pubDate>Tue, 08 Sep 2009 18:17:28 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=398</guid>
		<description><![CDATA[
If your company is a (specific type of) Federal Contractor, take note that as of today (September 8, 2009) the United States Citizenship and Immigration Services is requiring you to use the E-Verify system to verify your employees&#8217; (existing and new) eligibility to work in the United States.
The Federal Acquisition Rule; Case 2007-013; Employment Eligibility [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://texashrlaw.com/wp-content/uploads/2009/09/logo.jpg"><img class="alignnone size-medium wp-image-399" title="logo" src="http://texashrlaw.com/wp-content/uploads/2009/09/logo.jpg" alt="" width="213" height="83" /></a></p>
<p>If your company is a (specific type of) Federal Contractor, take note that as of today (September 8, 2009) the <a href="http://www.uscis.gov/portal/site/uscis/menuitem.5af9bb95919f35e66f614176543f6d1a/?vgnextoid=109cc691d0673210VgnVCM100000082ca60aRCRD&amp;vgnextchannel=68439c7755cb9010VgnVCM10000045f3d6a1RCRD" target="_blank">United States Citizenship and Immigration Services</a> is requiring you to use the E-Verify system to verify your employees&#8217; (existing and new) eligibility to work in the United States.</p>
<p>The <a href="http://edocket.access.gpo.gov/2008/E8-26906.htm" target="_blank">Federal Acquisition Rule; Case 2007-013; Employment Eligibility Verification</a> extends use of the E-Verify system to covered federal contractors and subcontractors, including those who receive American Recovery and Reinvestment Act funds.  Applicable federal contracts awarded and solicitations issued after Sept. 8 will include a clause committing government contractors to use E-Verify.</p>
<p><strong>What Federal Contractors are Subject to E-Verify?</strong></p>
<p>If your company is awarded a prime contract with a period of performance longer than 120-days and a value above $100,000 (not including only COTS items or a contract performed outside of the US), then you must sign up for the program within 30-days.  In addition, if the prime contract includes the E-Verify clause, the requirement extends to any subcontract flowing from the prime contract for services or construction valued at greater than $3000.</p>
<p>E-Verify must be used to confirm that all new hires, whether employed on a federal contract or not, and existing employees directly working on these contracts are legally authorized to work in the United States.</p>
<p>The E-Verify requirement is triggered on the contract or subcontract award date.</p>
<p>The WSJ has an interesting story on the topic <a href="http://online.wsj.com/article/SB125236773673291025.html" target="_blank">here</a> (subscription may be required).</p>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=398</wfw:commentRss>
		</item>
		<item>
		<title>Non-competes and the Employer</title>
		<link>http://texashrlaw.com/?p=388</link>
		<comments>http://texashrlaw.com/?p=388#comments</comments>
		<pubDate>Sat, 05 Sep 2009 19:27:26 +0000</pubDate>
		<dc:creator>Mary Ann Hisel</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[bet the business]]></category>

		<category><![CDATA[business owner]]></category>

		<category><![CDATA[competition]]></category>

		<category><![CDATA[employer]]></category>

		<category><![CDATA[enforceable]]></category>

		<category><![CDATA[litigation]]></category>

		<category><![CDATA[non-compete]]></category>

		<guid isPermaLink="false">http://texashrlaw.com/?p=388</guid>
		<description><![CDATA[With the economy in the shape it&#8217;s in, I&#8217;ve seen a rise in disputes involving business owners wanting to enforce their non-compete agreements.  This year has provided them with some good case law to support the enforceability of properly-crafted non-compete agreements.
As we&#8217;ve learned over the years, a good non-compete contains reasonable limitations as to time, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://texashrlaw.com/wp-content/uploads/2009/09/money-103x150.jpg"><img class="alignleft size-medium wp-image-389" title="money-103x150" src="http://texashrlaw.com/wp-content/uploads/2009/09/money-103x150.jpg" alt="" width="103" height="150" /></a>With the economy in the shape it&#8217;s in, I&#8217;ve seen a rise in disputes involving business owners wanting to enforce their non-compete agreements.  This year has provided them with some <a href="http://texashrlaw.com/?p=340" target="_blank">good case law</a> to support the enforceability of properly-crafted non-compete agreements.</p>
<p>As we&#8217;ve learned over the years, a good non-compete contains reasonable limitations as to time, geographical area, and scope of activity to be restrained.  The Houston 1st Court of Appeals recently affirmed that position in <a href="http://www.houston-opinions.com/files/1stCoA-2009-Gallagher-Healthcare-Inc-Services-v-Vogelsang-by-Keyes-non-competeenforceable.html" target="_blank"><em>Gallagher Healthcare Ins. Svcs. v. Vogelsang</em></a>, even where there was disagreement about whether the company had actually given the employee confidential/proprietary information in exchange for her promise not to compete and where the agreement did not clearly identify a geographical area to be limited.</p>
<p>The appellate court found that the employer&#8217;s conclusory statements offered in an affidavit vigorously challenged by Ms. Vogelsang were enough to serve as proof that its confidential information was an interest worthy of protection and that such information actually had been given to Ms. Vogelsang so that she could perform her job.</p>
<p>As for the lack of a clearly identifiable geographical area to be limited, the Court recognized that a properly crafted non-compete covenant limited to an employer&#8217;s clients/customers can serve as a reasonable alternative to an express specification of a geographical limitation.  Since Ms. Vogelsang&#8217;s agreement restrained her from any and all activity with clients she had worked with while employed by the company,  the Court reversed the trial court and rendered judgment that the non-compete was enforceable.</p>
<p>Now&#8230;this is all well and good.  Do you want to take a wild guess, though, as to what the employer in this case spent defending its position through the trial court proceedings and up to the appellate court?  I can guarantee you it wasn&#8217;t chump change.  And that&#8217;s without even considering the time key employees had to spend gearing up for trial, depositions, etc.  Could you and your business afford such an expense?</p>
<p>I think the real take-away for an employer is to realize that cutting corners or using a cut and paste/boiler plate agreement that you&#8217;ve obtained from a friend is all fine and good - right up until the moment it gets challenged and you are sweating whether it&#8217;s enforceable or not and your critical client and proprietary information (indeed, your Company and your livelihood!) is at stake.</p>
<p>Don&#8217;t let yourself or your company get caught in that situation.</p>
]]></content:encoded>
			<wfw:commentRss>http://texashrlaw.com/?feed=rss2&amp;p=388</wfw:commentRss>
		</item>
	</channel>
</rss>
