---
sourceDocument: Zurich IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-service-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Retarget a release

# Retarget a release {#ariaid-title1}

Release version: Zurich  
Updated July 31, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Change the release readiness target to reschedule the release period.

## Before you begin

Role required: sn_dpr_model.product_manager or sn_dpr_model.release_admin

## Procedure

1. Navigate to WorkspacesDigital Product Release Workspace.
2. Select the releases icon (![Releases icon.]()).
3. Select a release from the list to open.
4. On the Release form, select Overview.
5. Select the release action icon (![Release action icon.]()) and then select Retarget release.  
   Note:  
   Release readiness target and Release target are used interchangeably. Both terms refer to the same concept - release readiness target date.
6. On the Retarget release dialog box, select a different release readiness target from Release readiness target.  
   Note:  
   The new release readiness target date must be within the defined schedule of the release.
7. You can also make the release as an out-of-band release by selecting Out of band.  
   This option depends on the system properties---out_of_band_release_allowed and out_of_band_release_roles. For more information, see [Digital Product Release properties](https://www.servicenow.com/docs/3mKHi5y3tjshh~4cD79rJQ "Configure the system properties to customize various features of Digital Product Release according to your organization's needs.").
8. If you selected the out-of-band option, then select a release calendar from the Release calendar to tag the release and use its release target.
9. Select Confirm.

## Result

* The readiness target date of the release is updated to the new date.
* For timeline-oriented releases, the key dates impacted are adjusted based on the retargeted date. This adjustment is made after recalculating the number of days that have changed from the original schedule.  
  Note:  
  If a holiday schedule is attached to the release and the revised key dates fall on a holiday, the last workday before the holiday is considered as the revised key date.
{#dpr-work-release-readiness-target__ul_wfr_mnf_zfc}

## What to do next

Update the planned dates on the associated change requests manually because they are not automatically updated when you retarget the release.

*[\>]: and then