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

# Prerequisites

Confirm access, device, payload, and schedule readiness before starting a rollout.

Complete these checks before you schedule a rollout.

### Access and permissions

Confirm that you can create or manage rollouts for the target estate.

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

### Device readiness

Before you continue, confirm that:

* the target device is already boarded in **Device Management**
* the device status is **Pending Hierarchy** or **Active**
* the device is visible in the customer, estate, or hierarchy you manage

### Rollout payload readiness

Confirm that the item you want to deploy is ready:

* software packages are already uploaded before software rollouts
* content packages are already uploaded before content rollouts
* parameter changes are already defined before parameter rollouts

See:

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

### Scheduling checks

Before you start the rollout, confirm that:

* the selected device does not already have a conflicting rollout
* you know whether the rollout targets one device or a batch
* you are ready to choose the download and install schedule

Record the rollout name, payload version, target count, and schedule window. Use this baseline to verify the rollout summary before launch.

### Final go or no-go check

Before submission, record the payload version, target count, and schedule. Stop if the payload, device scope, or schedule differs from the deployment plan.

### Next step

When these checks are complete, continue to [Schedule rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-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/manage-rollouts/prerequisites.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.