> 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/schedule-rollouts.md).

# Schedule rollouts

Choose the right rollout task and schedule downloads and installs.

Schedule downloads and installs for one device or many devices.

### Before you schedule a rollout

Confirm these requirements 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)

### Choose the rollout type

Use the task that matches your goal:

* [Create a batch rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-batch-rollout) — schedule a rollout for multiple devices
* [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) — schedule a rollout for one device
* [Create a new batch for rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-new-batch-for-rollout) — add another batch to an existing rollout
* [Modify existing rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout) — edit a saved rollout or cancel a job in progress

### Scheduling flow

Most rollout schedules follow this order:

1. Create or open a rollout.
2. Select the rollout type.
3. Select the target device or devices.
4. Set the download schedule.
5. Set the install schedule.
6. Review the rollout summary.
7. Start the rollout.

### Scheduling options

When you schedule a rollout, you can choose one of these download options:

* **Download during device maintenance hours**
* **Download immediately on the next contact**
* **Start download on** a specific date and time

You can then choose one of these install options:

* **Force installation**
* **Install immediately after download**
* **Start install on** a specific date and time

{% hint style="info" %}
If a selected device already has a conflicting rollout, remove the conflict before continuing.
{% endhint %}

### Choose the schedule

Use maintenance hours when normal device activity must take priority. Use the next contact option when timing depends on device connectivity. Use a specific date and time when the deployment has a defined window.

Set download and install windows that match the same deployment plan. Review both windows together before starting the rollout.

### Verify the schedule

Before you start the rollout, confirm that:

* the target device or batch is correct
* the selected rollout type matches the payload you want to deliver
* the download and install windows match the intended deployment plan
* the target count matches the expected device or batch scope

Record the rollout name, payload, target count, and schedule before starting. If the summary differs from the plan, return to the relevant step and correct it.

### After you schedule the rollout

Track rollout progress here:

* [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)


---

# 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/schedule-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.