> 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/create-a-sensitive-event.md).

# Create a Sensitive Event

Create and submit a sensitive even report to initiate the Sensitive Event workflow.

Use the **Create a Sensitive Event** form to report and document sensitive events.

<figure><img src="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FFH0YeOtZmsmhehW84Gfk%2Fse%20ims.png?alt=media&amp;token=ad0ce96a-9889-4bbf-ad08-a00409cc99a3" alt="" width="563"><figcaption></figcaption></figure>

***

{% hint style="danger" %}
Required fields are highlighted in yellow and must be completed before submitting your request
{% endhint %}

{% stepper %}
{% step %}

### Define Event Details

Provide complete and accurate information about the sensitive event being reported.

* <mark style="background-color:yellow;">**Nature of the Event**</mark>**:** Select the type of sensitive event from the dropdown list.&#x20;
  * Available options include **Bullying, Corruption, Discrimination, Environmental Violation, Fraud, Harassment, Safety Violation, Whistleblower,** and **Other (Please Specify)**.
    * If **Other** is selected, an additional text field (**Other Event Type**) will appear, allowing you to specify the nature of the event.
* **Event ID:** \
  Automatically generated unique identifier used to track and reference the event throughout its lifecycle.
* **Location of the Event:** \
  Enter the location where the event occurred. Include details such as address, building, area, or site name.
* **Reported Date:**\
  Select or confirm the date and time when the event was reported. This field defaults to the current date and time.
  {% endstep %}

{% step %}

### Associate Business Information

Identify the organizational area associated with the sensitive event.

* **Business Division:**\
  Select the applicable business division or department. The list of available divisions is managed by your administrator.

{% hint style="info" %}
Selecting a division filters the options available in the **Business Line** field.
{% endhint %}

* **Business Line:**\
  Select the relevant business line associated with the event. Only business lines belonging to the chosen division are displayed.
  {% endstep %}

{% step %}

### Identify Witnesses

Record any individuals who observed or have direct knowledge of the event.

* **Witness(es):**\
  Select one or more witnesses from the list of active users.&#x20;
* **Any Witnesses Whose Name Is Not in the List?:**\
  If witnesses are not listed in the system, manually enter their names here.&#x20;
  {% endstep %}

{% step %}

### Specify Event Timing

Indicate when the event occurred.

* **Date / Time of Event:**\
  Select the exact date and time of the event.
* **From / To:**\
  If the event occurred over a period of time, specify the start and end dates.
  {% endstep %}

{% step %}

### Describe the Event

Provide a comprehensive description of what occurred.

* <mark style="background-color:yellow;">**Provide a Detailed Description of the Event**</mark>**:**\
  Enter a detailed, factual description of the event, including circumstances, actions taken, and individuals involved.&#x20;
* **Evidence:**\
  Attach any supporting documents, images, or other files related to the event.&#x20;
  * Click **Upload Files** to browse your documents.
    {% endstep %}

{% step %}

### Specify Anonymity Preference

Indicate whether you wish to remain anonymous.

* **Anonymity Preference**:
  * **Anonymous** → your identity will be hidden.
  * **Named** → additional fields appear: **Name, Email, Phone**. Fill in these fields if reporting with your identity.
    {% endstep %}

{% step %}

### Submit the Form

* Click **Submit Form**.
* The report will trigger the **Sensitive Event Management workflow**:
  * **Default reviewer:** Head of HR.
  * **Task location:** Pending Tasks folder of assigned role.
  * Tasks can be customized via the **Designer program** to assign to users, roles, or groups.
    {% endstep %}
    {% endstepper %}

***

### **Quick Tips**

* Complete all **mandatory fields** to avoid submission errors.
* Upload relevant evidence to strengthen the report.
* Double-check **Business Division and Line** for accurate routing.
* Use “Other” fields only when necessary.


---

# 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/create-a-sensitive-event.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.