
Update sequence
Record software versions and dependencies, prepare a backup, and test changes before release where practical. Retest forms and bookings afterward. Explain why a change was made, not just when it happened.
Confirm where backups are stored and how recovery works. Include databases and uploaded assets as well as application files. Use a real test inquiry to check delivery and follow-up.
- A written brief
- Named responsibilities
- Agreed review points




