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.

Table 1. Issue vs. Action
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. 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, and resolve or close it after the outcome is recorded. See Create and Manage Issues or Create and Manage Actions.

After recording the finding, return to the round and complete the remaining tasks.