Examples of recalculating a remediation target date
reference australia Updated Sep 10, 2026 1 min read sem-recalculate-rt-date-examples.md
The following examples show how the system recalculates the remediation target date based on different rule selections and risk rating changes.
Note: By default, SLAs define the remediation window for each risk level:
- Low risk: 30 days
- Medium risk: 15 days
- High risk: 10 days
| Target from (date) | Field change time | Initial risk (Target (days)) → New risk (Target (days)) | Existing RT date | Recalculated RT date | What happens |
|---|---|---|---|---|---|
| Default calculation | |||||
| Feb 1 | Feb 10 | Medium (15 days) → High (10 days) | Feb 16 | Feb 11 (applied) | Uses the standard formula with the new risk ratings target days, not the Field change time-based formula: Target from (date) + New risk Target (days) → Feb 1 + 10 = Feb 11. |
| Recalculate from trigger field change date | |||||
| Recalculate from risk change date | |||||
| Feb 1 | Feb 10 | Medium (15 days) → High (10 days) | Feb 16 | Feb 20 (applied) | Uses the recalculation formula: Field change time + Target (days) → Feb 10 + 10 = Feb 20. |
| Recalculate from trigger field change date and always set to the earliest target date | |||||
| Recalculate from risk change date and always set to earliest target date | |||||
| Feb 1 | Feb 10 | Medium (15 days) → Low (30 days) | Feb 16 (applied) | Mar 12 | Compares the existing RT date (Feb 16) with the recalculated date (Feb 10 + 30 = Mar 12) and selects the earliest date → Feb 16. |
| 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) | |||||
| Recalculate from risk change date and set to earliest target date only when risk rating increases | |||||
| Feb 1 | Feb 10 | Low (30 days) → High (10 days) | Mar 3 | Feb 20 (applied) | Because the risk increased, the system compares the existing RT date (Mar 3) with the recalculated date (Feb 20) and applies the earlier date → Feb 20. |
| Feb 1 | Feb 10 | High (10 days) → Low (30 days) | Feb 11 | Mar 12 (applied) | Because the risk decreased, the system compares the existing RT date (Feb 11) with the recalculated date (Feb 10 + 30 = Mar 12) and applies the later date → Mar 12. |
40 lines · 3.1 KB
--- title: Examples of recalculating a remediation target date description: The following examples show how the system recalculates the remediation target date based on different rule selections and risk rating changes. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/sem-recalculate-rt-date-examples.html release: australia product: Vulnerability Response classification: vulnerability-response topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 1 breadcrumb: [Recalculate RT date, 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] --- # Examples of recalculating a remediation target date The following examples show how the system recalculates the remediation target date based on different rule selections and risk rating changes. **Note:** By default, SLAs define the remediation window for each risk level: - Low risk: 30 days - Medium risk: 15 days - High risk: 10 days |Target from \(date\)|Field change time|Initial risk \(Target \(days\)\) → New risk \(Target \(days\)\)|Existing RT date|Recalculated RT date|What happens| |--------------------|-----------------|---------------------------------------------------------------|----------------|--------------------|------------| |Default calculation| |Feb 1|Feb 10|Medium \(15 days\) → High \(10 days\)|Feb 16|Feb 11 \(applied\)|Uses the standard formula with the new risk ratings target days, not the Field change time-based formula: Target from \(date\) + New risk Target \(days\) → Feb 1 + 10 = Feb 11.| |Recalculate from trigger field change date| |Recalculate from risk change date| |Feb 1|Feb 10|Medium \(15 days\) → High \(10 days\)|Feb 16|Feb 20 \(applied\)|Uses the recalculation formula: Field change time + Target \(days\) → Feb 10 + 10 = Feb 20.| |Recalculate from trigger field change date and always set to the earliest target date| |Recalculate from risk change date and always set to earliest target date| |Feb 1|Feb 10|Medium \(15 days\) → Low \(30 days\)|Feb 16 \(applied\)|Mar 12|Compares the existing RT date \(Feb 16\) with the recalculated date \(Feb 10 + 30 = Mar 12\) and selects the earliest date → Feb 16.| |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\)| |Recalculate from risk change date and set to earliest target date only when risk rating increases| |Feb 1|Feb 10|Low \(30 days\) → High \(10 days\)|Mar 3|Feb 20 \(applied\)|Because the risk increased, the system compares the existing RT date \(Mar 3\) with the recalculated date \(Feb 20\) and applies the earlier date → Feb 20.| |Feb 1|Feb 10|High \(10 days\) → Low \(30 days\)|Feb 11|Mar 12 \(applied\)|Because the risk decreased, the system compares the existing RT date \(Feb 11\) with the recalculated date \(Feb 10 + 30 = Mar 12\) and applies the later date → Mar 12.|
| title | Examples of recalculating a remediation target date |
| description | The following examples show how the system recalculates the remediation target date based on different rule selections and risk rating changes. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/sem-recalculate-rt-date-examples.html |
| release | australia |
| product | Vulnerability Response |
| classification | vulnerability-response |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | Recalculate RT dateCreate or edit a Vulnerability Response remediation target ruleConfiguring Vulnerability Response using the Setup AssistantVulnerability Response implementationVulnerability ResponseUnified Security Exposure ManagementSecurity Operations |