Every website and application changes after launch, even if nobody touches the code. Dependencies age, security vulnerabilities are discovered, browsers and operating systems update, and your business needs evolve.
Without a plan, maintenance happens in emergencies, which is the most stressful and expensive way to do it.
Core elements of a good plan
- Security updates: regular patching of frameworks, libraries, plugins and servers.
- Monitoring: uptime, error tracking and performance alerts.
- Backups: automated backups with tested restore procedures.
- Bug fixes: a clear process for reporting, prioritising and resolving issues.
- Compatibility: updates for new browsers, devices and OS versions.
- Small improvements: time reserved for enhancements as needs change.
- Documentation: up-to-date notes on architecture, hosting and procedures.
Agree the terms in writing
A maintenance plan should state clearly what's included, what isn't, and how quickly issues are handled.
- Support hours and the channels for raising issues.
- Response and resolution targets by severity.
- Escalation steps for critical problems.
- What counts as maintenance versus new feature work.
- How unused or extra hours are handled.
Test your backups. A backup that has never been restored is an assumption, not a safety net.
Signs you need a plan now
- Nobody knows when dependencies were last updated.
- Problems are discovered by customers rather than monitoring.
- Only one person knows how to deploy or fix the system.
- You don't know when backups last ran successfully.
Maintenance is rarely exciting, but it's what keeps software secure, reliable and ready to grow.