What to change
Tie approval to an identifiable release, not merely to a preview address that can change. Ask the supplier to record the reviewed revision and demonstrate that the public deployment contains it. Any additional changes should be visible as a separate review decision. This makes acceptance specific enough to reproduce and gives the owner a meaningful reference if a fault later requires restoration of the last approved version.
A worked example
Illustrative example
Illustrative test: A harmless visible test change distinguishes the approved revision from a later draft.
How to check the result
The published release matches the approval evidence and any differences are explicitly accepted.
A mistake to avoid
A reusable preview URL alone does not identify what was approved.
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.