Confirm the dependency and scope
Identify exactly what has stopped: stock, transport, cloud/SaaS, contractor, telecoms, payment provider or another service. Record the provider status and expected duration if known.
Know which external dependency can stop the critical service first, the point at which you switch, and whether the alternative is actually usable before the incident.
Use the documented minimum operation rather than improvising under pressure. Record decisions, ownership and the next review point as the incident develops.
Identify exactly what has stopped: stock, transport, cloud/SaaS, contractor, telecoms, payment provider or another service. Record the provider status and expected duration if known.
Apply the pre-defined switch point. Contact the alternate supplier or workaround and protect scarce stock, capacity or licences for the minimum operation.
Update customers, reschedule work and monitor secondary dependencies. Record costs, delays and contractual issues for later recovery and review.
Pre-agreed thresholds reduce hesitation and stop a degraded situation from drifting without ownership.
Map suppliers to the specific critical service they support rather than treating every vendor equally.
Set a time, stock level or service threshold that triggers the alternative.
Check account approval, pricing, capacity, compatibility, delivery area and lead time in advance.
Keep appropriate exports, records and exit information outside a single provider where feasible.
Reconcile orders, duplicate requests, data changes and temporary contracts before switching back.
Use current provider, regulator and official guidance during a real incident. GPN is the planning layer, not the authority controlling the incident.