--- title: Add or modify risk and impact conditions description: Define the risk calculation rules that determine the risk and impact of a change. The Change Management - Change Risk Calculator plugin is active by default in the base system. locale: en-US canonical_url: https://www.servicenow.com/docs/r/it-service-management/change-management/define-risk-and-impact-conditions.html release: brazil product: Change Management classification: change-management topic_type: task last_updated: "2026-07-16" reading_time_minutes: 3 breadcrumb: [Risk conditions and calculation, Analyze change request risk and impact, Reference, Change Management, IT Service Management] --- # Add or modify risk and impact conditions Define the risk calculation rules that determine the risk and impact of a change. The Change Management - Change Risk Calculator plugin is active by default in the base system. ## Before you begin Role required: itil\_admin or admin ## About this task Risk conditions are run against the change request in the order of their **Order** field from lowest to highest. The first risk condition that matches the change request record is applied. All subsequent risk conditions are then ignored whether they match or not. A risk calculation rule is defined with two elements. - Conditions that can evaluate to *true* or *false*. You can use a condition builder or write a script. - **Risk** and **Impact** field value settings when the conditions evaluate to **true**. ## Procedure 1. Navigate to **All** > **Change** > **Administration** > **Risk Conditions**. 2. Select **New**, or select the risk condition to modify. To stop a base-system condition such as **Insufficient lead time** from applying, open the condition and clear the **Active** check box instead of deleting it so that you can re-enable it later. You can also edit risk conditions from within the Change Request form by opening the form context menu and selecting **Edit Risk Conditions**. 3. On the form, fill in the fields.
Field Description
Name Descriptive name for the rule.
RiskImpact Value that this risk calculation sets in the **Risk** or **Impact** field of the change request.
Active Option that, when selected, applies the rule.
Order Order in which this risk calculation is evaluated. Rules with lower numbers are evaluated first. If there are two or more rules with differing orders, the rule with the lowest order is evaluated and the others are ignored.
Use advanced condition Option that, when selected, lets you enter a script instead of using the condition builder.
Use script values Option that, when selected, hides the **Risk** and **Impact** fields. The script specifies the risk and impact values.
Description Description of how this risk calculation is applied.
**Important:** If the **Calculated risk** value doesn't update, check the following: - The rule's **Active** check box is selected. - No rule with a lower **Order** value matched the change request first. The first matching rule wins, and the system ignores later rules. - If **Use script values** is selected, the script assigns both the **Risk** and **Impact** values. 4. Specify the rule based on your selected rule method.
Choice Action
**Condition** Use the condition builder to add conditions. Do not use the Keywords field as a filter condition. Risk and impact values are not calculated for keywords. To achieve equivalent filtering, use the **Use advanced condition** option and write a script that performs the text comparison explicitly.**Note:** The **Condition** section is hidden if you selected **Use advanced condition**.
**Use advanced conditions** Write the script in the **Advanced condition** field using standard business rule syntax. The condition must set the global variable answer to *true* or *false*.
**Use script values** Write the script in the **Script values** field. Specify the **Risk** and **Impact** values in the script.The conditions are set using either the condition builder or an advanced condition script.
In the following example, the **Advanced condition** script first determines whether the CI is a business service. If so, the script identifies whether the **Business criticality** value is **1 - most critical** or **2 - somewhat critical**. If it does, it sets the global variable answer to *true*. \[Omitted image "risk-condition-rule.png"\] Alt text: Critical business service risk condition When the **Advanced condition** script returns *true*, the script in the **Script values** field sets the change request **Impact** and **Risk** values based on the **Business criticality** value. To set risk based on lead time per change type, create two conditions. The previous example applies to change processes configured to use change models. If you're using legacy change types, set the condition using the **Type** field instead of the **Model** field. - Build a condition where **Model** is **Normal** and the planned start date is fewer than seven days from now, then set **Risk** to **High**. - Build a condition where **Model** is **Standard** and the planned start date is fewer than three days from now, then set **Risk** to **Moderate**. Set the **Order** values so these conditions evaluate before broader rules. The first matching condition is applied. **Parent Topic:**[Risk conditions and calculation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/change-risk-assess-detect-conflict.md) **Related topics** [Risk Calculator property]()