National rollouts / multi-site delivery

One playbook. Every site visible.

Pilot through steady state with repeatable delivery standards, comparable controls and a portfolio view that finds the exception before it slows the wave.

PILOT & PROVESTANDARD PLAYBOOKSITE READINESSWAVE PLANNINGQUALITY ASSURANCESTEADY STATEPILOT & PROVESTANDARD PLAYBOOKSITE READINESSWAVE PLANNINGQUALITY ASSURANCESTEADY STATE
01 / Rollout architecture

Repeat the standard. Manage the exception.

Scale depends on a hard distinction between what must be common and what may flex. That protects pace without concealing local risk.

01 / PROVE

Pilot the model

Validate scope, design, cost, sequence, acceptance criteria and operating assumptions.

02 / STANDARDISE

Build the playbook

Standard designs, packages, controls, evidence, roles, gates and lessons learned.

03 / RELEASE

Mobilise the pipeline

Surveys, permissions, procurement, logistics, resource and site-release criteria.

04 / DEPLOY

Control the waves

Comparable milestones, portfolio RAID, dependencies and intervention triggers.

05 / ACCEPT

Assure quality

Inspection, test evidence, defects, commissioning and controlled acceptance.

06 / OPERATE

Reach steady state

Operational transition, support model, supplier performance and improvement.

Large infrastructure portfolio viewed across multiple sites
Portfolio visibility. Site-level accountability.MULTI-SITE DELIVERY
ONE CONTROL MODEL
02 / Scale without blur

Comparable does not mean identical.

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.

  • Programme, tranche and site governance
  • Site pipeline and readiness gates
  • Standard design and scope control
  • Supplier and contractor coordination
  • Commissioning and operations transition
03 / Portfolio view

See the wave. Find the outlier.

Comparable site metrics reveal whether the problem is local, systemic or travelling through the programme.

PORTFOLIO / WAVE READINESS● DEPLOYMENT ACTIVE

Sites released by wave

Portfolio exceptions

Readiness varianceSITE 07 / CONSENT EVIDENCE / HOLD RELEASE
Supplier capacityWAVE 03 / RESOURCE COLLISION / REBALANCE
Acceptance trendREPEAT DEFECT / ROOT CAUSE / UPDATE PLAYBOOK
PIPELINESITES QUALIFIED
READYGATES PASSED
WAVESCAPACITY ALIGNED
HANDOVEREVIDENCE CLOSED
04 / Deployment lifecycle

Pilot to operation. No dropped handover.

Each wave improves the next. Controls capture lessons while there is still a pipeline capable of benefiting from them.

STEP 01

Pilot

Prove technical, commercial and operating assumptions.

STEP 02

Mobilise

Build playbook, suppliers, site pipeline and capacity.

STEP 03

Deploy

Release waves, assure sites and control exceptions.

STEP 04

Operate

Complete handover, support assets and improve the model.

“The playbook controls repeatable work. Governance controls the moment it stops being repeatable.”
FOREST GROVE / ROLLOUT PRINCIPLE 04

Make the next site more predictable.

Tell us the asset type, number of sites, deployment stage and constraint. We will map the rollout structure.