What to change
Ask the supplier to identify whether code and content must be restored as a compatible pair. Review the change that altered the structure and test the proposed rollback target against the intended content snapshot. If there is no safe direct reversal, record the alternative repair route before the next risky release. The practice should understand which versions can work together without needing to infer compatibility from similar filenames or reassuring deployment labels.
A worked example
Illustrative example
Illustrative test: A sample guide using the changed field renders correctly in the proposed restored pair. A newer content export may use a field structure that an older website version cannot read. The supplier pairs the proposed rollback with a compatible content snapshot and tests a guide using the changed field. Your team checks its complete expected information. If no suitable pair exists, the documented repair alternative remains explicit, preventing a successful code deployment from being mistaken for a safe recovery of the content itself.


What this means for your practice
An older website may expect content organised differently from today's editing system. Restoring only the code can leave headings, fields or whole sections missing. Ask your supplier whether the proposed recovery version needs a matching content snapshot. Identify the structural change and test representative pages using the intended pair before relying on it. If there is no safe direct reversal, record the alternative repair route ahead of the next risky release. Your team should understand which combinations work without comparing technical filenames or assuming that two recent backups are compatible. The acceptance result is complete expected content in the restored page, not simply a successful deployment message.
How to check the result
The chosen recovery combination produces complete expected content.
A mistake to avoid
Restoring code alone can expose incompatibility with newer content structures.
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.
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.
