March 3, 2016 | Barb Carr

Technically Speaking – Management was Shocked When They Saw This Report!

Struggling with the same type of incidents, but can’t figure out why?  Does someone complain about management everyday, but management believes they are always right? The Root Cause Distribution Report, available in the TapRooT® Version 5 Software, can help by bringing generic issues to light that may be overlooked.  The Root Cause Distribution Report shows us a top-down view of the organization and aggregates all the investigation data into one simple report.

We can narrow down our scope by choosing specific locations, classifications, or date ranges too. This can be valuable if we have several locations across the world, or we use TapRooT® in multiple ways such as Safety, Environmental or Quality incidents.

We can see in this example below that Management System has significantly more Root Causes identified than any other category. The next page of the report will detail the Root Causes from each category so we can investigate further.

RCT distribution

On the next page we can see the specific Root causes that make up each Basic Cause Category. It appears that our Standards and Policies do not exist or are poorly written. What should we do? Maybe we should PROACTIVELY review our current policies and look for places to improve, or setup a quarterly review of our policies to keep them updated.


The Root Cause Distribution Report helps identify areas where generic or systemic analysis can be applied. Have a look at the report in your TapRooT® Software by going to the left menu and selecting SEARCH & TREND > ROOT CAUSE DISTRIBUTION.


Technically Speaking is a weekly series that highlights various aspects of our Version 5 software, introduces you to the upcoming TapRooT® VI release and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, doesn’t mean it has to be complicated!


Software, Software - Technically Speaking
Show Comments

Leave a Reply

Your email address will not be published. Required fields are marked *