Respond to an Incident Workflow
Background
When an incident occurs on a project, your team may use workflows to ensure the right people review the details and complete necessary follow-up tasks. Responding to an incident workflow might involve simply approving a step to move it forward, or it may require you to complete an Action Step—such as uploading a missing injury record or closing related observations—before the incident can proceed.
Things to Consider
Required User Permissions:
'Standard' level permissions or higher on the project's Incidents tool.
You must also be the Assignee for the current workflow step.
Additional Information:
Banner Notifications: You will only see workflow banners (like "Workflow Step Overdue") for standard approval steps. Banners do not appear for Action Steps that require documentation. Always check the workflow sidebar to see if the workflow is paused and waiting for you to add something.
Automatic Updates: When you fulfill an Action Step by uploading the required document or closing the requested observations, the workflow moves forward automatically. You do not need to click a "Submit" or "Continue" button.
Prerequisites
An active workflow must be initiated on the incident.
Steps
Navigate to the project's Incidents tool.
Click View next to the incident that requires your response.
Look at the right sidebar. Under the Current Step section, you will see your assigned task.
If your current step is a standard response (like a simple approval):
Choose your response (e.g., Approve, Reject).
Click Continue to move the incident to the next step.
Completing Required Action Steps: If the workflow is paused for required documentation, it will tell you exactly what is missing under the Current Step (for example, "Add required documentation: Near Miss Record, Root Cause Analysis").
To add required documentation: Go to the correct tab in the incident (such as General, Records, or Root Cause Analysis) and add the requested items.
To close linked observations: If the step requires linked observations to be closed, navigate to the Observations tool and make sure all observations tied to this incident are marked as 'Closed'.
Verify the workflow progressed. The sidebar will update automatically with a history log proving that the documents were added or the observations were closed.
See Also
Loading related articles...