Scenario event form

---
title: Scenario event form
description: Use the Scenario event form in Operational Resilience Workspace to associate a scenario event with your scenario analysis.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/sce-event-form.html
release: australia
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Add a scenario event, Adding a scenario event to the analysis, Enable the legacy scenario analysis flow, Legacy scenario analysis, Scenario analysis, Manage, Operational Resilience, Governance, Risk, and Compliance]
---

# Scenario event form

Use the Scenario event form in Operational Resilience Workspace to associate a scenario event with your scenario analysis.

## Scenario event form

For a description of the field values, see the following table.

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

Field

</th><th>

Description

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

Details tab

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

Analysis scenario event panel

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

Event Name

</td><td>

Unique name for the event. This field is auto-filled.

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

Event group

</td><td>

Unique name for the event group. This field is auto-filled.

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

Status

</td><td>

Status of the event. Available options are:-   Draft
-   Completed

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

Description

</td><td>

Description of the event. This field is auto-filled.

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

Scenario

</td><td>

Scenario associated with the event. This field is auto-filled.

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

Pillars

</td><td>

Pillars associated with the event. This field is auto-filled.

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

Description

</td><td>

Description of the event. This field is auto-filled.

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

Impact panel

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

Potential start date time

</td><td>

Potential start date and time for the event. This field is auto-filled.

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

Potential end date time

</td><td>

Potential end date and time for the event.

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

Duration

</td><td>

Duration of the event. This field is auto-filled.

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

Notes

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

Observations

</td><td>

Observations added for the event by the participant.

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

Gaps

</td><td>

Gaps added for the event by the participant.

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

Recommendations

</td><td>

Recommendations added for the event by the participant.

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

Participants tab

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

Scenario analysis

</td><td>

Scenario analysis that is associated with the scenario event. This field is auto-filled.

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

Role

</td><td>

Role of the participant. Available options are:-   HR
-   Legal
-   Finance
-   Technology
-   People
-   Data
-   Security
-   Supplier Tier1
-   Supplier Tier2
-   Supplier Tier3

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

Participant

</td><td>

Participant of the scenario analysis such as Operational Resilience administrator or manager.

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

Instruction

</td><td>

Text box for adding the instructions for the participants of the scenario event.

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

Responses

</td><td>

Details about the response task such as its number, participant, impact duration, state, and so on.

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

Dependencies

</td><td>

Dependencies \(assets\) that are associated with the scenario event.

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

Scope

</td><td>

Services that are associated with the scenario event.

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

Issues

</td><td>

Issues that are associated with the scenario event.

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