Rollout & Migrations · Deliverable
Rollout Plan with Site-by-Site Schedule.
Detailed rollout plan with site-by-site schedule and resource allocation
Part of Rollout & Migrations. Last reviewed October 2026.
Quick answer
What is Rollout Plan with Site-by-Site Schedule?
A rollout plan is the written document that sets which sites, devices and users are deployed in what order, by which engineers, within which access windows. Deploris builds it from a site audit and delivers a site-by-site schedule, resource allocation, dependency list and rollback path for sign-off before any field work starts.
WHAT THE WORK COVERS
What Rollout Plan with Site-by-Site Schedule includes.
- 01Estate audit covering device counts, models, floors, VIP users and shared or kiosk endpoints per site
- 02Wave design that groups sites by risk, size, lease or freeze dates and business calendar blackouts
- 03Resource allocation showing engineers, squads, shifts and travel per site and per day
- 04Dependency register for network readiness, power, building access, change approvals and hardware delivery
- 05Pilot wave definition with entry and exit criteria before the main waves are released
- 06Rollback and escalation paths per wave, including who can stop a site and who approves a retry
- 07Communication calendar for site contacts, end users and your service desk
HOW WE DELIVER IT
How it is delivered.
- 1
Audit and scope the estate
We collect your device inventory, site list, access rules and success criteria, then reconcile them against what is physically on site so the plan rests on real counts.
- 2
Draft waves and the master schedule
We sequence a pilot and production waves by risk and calendar, assign engineer capacity per day, and mark every dependency that could move a date.
- 3
Review with stakeholders
Your project owner, service desk and site contacts review the draft. We resolve conflicts such as change freezes, stock arrival dates and building access limits.
- 4
Baseline and sign-off
The agreed schedule is frozen as the baseline in the written scope. Later changes go through a simple change log so everyone sees why a date moved.
INPUTS AND OUTPUTS
What you provide and what you receive.
You provide
- Current asset inventory export from your CMDB, Intune, SCCM or Jamf
- Site list with addresses, contacts, opening hours and building access rules
- Change freeze dates, business blackout periods and your approval process
- Target configuration, hardware delivery dates and any security or network pre-requisites
You receive
- Signed-off rollout plan with the baseline schedule by site and wave
- Resource allocation matrix showing engineers, shifts and travel per site
- Dependency and risk register with a named owner for each item
- Rollback and escalation procedure for each wave
WHEN IT FITS
When this is the right deliverable.
You are refreshing or migrating devices across many sites and need one schedule that your project office, service desk and site contacts all work from.
A previous rollout slipped because of building access, late hardware or change freezes, and you need dependencies tracked before dates are promised.
Leadership wants a fixed order of sites and a defensible capacity model before approving budget for the field work.
WHERE WE DELIVER
Delivered in 75+ metros across 11 countries.
Local, vetted engineers deliver this work on site across the United States and Western Europe, coordinated by one engagement manager.
QUESTIONS
Frequently asked questions.
What should a site-by-site rollout plan include?
How do you decide the order of sites in a rollout wave?
Can the rollout schedule change after it is signed off?
Who writes the rollout plan, Deploris or our project team?
MORE DELIVERABLES
More from Rollout & Migrations.
QUOTE
Request a quote.
Share a few details and we will come back with the next steps.
Get started
Need engineers on site? Tell us where.
Tell us the sites, the scope and the timeline. We reply with a written plan.