Smart meter rollout Gantt chart with pilot gate and regional waves
An editable smart meter rollout Gantt chart: a pilot area, back-office data integration, customer notices, installer onboarding and three staggered regional waves, with gates before mass roll-out and exception visits.
What the smart meter rollout gantt chart with pilot gate and regional waves process is
A metering roll-out looks like a big installation job, but the installation is the easy part to schedule. The date is decided earlier, by two gates and a wait: what the pilot area teaches you, whether meter reads actually reach the billing and data systems, and how long customers must be told before an installer knocks. Install too soon and you create a backlog of meters that send reads nobody can use, or visits to people who were never told.
This template has four groups: Planning and pilot, Customer and installers, Systems and data, and Regional waves. It has 22 tasks and four milestones. "Define rollout scope and meter types" (3 working days) is the only starting task. The pilot runs "Select and brief the pilot area" (4), "Install pilot meters" (8) and "Review pilot reads and fault rates" (6), which starts 3 days into the installation so the first reads are examined while the last meters go in. "Pilot learning gate" is a milestone that closes the group.
The back-office work starts while the pilot is still in the field. "Specify meter data feeds to billing" (4) and "Build meter data integration" (12) run beside the pilot, but "Test meter reads end to end" (5) waits for "Install pilot meters" because it needs real reads, not sample files. "Back-office ready" also waits for "Train contact centre on meter queries" (4), so the people who answer customers know what a meter question looks like before the first notice goes out. "Mass roll-out go decision" waits for both "Pilot learning gate" and "Back-office ready".
Customer and installer work is where the overlap is safe. "Draft customer notice and appointment script" (3) and "Recruit and vet installers" (8) start as soon as scope is set, and "Onboard and train installers" (5) follows. "Send notices to wave one customers" (10) waits for the pilot gate, because the pilot is where you learn what the notice should say, and "Install wave one meters" (15) waits for the go decision, the notices and the trained installers. With these illustrative durations the notices finish two working days after the go decision, so they, not the gate, set the start of wave one. "Install wave two meters" and "Install wave three meters" each start 5 days after the wave before, but wave two also waits for "Send notices to wave two and three customers" (10), so that wait, not the stagger, sets it.
The plan ends with the work that always runs late. "Visit no-access and exception installs" (18) starts after wave one finishes and ends 3 days after wave three, so no-access, faulty-meter and awkward-site visits are worked while the waves run instead of being left for the last week. "Reconcile installed meters with billing records" (5) leads to the "Rollout closed" milestone. All durations are illustrative: replace them with what your teams and the utility's own pilot results tell you. A timeline schedules the work; it does not make a meter accurate, certified or compliant, and it does not decide who is allowed to install. For a similar staggered pattern see /templates/multi-store-opening-gantt-chart and /templates/ev-charging-network-gantt-chart, and for the method see /guides/gantt-chart-staggered-site-rollout.
What this flowchart covers
In this template
- Four groups, Planning and pilot, Customer and installers, Systems and data and Regional waves, with 22 tasks and four milestones: "Pilot learning gate", "Back-office ready", "Mass roll-out go decision" and "Rollout closed".
- A pilot that overlaps its own review: "Review pilot reads and fault rates" starts 3 days after "Install pilot meters" starts, and "Test meter reads end to end" waits for the pilot installation.
- A go decision with two inputs: "Mass roll-out go decision" waits for both "Pilot learning gate" and "Back-office ready", and the latter waits for "Train contact centre on meter queries".
- Three staggered waves: "Install wave two meters" and "Install wave three meters" each start 5 days after the previous wave starts, with a 10-day notice task ahead of waves two and three.
- "Visit no-access and exception installs", an 18-day task that starts after "Install wave one meters" and finishes 3 days after "Install wave three meters", before "Reconcile installed meters with billing records".
When to use this template
- You are planning a utility metering roll-out and need to agree dates between the field team, the data and billing team, customer communications and the installer contractor.
- You want to see whether the pilot, the back-office integration or the customer notice period is what holds up mass installation.
- A programme owner has a date for the roll-out to be finished and you want to compare the finish date with the date you need.
- You want a reusable skeleton for regional waves where each wave overlaps the last but waits for its own notices.
The plan, task by task
Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.
| # | Task | Group | Working days | Depends on |
|---|---|---|---|---|
| 1 | Define rollout scope and meter types | Planning and pilot | 3 | |
| 2 | Select and brief the pilot area | Planning and pilot | 4 | 1 |
| 3 | Install pilot meters | Planning and pilot | 8 | 2 |
| 4 | Review pilot reads and fault rates | Planning and pilot | 6 | 3SS+3 |
| 5 | Pilot learning gate | Planning and pilot | Milestone | 4 |
| 6 | Draft customer notice and appointment script | Customer and installers | 3 | 1 |
| 7 | Send notices to wave one customers | Customer and installers | 10 | 5, 6 |
| 8 | Send notices to wave two and three customers | Customer and installers | 10 | 7 |
| 9 | Recruit and vet installers | Customer and installers | 8 | 1 |
| 10 | Onboard and train installers | Customer and installers | 5 | 9 |
| 11 | Train contact centre on meter queries | Customer and installers | 4 | 6 |
| 12 | Specify meter data feeds to billing | Systems and data | 4 | 1 |
| 13 | Build meter data integration | Systems and data | 12 | 12 |
| 14 | Test meter reads end to end | Systems and data | 5 | 3, 13 |
| 15 | Back-office ready | Systems and data | Milestone | 11, 14 |
| 16 | Mass roll-out go decision | Regional waves | Milestone | 5, 15 |
| 17 | Install wave one meters | Regional waves | 15 | 7, 10, 16 |
| 18 | Install wave two meters | Regional waves | 15 | 8, 17SS+5 |
| 19 | Install wave three meters | Regional waves | 15 | 8, 18SS+5 |
| 20 | Visit no-access and exception installs | Regional waves | 18 | 17, 19FF+3 |
| 21 | Reconcile installed meters with billing records | Regional waves | 5 | 20 |
| 22 | Rollout closed | Regional waves | Milestone | 21 |
How it works
Size the pilot for learning, not volume
Set "Select and brief the pilot area" and "Install pilot meters" to what gives you a meaningful sample of your housing and signal conditions. The pilot only helps if "Review pilot reads and fault rates" has time to change something.
Start the data work with the pilot
Keep "Specify meter data feeds to billing" and "Build meter data integration" beside the pilot. If a vendor or another team needs longer, change the duration and read the effect on "Back-office ready".
Treat the contact centre as part of readiness
"Train contact centre on meter queries" feeds "Back-office ready". If your support team learns from the pilot, link it to "Review pilot reads and fault rates" instead.
Replace the notice period with your own
"Send notices to wave one customers" is a wait of 10 working days here. Use the lead time you have committed to your customers, and fix it in the notes of the task.
Adjust the stagger
The start-to-start lag of 5 days between waves says how far apart the crews and regions are. Increase it if one installer team serves all three waves, or link a wave to the one before it differently if the regions are independent.
Add owners, share and export
Put the responsible person in People, share the chart with field, data and customer teams, and export a PDF or CSV for the programme board when you need a copy.
Frequently asked questions
What decides when mass roll-out can start?
In this plan, the pilot learning gate and back-office readiness, and then the customer notices. Installers being ready is not enough. Replace the durations with your own and use View, Critical path to see which chain sets the finish date.
Does the chart check meter accuracy, data protection or regulatory requirements?
No. It schedules the work. Certification, privacy, consent and installation rules follow your own procedures and whatever your regulator and utility require. The chart shows when each task is meant to happen.
Why is the exception visit a task that overlaps the waves?
Because no-access, faulty-meter and difficult-site visits begin as soon as wave one produces them. A single task from the end of wave one to 3 days after wave three keeps them in the plan instead of in a final scramble.
How do I model a different number of waves?
Copy an install wave task, link it start-to-start to the previous one, and add a notice task if it needs its own lead time. For the pattern, see /guides/gantt-chart-staggered-site-rollout and /guides/gantt-chart-overlapping-tasks.
Can I use it for water or gas meters?
Yes, with changes to the task names and durations. For installation work with commissioning steps, see /templates/equipment-installation-gantt, and for a rollout with a people-side change, see /templates/change-management-gantt.