<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: New hire attacks employee: Was it HR&#8217;s fault?</title>
	<atom:link href="http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/</link>
	<description>Up-to-the-minute cases and law impacting HR</description>
	<lastBuildDate>Fri, 17 Jul 2009 14:01:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: mike r</title>
		<link>http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-3069</link>
		<dc:creator>mike r</dc:creator>
		<pubDate>Thu, 08 Jan 2009 15:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrlegalnews.com/?p=691#comment-3069</guid>
		<description>To Keith Hamm:

I am in FULL agreement.  In the words of some great person....What HE said.</description>
		<content:encoded><![CDATA[<p>To Keith Hamm:</p>
<p>I am in FULL agreement.  In the words of some great person&#8230;.What HE said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Hamm, SPHR</title>
		<link>http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-3068</link>
		<dc:creator>Keith Hamm, SPHR</dc:creator>
		<pubDate>Thu, 08 Jan 2009 15:08:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrlegalnews.com/?p=691#comment-3068</guid>
		<description>We document the reason(s) for any employee leaving our organization. If asked, I provide responses based on that documentation only. All employment references go through me. I personally review each exit evaluation for any hint of bias or other danger signals. Facts are a great defense. Most of this goes back to the documentation. We train our supervisors and management very well in how to document actions and behaviors. This works in our favor as well as the employees&#039;. A good employee exiting can count on a good reference and we can back that up with specifics as well. Getting supervisors to document (and do it correctly) is a hard habit to start, but well worth the effort.</description>
		<content:encoded><![CDATA[<p>We document the reason(s) for any employee leaving our organization. If asked, I provide responses based on that documentation only. All employment references go through me. I personally review each exit evaluation for any hint of bias or other danger signals. Facts are a great defense. Most of this goes back to the documentation. We train our supervisors and management very well in how to document actions and behaviors. This works in our favor as well as the employees&#8217;. A good employee exiting can count on a good reference and we can back that up with specifics as well. Getting supervisors to document (and do it correctly) is a hard habit to start, but well worth the effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike r</title>
		<link>http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-3061</link>
		<dc:creator>mike r</dc:creator>
		<pubDate>Wed, 07 Jan 2009 22:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrlegalnews.com/?p=691#comment-3061</guid>
		<description>I think there are more protections for employers providing information than we usually think.  

I believe that it is prudent to provide only &quot;factual&quot; information that is relevant to the position they are applying for.  Normally I provide the basics; name rank and serial number.  If I am provided inforamtion about what job the employee is applying, then I can provide more relevant information. If I am asked for specific information about performance, I may provide my evaluation of the employee&#039;s performance (judgment), but will back it up with factual behavioral evidence.    

For example, we provide residential care in some of our programs.  If I have an employee who blurred their professional boundaries and fraternized with a client and they were applying for a cashier&#039;s position at a restaurant, then the fraternization issue is not an issue and would not be shared in the reference.  However, if they were going to work in a nursing home or to do home health care, I would make sure that it is included in the reference.</description>
		<content:encoded><![CDATA[<p>I think there are more protections for employers providing information than we usually think.  </p>
<p>I believe that it is prudent to provide only &#8220;factual&#8221; information that is relevant to the position they are applying for.  Normally I provide the basics; name rank and serial number.  If I am provided inforamtion about what job the employee is applying, then I can provide more relevant information. If I am asked for specific information about performance, I may provide my evaluation of the employee&#8217;s performance (judgment), but will back it up with factual behavioral evidence.    </p>
<p>For example, we provide residential care in some of our programs.  If I have an employee who blurred their professional boundaries and fraternized with a client and they were applying for a cashier&#8217;s position at a restaurant, then the fraternization issue is not an issue and would not be shared in the reference.  However, if they were going to work in a nursing home or to do home health care, I would make sure that it is included in the reference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-3059</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 07 Jan 2009 20:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrlegalnews.com/?p=691#comment-3059</guid>
		<description>This unveils a dilemma for many: You don&#039;t want to give out too much reference info for fear of being held liable for defamation while at the same time you&#039;re trying to glean as much info as possible (from other employers) about potential new-hires to avoid negligent hiring/retention actions. To wit, Karin&#039;s &quot;Catch-22&quot; analogy rings quite true....God Bless America!</description>
		<content:encoded><![CDATA[<p>This unveils a dilemma for many: You don&#8217;t want to give out too much reference info for fear of being held liable for defamation while at the same time you&#8217;re trying to glean as much info as possible (from other employers) about potential new-hires to avoid negligent hiring/retention actions. To wit, Karin&#8217;s &#8220;Catch-22&#8243; analogy rings quite true&#8230;.God Bless America!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Judy Buckley</title>
		<link>http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-3053</link>
		<dc:creator>Judy Buckley</dc:creator>
		<pubDate>Wed, 07 Jan 2009 17:32:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrlegalnews.com/?p=691#comment-3053</guid>
		<description>Karin is probably right that the new employee could sue, but I believe I&#039;ve heard the person attacked also could sue the previous employer for not disclosing that information - if she found out about it. It puts both the old and new employers in a difficult position - if the info were revealed, the new employer could either not hire the person or let him know he was being watched. All this because that person couldn&#039;t or wouldn&#039;t behave appropriately.</description>
		<content:encoded><![CDATA[<p>Karin is probably right that the new employee could sue, but I believe I&#8217;ve heard the person attacked also could sue the previous employer for not disclosing that information &#8211; if she found out about it. It puts both the old and new employers in a difficult position &#8211; if the info were revealed, the new employer could either not hire the person or let him know he was being watched. All this because that person couldn&#8217;t or wouldn&#8217;t behave appropriately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike r</title>
		<link>http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-3052</link>
		<dc:creator>mike r</dc:creator>
		<pubDate>Wed, 07 Jan 2009 17:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrlegalnews.com/?p=691#comment-3052</guid>
		<description>I wonder if the previous employer who characterized the employee&#039;s firing as a &quot;dispute with a co-worker&quot; could be sued.  

As I recall there were several cases a few years ago where the previous employer FAILED to provide relevant information during a reference check and was held accountable in court.  

As I recall, one case involved an employee who was fired for bringing a gun to work.  He was fired and when he applied to work at another company his reference check came back clean.  
Unfortunately, he shot his co-workers at his new job.  The survivors sued the company and it was found that the previous company did not provide the needed information.  Then the previous company was sued and lost the case.</description>
		<content:encoded><![CDATA[<p>I wonder if the previous employer who characterized the employee&#8217;s firing as a &#8220;dispute with a co-worker&#8221; could be sued.  </p>
<p>As I recall there were several cases a few years ago where the previous employer FAILED to provide relevant information during a reference check and was held accountable in court.  </p>
<p>As I recall, one case involved an employee who was fired for bringing a gun to work.  He was fired and when he applied to work at another company his reference check came back clean.<br />
Unfortunately, he shot his co-workers at his new job.  The survivors sued the company and it was found that the previous company did not provide the needed information.  Then the previous company was sued and lost the case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karin</title>
		<link>http://www.hrlegalnews.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-3048</link>
		<dc:creator>Karin</dc:creator>
		<pubDate>Wed, 07 Jan 2009 15:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrlegalnews.com/?p=691#comment-3048</guid>
		<description>Isn&#039;t that a catch 22 in regards to the former employer verifying employment, etc?

Couldn&#039;t the new hire sue for defimation of character if he didn&#039;t get the position?  Getting the truth from a former employer about work history isn&#039;t as easy as it once was.</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t that a catch 22 in regards to the former employer verifying employment, etc?</p>
<p>Couldn&#8217;t the new hire sue for defimation of character if he didn&#8217;t get the position?  Getting the truth from a former employer about work history isn&#8217;t as easy as it once was.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

