Deployment requests in ReleaseOps

---
title: Deployment requests in ReleaseOps
description: Deployment requests contain one or more update sets. They are attached to a release, which runs through a pipeline to a destination environment.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/application-development/releaseops/deployment-requests.html
release: australia
product: ReleaseOps
classification: releaseops
topic_type: concept
last_updated: "2026-09-17"
reading_time_minutes: 1
keywords: [ReleaseOps, deploy changes, update sets, pipeline, ATF, schedule a release, deployment request, deployment analyzer, large scale deployment ServiceNow]
breadcrumb: [Explore, ReleaseOps, Run, AI Workflow Factory Prime, Agentic app development, Building applications]
---

# Deployment requests in ReleaseOps

Deployment requests contain one or more update sets. They are attached to a release, which runs through a pipeline to a destination environment.

Deployment requests are the building blocks of moving code into production. They capture the content that a developer intends to move, including update sets. Deployment requests also describe how and when that code should go into production.

When creating a deployment request, you can attach it to either a release or a pipeline, if the release hasn't been created yet, which enables the request to move to the assessment stage. However, for the deployment request to move to production, a release must be defined.

**Parent Topic:**[Exploring ReleaseOps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/releaseops/exploring-release-ops.md)