{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":17508,"path":"governance-risk-compliance/grc-risk-management-workspace/risk-event-response-template-form.md","title":null,"bundle":null,"doc_type":null,"release":null,"body":"---\ntitle: Risk Event Response Template form\ndescription: Use the Risk Event Response Template form to define assignment rules. Rules automatically assign owners, approvers, issues, and Root Cause Analysis \\(RCA\\) tasks to risk events based on entity, event type, category, and impact thresholds.\nlocale: en-US\ncanonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/grc-risk-management-workspace/risk-event-response-template-form.html\nrelease: australia\nproduct: GRC: Risk Management Workspace\nclassification: grc-risk-management-workspace\ntopic_type: reference\nlast_updated: \"2026-03-12\"\nreading_time_minutes: 6\nbreadcrumb: [Create a risk event response template, Use Risk Events, Use, Risk Management, Governance, Risk, and Compliance]\n---\n\n# Risk Event Response Template form\n\nUse the Risk Event Response Template form to define assignment rules. Rules automatically assign owners, approvers, issues, and Root Cause Analysis \\(RCA\\) tasks to risk events based on entity, event type, category, and impact thresholds.\n\nSee the following table for a description of the field values.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nNumber\n\n\n\nTemplate number. This field is automatically set.\n\n
\n\nEntity\n\n\n\nEntity that the template is created for.**Note:** When you select an entity in a Risk Event Response Template, the template applies to that entity and all its downstream entities unless a downstream entity has its own specific Risk Event Response Template. If a downstream entity does not have a separate template, the system applies the template from the nearest parent entity in the hierarchy.\n\n
\n\nCategory\n\n\n\nCategory that the risk event applies to if there’s an occurrence. You can edit the category to apply one of the following options.- **Personal**: For example, any physical harm caused to an employee.\n- **Legal**: For example, an employee conducts a business that is a conflict of interest.\n- **Information Security**: For example, a theft, burglary, or system crash.\n- **Human Resources**: For example, sensitive lawsuits by an employee against another employee.\n- **All**: Any risk event that is reported.\n\n
\n\nApproval rule based on\n\n\n\nRule used while assigning the event. - **Gross Loss**\n- **Net Loss**\n- **Expected Loss**\n\nThis field depends on the values in the **Event type** and **Sub type** fields. For example, - If the event type is **Financial**, and the sub type is **Actual**, the approval rule is based on gross loss, net loss, or expected loss.\n- If the event type is **Financial**, and the Sub type is **Potential**, the approval rule is expected loss, by default.\n- If the Event type is **Non-Financial Impact**, the approval rule is Non-financial, by default.\n\n
\n\nEvent type\n\n\n\nClassification of the event based on the type of impact on the organization. This field determines whether the event has a financial or non‑financial consequence. The options are as follows:- **Financial Impact**: Indicates that the event has an associated financial loss. Enter the amount. You can choose the currency.\n- **Non-Financial Impact**: Indicates that while the event doesn’t have any financial loss, it does have a non-financial impact on the organization. For example, non-financial impact can be negative market news or a decline in employee morale.\n\n
\n\nSub type\n\n\n\nClassification of the event based on whether the impact has already occurred or may occur in the future. The options are as follows:- **Actual**\n- **Potential**\n\n
\n\nAuto close event once approved\n\n\n\nOption to select if the event must be closed after approval. Selecting this option results in closing of the event after the issue and root cause are closed. If a risk event has open issues or tasks, the risk event isn’t closed even after approval.\n\n
\n\nCurrency conversion date\n\n\n\nCurrency conversion dates for the risk event entries. You can select specific dates for currency conversion rather than relying solely on the date of impact to calculate the net loss. The options are as follows:- **Risk event entry date**\n- **First loss entry date**\n- **Last loss entry date**\n- **First recovery entry date**\n- **Last recovery entry date**\n- **Custom date**\n\n
\n\nRisk Event Owner Assignment\n\n
\n\nAssignment type\n\n\n\nSpecifies how the risk event owner is determined for the record. The selected assignment type controls whether the event is assigned to an individual user, a group, or derived dynamically from the selected entity. The options are as follows:- **User**: Option to assign ownership directly to a specific user.\n- **Group**: Option to assign ownership to a group.\n- **User field on entity**: Option to assign ownership based on a predefined user field on the associated entity record.\n- **Entity stakeholder**: Option to assign ownership to a stakeholder associated with the selected entity.\n\n
\n\nOwner\n\n\n\nUser assigned as the risk event owner. This field appears only when **User** is selected from **Assignment type**.\n\n
\n\nOwning group\n\n\n\nGroup responsible for the risk event. This field appears only when **Group** is selected from **Assignment type**.\n\n
\n\nRisk event owner field on entity\n\n\n\nUser field on the associated entity used to derive the risk event owner. For example, the owner of the entity can be the risk event owner. This field appears only when **User field on entity** is selected from **Assignment type**.\n\n
\n\nPersona\n\n\n\nStakeholder role associated with the entity. Specifies the stakeholder role, such as Head of Business or Risk Manager, that the system uses to determine ownership or responsibility when assignment is based on an entity stakeholder. This field appears only when **Entity stakeholder** is selected from **Assignment type**.**Note:** Based on the selected persona, the **Owning group** field is auto-populated.\n\n
\n\nIssue Creation and Assignment\n\n
\n\nAutomatically create issue\n\n\n\nOption to create issue automatically based on the configured threshold and assignment settings.\n\n
\n\nThreshold for issue creation\n\n\n\nOption to specify the threshold amount after which an issue is created automatically. For example, users can specify that after an event crosses loss worth $1000, an issue must be created.**Note:** This field appears only when **Automatically create issue** is selected.\n\n
\n\nAssignment type\n\n\n\nOptions to determine the issue owner for the record. The selected assignment type controls whether the issue is assigned to an individual user, a group, or derived dynamically from the selected entity. The options are as follows:- **User**: Option to assign ownership directly to a specific user.\n- **Group**: Option to assign ownership to a group.\n- **User field on entity**: Option to assign ownership based on a predefined user field on the associated entity record.\n- **Entity stakeholder**: Option to assign ownership to a stakeholder associated with the selected entity.\n\n**Note:** This field appears only when **Automatically create issue** is selected.\n\n
\n\nAssigned to\n\n\n\nUser assigned as the issue owner. This field appears only when **User** is selected from **Assignment type**.\n\n
\n\nAssignment group\n\n\n\nGroup responsible for the issue. This field appears only when **Group** is selected from **Assignment type**.\n\n
\n\nIssue assignee field on entity\n\n\n\nUser field on the associated entity used to derive the issue owner. For example, the owner of the entity can be the issue owner. This field appears only when **User field on entity** is selected from **Assignment type**.\n\n
\n\nPersona\n\n\n\nStakeholder role associated with the entity. This field identifies the type of stakeholder \\(for example, Head of Business or Risk Manager\\) used to determine ownership or responsibility when assignment is based on an entity stakeholder. This field appears only when **Entity stakeholder** is selected from **Assignment type**.\n\n
\n\nOwning group\n\n\n\nBased on the selected Persona, the **Owning group** field is auto-populated.\n\n
\n\nRoot Cause Analysis Task\n\n
\n\nAutomatically create RCA task\n\n\n\nOption to create a task for root cause analysis \\(RCA\\). Automatically create a Root Cause Analysis \\(RCA\\) task based on the amount entered in the **Threshold for task creation** field.\n\n
\n\nAssigned to\n\n\n\nPerson that the RCA task is assigned to.**Note:** This field appears only when **Automatically create RCA task** is selected.\n\n
\n\nThreshold for task creation\n\n\n\nOption to specify the threshold amount after which an RCA task is created automatically. For example, users can specify that after an event crosses loss worth $1000, an RCA task must be created.**Note:** This field appears only when **Automatically create RCA task** is selected.\n\n
\n\nPriority\n\n\n\nPriority of the event. The options are as follows: - **Critical**\n- **High**\n- **Moderate**\n- **Low**\n- **Minor**\n\n**Note:** This field appears only when **Automatically create RCA task** is selected.\n\n
**Parent Topic:**[Create a risk event response template](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/grc-risk-management-workspace/create-risk-event-response-template.md)\n\n"}}