What to change
Ask for a demonstrated recovery path, not just possession of an archive. The handover should explain the backup's scope, required software, dependencies and any missing configuration without exposing secrets unnecessarily. Have an authorised maintainer who did not create the backup restore it in an isolated environment. Their questions reveal undocumented assumptions. Acceptance should include a usable sample of public routes and assets, showing that the file is operationally meaningful.
A worked example
Illustrative example
Illustrative test: The replacement maintainer restores a sample without borrowing the creator's personal machine.
How to check the result
The backup has a reproducible restoration route and known limitations.
A mistake to avoid
A successfully downloaded archive is not proof of recoverability.
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.