<?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; New Features</title>
	<atom:link href="http://www.incidentcheck.com/index.php/category/new-features/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; 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>Setting up Group Level Access</title>
		<link>http://www.incidentcheck.com/index.php/setting-up-group-level-access/</link>
		<comments>http://www.incidentcheck.com/index.php/setting-up-group-level-access/#comments</comments>
		<pubDate>Fri, 25 May 2012 16:45:18 +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=190</guid>
		<description><![CDATA[Group Level Access (GLA) is a mechanism that we use in Incident Check to provide multiple levels of access to the data. This post will outline the basics for setting up GLA. Step 1: Decide what criteria to use to define access levels This portion is done by the safety administrator(s) and is a decision [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Group Level Access (GLA) is a mechanism that we use in Incident Check to provide multiple levels of access to the data.</p>
<p>This post will outline the basics for setting up GLA.<span id="more-190"></span></p>
<h2>Step 1: Decide what criteria to use to define access levels</h2>
<p>This portion is done by the safety administrator(s) and is a decision about what category you would like to use to set up access groups. For example, at <a title="3CIS" href="http://www.3cis.com">3CIS</a>, we have 3 distinct divisions &#8211; Wireless, Cabling, and Software.   This is the logical choice for us to set up access for non admins to see things happening in their own area.</p>
<p>Other companies may have divisions, reporting units, operating companies, Unit #, Rig #, etc.  This can be anything that makes sense for your particular situation.</p>
<h2>Step 2: Set up a Report Group</h2>
<p>Now, after logging into Incident Check as an administrator, go to Settings and choose Report Grouping.</p>
<p>Create (or find) the report group you decided on in step 1 and click it.  On the right, you will see an option that says &#8220;Used For Group Access&#8221;.  Check this and it will now allow you to assign users.  For 3CIS, this is &#8220;Division&#8221;.</p>
<p>It is best practice, though not strictly necessary, to have the group locked and mandatory as well.  If in doubt, set both of these.</p>
<p>Under Groups, add the different groups that apply.  Again, for 3CIS, these are &#8220;Cabling&#8221;, &#8220;Wireless&#8221;, and &#8220;Software&#8221;.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2012/05/gla11.png"><img class="aligncenter size-full wp-image-198" title="gla1" src="http://www.incidentcheck.com/wp-content/uploads/2012/05/gla11.png" alt="" width="795" height="606" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<h2>Step 3: Add/Modify users</h2>
<p>When you are happy with the setup, it is now time to add users to that group.  Click Settings&#8230;User Accounts, and choose (or create) someone to whom group access applies.</p>
<p>In the Access Level drop-down, there are now 3 choices:</p>
<ul>
<li>Reporter</li>
<li>Group Access</li>
<li>Admin</li>
</ul>
<p>Choosing Group Access now enables the Group Access area.  You will see the group that you specified in step 2.  For 3CIS, this is Division, and in that drop-down, there is Wireless, Cabling, and Software.  Pick the one that applies for this person and click one of the Save buttons.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2012/05/gla2.png"><img class="aligncenter size-full wp-image-200" title="gla2" src="http://www.incidentcheck.com/wp-content/uploads/2012/05/gla2.png" alt="" width="799" height="566" /></a></p>
<p>&nbsp;</p>
<h2>End Result</h2>
<p>For the newly set up person, they will now only see Incident, Near Misses, and Hazards that are part of that group.  And, when creating a new report, the report is automatically tagged with the groups they are in.</p>
<p>You will see what group a person is part of in the top right of the menu, giving a clear indicator of what reports that person is seeing.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2012/05/gla3.png"><img class="aligncenter size-full wp-image-201" title="gla3" src="http://www.incidentcheck.com/wp-content/uploads/2012/05/gla3.png" alt="" width="223" height="150" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Note: Not all companies require or use GLA. If you do not have this ability but would like it, please contact us to turn this on for your company.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/setting-up-group-level-access/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Report grouping is Now Active!</title>
		<link>http://www.incidentcheck.com/index.php/report-grouping-is-now-active/</link>
		<comments>http://www.incidentcheck.com/index.php/report-grouping-is-now-active/#comments</comments>
		<pubDate>Tue, 22 May 2012 17:10:59 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Incident Check]]></category>
		<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=179</guid>
		<description><![CDATA[The latest release to Incident Check is out and active, and here is rundown of the most significant change &#8211; Report Group Access Restriction. Many of our customers need to limit access to reports for different divisions of their companies.  Currently, we have two access levels &#8211; Reporters and Administrators.  Reporters add and edit their [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The latest release to Incident Check is out and active, and here is rundown of the most significant change &#8211; Report Group Access Restriction.</p>
<p>Many of our customers need to limit access to reports for different divisions of their companies.  Currently, we have two access levels &#8211; Reporters and Administrators.  Reporters add and edit their own reports and can only see what they have entered, whereas Administrators see and have access to everything.</p>
<p>However, there is an in-between access level that we have now addressed.  The challenge from the technical point of view was how to provide this functionality in a way that supports all of our various customers from the many different industries that have a strong safety component to them.</p>
<p>We have done this through our report groups, the current mechanism for &#8216;tagging&#8217; reports with company specific information &#8211; things like Division, Contractor, Operating Company, Supervisor, and many others defined by our users.  Now you can assign users into one or more of these groups and they will only see the appropriately tagged reports.</p>
<p>For people contemplating using this mechanism, all that is needed is to decide what characteristics you would like to use to restrict access, and then use the Settings area (available to admins only) to make this a locked and mandatory group.  Then simply add people to that group.</p>
<p>We are very excited to hear how our customers start using this feature and we are looking forward to feedback.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/report-grouping-is-now-active/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>
		<item>
		<title>Custom Incident Types</title>
		<link>http://www.incidentcheck.com/index.php/custom-incident-types/</link>
		<comments>http://www.incidentcheck.com/index.php/custom-incident-types/#comments</comments>
		<pubDate>Tue, 17 Apr 2012 17:40:13 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=132</guid>
		<description><![CDATA[In response to user feedback, Incident Check now supports custom incident types.  In addition to the pre-defined types: Injury, Loss, Spill, Theft, Equipment Failure, etc., users can now define their own type.  We have customers using this for such as diverse as &#8220;Lightning Strike&#8221;, &#8220;Underground Line Hit&#8221;, and &#8220;Weight Overage&#8221;. By defining your own incident [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>In response to user feedback, Incident Check now supports custom incident types.  In addition to the pre-defined types: Injury, Loss, Spill, Theft, Equipment Failure, etc., users can now define their own type.  We have customers using this for such as diverse as &#8220;Lightning Strike&#8221;, &#8220;Underground Line Hit&#8221;, and &#8220;Weight Overage&#8221;.</p>
<p>By defining your own incident types, you gain more control over exactly what is reported, as well as being able to see more in-depth trends and analysis, ultimately giving you better prediction tools for the future.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/custom-incident-types/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
