<?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: How to Create a Visitor’s Safety Policy</title>
	<atom:link href="http://www.safetyxchange.org/compliance-risk-management/why-you-need-one-how-to-create-it-part-1-of-2/feed" rel="self" type="application/rss+xml" />
	<link>http://www.safetyxchange.org/compliance-risk-management/why-you-need-one-how-to-create-it-part-1-of-2</link>
	<description>Putting Safety First</description>
	<lastBuildDate>Sun, 29 Jan 2012 04:58:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2019</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: timothy_healey@hsb.com</title>
		<link>http://www.safetyxchange.org/compliance-risk-management/why-you-need-one-how-to-create-it-part-1-of-2/comment-page-1#comment-310</link>
		<dc:creator>timothy_healey@hsb.com</dc:creator>
		<pubDate>Mon, 17 Aug 2009 14:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.safetyxchange.org/article.php?id=433#comment-310</guid>
		<description>I trust your upcoming model visitor&#039;s safety policy will include a facility&#039;s ability to distinguish between a Visitor and a Contractor.  Visitors defined perhaps as a single person or a small group who is escorted while on site as both a safety and a security measure.  By contrast, &#039;contractors&#039; may be those people who are invited onto the facility to conduct some specified work in accordance with a written agreement (the contract)and who require unescorted access for at least part of the facility.

I guess you can see that this is a sensitive topic, as time and again I see a &#039;one size fits all&#039; approach at faciities that typically seek to impose excessive, unworkable mandates by having a single &#039;Contractor Safety Procedure&#039; that assumes that an outside entity invited onto their site will be doing construction-type work including hot work, tranching, heavy vehicle operations, and so on.

Great topic.  I look forward to your next installment.

- Tim</description>
		<content:encoded><![CDATA[<p>I trust your upcoming model visitor's safety policy will include a facility's ability to distinguish between a Visitor and a Contractor.  Visitors defined perhaps as a single person or a small group who is escorted while on site as both a safety and a security measure.  By contrast, 'contractors' may be those people who are invited onto the facility to conduct some specified work in accordance with a written agreement (the contract)and who require unescorted access for at least part of the facility.</p>
<p>I guess you can see that this is a sensitive topic, as time and again I see a 'one size fits all' approach at faciities that typically seek to impose excessive, unworkable mandates by having a single 'Contractor Safety Procedure' that assumes that an outside entity invited onto their site will be doing construction-type work including hot work, tranching, heavy vehicle operations, and so on.</p>
<p>Great topic.  I look forward to your next installment.</p>
<p>- Tim</p>
]]></content:encoded>
	</item>
</channel>
</rss>

