Control essential accounts
Identify administrators for the domain, hosting, repository, forms and connected services. Maintain an access inventory without placing passwords in public documents. Define authorised people and a recovery procedure. A supplier’s personal account should not be an unknown dependency of business operations.
Check what a backup covers
Code, content, files and configuration may live in different places. Document what is backed up, when and for how long. Test restoration in a suitable environment. A backup that has never been restored does not demonstrate recovery of the complete site or its most recent information.
Separate support and development
Clarify whether maintenance includes updates, small changes, monitoring or incident response. Define agreed hours and channels. A monthly fee does not imply permanent availability or unlimited development. Keep functional improvements in an estimable list and avoid counting the same work in another contracted service.
Schedule a business review
Periodically review services, prices, contacts and forms alongside technical health. Check that the site still describes what the business can actually deliver. Link updates to language versions and the assistant’s knowledge. Useful maintenance preserves both technical continuity and the accuracy of the offer.
Key takeaways
- Handover should support continuity even when the team changes.