Currently, the “Responsible Locator” field in the incident investigation workflow automatically categorizes that user as “At Fault,” which in turn affects their risk score. This creates a challenge for organizations that want to accurately document which user handled the area of the locate involved in an incident without implying fault or impacting individual performance metrics.
It would be valuable to have a way to capture this information objectively, so companies can maintain accurate records while ensuring the data doesn’t unintentionally assign blame. This could potentially take the form of an adjustment to the existing field or an alternate way to record the responsible locator’s involvement.
Currently, the “Responsible Locator” field in the incident investigation workflow automatically categorizes that user as “At Fault,” which in turn affects their risk score. This creates a challenge for organizations that want to accurately document which user handled the area of the locate involved in an incident without implying fault or impacting individual performance metrics.
It would be valuable to have a way to capture this information objectively, so companies can maintain accurate records while ensuring the data doesn’t unintentionally assign blame. This could potentially take the form of an adjustment to the existing field or an alternate way to record the responsible locator’s involvement.
0 Votes
0 Comments
Login or Sign up to post a comment