<?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; Uncategorized</title>
	<atom:link href="http://www.incidentcheck.com/index.php/category/uncategorized/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>New Release &#8211; Investigation Timeline</title>
		<link>http://www.incidentcheck.com/index.php/new-release-investigation-timeline/</link>
		<comments>http://www.incidentcheck.com/index.php/new-release-investigation-timeline/#comments</comments>
		<pubDate>Tue, 29 Oct 2013 17:08:57 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=374</guid>
		<description><![CDATA[We are pleased to announce more new Incident Check Features! Additional functionality now available: Investigation Timeline Causal Analysis comments Faster corrective action updates Full size images File upload changes Leading / Lagging indicator summary Injury details &#8211; body part, nature of injury and injury cause Investigation Timeline Administrators can set a report to have an [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>We are pleased to announce more new Incident Check Features!</p>
<p>Additional functionality now available:</p>
<ul>
<li>Investigation Timeline</li>
<li>Causal Analysis comments</li>
<li>Faster corrective action updates</li>
<li>Full size images</li>
<li>File upload changes</li>
<li>Leading / Lagging indicator summary</li>
<li>Injury details &#8211; body part, nature of injury and injury cause</li>
</ul>
<p><strong>Investigation Timeline</strong></p>
<p>Administrators can set a report to have an investigation timeline on any report type in the system through the settings.  This will then allow you to specify dates and times and a description of the investigative activity that was undertaken.  Along with this you can upload files that are relevant to that investigation step.</p>
<p>Once this is complete, we have a mechanism where you can step through the timeline to review each step that you will see in the sidebar beside the incident.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture.png"><img class="alignnone  wp-image-377" alt="Capture" src="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture.png" width="701" height="207" /></a></p>
<p><strong>Causal Analysis comments</strong></p>
<p>When choosing your causal analysis items, we now have an area for comments that pertain to each particular cause.</p>
<p>&nbsp;</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture2.png"><img class="alignnone  wp-image-382" alt="Capture" src="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture2.png" width="538" height="299" /></a></p>
<p><strong>Faster corrective action updates</strong></p>
<p>In the corrective action emails, we have changed things just slightly to allow people to quickly click the email link and then choose to complete or cancel the corrective action without having to log in to Incident Check.</p>
<p><strong>Full page images in PDFs</strong></p>
<p>In the generated PDF for a report, there is now the option to attach full size images to the end of  the report.  This is very helpful when there is fine detail on an image that the thumbnail does not show.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture3.png"><img class="alignnone  wp-image-383" alt="Capture" src="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture3.png" width="192" height="380" /></a></p>
<p>&nbsp;</p>
<p><strong>File upload changes</strong></p>
<p>We have modernized the file upload portion of the report page to allow either images or files to be uploaded, and to have multiple uploads running at the same time.</p>
<p><strong>Leading / Lagging indicator summary</strong></p>
<p>A quick report, the first of many, that will start focusing on Leading Indicators.  This is an area of focus for Incident Check in general in the upcoming weeks and months, as we are seeing more and more customers really looking to leading indicators to ensure that things are being handled pro-actively.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture4.png"><img class="alignnone  wp-image-384" alt="Capture" src="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture4.png" width="728" height="301" /></a></p>
<p><strong>Injury details</strong></p>
<p>Now, when a report dealing with an injury is entered, you have the option of adding details on the injured body part as well as  the nature of the injury and the cause of the injury.  Note that this cause is different from the overall causal analysis in subtle ways.  With Causal Analysis, a person is trying to get at the reasons for the incident happening.  With an injury cause, we are focusing on the more specific details of the injury itself.</p>
<p>&nbsp;</p>
<p>As always, feedback on these features is appreciated and if you would like to discuss them, feel free to email or calla t any time.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/new-release-investigation-timeline/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting a Latitude and Longitude for a Location</title>
		<link>http://www.incidentcheck.com/index.php/getting-a-latitude-and-longitude-for-a-location/</link>
		<comments>http://www.incidentcheck.com/index.php/getting-a-latitude-and-longitude-for-a-location/#comments</comments>
		<pubDate>Mon, 23 Jul 2012 15:54:41 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=238</guid>
		<description><![CDATA[For Incident Check, we require that all reports (incidents, near misses, and hazards) are tagged with a specific location.  This is for many reasons, the biggest one being that this is how our customers generally tracked things before Incident Check was implemented. There has been 1 stumbling block for locations, however, and that is our [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>For Incident Check, we require that all reports (incidents, near misses, and hazards) are tagged with a specific location.  This is for many reasons, the biggest one being that this is how our customers generally tracked things before Incident Check was implemented.</p>
<p>There has been 1 stumbling block for locations, however, and that is our mandatory latitude and longitude.  But, getting this information is as simple as firing up Google Maps.</p>
<p>For example, 3CIS headquarters is in Edmonton.  To get a lat/lon pair, simply zero in on the building in Google Maps, right click, and choose &#8220;What&#8217;s here?&#8221; from the menu.</p>
<p>You will then see the latitude and longitude in the search box at the top, like in the following screenshot:</p>
<p>&nbsp;</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2012/07/latlong.png"><img class="alignnone  wp-image-239" src="http://www.incidentcheck.com/wp-content/uploads/2012/07/latlong.png" alt="" width="878" height="593" /></a></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/getting-a-latitude-and-longitude-for-a-location/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Loss Tracking</title>
		<link>http://www.incidentcheck.com/index.php/loss-tracking-2/</link>
		<comments>http://www.incidentcheck.com/index.php/loss-tracking-2/#comments</comments>
		<pubDate>Mon, 16 Jul 2012 20:03:59 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=235</guid>
		<description><![CDATA[Incidents, as we define them, are events that either 1) result in damage to people (injuries, etc.) or 2) result in damage or loss to the environment or property.  Of course, injuries and fatalities are the worst possible outcome and we all work to prevent them as much as possible.  That is always the first [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Incidents, as we define them, are events that either 1) result in damage to people (injuries, etc.) or 2) result in damage or loss to the environment or property.  Of course, injuries and fatalities are the worst possible outcome and we all work to prevent them as much as possible.  That is always the first focus.</p>
<p>However, we also want to track the amount of money involved in the other types of incidents.  These can be a powerful motivator for people to really understand what is happening at all levels in a company, and to realize substantial cost savings.</p>
<p>Many times people do not want to track these as the idea of a higher incident count is not appealing.  Lost a ladder at a job-site?  1 more incident this month.  Computer equipment stolen from head office?  Another one.  If someone looks at this and sees a large incident count, then they might draw the wrong conclusions, the thinking goes.</p>
<p>The industry already does a good job of this currently however.  The difference is that those incidents are not reportable, whereas classes of injuries are reportable.  We are doing our best to educate people on this, as the value of tracking losses can be a great way to have Incident Check pay for itself and more.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/loss-tracking-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Participation Tax&#8221;</title>
		<link>http://www.incidentcheck.com/index.php/participation-tax/</link>
		<comments>http://www.incidentcheck.com/index.php/participation-tax/#comments</comments>
		<pubDate>Thu, 31 May 2012 15:20:30 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=227</guid>
		<description><![CDATA[An article in Inc. Magazine sums up the reason why we don&#8217;t charge per user in Incident Check.  We don&#8217;t want to penalize companies for having more users in the system; in fact, we want the opposite, ideally everyone that needs to use the system should have access. In the safety area, particularly, company and [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>An article in Inc. Magazine sums up <a href="http://www.inc.com/magazine/201206/jason-fried/huge-accounts-make-me-nervous-it-takes-a-village.html" target="_blank">the reason why we don&#8217;t charge per user in Incident Check</a>.  We don&#8217;t want to penalize companies for having more users in the system; in fact, we want the opposite, ideally everyone that needs to use the system should have access.</p>
<p>In the safety area, particularly, company and workplace safety is everyone&#8217;s responsibility, so we would not want to stop people from using the best system out there for entering incidents, near misses, and hazards &#8211; Incident Check.</p>
<p>No &#8220;Participation Tax&#8221; here.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/participation-tax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Other Changes</title>
		<link>http://www.incidentcheck.com/index.php/other-changes/</link>
		<comments>http://www.incidentcheck.com/index.php/other-changes/#comments</comments>
		<pubDate>Tue, 22 May 2012 17:19:47 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=185</guid>
		<description><![CDATA[The major change in the latest release, as already blogged about, is the Report Group Access Restriction.  There are a couple of other changes worth mentioning as well, however: 1.  Alerts on Custom Incident Types: Following up to our immediately successful and well used Custom Incident Types, we added the ability to alert on those [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The major change in the latest release, as already blogged about, is the Report Group Access Restriction.  There are a couple of other changes worth mentioning as well, however:</p>
<p>1.  Alerts on Custom Incident Types: Following up to our immediately successful and well used Custom Incident Types, we added the ability to alert on those incident types when setting up automated emails.  You will now see this in the Alerts section of the Settings area (Admins only, of course).</p>
<p>2.  Incident Breakdown Chart: In general we hear a lot that <a title="pie charts are bad" href="http://www.stevefenton.co.uk/Content/Pie-Charts-Are-Bad/">Pie Charts are Bad</a>.  But, in this case we could not resist and truly feel that they are a great upgrade over the previous bar chart.  To illustrate the point, consider the following (fake data from 3CIS):</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2012/05/chart.png"><img class="alignnone size-full wp-image-186" src="http://www.incidentcheck.com/wp-content/uploads/2012/05/chart.png" alt="" width="800" height="576" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>We feel that this chart gives us the most immediate impact of determining what we need to work on.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/other-changes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Impacts to WHMIS?</title>
		<link>http://www.incidentcheck.com/index.php/impacts-to-whmis/</link>
		<comments>http://www.incidentcheck.com/index.php/impacts-to-whmis/#comments</comments>
		<pubDate>Thu, 26 Apr 2012 14:24:10 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=162</guid>
		<description><![CDATA[After receiving an email from Safety+Health concerning the GHS  (United Nations’ Globally Harmonized System of Classification and Labeling of Chemicals), I started wondering if this will impact WHMIS training in the future. Currently WHMIS is one of those certificates that don&#8217;t have hard expiration dates.  It is good practice to have employees go for refresher [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>After receiving an email from <a title="Safety+Health" href="http://www.nsc.org/safetyhealth/Pages/home.aspx" target="_blank">Safety+Health </a>concerning the <a title="GHS" href="http://www.nsc.org/safetyhealth/Pages/512GHS-is-here.aspx" target="_blank">GHS </a> (United Nations’ Globally Harmonized System of Classification and Labeling of Chemicals), I started wondering if this will impact WHMIS training in the future.</p>
<p>Currently WHMIS is one of those certificates that don&#8217;t have hard expiration dates.  It is good practice to have employees go for refresher courses after a number of years, but the fact that you have taken the course and your certificate has a Date of Issue is generally sufficient.</p>
<p>With a change to labelling potentially on the horizon, however, this might make it more of an issue.  Something to think about when planning for training sessions in the future.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/impacts-to-whmis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
