Pilot the model
Validate scope, design, cost, sequence, acceptance criteria and operating assumptions.
Pilot through steady state with repeatable delivery standards, comparable controls and a portfolio view that finds the exception before it slows the wave.
Scale depends on a hard distinction between what must be common and what may flex. That protects pace without concealing local risk.
Validate scope, design, cost, sequence, acceptance criteria and operating assumptions.
Standard designs, packages, controls, evidence, roles, gates and lessons learned.
Surveys, permissions, procurement, logistics, resource and site-release criteria.
Comparable milestones, portfolio RAID, dependencies and intervention triggers.
Inspection, test evidence, defects, commissioning and controlled acceptance.
Operational transition, support model, supplier performance and improvement.

Every site reports against common definitions and dates. Local conditions remain explicit deviations with owners, evidence and resolution routes—not footnotes lost inside a portfolio average.
Comparable site metrics reveal whether the problem is local, systemic or travelling through the programme.
Each wave improves the next. Controls capture lessons while there is still a pipeline capable of benefiting from them.
Prove technical, commercial and operating assumptions.
Build playbook, suppliers, site pipeline and capacity.
Release waves, assure sites and control exceptions.
Complete handover, support assets and improve the model.
“The playbook controls repeatable work. Governance controls the moment it stops being repeatable.”
Tell us the asset type, number of sites, deployment stage and constraint. We will map the rollout structure.