<?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</title>
	<atom:link href="http://www.incidentcheck.com/index.php/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>Version 2.8</title>
		<link>http://www.incidentcheck.com/index.php/version-2-8/</link>
		<comments>http://www.incidentcheck.com/index.php/version-2-8/#comments</comments>
		<pubDate>Thu, 10 Jul 2014 05:27:34 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[New Features]]></category>
		<category><![CDATA[Release Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=404</guid>
		<description><![CDATA[We are excited to announce that version 2.8 of IncidentCheck has been released to production!  This latest version contains many enhancements and new features based on, as always, user feedback and comments, plus our continuing vision that IncidentCheck be the leading incident reporting and management software there is. Release 2.8 features: Statistics Overhaul Reassigning Groups [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>We are excited to announce that version 2.8 of IncidentCheck has been released to production!  This latest version contains many enhancements and new features based on, as always, user feedback and comments, plus our continuing vision that IncidentCheck be the leading incident reporting and management software there is.</p>
<p>Release 2.8 features:</p>
<ul>
<li>Statistics Overhaul</li>
<li>Reassigning Groups for Admins</li>
<li>Hidden and GeoCoded Groups</li>
<li>Location moved to Groups</li>
<li>Void Reports</li>
<li>Injury Trend Graphs</li>
</ul>
<h2></h2>
<h2>Details:</h2>
<h3>Statistics Overhaul</h3>
<p>Over time the statistics area has grown to have many different graphs, sometimes very similar in nature.  We have overhauled this to make the interface much more consistent and at the same time providing more detailed time periods, right down to a daily range.</p>
<p>All of your graphs are still there, but they might be under slightly new headings, so take a look around.  if you need help finding one of your favorites, never hesitate to call/email.</p>
<h3>Reassigning Groups for Admins</h3>
<p>As report groups are entered, spelling mistakes inevitably crop up.  Previously you would need to find all of the reports with the misspelled group and then change them, then remove the group from the available choices.  We have consolidated this into 1 action &#8211; in the Admin Settings, Report Groups area, when you delete a group, you are given the option of reassigning instead of just deleting (removing) it from the reports it appears on.  In the following case, I want to ensure that &#8220;3CIS&#8221; (with capitals) is used instead of &#8220;3cis&#8221;:<a href="http://www.incidentcheck.com/wp-content/uploads/2014/07/reassign1.png"><img class="aligncenter size-full wp-image-408" src="http://www.incidentcheck.com/wp-content/uploads/2014/07/reassign1.png" alt="reassign" width="546" height="236" /></a></p>
<h3>Hidden Groups and GeoCoded Groups</h3>
<p>Also new in the group area are Hidden Groups.  These groups are allowed to be entered and seen by administrators only.  Some care is needed, however, when generating PDF reports, as if you generate it with the new option of adding hidden fields, that will be put in the PDF and therefore might be seen by others.</p>
<p>GeoCoded Groups allow you to specify a lat and long for each group, if you would like to add the report to a map.</p>
<h3>Location moved to Groups</h3>
<p>Closely related to geocoded groups is the move of Office Location, previously its own stand alone field to just be another group.  This greatly simplifies things while still allowing you to use it in the same manner as before.  When we looked at Location and how it was being used, we eventually realized that it should have been in the Group section all along, so this now fixes that.</p>
<h3>Void Reports</h3>
<p>Many industries have the notion of a VOID report, which is a report the want to track, but which is pretty much invisible when it comes time to tally stats.  You can now mark a report as VOID and keep it in the system without fear that it will show up on TRIF or in quarterly stats.</p>
<h3>Injury Trend Graphs</h3>
<p>Following up on the detailed injury fields that we added a while back, we now have new graphs to show injury statistics.  This is under Statistics -&gt; Graphs -&gt; Injuries.  We have started with a small set, but as you have ideas for new graphs, please let us know and we can add them.</p>
<p>&nbsp;</p>
<p>We are very excited about these changes and they lay the groundwork for even more additions in the future.  We have a long roadmap with our user suggestions and we continually strive to add features to bring more and more value to our customers.</p>
<p>&nbsp;</p>
<p>Thanks &#8211; The IncidentCheck team</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/version-2-8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>New Release &#8211; Custom Reports</title>
		<link>http://www.incidentcheck.com/index.php/new-release-custom-reports/</link>
		<comments>http://www.incidentcheck.com/index.php/new-release-custom-reports/#comments</comments>
		<pubDate>Wed, 02 Oct 2013 14:07:38 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[How To]]></category>
		<category><![CDATA[New Features]]></category>
		<category><![CDATA[Support]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=368</guid>
		<description><![CDATA[With this latest release, we have added: Custom Reports &#8211; monthly, quarterly, and yearly PDF reports A more polished Report PDF Small changes to the report entry form to make reprot entry that much faster and easier Small bug fixes and small enhancements Custom PDF Reports Under the Statistics menu item, you will now see [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>With this latest release, we have added:</p>
<ul>
<li>Custom Reports &#8211; monthly, quarterly, and yearly PDF reports</li>
<li>A more polished Report PDF</li>
<li>Small changes to the report entry form to make reprot entry that much faster and easier</li>
<li>Small bug fixes and small enhancements</li>
</ul>
<h3>Custom PDF Reports</h3>
<p>Under the Statistics menu item, you will now see a new item called &#8220;Reports&#8221;.  From here you can pick monthly, quarterly, or yearly reports.  These reports allow you to choose graphs to display and provide titles and a narrative for those graphs to provide a beautifully presented document for showing your organization where things stand.</p>
<p>This is the first step of many enhancements in this area, and we are soliciting feedback on how this area can be developed to provide you with the information you need.  So, if you have any suggestions, feel free to let us know.</p>
<h3>Report PDF Changes</h3>
<p>We have changed the design of the PDF report for individual incidents &#8211; the previous design had too much whitespace and the new design addresses that issue as well as cleans up the typography and general layout.  We think this is a huge improvement over the previous design and would be curious to hear any feedback from our users on this.</p>
<h3>Streamlined Report Entry</h3>
<p>We have changed the report entry to make it easier and faster to enter the initial details of a report.  This makes better use of the space in the form and eliminates scrolling on most devices that was previously necessary.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/new-release-custom-reports/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Look and Feel</title>
		<link>http://www.incidentcheck.com/index.php/new-look-and-feel/</link>
		<comments>http://www.incidentcheck.com/index.php/new-look-and-feel/#comments</comments>
		<pubDate>Wed, 22 May 2013 14:45:33 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[Incident Check]]></category>
		<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=331</guid>
		<description><![CDATA[Incident Check now has a newer look and feel to keep up with the growing demand and to have a more responsive design.  This allows for a better user experience when working on phones, tablets, and the desktop. This also sets the stage for new upcoming changes with more personalization. We feel Incident Check is [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Incident Check now has a newer look and feel to keep up with the growing demand and to have a more responsive design.  This allows for a better user experience when working on phones, tablets, and the desktop.</p>
<p>This also sets the stage for new upcoming changes with more personalization.</p>
<p>We feel Incident Check is the best incident management system out there and it continues to get better with each release.</p>
<p>Check out the screenshots for a taste of the difference:</p>
<p>Before:</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/05/before.png"><img class="aligncenter size-full wp-image-333" alt="before" src="http://www.incidentcheck.com/wp-content/uploads/2013/05/before.png" width="1218" height="775" /></a></p>
<p>After:</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/05/after.png"><img class="aligncenter size-full wp-image-334" alt="after" src="http://www.incidentcheck.com/wp-content/uploads/2013/05/after.png" width="1195" height="790" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/new-look-and-feel/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Account Organization, Word Exports, and Corrective Action Lists</title>
		<link>http://www.incidentcheck.com/index.php/account-organization-word-exports-and-corrective-action-lists/</link>
		<comments>http://www.incidentcheck.com/index.php/account-organization-word-exports-and-corrective-action-lists/#comments</comments>
		<pubDate>Fri, 05 Apr 2013 17:57:18 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=326</guid>
		<description><![CDATA[In our quest to make Incident Check the best incident management system out there, we are continually adding new features based on client feedback, industry best practices, and general trends. To that end, the newest features include exports of the tabular summaries to Word, a new way to view your account organization, and a list [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>In our quest to make Incident Check the best incident management system out there, we are continually adding new features based on client feedback, industry best practices, and general trends.</p>
<p>To that end, the newest features include exports of the tabular summaries to Word, a new way to view your account organization, and a list of all outstanding corrective actions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/account-organization-word-exports-and-corrective-action-lists/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Latest Feature &#8211; Group Level Alerts</title>
		<link>http://www.incidentcheck.com/index.php/latest-feature-group-level-alerts/</link>
		<comments>http://www.incidentcheck.com/index.php/latest-feature-group-level-alerts/#comments</comments>
		<pubDate>Tue, 19 Mar 2013 21:32:27 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=319</guid>
		<description><![CDATA[Incident Check &#8211; the easy and affordable way for your company to track incidents, near misses, and hazards on the job &#8211; now alerts based on Report Groups. We use Report Groups as a &#8220;tag&#8221; for reports, leaving this generic enough for our many varied companies to use as they see fit.  Some examples are [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Incident Check &#8211; the easy and affordable way for your company to track incidents, near misses, and hazards on the job &#8211; now alerts based on Report Groups.</p>
<p>We use Report Groups as a &#8220;tag&#8221; for reports, leaving this generic enough for our many varied companies to use as they see fit.  Some examples are companies tagging reports with Divisions, Truck #, Crew #, Project ID, Rig #, Supervisor, and many many more.</p>
<p>While Incident Check always had email alerts, now administrators will have the ability to send emails based on the Report Group, allowing for increased flexibility in alerting your users.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/latest-feature-group-level-alerts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Latest Release Features &#8211; Stats and Multiple Groups</title>
		<link>http://www.incidentcheck.com/index.php/latest-release-features-stats-and-multiple-groups/</link>
		<comments>http://www.incidentcheck.com/index.php/latest-release-features-stats-and-multiple-groups/#comments</comments>
		<pubDate>Tue, 05 Feb 2013 20:38:44 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Release Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=310</guid>
		<description><![CDATA[The latest changes to IncidentCheck include 2 main changes to how groups are handled in the system. 1.  Better Group Level Statistics Statistics now have a way to break them down by the Groups that are set up in the system.  In our use at 3CIS, we have Wireless, Cabling, and Software Divisions in the [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The latest changes to IncidentCheck include 2 main changes to how groups are handled in the system.</p>
<p>1.  Better Group Level Statistics</p>
<p>Statistics now have a way to break them down by the Groups that are set up in the system.  In our use at 3CIS, we have Wireless, Cabling, and Software Divisions in the company.  You can now choose the ones you would like to see and export the graph or data to provide comprehensive, side-by-side comparisons of the performance of each division.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/02/stats.png"><img class="alignnone size-full wp-image-312" alt="stats" src="http://www.incidentcheck.com/wp-content/uploads/2013/02/stats.png" width="449" height="357" /></a></p>
<p>2.  Multi-Groups per User</p>
<p>Additionally, we added the ability to have users be part of more than one group under a given label.  Again, in our case this means that a user from 3CIS can be part of the Cabling Division, the Wireless, or the Software division, or any combination of the 3.  Previously we limited this to only 1 choice but the newest change reflects the reality at many of our customers&#8217; companies &#8211; people are often part of more than one division or other group.</p>
<p>To do this, you set up a User Account for Group Access as per usual, but instead of a drop-down to choose the group, we have a combo box where you can Control-Click to select multiple items, as in the screenshot below:</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/02/gla.png"><img class="alignnone size-full wp-image-314" alt="gla" src="http://www.incidentcheck.com/wp-content/uploads/2013/02/gla.png" width="544" height="242" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/latest-release-features-stats-and-multiple-groups/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>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>
	</channel>
</rss>
