What to change
Choose coverage of possible unintended effects by dependency as well as by edited filename. Ask the supplier to identify which routes use the changed component and select representative important cases. Include a control path that should retain its behaviour. The owner need not inspect every implementation detail, but should see why the chosen sample is capable of detecting a shared failure. Preserve those examples with the component's change record for future releases.
A worked example
Illustrative example
Illustrative test: A shared navigation change is exercised from a guide, a service page and a directory. A shared navigation adjustment may be edited in one component but appear on service pages, directories and every guide. The supplier identifies those families and the practice reviews one meaningful action on each, plus a control route. A later change can reuse that sample. This catches shared effects that a checklist based only on directly edited filenames would miss, while keeping review focused on representative public behaviour.
What this means for your practice
A small edit to navigation or a common form component may affect many pages even when only one source file changes. Ask your supplier to identify the public page families that depend on it. Choose representative tasks from each and include a working control that should remain unchanged. The practice does not need to inspect every technical dependency, but it should understand why the sample can detect a shared problem. Keep those examples with the component's change record for future releases. Reviewing only pages that were directly edited can miss the wider effect of reusable parts that appear throughout the website.
How to check the result
The sample covers the dependency's real public reach.
A mistake to avoid
A file list can understate the impact of one reusable component.
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.