What to change
Establish the authoritative release sequence and make competing work visible before publication. Ask each supplier which revision they started from and what their deployment replaces. A shared release record or controlled merge process should preserve approved changes from both streams. Rehearse with two harmless independent edits to show how conflicts are detected. The owner should receive a clear combined preview instead of being asked to approve separate previews that cannot coexist publicly.
A worked example
Illustrative example
Illustrative test: Two independent sample edits remain present in the accepted combined deployment.
How to check the result
Publication preserves both approved changes or explicitly resolves their conflict.
A mistake to avoid
Separate successful previews do not prove that the updates can be deployed together.
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.