> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/rollouts/manage-rollouts.md).

# Manage rollouts

Move from rollout readiness to scheduling and monitoring without missing key checks.

Prepare, schedule, and monitor rollouts from one workflow.

### Before you start

Confirm that:

* you know what type of rollout you need to run
* the target devices are already available in Device Management
* the software, parameters, or content are ready for deployment

Review these pages first:

* [Prerequisites](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/manage-rollouts/prerequisites)
* [User privileges](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/manage-rollouts/user-privileges)

{% stepper %}
{% step %}

### 1. Prepare rollout content

Add the files and configuration needed for the rollout.

Use one of these pages based on what you want to deploy:

* [Software management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/software-management)
* [Parameter management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/parameter-management)
* [Content management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/content-management)
  {% endstep %}

{% step %}

### 2. Schedule the rollout

Create the rollout for a single device or for a batch of devices.

Start here:

* [Schedule rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts)

Then use the task that matches your rollout type:

* [Create a batch rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-batch-rollout)
* [Create rollout for a single device](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-rollout-for-a-single-device)
* [Modify existing rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout)
  {% endstep %}

{% step %}

### 3. Monitor rollout progress

Track rollout status after submission.

Use these pages to review current rollout progress and results:

* [Managing rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/managing-rollouts)
* [Monitor estate-wide rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/monitor-estate-wide-rollouts)
  {% endstep %}
  {% endstepper %}

### Choose the right rollout path

Use these quick rules:

* use [Software management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/software-management) when the rollout installs or updates application packages
* use [Parameter management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/parameter-management) when the rollout changes configuration values
* use [Content management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/content-management) when the rollout distributes files or media
* use [Create rollout for a single device](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-rollout-for-a-single-device) when one device needs a targeted rollout
* use [Create a batch rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-batch-rollout) when many devices need the same rollout

### What to verify before submission

Check these points before you create or schedule a rollout:

* the package, parameter set, or content is the correct one
* the target device or batch is correct
* the schedule matches the intended install window
* the rollout type matches the operational goal

Record the rollout name, payload version, target count, and schedule window before submission. Stop and correct the rollout if its summary differs from this baseline.

Record the rollout name, payload version, target scope, and schedule window. Use this record to verify the submitted rollout and investigate failures.

### Verify the result

After you submit and monitor the rollout, confirm that:

* the rollout was created with the expected scope
* the rollout reaches the expected status after submission
* any failures or delays are visible in the monitoring pages
* the next action is clear: monitor, modify, or create another rollout
* the rollout record shows the intended name, scope, and schedule
* the rollout scope and timing match the recorded deployment plan

### Result

You can move from rollout readiness to rollout scheduling and monitoring with the right checks in the right order.

### Next steps

* [Schedule rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts) — choose the exact rollout task
* [Managing rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/managing-rollouts) — inspect rollout status and details
* [Monitor estate-wide rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/monitor-estate-wide-rollouts) — review broader rollout progress
* [Rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts) — return to the rollout hub


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/rollouts/manage-rollouts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.