Incidents Root Cause Analysis Beta Guide

Overview

 In Beta

This feature is currently in beta.

The Incidents Root Cause Analysis (RCA) Form is an updated section within the Procore Incidents tool. The Root Cause Analysis form helps safety teams look beyond surface-level descriptions. By capturing highly structured data alongside customizable fieldsets and custom fields, teams can accurately discover why a safety incident occurred

Key Benefits:

  • Deeper Safety Insights: This feature replaces basic investigation summaries with a clear framework. The framework helps you identify underlying procedural, environmental, or systemic failures.

  • Customizable Frameworks: Company Administrators can customize the Root Cause Analysis form. By using configurable fieldsets, administrators can turn fields on or off, make fields required, or add unique custom fields.

  • Granular Data Control: Administrators can restrict sensitive root cause information to specific user roles by using dedicated, granular permissions.

Beta Participation & Feedback

Important: Because this is a Beta release, some features and configurations may change based on user feedback. Your insights are critical to the final development of this feature.

  • How to Access: Access must be enabled by a Procore Admin in Procore Explore. Once enabled, navigate to the company level Admin tool to begin configuration.

  • How to Provide Feedback: Please contact your Procore Point of Contact.

  • Support: If you encounter a blocking bug, please contact your Procore Point of Contact or submit a ticket via the Procore Support Center.

Permissions & Prerequisites

Before you begin, ensure you have the correct permissions:

Required Tool

  • Your project must have an active Incidents tool.

User Permission Levels

  • Company Administrator: Full access to configure settings, create custom fields, and build configurable fieldsets for the Root Cause Analysis form at the Company level.

  • Project Administrator: Full access to create, edit, and view all incident records and root cause details.

  • Standard User: Can create, view and edit incidents they created. Access to view or edit incidents created by others requires granular permissions.

  • Read-Only User: By default, Read Users cannot view Root Cause Analysis data. Access requires additional granular permissions.

Granular Permissions for Root Cause Analysis

Root cause investigations often involve sensitive data. Because of this, this beta introduces specific granular permissions for the Incidents tool.

Incidents Root Cause Analysis Walkthrough

Configure the Form Layout (Company Administrators)

Company Administrators must configure the form layout using Configurable Fieldsets before project teams can use it.

  1. Navigate to the Company level Admin tool.

  2. Locate the 'Tool Settings' section and select Incidents.

  3. Select the Sub-Fieldsets tab.

  4. Select your existing Incident fieldset, or select Create New Fieldset.

  5. Scroll down to the Root Cause Analysis section.

  6. Configure your form fields using the following options:

    • Toggle Visibility: Select or clear the checkboxes to turn fields on or off.

    • Require Fields: Mark fields as required to force users to collect this data before saving an incident.

    • Add Custom Fields: Select Create Custom Field to add specialized dropdown menus, text areas, or checkboxes unique to your safety program.

  7. Select Save.

Create an Incident with Root Cause Data (Project Users)

  1. Navigate to the project's Incidents tool.

  2. Select the Incidents tab, and then select Create.

  3. Complete the Incident Information section fields, including Title, Status, Assignees, and Event Date.

  4. Scroll past the Witness section to find the Root Cause Analysis section.

  5. Fill out the following fields based on your investigation findings:

    • Hazard: Select the hazard involved from the dropdown menu, such as "Caught In". This data migrates from the older investigation section.

    • Contributing Condition: Select the condition that contributed to the incident, such as "Defective Equipment".

    • Contributing Behavior: Select the behavior that contributed to the incident, such as "Distraction".

    • Work Activity: Select the specific task being performed when the incident occurred, such as "Trenching".

    • Equipment: Select or type the machinery, tools, or equipment involved in the incident, such as "Forklift".

    • Root Cause Description: Type a detailed explanation of the fundamental reason why the incident occurred.

    • Note: Any custom fields configured by your Company Administrator will display directly below these standard fields.

  6. Click Create.

See Also

Loading related articles...