<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Incident Check &#187; Safety Concerns</title>
	<atom:link href="http://www.incidentcheck.com/index.php/category/safety-concerns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.incidentcheck.com</link>
	<description>Affordable Incident Tracking Software</description>
	<lastBuildDate>Thu, 10 Jul 2014 05:27:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.2.2</generator>
	<item>
		<title>Near Misses &#8211; Failures or Successes?</title>
		<link>http://www.incidentcheck.com/index.php/near-misses-failures-or-successes/</link>
		<comments>http://www.incidentcheck.com/index.php/near-misses-failures-or-successes/#comments</comments>
		<pubDate>Tue, 14 Aug 2012 17:54:34 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Safety Concerns]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=247</guid>
		<description><![CDATA[Wired magazine has an article out examining the perception of near misses (or close calls) and investigates if they are &#8220;Near Disasters&#8221; or &#8220;Lucky Breaks&#8221;. Essentially, they argue that we should look at them as a failure, not a success, as they are leading indicators of incidents.  Citing the Process Improvement Institute, across many industries [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Wired magazine has an article out examining the perception of near misses (or close calls) and investigates if they are &#8220;Near Disasters&#8221; or &#8220;Lucky Breaks&#8221;.</p>
<p>Essentially, they argue that we should look at them as a failure, not a success, as they are leading indicators of incidents.  Citing the <a title="PII" href="http://www.piii.com/">Process Improvement Institute</a>, across many industries there are between 50 and 100 near misses recorded per serious incident, and about 10,000 smaller errors occur during that time.</p>
<p><a title="Wired Near Misses" href="http://www.wired.com/wiredscience/2012/08/st_essay_close_calls/">It is also a great read.</a></p>
<p>With <a title="Incident Check" href="http://www.incidentcheck.com">Incident Check</a>, we have been focusing on that for years.  We provide the necessary tools to track near misses and provide roll-up statistics to show how many near misses are being recorded.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/near-misses-failures-or-successes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 Whys</title>
		<link>http://www.incidentcheck.com/index.php/5-whys/</link>
		<comments>http://www.incidentcheck.com/index.php/5-whys/#comments</comments>
		<pubDate>Wed, 09 May 2012 16:24:12 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Incident Check]]></category>
		<category><![CDATA[Safety Concerns]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=172</guid>
		<description><![CDATA[Ran across this nice little article about root cause analysis with your kids: When Kids Start Doing Root Cause Analysis. With Incident Check, we focus on the root cause analysis and provide a completely customizable  set of factors that are set up by your safety professional. We start with a basic set, but you are [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Ran across this nice little article about root cause analysis with your kids: <a title="root cause" href="http://blog.marksweep.com/post/22692428919/when-kids-start-doing-root-cause-analysis"> When Kids Start Doing Root Cause Analysis</a>.</p>
<p>With Incident Check, we focus on the root cause analysis and provide a completely customizable  set of factors that are set up by your safety professional.</p>
<p>We start with a basic set, but you are free to remove all of them in order to set things up to work best with your company.  Our initial set consists of Immediate and Root Causes.  Under Immediate causes we have Unsafe Conditions and Unsafe Practices, under Root Causes we have Systemic Factors, Peronal factors, and Job factors.  We feel this is a very good base for people to use to really get at what is important &#8211; figuring out the underlying reasons for incidents and doing our best to eliminate them.</p>
<p>This is highlighted in our Pareto Charts that show the top 80% of factors leading to incidents, near misses, or hazards.  And we find that these charts become much more valuable over time.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/5-whys/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Spring Issues</title>
		<link>http://www.incidentcheck.com/index.php/spring-issues/</link>
		<comments>http://www.incidentcheck.com/index.php/spring-issues/#comments</comments>
		<pubDate>Fri, 20 Apr 2012 16:55:36 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Incident Check]]></category>
		<category><![CDATA[Safety Concerns]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=152</guid>
		<description><![CDATA[At 3CIS &#8211; the company behind Incident Check &#8211; we not only build and support Incident Check, we also use it for our telecommunications division.  in addition to reaping the benefits of having reports at our fingertips, easily entered reports and corrective actions, we use the information we have learned in our extremely safety-conscious business to [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>At <a href="http://www.3cis.com" title="3CIS website">3CIS</a> &#8211; the company behind Incident Check &#8211; we not only build and support Incident Check, we also use it for our telecommunications division.  in addition to reaping the benefits of having reports at our fingertips, easily entered reports and corrective actions, we use the information we have learned in our extremely safety-conscious business to enhance Incident Check.</p>
<p>A key component of our safety program is to identify general issues that our workers face based on the upcoming season.</p>
<p>In winter, cold and icy conditions play a huge factor in planning; likewise in summer we are on alert for extreme temperatures in the other direction, meaning plenty of sunscreen and water out in the field.</p>
<p>What about the milder seasons &#8211; spring and fall?  Well, with the [eventual] arrival of spring her in Alberta, issues that have been noted in the past are allergic reactions.  We have to be aware that insects now share the workspace outdoors, and pollen from plants can be heavy in the air.  For workers with allergies, proper preparation can mean the difference between completing a job safely and effectively and lost time due to the complications of not having medication.  Anyone allergic to bees is responsible for carrying EpiPens and our workers all have First Aid training, but reminders at the beginning of the season get people in the right frame of mind and raise awareness to the issues they may see in the field.</p>
<p>To ensure that we remember these, we note items such as these in our Actions Calendar.  I like to refer to the Actions Calendar as &#8220;Corrective Actions that are not tied to Incidents&#8221;.  By putting them in as a recurring action, you will get reminders and have a calendar layout that will remind you to bring it up at the appropriate safety meeting.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/spring-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Mining the Pyramid&#8221;</title>
		<link>http://www.incidentcheck.com/index.php/mining-the-pyramid/</link>
		<comments>http://www.incidentcheck.com/index.php/mining-the-pyramid/#comments</comments>
		<pubDate>Wed, 18 Apr 2012 15:13:09 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[New Features]]></category>
		<category><![CDATA[Safety Concerns]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=143</guid>
		<description><![CDATA[At a recent safety conference, I attended a talk that centered around Heinrich&#8217;s Law.  While this &#8220;law&#8221; is being revisted and further studies, the Heinrich Pyramid remains one of the featured graphics among safety professionals.  And naturally, Incident Check also features this alongside Pareto Charts for Causal Analysis, a Report Map, and pretty much every [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>At a recent safety conference, I attended a talk that centered around <a title="Heinrich's Law" href="http://en.wikipedia.org/wiki/Herbert_William_Heinrich">Heinrich&#8217;s Law</a>.  While this &#8220;law&#8221; is being revisted and further studies, the Heinrich Pyramid remains one of the featured graphics among safety professionals.  And naturally, Incident Check also features this alongside Pareto Charts for Causal Analysis, a Report Map, and pretty much every other metic or breakdown a company needs.</p>
<p>However, the concept of &#8220;mining the pyramid&#8221; is one where you look into all of the recorded near misses and incidents and begin identifying those that are high risk.  The intention is to drive out more of the trends that your company needs to focus on &#8211; those near misses and incidents that are serious but might be lost among all the other reporting.</p>
<p>We at Incident Check are looking to provide tools to facilitate this process &#8211; underlying every incident, hazard, and near miss report is the risk matrix with the severity and the liklihood of reccurrence giving the overall total risk.  We are now working on ways to highlight this inside of the existing Acident Pyramid to provide a strong visual representation of these events.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/mining-the-pyramid/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
