Choose an Issue or an Action
Choose how to record follow-up work when a round reveals an abnormal condition or a separately assignable activity.
Record the finding before leaving the round so it can be owned and followed through to completion. The available choice depends on the configured workflow.
| Raise an Issue when... | Create an Action when... |
|---|---|
| You find a new anomaly during round execution that needs investigation, such as an Observation, Maintenance condition, Incident, Near Miss, or Hazard. Use an Issue when a new finding must remain visible after the current task or round. | A separately assignable follow-up activity is needed with its own priority, due date, and assignee, and the configured Issue workflow allows an Action to be created. |
| The finding may need to become an ERP Notification. This option requires SAP integration and the applicable configuration. | The follow-up must be tracked separately from the original finding. |
After choosing the record type, follow its lifecycle: create it, take ownership when you are responsible for the work, record progress while the work is investigated or performed, and resolve or close it after the outcome is recorded.
- Issues: create the Issue and record the finding, priority, location or asset, and supporting details; assign the Issue to yourself only when you are responsible for investigating or resolving it; resolve and close the Issue after the required work and resolution details are complete.
- Actions: create the Action and record the required follow-up; assign the Action to yourself when you are taking responsibility for it; resolve and close the Action after its outcome is recorded.
After recording the finding, return to the round and complete the remaining tasks.
