---
title: Create Digital Resilience Incident form
description: On the Create Digital Resilience Incident form, fill in the fields.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/create-new-dig-res-inci.html
release: australia
topic_type: reference
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Report a major incident manually, Manage, Using Digital resilience incident reporting, Manage, Operational Resilience, Governance, Risk, and Compliance]
---

# Create Digital Resilience Incident form

On the Create Digital Resilience Incident form, fill in the fields.

<table id="table_uj1_q5x_nvb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Number

</td><td>

Number of the case. This field is automatically set. For example, DRI000108.

</td></tr><tr><td>

Name

</td><td>

Name of the incident. For example, `DRI Case 1`.

</td></tr><tr><td>

Description

</td><td>

Description of the incident.

</td></tr><tr><td>

State

</td><td>

Workflow state of the incident. This field is automatically set to **Draft**.

</td></tr><tr><td>

Type

</td><td>

Nature or type of the incident. This field is automatically set to **Digital Resilience Incident Case**.

</td></tr><tr><td>

Subtype

</td><td>

Sub type of incident. For example, **Documentation Loss**.

</td></tr><tr><td class="sub-head" colspan="2">

Assignment

</td></tr><tr><td>

Requester

</td><td>

Person who reported the incident.

</td></tr><tr><td>

Assignment group

</td><td>

Group assigned to the case. **Note:** The assignment group is preconfigured to the case type during configuration setup.

</td></tr><tr><td>

Approvers

</td><td>

Approvers of the incident.

</td></tr><tr><td>

Requested on behalf of

</td><td>

Name of the person on whose behalf you’ve created the incident.

</td></tr><tr><td>

Analyst

</td><td>

Analyst who analyzes and works on the incident. The analyst is a part of the Assignment group.

</td></tr><tr><td>

Watch list

</td><td>

People who must be aware of the incident.

</td></tr><tr><td class="sub-head" colspan="2">

Primary origin

</td></tr><tr><td>

Source

</td><td>

Source of the case. This field is automatically set to **Manual** when the reporting case is manually created.

</td></tr><tr><td class="sub-head" colspan="2">

Schedule

</td></tr><tr><td>

Date of discovery

</td><td>

Date that the case is discovered by you. For example, the case may have occurred on 18-02-2024, but is discovered by the user only on 12-03-2024.

</td></tr><tr><td>

Date of occurrence

</td><td>

Date that the case occurred on. For example, the case may have occurred on 18-02-2024.

</td></tr><tr><td>

Closed date

</td><td>

Date that the case is closed on.

</td></tr><tr><td>

Reported date

</td><td>

Date that the case gets reported on.

</td></tr><tr><td>

Pending approval start date

</td><td>

Date that the case was resolved on.

</td></tr><tr><td>

Approved date

</td><td>

Post case review date of the case.

</td></tr><tr><td class="sub-head" colspan="2">

Reporting status

</td></tr><tr><td>

Regulatory reporting status

</td><td>

Primary cause of the case occurrence. Available options are:-   **Potentially reportable**
-   **Reportable**

</td></tr><tr><td>

Regulatory area

</td><td>

Digital Operational Resilience Act

</td></tr><tr><td class="sub-head" colspan="2">

Activity

</td></tr><tr><td>

Work notes \(Private\)

</td><td>

Notes or information regarding the case.

</td></tr><tr><td>

Comments \(Customer visible\)

</td><td>

Additional information regarding the case for the customers.

</td></tr><tr><td>

Email

</td><td>

Option to compose an email about the case to the stakeholders.

</td></tr><tr><td>

Attachments

</td><td>

Option to attach the PDF of the case.

</td></tr></tbody>
</table>