> 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/create-a-new-batch-for-rollout.md).
# Create a new batch for rollout
Add another batch to an existing rollout.
Add another batch to an existing rollout.
### Before you start
Confirm that:
* the parent rollout already exists
* you selected the correct rollout
* the new batch needs its own target devices, payload, or schedule
Compare the existing batches before creating another one. Use a new batch only when its target, payload, or schedule differs from the existing work.
### Create the batch
1. Go to **Verifone Central** → **Device Management** → **Rollouts**.
2. Select the rollout where you want to add the batch.
3. Select **Actions** → **Start New Batch**.
The remaining flow matches the standard rollout creation flow.
Use the same selection, payload, and schedule steps that you use when you [create a batch rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-batch-rollout).
Before you start the batch, compare its target count, payload, and schedule with every existing batch. Stop if it duplicates existing work.
### Verify the result
After you save the batch, confirm that:
* the new batch appears under the correct rollout
* the batch uses the intended devices and schedule
* the rollout list reflects the new batch in the estate-wide view
* the new batch does not duplicate an existing target and schedule
* the parent rollout name and new batch name match the deployment plan
### Result
The new batch appears under the existing rollout.
---
# 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/create-a-new-batch-for-rollout.md?ask=&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.
