Recalculate a remediation target date
The remediation target (RT) date defines when a finding must be remediated. Recalculation verifies that RT dates stay accurate and reflect the latest risk rating updates. When a finding’s risk rating changes, the system can recalculate RT dates using the most recent update date, helping maintain accurate SLAs and avoid outdated or overdue target dates.
Before you begin
Note: By default, recalculation applies only to findings that aren’t overdue. To include overdue findings in the recalculation, enable the sn_sec_cmn.evaluate_targetmissed_records system property.
Role required: admin
About this task
[Omitted video] Description: Recalculate remediation target date
Procedure
-
Navigate to Security Exposure Management > Administration > Remediation Target Rules.
-
Open an existing rule to make updates.
If you need to create a new rule, select New.
For instructions, see Create or edit a Vulnerability Response remediation target rule.
-
Select the fields that should trigger recalculation of the remediation target (RT) date.
- In Workspace and Classic view, use the Recalculate when any of these fields change field.
- You can select one or more of the available fields, such as Risk rating and Assignment group. At least one field must be selected for recalculation to occur.
-
Choose how the system should recalculate the remediation target (RT) date when the risk rating changeswhen a selected field changes.
- In Workspace, this option appears in the Recalculate target date section
- In Classic view, use the Target recalculation method field.
|
Choice |
Description |
|---|---|
|
Default calculation |
Recalculates the RT date using the standard formula (Target from (date) + Target (days)), based on the rule that currently matches the finding's risk ratingthe finding. The Field change time-based recalculated date is not applied. |
|
Recalculate from trigger field change date |
Updates the Remediation Target date to: Field change time + Target (days) based on the rule that matches the finding's updated values. |
|
Recalculate from risk change date |
Updates the Remediation Target date to: Field change time + Target (days) based on the new risk rating. |
|
Recalculate from trigger field change date and always set to the earliest target date |
Compares the existing RT date with Field change time + Target (days) and applies the earlier date. |
|
Recalculate from risk change date and always set to earliest target date |
Compares the existing RT date with Field change time + Target (days) and applies the earlier date. |
|
Recalculate from risk rating change date and set to the earliest target date only when risk rating increases (available only when Risk rating is selected as a trigger field) |
If the risk increases: Compares the existing RT date and the recalculated RT date and applies the earliest date. If the risk decreases: Compares the existing RT date and the recalculated RT date and applies whichever date is farther out (later). |
|
Recalculate from risk change date and set to earliest target date only when risk rating increases |
If the risk increases: Compares the existing RT date and the recalculated RT date and applies the earliest date. If the risk decreases: Compares the existing RT date and the recalculated RT date and applies whichever date is farther out (later). |
What to do next
For more information on remediation target rules, see:
---
title: Recalculate a remediation target date
description: The remediation target \(RT\) date defines when a finding must be remediated. Recalculation verifies that RT dates stay accurate and reflect the latest risk rating updates. When a finding’s risk rating changes, the system can recalculate RT dates using the most recent update date, helping maintain accurate SLAs and avoid outdated or overdue target dates.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/security-management/vulnerability-response/sem-recalculate-rt-date.html
release: brazil
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 3
keywords: [Remediation target, Recalculate remediation target date]
breadcrumb: [Create or edit a Vulnerability Response remediation target rule, Configuring Vulnerability Response using the Setup Assistant, Vulnerability Response implementation, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---
# Recalculate a remediation target date
The remediation target \(RT\) date defines when a finding must be remediated. Recalculation verifies that RT dates stay accurate and reflect the latest risk rating updates. When a finding’s risk rating changes, the system can recalculate RT dates using the most recent update date, helping maintain accurate SLAs and avoid outdated or overdue target dates.
## Before you begin
**Note:** By default, recalculation applies only to findings that aren’t overdue. To include overdue findings in the recalculation, enable the **sn\_sec\_cmn.evaluate\_targetmissed\_records** system property.
Role required: admin
## About this task
\[Omitted video\] Description: Recalculate remediation target date
## Procedure
1. Navigate to **Security Exposure Management** > **Administration** > **Remediation Target Rules**.
2. Open an existing rule to make updates.
If you need to create a new rule, select **New**.
For instructions, see [Create or edit a Vulnerability Response remediation target rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/create-time-to-remediate-rule.md).
3. Select the fields that should trigger recalculation of the remediation target \(RT\) date.
- In Workspace and Classic view, use the **Recalculate when any of these fields change** field.
- You can select one or more of the available fields, such as **Risk rating** and **Assignment group**. At least one field must be selected for recalculation to occur.
4. Choose how the system should recalculate the remediation target \(RT\) date when the risk rating changeswhen a selected field changes.
- In Workspace, this option appears in the Recalculate target date section
- In Classic view, use the **Target recalculation method** field.
<table id="choicetable_bb3_q3b_fhc"><thead><tr><th align="left" id="d372431e175">
Choice
</th><th align="left" id="d372431e178">
Description
</th></tr></thead><tbody><tr><td id="d372431e184">
**Default calculation**
</td><td>
Recalculates the RT date using the standard formula \(Target from \(date\) + Target \(days\)\), based on the rule that currently matches the finding's risk ratingthe finding. The Field change time-based recalculated date is not applied.
</td></tr><tr><td id="d372431e201">
**Recalculate from trigger field change date**
</td><td>
Updates the Remediation Target date to: Field change time + Target \(days\) based on the rule that matches the finding's updated values.
</td></tr><tr><td id="d372431e211">
**Recalculate from risk change date**
</td><td>
Updates the Remediation Target date to: Field change time + Target \(days\) based on the new risk rating.
</td></tr><tr><td id="d372431e221">
**Recalculate from trigger field change date and always set to the earliest target date**
</td><td>
Compares the existing RT date with Field change time + Target \(days\) and applies the earlier date.
</td></tr><tr><td id="d372431e232">
**Recalculate from risk change date and always set to earliest target date**
</td><td>
Compares the existing RT date with Field change time + Target \(days\) and applies the earlier date.
</td></tr><tr><td id="d372431e242">
**Recalculate from risk rating change date and set to the earliest target date only when risk rating increases \(available only when __Risk rating__ is selected as a trigger field\)**
</td><td>
If the risk increases: Compares the existing RT date and the recalculated RT date and applies the earliest date. If the risk decreases: Compares the existing RT date and the recalculated RT date and applies whichever date is farther out \(later\).
</td></tr><tr><td id="d372431e257">
**Recalculate from risk change date and set to earliest target date only when risk rating increases**
</td><td>
If the risk increases: Compares the existing RT date and the recalculated RT date and applies the earliest date. If the risk decreases: Compares the existing RT date and the recalculated RT date and applies whichever date is farther out \(later\).
</td></tr></tbody>
</table>5. Select **Save**.
## What to do next
For more information on remediation target rules, see:
- [Vulnerability Response remediation target rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/time-to-remediate-rules.md)
- [Create or edit a Vulnerability Response remediation target rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/create-time-to-remediate-rule.md)
- [Examples of recalculating a remediation target date](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/sem-recalculate-rt-date-examples.md)
| title | Recalculate a remediation target date |
| description | The remediation target \(RT\) date defines when a finding must be remediated. Recalculation verifies that RT dates stay accurate and reflect the latest risk rating updates. When a finding’s risk rating changes, the system can recalculate RT dates using the most recent update date, helping maintain accurate SLAs and avoid outdated or overdue target dates. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/security-management/vulnerability-response/sem-recalculate-rt-date.html |
| release | brazil |
| product | Vulnerability Response |
| classification | vulnerability-response |
| topic_type | task |
| last_updated | 2026-09-10 |
| reading_time_minutes | 3 |
| keywords | Remediation targetRecalculate remediation target date |
| breadcrumb | Create or edit a Vulnerability Response remediation target ruleConfiguring Vulnerability Response using the Setup AssistantVulnerability Response implementationVulnerability ResponseUnified Security Exposure ManagementSecurity Operations |