A regional rollout needs local evidence

A library membership service works at the first regional launch. The programme reuses the same approval pack for the next region, where the support desk closes earlier and a local address format fails validation. The shared software has passed; the local service has not.

Regional rollout planning needs evidence tied to the place where people will use the service. A reusable platform can reduce repeated work, but it cannot establish that every region's operating arrangements are ready.

Reuse evidence only within its boundary

In this fictional rollout, both regions use the same membership application. Region A accepts applications at a staffed counter throughout its advertised hours. Region B offers an evening online service, but staff cannot resolve identity-document questions until the next working period.

Those are different customer journeys even if the form is identical. The second region needs an accurate pending state, an agreed handoff and customer wording that matches its actual service. Copying the first region's response promise would create an unsupported commitment.

The GOV.UK Service Standard asks UK public services to provide a joined-up experience across channels. It is a useful reference for examining the online-to-counter handoff here, not a legal requirement for every regional rollout.

Build a local evidence matrix

Keep common platform evidence once, with its version and scope. Add a regional record for the conditions that can differ.

The matrix is an author-proposed planning aid. It should expose missing evidence, not turn every empty cell into a ceremonial sign-off exercise. If a field does not vary, record why the shared evidence covers it.

Make the decision at the affected scope

Suppose Region B's address validation rejects a supported district format. The team must decide whether to correct the validation, provide an approved usable alternative or hold the affected launch. It cannot silently redefine eligibility to make the form pass.

A problem in one region need not block an independent region whose evidence is complete. Conversely, an overall programme status of green should not conceal a local unresolved condition. Record precisely which region, channel and feature the decision covers, along with any conditions that must remain true.

This is the readiness decision. The detailed sequence for switching systems or recovering a failed cutover belongs in separate operational plans.

Carry evidence into the live service

The GOV.UK live-phase guidance treats running and improving a service as continuing work. Applied to this example, the regional record should identify who owns the observed address failures, support queues and counter handoffs after launch.

Review evidence when a local policy, supplier or service window changes. Keep the former version so an incident can be understood against the conditions that existed at the time. Supplier handover and the distinction between launch claims and evidence support that continuing responsibility.

The next region's approval should say what was reused, what was checked locally and what remains conditional. That is more useful than a single launch date carried across the map.