Support & operations · Practical guide

Combine suppliers' changes before either overwrites the website

Different suppliers publish independent updates, and the later deployment removes changes accepted in the earlier one.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

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. One supplier may update directions while another adjusts the enquiry form from an older copy of the project. Each preview looks correct in isolation. The combined review shows whether publishing the second would remove the first. The release process preserves both harmless sample changes or records an explicit conflict decision. Your practice then approves one coherent public result rather than two separate demonstrations that cannot actually coexist.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

What this means for your practice

Two suppliers can each show a successful preview while their releases replace the same underlying files. Publishing the second may remove work approved in the first. Ask each supplier which version they started from and what their deployment replaces. Establish one release sequence or controlled combination process, with a preview showing both sets of changes together. A harmless pair of independent edits can demonstrate that the process preserves them. Your practice should approve the combined result rather than assume separate previews can coexist. Keep the starting versions and any resolved conflict in the release record so future maintenance can follow the same reliable route.

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.

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.

Checks to discuss

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.