---
title: "Closing an Incident Record"
slug: "closing-an-incident-record"
tags: ["v8.2"]
updated: 2026-10-06T22:32:09Z
published: 2026-10-06T22:32:09Z
canonical: "docs.serenityops.com/closing-an-incident-record"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serenityops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Closing an Incident Record

In Serenity, closing an incident signals the completion of the response, documentation, and review process. While the platform provides guardrails to ensure compliance and completeness, **each organization defines its own policies** for when an incident can be formally closed.

## When Should an Incident Be Closed?

This decision is typically guided by your internal **EHS policy or SOPs**. Here are some common approaches:

| **Closure Trigger** | **Description** |
| --- | --- |
| **After Reports are finalized** | Some teams close the incident once injury, release, or property damage reports are finalized |
| **Post-Investigation** | Others wait until formal investigations and root cause analysis are completed and findings are identified |
| **After All Follow-ups** | Some organizations require that all findings and corrective and preventive actions (CAPAs) are completed |

**Tip:** Serenity supports **any of these workflows**. The only enforced system rule is that **all associated detailed reports must be finalized** before closure.

## System Requirements for Closure

To close an incident, the following must be true:

- All injury and illness reports are finalized
- All release reports are finalized
- All property damage and vehicle damage reports are finalized

If any of these reports are still open, selecting **Close incident** displays a message listing the open reports. Complete them before closing the incident.

## How to Close an Incident

1. Open the incident record
2. Select the **Close incident** button (top right of the screen)
3. In the **Close Task** window, enter **Close notes** and, if the closure needs approval, select **Request review**. When you request a review, select one or more **Reviewers** (required)
4. Select **Continue** to proceed to the certification step
5. Read the certification statement: "I certify that I have examined this document and that to the best of my knowledge the entries are true, accurate, and complete."
6. Type your signature or draw it, using the **Type signature** or **Draw signature** tab
7. Select **Sign and submit**

![](https://cdn.us.document360.io/7951ec8a-9aa7-4a24-82dd-bc5d6b13dc78/Images/Documentation/close-incident-dialog.png?sv=2026-02-06&spr=https&st=2026-11-03T19%3A09%3A17Z&se=2026-11-03T20%3A09%3A17Z&sr=c&sp=r&sig=GGoAYxnbOyjW5JXMVS1KEJkCwDAMgZ1LsiaesoEgFgk%3D)

![Certification and signature step](https://cdn.us.document360.io/7951ec8a-9aa7-4a24-82dd-bc5d6b13dc78/Images/Documentation/base64-converted-image-1791325676405.gif?sv=2026-02-06&spr=https&st=2026-11-03T19%3A09%3A17Z&se=2026-11-03T20%3A09%3A17Z&sr=c&sp=r&sig=GGoAYxnbOyjW5JXMVS1KEJkCwDAMgZ1LsiaesoEgFgk%3D)

## What Happens Next?

### Without Review:

- The incident moves directly to the **Complete** stage
- It becomes read-only. A **Reopen incident** button appears, and only users with the Admin role in the Environmental, Health, & Safety category can reopen it

### With Review:

- The incident enters the **Closure stage**
- The selected **Reviewers are notified by email**
- Reviewers can:
  - **Approve** the incident for closure
  - **Request changes**, which sends a notification back to the assignee to revise and re-submit the record

**Note:** This ensures that your team can apply a review and approval workflow **only when needed**, without delaying more routine incident closures.

## Best Practices

- Define closure criteria in your organization’s EHS policy or training guide
- Use **Close Notes** to summarize final observations, especially if review is required