What to change
Ask the supplier to explain how a page chooses between a global default and a branch-specific value. The important evidence is the order in which those settings take effect, including what a blank local value means. Have the branch owner confirm the intended exception before changing that order. The repair should preserve legitimate local choices while allowing branches without an exception to continue using the approved default.
A worked example
Illustrative example
Illustrative test: Riverside retains its approved provider booking link, while Harbour inherits the central booking destination. Clearing a local option in preview produces the documented fallback rather than an unexplained empty link. Riverside may use a branch-specific booking provider while Harbour should inherit the central destination. The supplier demonstrates both settings after a rebuild, then shows the documented result when a local value is cleared in preview. Your branch owners verify the destinations rather than inspect configuration order. The test protects genuine exceptions while keeping central updates maintainable, instead of hiding the problem by copying the same default into every branch record.
What this means for your practice
A shared website setting can provide a useful default while individual branches need their own destinations. Ask your supplier to explain which value wins when both exist and what an empty local setting means. Have each affected branch owner confirm the intended exception before changing that order. Review a branch with its own booking provider alongside one using the central destination. The public pages should demonstrate both cases after a normal rebuild. Copying the default manually into every branch can conceal the underlying problem and make future central changes harder to manage. Your team needs a clear rule it can maintain, not a collection of unexplained fixes.
How to check the result
The supplier can explain the inheritance rule, and the public pages demonstrate both the intended branch override and the global default.
A mistake to avoid
Copying the default into every branch can hide the faulty inheritance rule and make later central updates unreliable.
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.