<?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.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/</link>
	<description>Headlines and advice for the practicing recruiter</description>
	<lastBuildDate>Mon, 20 Jun 2011 04:03:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Pat S</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2073</link>
		<dc:creator>Pat S</dc:creator>
		<pubDate>Fri, 03 Oct 2008 18:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2073</guid>
		<description>Let&#039;s all move to Ohio!</description>
		<content:encoded><![CDATA[<p>Let&#8217;s all move to Ohio!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2072</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Fri, 03 Oct 2008 18:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2072</guid>
		<description>Kim - Excellent question. This recommendation to our hiring authorities is relatively recent and I have not yet received feedback on its use. Of course, a basic issue is the extent to which any particular hiring authority (manager) feels assertive or empowered enough to utilize it. Overcoming fear of &quot;confrontation&quot; is one of the first steps we have to deal with. I can understand that it would take a healthy level of assertiveness to first attempt a &quot;warning&quot; about &quot;secondary liability&quot; with a front-line HR person, followed by a request to speak to a &quot;supervisor&quot; when the expected party line is given as a first response. In our hiring process training, we (HR) are encouraging the hiring managers to do this but are explicitly offering support and consultation if they would like assistance. Since it&#039;s still such a new strategy for us, we have not had time to assess its effectiveness. Another benefit for us is that we are located in Ohio, a state that holds employers harmless for sharing job performance data, as long as it&#039;s truthful and focused on the job-specific criteria, and especially if there were potential liability issues related to a former employee&#039;s behavior on the job.

Hope this helps! :)</description>
		<content:encoded><![CDATA[<p>Kim &#8211; Excellent question. This recommendation to our hiring authorities is relatively recent and I have not yet received feedback on its use. Of course, a basic issue is the extent to which any particular hiring authority (manager) feels assertive or empowered enough to utilize it. Overcoming fear of &#8220;confrontation&#8221; is one of the first steps we have to deal with. I can understand that it would take a healthy level of assertiveness to first attempt a &#8220;warning&#8221; about &#8220;secondary liability&#8221; with a front-line HR person, followed by a request to speak to a &#8220;supervisor&#8221; when the expected party line is given as a first response. In our hiring process training, we (HR) are encouraging the hiring managers to do this but are explicitly offering support and consultation if they would like assistance. Since it&#8217;s still such a new strategy for us, we have not had time to assess its effectiveness. Another benefit for us is that we are located in Ohio, a state that holds employers harmless for sharing job performance data, as long as it&#8217;s truthful and focused on the job-specific criteria, and especially if there were potential liability issues related to a former employee&#8217;s behavior on the job.</p>
<p>Hope this helps! <img src='http://www.hrrecruitingalert.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim S</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2070</link>
		<dc:creator>Kim S</dc:creator>
		<pubDate>Fri, 03 Oct 2008 17:34:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2070</guid>
		<description>This is a question in regards to the comment Marc left, what have your hiring authorities experienced using this technique?  Have they been able to get more than the typical &quot;safe&quot; reference responses?</description>
		<content:encoded><![CDATA[<p>This is a question in regards to the comment Marc left, what have your hiring authorities experienced using this technique?  Have they been able to get more than the typical &#8220;safe&#8221; reference responses?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay M</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2069</link>
		<dc:creator>Kay M</dc:creator>
		<pubDate>Fri, 03 Oct 2008 17:13:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2069</guid>
		<description>I feel at times HR&#039;s hands are tied on what we can and cannot say when we terminate an employee for cuase.</description>
		<content:encoded><![CDATA[<p>I feel at times HR&#8217;s hands are tied on what we can and cannot say when we terminate an employee for cuase.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat S</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2065</link>
		<dc:creator>Pat S</dc:creator>
		<pubDate>Fri, 03 Oct 2008 16:15:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2065</guid>
		<description>I wonder if the previous employer could be at fault for not revealing the groping incident.</description>
		<content:encoded><![CDATA[<p>I wonder if the previous employer could be at fault for not revealing the groping incident.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2064</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Fri, 03 Oct 2008 16:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2064</guid>
		<description>It is my understanding, however, that the victim would be able to go after the perpetrator&#039;s prior employer for providing what amounts to a &quot;negligent reference.&quot; We are currently encouraging our hiring authorities to mention this to referees when they are faced with resistance in getting any detailed job performance information regarding a prospective employee. I&#039;d welcome others&#039; opinions on this matter.</description>
		<content:encoded><![CDATA[<p>It is my understanding, however, that the victim would be able to go after the perpetrator&#8217;s prior employer for providing what amounts to a &#8220;negligent reference.&#8221; We are currently encouraging our hiring authorities to mention this to referees when they are faced with resistance in getting any detailed job performance information regarding a prospective employee. I&#8217;d welcome others&#8217; opinions on this matter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2061</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Fri, 03 Oct 2008 15:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2061</guid>
		<description>Couldn&#039;t or shouldn&#039;t his previous employer be liable for negligent referencing?</description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t or shouldn&#8217;t his previous employer be liable for negligent referencing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2058</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Fri, 03 Oct 2008 15:45:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2058</guid>
		<description>I&#039;m wondering what the follow-up question(s) were to the &quot;dispute with a co-woker&quot; red flag response.</description>
		<content:encoded><![CDATA[<p>I&#8217;m wondering what the follow-up question(s) were to the &#8220;dispute with a co-woker&#8221; red flag response.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jackie T - SPHR</title>
		<link>http://www.hrrecruitingalert.com/new-hire-attacks-employee-was-it-hrs-fault/comment-page-1/#comment-2055</link>
		<dc:creator>Jackie T - SPHR</dc:creator>
		<pubDate>Fri, 03 Oct 2008 15:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrrecruitingalert.com/?p=263#comment-2055</guid>
		<description>Just shows that completing the due dilligence when hiring a new employees is valuable and will support your business should a situation like this occur.</description>
		<content:encoded><![CDATA[<p>Just shows that completing the due dilligence when hiring a new employees is valuable and will support your business should a situation like this occur.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

