A shared setting overrides a branch-specific website option

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.

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.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordRecord the intended default and one verified branch exception, with the public destination each should produce.Ask the supplier to show which configuration layer supplies the final value and why the local option is being ignored.Verify a branch with an explicit override and another using the default separately after a normal rebuild.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.