> 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/incident-application/creating-and-managing-incidents/review-incident-report.md).

# Review Incident Report

Review a submitted incident and determine the appropriate next steps.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Review Incident Report

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

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

***

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

The **Review Incident Report** 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>

When an incident is submitted, review the report to understand the situation and determine the appropriate course of action.

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

{% hint style="warning" %}
To download a PDF copy of the incident report, click **Download PDF** at the bottom of the form.
{% endhint %}

{% 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 Incident

Review the incident report to ensure it is complete and appropriate for further processing. Consider the following:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>✅ <strong>Clarity &#x26; Completeness</strong></td><td>Is the incident clearly documented with sufficient detail, accurate information, and supporting evidence?</td></tr><tr><td>✅ <strong>Classification &#x26; Impact</strong></td><td>Does the report correctly classify the incident, reflecting the true risk and urgency of the situation?</td></tr><tr><td>✅ <strong>Context &#x26; Related Elements</strong></td><td>Does the report provide sufficient context to understand the incident and its related impacts, dependencies, or associations?</td></tr><tr><td>✅ <strong>Response &#x26; Follow-Up Actions</strong></td><td>Were immediate response actions appropriate, and are any proposed follow-up actions clear, effective, and measurable?</td></tr></tbody></table>

{% hint style="info" %}
This task uses a form similar in layout and content to the **New Incident** form.

* For instructions on how to complete each field, refer to the [corresponding form documentation](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents/create-new-incident.md).
  {% endhint %}

***

{% endstep %}

{% step %}

### Assign Investigator (Optional)

Select the user, role, or group responsible for investigating the root cause of the incident.

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

***

{% endstep %}

{% step %}

### Provide Recommendations for Consideration

Document actionable recommendations, improvement opportunities, or preventive measures identified during the incident review.

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

***

{% endstep %}

{% step %}

### Provide Feedback

Use the **Comments** field to share feedback, ask questions, or collaborate with others.

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

{% hint style="info" %}

#### Commenting Guidelines

* You can **edit**, **delete**, or **reply** to your own comments.
* You can **reply** to others' comments but cannot edit or delete them.
  {% endhint %}

***

{% endstep %}

{% step %}

### Escalate to QE or CAPA (Optional)

If the incident requires further review and processing beyond standard incident 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 Review

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

* **Requires More Details (Send Back to Creator)**

  Return the report to its creator for revisions or additional information.

  → Next Step: [Modify Incident Report](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents/modify-incident-report.md)

{% hint style="info" %}
Once changes are made, the creator can resubmit the report for further review.
{% endhint %}

* **Request a Root Cause Analysis**

  Request a formal investigation to determine the underlying cause of the incident.

  → Next Step: [Execute Root Cause Investigation & Create Actions](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents/execute-root-cause-investigation-and-create-actions.md)
* **Escalate the Issue**

  Escalate the incident 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 %}

* **No Issue (Close Incident)**

  Close the incident if no underlying issue is found.

* **Review Completed (Trigger Actions)**

  Complete the review and initiate any defined follow-up actions.

  → Next Step: [Execute Action(s)](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents/execute-action-s.md)

{% hint style="warning" %}

#### How Resolution Proceeds

Depending on the incident report, one of the following will occur:

* If **actions** are defined, they will be assigned to their respective owners for [execution](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents/execute-action-s.md).
  * Once all items are completed and approved, the reviewer will [verify the resolution](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents/check-effectiveness-and-approve-report.md).
* If **no actions** are defined, resolution is assumed to proceed without individual task tracking.
  * In this case, the reviewer will proceed directly to [validating that the resolution meets requirements](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents/check-effectiveness-and-approve-report.md).
    {% endhint %}

After selecting the appropriate resolution, click **Submit** to finalize your review 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 Incidents</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/incident-application/tracking-and-monitoring-incidents.md">Tracking &amp; Monitoring Incidents</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/incident-application/creating-and-managing-incidents/review-incident-report.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.