Start with a system and ownership inventory
List the domain registrar, DNS provider, hosting, repository, CMS, payment tools and email provider. Record the business owner and authorised users for each account without placing passwords in the document. Use individual access and multi-factor authentication where available. A maintenance plan cannot work reliably if no one knows who controls the domain.
Treat backup restoration as a task
Define which files and data are backed up, how long copies are retained and who can restore them. Test a restore in an appropriate isolated environment and record the result. A successful backup notification does not prove recovery will work. Stores and applications may need more frequent data protection than a mostly static marketing site.
Update with a way to recover
Review dependency and platform updates, test important journeys and keep a rollback option. For a store, include product, cart, payment and order flows. For an agency site, check navigation, contact methods and forms. The cadence should reflect the software and risk; blindly updating everything or never updating anything can both create problems.
Make monitoring actionable
Agree which outages or errors produce alerts, who receives them and when they are reviewed. Test the alert route. Monitoring does not create an around-the-clock support commitment by itself. Response targets, support hours and emergency work need to be stated in the agreement.
Separate care from new development
A care plan may include routine updates and a defined amount of small content work. New features, platform migrations, incident investigation and major redesigns should have a clear quoting process. Review monthly what changed, what failed and what needs a separate decision so maintenance remains understandable to the business.
Your practical checklist
- Accounts and responsibilities documented
- Backups and a restore check agreed
- Update and rollback process defined
- Important customer journeys tested
- Alerts reach an agreed contact
- Support coverage and exclusions written down
Working through a similar question?
We’re happy to help you find a practical starting point.
Talk to AMGK