> 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/regulatory-compliance/sensitive-events-application/navigating-the-sensitive-events-workflow.md).
# Navigating the Sensitive Events Workflow
Perform the tasks assigned to your role to advance event reports through the Sensitive Event workflow.
### Workflow Overview
The **Sensitive Event(s)** application manages the full lifecycle of a sensitive event report, from initial submission through review, investigation, containment, corrective actions, and final resolution. The workflow ensures timely review, appropriate intervention, and organizational accountability.
***
### Workflow Stages
The workflow is organized into key stages, each with specific roles and responsibilities.
{% hint style="success" %}
For detailed instructions on any stage, click the corresponding button.
{% endhint %}
{% stepper %}
{% step %}
### Create New Sensitive Event
> **Performed By:** Reporter (e.g., Employee, Site Manager, Project Lead)
**Responsibilities:**
* Identify and report a sensitive event.
* Provide necessary details, including:
* Event description and context
* Location information
* Witnesses
* Evidence & supporting documentation
* Submit the report to initiate the workflow.
***
{% endstep %}
{% step %}
### Review Event Report
> **Performed By:** Reviewer (e.g., Compliance Officer, Risk Manager)
**Responsibilities:**
* Confirm the report is complete and accurate.
* Determine the appropriate next step:
* Assign for investigation
* Assign for immediate containment
* Add comments or flag issues for attention.
* Escalate the report for further investigation if necessary.
***
{% endstep %}
{% step %}
### Containment of the Event
> **Performed By:** Assigned Owner (e.g., Department Manager, Compliance Manager, Executive Sponsor)
**Responsibilities:**
* Review investigation findings and recommendations.
* Implement immediate containment measures if required.
* Document containment actions and provide supporting evidence.
* Decide whether to:
* Approve issue containment
* Return the report to the investigator for additional information or investigation
***
{% endstep %}
{% step %}
### Execute Corrective Action(s)
> **Performed By:** Assigned Action Item Owner(s) (Internal or External)
**Responsibilities:**
* Complete corrective actions defined in the workflow.
* Provide observations and upload supporting documentation for each executed action.
* If an action involves a Supplier Corrective Action Request (SCAR), the supplier representative executes the SCAR instead of the standard workflow.
{% hint style="warning" %}
**Note:** The workflow cannot proceed until all actions, including SCARs, are completed, reviewed, and approved.
{% endhint %}
***
{% endstep %}
{% step %}
### Sign-off on Resolution
> **Performed By:** Head of HR or Designated Reviewer
**Responsibilities:**
* Review all details of the event, including investigation, containment/correction measures, and executed actions.
* Provide feedback via comments, if needed.
* Approve the resolution to conclude the workflow, or reject the resolution and return the report for further investigation.
{% endstep %}
{% endstepper %}
***
---
# 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/regulatory-compliance/sensitive-events-application/navigating-the-sensitive-events-workflow.md?ask=&goal=
```
`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.
