What to change
Map the failing action to its immediate dependencies and collect evidence before assigning cause. Ask the supplier to compare the public symptom with the provider's actual response and any relevant official status information. A status notice is context, not proof that every observed fault has the same cause. Preserve a working control where possible, then decide whether the next action is a local fix, an agreed fallback or coordinated supplier escalation.
A worked example
Illustrative example
Illustrative test: A fictional dependency failure is traced without modifying unrelated page code. A public task may fail while its external provider reports an interruption. The supplier compares the actual provider response with local evidence and a working control before assigning cause. The coordinator chooses a justified escalation or agreed fallback, while retaining awareness of possible local defects. This prevents unnecessary changes to unrelated website code without treating a status-page notice as proof that every simultaneous symptom shares the same explanation.
What this means for your practice
A booking or other public function may depend on an external provider. When it fails, ask the supplier to map that immediate dependency and compare its response with the symptom on your site. The provider's official status page can offer context, but does not prove every local failure has the same cause. Keep independent local evidence and a working control where possible. Then decide whether the next action is a website repair, an agreed fallback or coordinated provider escalation. This avoids changing unrelated code in response to a provider interruption, while also avoiding the opposite mistake of blaming the provider too quickly and overlooking a simultaneous local defect.
How to check the result
The incident has an evidence-based next action and an accountable coordinator.
A mistake to avoid
Blaming a provider too quickly can conceal a simultaneous local defect.
Turn reading into a next step
Your action checklist
Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.
Record what you know, what is still missing and the answer you need from your team or supplier.
Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.
Further reading
These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.
Related guides
Need help with this?
Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.
Explore support & operations services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.