> 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/quality-managers/complaint-application/creating-and-managing-complaints/check-effectiveness-of-actions.md).

# Check Effectiveness of Actions

Verify that the complaint has been effectively addressed and determine whether the report can be closed.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Check Effectiveness of the Actions

<i class="fa-user">:user:</i> **Performed By:** Assigned Reviewer (e.g., Supervisor, Department Manager, QA Analyst)

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

***

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

The **Check Effectiveness of the Actions** 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 <a href="#completing-the-task" id="completing-the-task"></a>

After all defined actions have been completed and approved, review the complaint to confirm that the response effectively resolved the issue and meets organizational requirements.

<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 %}

### Evaluate Effectiveness

Review the complaint outcome to confirm that the issue has been appropriately addressed and that the report is ready for closure. Consider the following:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>✅ <strong>Resolution Effectiveness</strong></td><td>Did the implemented measures effectively address the complaint and resolve the identified issue?</td></tr><tr><td>✅ <strong>Residual Risk</strong></td><td>Are there any remaining risks, unresolved issues, adverse impacts, or follow-up activities requiring additional attention or escalation?</td></tr><tr><td>✅ <strong>Overall Readiness for Closure</strong></td><td>Does the report contain sufficient documentation, approvals, evidence, and outcomes to support formal closure?</td></tr></tbody></table>

***

{% endstep %}

{% step %}

### Document Resolution & Closure

Use the available fields to document the final resolution of the complaint.

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

* **Date of Resolution:** Select the date the complaint was resolved.
* **Complainant Notified:** Select if the complainant has been informed of the resolution.
* **Resolution Provided:\*** Describe the resolution implemented to address the complaint, including any actions taken and outcomes achieved.
* **Feedback from Complainant:** Document any feedback, comments, concerns, or confirmation received from the complainant regarding the resolution.

***

{% endstep %}

{% step %}

### Escalate to QE or CAPA (Optional)

If the complaint requires further review and processing beyond standard complaint handling, escalate the issue to a quality event (QE) or CAPA.

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

* **Escalate the Issue to QE or CAPA?:** Select the appropriate escalation path.
  * In the field that appears, select the user, role, or group responsible for reviewing the report.

***

{% endstep %}

{% step %}

### Finalize Assessment

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

* **Close**

  Close the complaint, concluding the workflow.
* **Escalate the Issue**

  Escalate the complaint to a quality event or CAPA for further processing.

{% hint style="warning" %}

#### How Escalation Works

Based on the selected escalation path, the issue is automatically routed to the appropriate workflow:

* **Quality Event**

  → Workflow: [**Quality Event Management**](/interfacing-help-files/quality-managers/quality-event-application/creating-and-managing-quality-events.md)

  → Task: [**Review Issue**](/interfacing-help-files/quality-managers/quality-event-application/creating-and-managing-quality-events/review-issue.md)
* **CAPA**

  → Workflow: [**CAPA Management**](/interfacing-help-files/quality-managers/implementing-capas-apps/navigating-the-capa-management-workflow.md)

  → Task: [**Review CAPA**](/interfacing-help-files/quality-managers/implementing-capas-apps/navigating-the-capa-management-workflow/review-capa.md)
  {% endhint %}

After selecting the appropriate resolution, click **Submit** to finalize your assessment and advance the workflow.

***

{% endstep %}
{% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Tracking &#x26; Monitoring Complaints</strong></td><td>Monitor the status and progress of incidents using lists and dashboards.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FNZOvD3ldHJ3i1zsvDksS%2FCR-V16-Icons-1.png?alt=media&amp;token=7c420cc4-9abf-4601-8fc3-8e9769771b27">App-V16-Icons-1.png</a></td><td><a href="/interfacing-help-files/quality-managers/complaint-application/tracking-and-monitoring-complaints.md">Tracking &amp; Monitoring Complaints</a></td></tr></tbody></table>


---

# 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/quality-managers/complaint-application/creating-and-managing-complaints/check-effectiveness-of-actions.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.