9.5. Sign Off on the Action

Once the action item has been completed, the assigned reviewer will receive a notification in their Pending Tasks, prompting them to sign off on it.

*If the action item involved a SCAR, this step will take place after the completion of the SCAR Management workflow.

*An email notification will also be sent to alert the reviewer about the task. For more information on email notifications and their role in the application, click here.

Clicking on either the subject in Pending Tasks or the button in the email will direct users to the Sign Off on the Action form. This form displays all information entered in the Execute the Action form; however, most fields are set to read-only. Users can review the execution of the action, perform an effectiveness check, and provide any necessary feedback or comments. After their review, users can decide to either approve the action, officially marking it as completed, or reject it, returning it to the designated owner for further modifications.

*For guidance on common form functions, please refer to the dedicated section in the manual.

1. Accordion: The form includes a collapsible section, known as an accordion, which allows for an evaluation of the action’s effectiveness.
   • Effectiveness Check
     

     **Note that while other accordions in the form are read-only, users can still review the information within them, which is carried over from previous stages of the workflow, to inform their assessment

2. General Comment: This is a rich text field that allows users to provide feedback on the action taken.
   

   !!If an action is to be rejected, this field will become mandatory, as users are required to provide a reason for the rejection. Any notes provided will be visible to the action item owner in the Action Refused by Reviewer form.

3. Comment: This field allows users to add additional comments or notes on the action.
   

   **The Comment control functions similarly to a discussion board, enabling collaborative discussions with stakeholders involved in the workflow.

4. Save Form: This button allows users to save the form.
   • It will remain in the Pending Tasks folder.
5. Reject Action: This button allows users to reject the action.
   • If selected, the assigned action item owner will be tasked with re-executing it.
     

     !!If the action item involved a SCAR, it is not possible to reject it.

6. Approve Action: This button allows users to approve the completed action, bringing the workflow to an end.