What to change
Separate deployment from cache behaviour. Ask the supplier to compare the public page's asset references with the content actually returned for those addresses. Test both a fresh visitor and a returning browser, because either can expose a different problem. The correction should use the site's deliberate asset-versioning and cache policy rather than asking every visitor to clear their browser. Preserve the exact mismatched references as useful evidence for the hosting owner.
A worked example
Illustrative example
Illustrative test: Both sessions perform the affected action using the compatible asset version.
How to check the result
Public markup and assets agree without requiring visitor troubleshooting.
A mistake to avoid
A hard refresh on the developer's machine is not a sitewide fix.
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.
Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.
Further reading
These primary sources provide additional context for the project decisions above.
Related decisions
Turn the brief into a working service
Kay & Co. can help you scope the work, design the experience and deliver the right solution for your organisation.
Explore support & operations services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.