Notice: Use of undefined constant SCRIPT_DEBUG - assumed 'SCRIPT_DEBUG' in /usr/share/nginx/html/wp-includes/formatting.php on line 4144 Notice: Undefined variable: output in /usr/share/nginx/html/wp-content/themes/inspire/includes/theme-actions.php on line 60
Archive by Author

New Release – Investigation Timeline

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 – body part, nature of injury and injury cause Investigation Timeline Administrators can set a report to have an […]

Comments ( 0 )

Latest Release Features – Stats and Multiple Groups

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 […]

Comments ( 0 )

Near Misses – Failures or Successes?

Wired magazine has an article out examining the perception of near misses (or close calls) and investigates if they are “Near Disasters” or “Lucky Breaks”. 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 […]

Comments ( 0 )

Getting a Latitude and Longitude for a Location

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 […]

Comments ( 0 )

Loss Tracking

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 […]

Comments ( 0 )

“Participation Tax”

An article in Inc. Magazine sums up the reason why we don’t charge per user in Incident Check.  We don’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 […]

Comments ( 0 )

Other Changes

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 […]

Comments ( 0 )

Report grouping is Now Active!

The latest release to Incident Check is out and active, and here is rundown of the most significant change – 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 – Reporters and Administrators.  Reporters add and edit their […]

Comments ( 0 )

5 Whys

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 […]

Comments ( 0 )

“Why is your product so cheap?”

This is a question I get many times when talking with potential and existing clients.  First, I like to change that to “inexpensive”, as a marketer once coached us. Second, most of the people asking are used to dealing with 2 different types of situations: In-house IT departments “Enterprise” Software Sales With Incident Check, we […]

Comments ( 0 )