> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/review-and-approve-audit-results.md).

# Review & Approve Audit Results

Review audit results, assess findings, and either request clarification or sign off on the audit.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Review & Approve Audit Results

<i class="fa-user">:user:</i> **Performed By:** Assigned Resource (e.g., Audit Manager, Audit Director, Chief Audit Executive)

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

## Accessing the Task <a href="#accessing-the-task" id="accessing-the-task"></a>

The **Review & Approve Audit Results** task can be accessed through any of the following:

* The **To Do** module.
* The **Notification Panel** (via the **Notification Bell**).
* The **direct link** provided in the email notification.

***

## Completing the Task

After audit results are submitted, review the audit thoroughly to ensure it is complete, accurate, and ready for final approval.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% hint style="success" %}
For guidance on common form features and functions, see [**Working with Forms**](/interfacing-help-files/end-users/exploring-apps/working-with-forms.md).
{% endhint %}

{% hint style="info" %}

#### Saving Your Work

To save progress without submitting, click **Save** in the top-right corner of the panel.&#x20;

* The task remains in the **To Do** module for you to revisit and complete later.
  {% endhint %}

***

{% stepper %}
{% step %}

### Review Audit Information

Review the audit details to familiarize yourself with its scope, key parameters, schedule, and assigned participants.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

{% endstep %}

{% step %}

### Review Requirement Reports

Individually review the requirement reports submitted by auditors.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

* **View** ( ![](https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIAlpvjgSBR3lKZjwsXm7%2FIMS-KI-L-9.svg?alt=media\&token=262f3701-b544-43fe-b1bc-d17a29a18e55) ): Click to open a requirement report in read-only mode.
  * In **View** mode:
    * Review all details
    * [View or download available templates](/interfacing-help-files/end-users/exploring-apps/working-with-forms/generating-templates.md)
* **Expand** ( <i class="fa-up-right-and-down-left-from-center">:up-right-and-down-left-from-center:</i> ): Click to access the full requirement description.

***

{% endstep %}

{% step %}

### Review Findings & Comments

Review any findings and/or comments related to the audit and its requirements (submitted by the auditors). You may also add your own comments as needed.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

* **View** ( ![](https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIAlpvjgSBR3lKZjwsXm7%2FIMS-KI-L-9.svg?alt=media\&token=262f3701-b544-43fe-b1bc-d17a29a18e55) ): Click to open a finding in read-only mode.
* **Expand** ( <i class="fa-up-right-and-down-left-from-center">:up-right-and-down-left-from-center:</i> ): Click to access the full notes associated with a finding.

***

{% endstep %}

{% step %}

### Escalate Findings

You may initiate quality events or CAPAs based on audit findings.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% hint style="danger" %}

#### How Findings Trigger Quality Events and CAPAs

* A finding can only be used once to trigger a Quality Event or CAPA.
* A single quality event or CAPA applies to all findings selected in the corresponding dropdown.
  * To create separate quality events or CAPAs, select one finding at a time and click **Create Quality Event** or **Create CAPA** after each selection.
    {% endhint %}

#### <i class="fa-link-slash">:link-slash:</i> Quality Event

To initiate a quality event:

* **QE / CAPA Reviewer:** Select the user, role, or group responsible for reviewing the quality event.
* **Finding(s) for Quality Event:** Select one or more findings.
* **Create Quality Event:** Click to create a quality event.
  * A confirmation message will display the Quality Event ID.

{% hint style="info" %}
Following initiation, the assigned party will receive the [**Review the Issue**](/interfacing-help-files/quality-managers/quality-event-application/creating-and-managing-quality-events/review-issue.md) task. Details about the audit plan and the selected findings associated with the audit plan will be included in this task.

* For more information on the **Quality Event Management** workflow, refer to the [corresponding documentation](/interfacing-help-files/quality-managers/quality-event-application.md).
  {% endhint %}

#### <i class="fa-brake-warning">:brake-warning:</i> CAPA

To initiate a CAPA:

* **QE / CAPA Reviewer:** Select the user, role, or group responsible for reviewing the CAPA.
* **Finding(s) for CAPA:** Select one or more findings.
* **Create CAPA:** Click to create a CAPA.
  * A confirmation message will display the CAPA ID.

{% hint style="info" %}
Following initiation, the assigned party will receive the [Review CAPA](/interfacing-help-files/quality-managers/implementing-capas-apps/navigating-the-capa-management-workflow/review-capa.md) task. Details about the audit plan will be included in this task.

* For more information on the **CAPA Management** workflow, refer to the [corresponding documentation](/interfacing-help-files/quality-managers/implementing-capas-apps.md).
  {% endhint %}

{% hint style="danger" %}
All finding types can trigger a quality event; however, only **major observations** can trigger a CAPA.
{% endhint %}

***

{% endstep %}

{% step %}

### Distribute Audit Report (Optional)

If the finalized audit report should be shared, specify the intended recipients.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

* [**Distribute Audit Report To:**](#user-content-fn-1)[^1] Select one or more users, roles, or groups.
  * Once the audit is approved, selected recipients will receive an email with the audit report attached as a PDF.

***

{% endstep %}

{% step %}

### Finalize Review

From the **Task Resolution** dropdown, select one of the following actions:

* **Clarification Required**

  Return the audit to the assigned auditor(s) for updates or clarification.

  → Next Step: [Evaluate Requirements](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/evaluate-requirements.md)

{% hint style="info" %}
Once updated, the audit can be resubmitted for further review.
{% endhint %}

* **Sign-Off**

  Approve the audit results, concluding the workflow.

  You will be prompted to apply your digital signature to confirm approval.

  → See: [Applying Digital Signatures](/interfacing-help-files/end-users/exploring-apps/working-with-forms/applying-digital-signatures.md)

After selecting the appropriate resolution, click **Submit** to record your decision and advance the workflow.

***

{% endstep %}
{% endstepper %}

***

[^1]: 💡 **For Administrators:**

    * Manage the options that populate the **Distribute** dropdown in:
      * **Library** > [**Organization**](/interfacing-help-files/process-analysts/organization-management.md).
    * Only **active** users, roles, and groups will appear in the dropdown.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/review-and-approve-audit-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
