9.1.3. Quality Event Triggered from Audit Application

In the final stage of the Audit Planning & Execution workflow, the audit team leader can choose to trigger a quality event for selected observations linked to the audit plan.

Before triggering the quality event, the team leader must assign a party (user, role, or group) to act as the reviewer. This party will be tasked with completing the Review the Issue task. Details about the audit plan and the selected observations associated with the audit plan will be included in this task.

*For more information on how to trigger a quality event directly from the Audit application, click here.

In the Review the Issue form, the following automatic configurations will be applied:

• The quality event name will be set to ‘Event from Audit Plan – [Audit Plan ID – Audit Plan Name],’ reflecting its source.
• The quality event ID will follow the format ‘QE-AF-[No.].’
  
  *

  Representation of Audit Findings in Quality Event IDs

  When a quality event is triggered directly from the Audit application, the Audit Finding event type is represented in the Quality Event ID by the abbreviation AF.
  
  However, if the quality event is created independently, the abbreviation used for Audit Finding will vary based on its nature:

  • AFI is used for internal audit findings.
  • AFE is used for external audit findings.

  
  
• The event type will be set to Audit Finding (Internal).
  • The Event Type field will be disabled to prevent modifications.
• The severity will be set to Minor.
  • Users can modify this selection, if needed, to more accurately reflect the issue at hand.
• The site will match the selected site for the audit.
  • Users can also modify this selection, if needed.
• The Audit Plan ID (Internal) field will be disabled
  • It will retain the applicable value generated in the Audit application.
• The Audit Information accordion will be visible, containing the relevant audit details.