
Update sequence
Record software versions and dependencies, prepare a backup, and test changes before release where practical. Retest forms and bookings afterward. Keep enough history to separate a planned test from an unrelated change.
Confirm where backups are stored and how recovery works. Include databases and uploaded assets as well as application files. Test the important customer action before publishing a change.
- A written brief
- Named responsibilities
- Agreed review points




