Release key date form

reference australia Updated Sep 10, 2026 1 min read release-key-date-form.md

Manage your release key dates for a timeline-oriented release.

Release key date

For more information about adding key dates to a release, see Add key dates to a timeline-oriented release.

For more information about viewing and managing key dates in a release, see Work on a timeline-oriented release for a single product or service.

Field	Description
Name	Unique name of the key date.
Type	Type of key date. Select one of the options:- Milestone: An event used to mark the progress toward the overall goal. For example, dev complete. Key event: Any release activity that holds strategic significance. Deadline: The latest date by which a task or activity must be completed. For example, code freeze date. Important date: Any date that holds significance in the release timeline.
Due date	Date and time of the release key date. This date must be between the release start date and end date. Note: You can only add a future dateand it must not be a holiday according to the selected holiday schedule in the release.
Assigned to	The person that is responsible for achieving the key date event.
Description	Short description of the key date.

**Parent Topic:**[Digital Product Release reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/digital-product-release/dpr-reference.md)

81 lines · 2.4 KB Wrap lines

---
title: Release key date form
description: Manage your release key dates for a timeline-oriented release.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/digital-product-release/release-key-date-form.html
release: australia
product: Digital Product Release
classification: digital-product-release
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Reference, Digital Product Release, IT Service Management]
---

# Release key date form

Manage your release key dates for a timeline-oriented release.

## Release key date

For more information about adding key dates to a release, see [Add key dates to a timeline-oriented release](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/digital-product-release/dpr-work-release.md).

For more information about viewing and managing key dates in a release, see [Work on a timeline-oriented release for a single product or service](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/digital-product-release/dpr-work-release.md).

<table id="table_ozl_shv_cdc"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Name

</td><td>

Unique name of the key date.

</td></tr><tr><td>

Type

</td><td>

Type of key date. Select one of the options:-   Milestone: An event used to mark the progress toward the overall goal. For example, dev complete.
-   Key event: Any release activity that holds strategic significance.
-   Deadline: The latest date by which a task or activity must be completed. For example, code freeze date.
-   Important date: Any date that holds significance in the release timeline.

</td></tr><tr><td>

Due date

</td><td>

Date and time of the release key date. This date must be between the release start date and end date.

**Note:** You can only add a future dateand it must not be a holiday according to the selected holiday schedule in the release.

</td></tr><tr><td>

Assigned to

</td><td>

The person that is responsible for achieving the key date event.

</td></tr><tr><td>

Description

</td><td>

Short description of the key date.

</td></tr></tbody>
</table>**Parent Topic:**[Digital Product Release reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/digital-product-release/dpr-reference.md)