Practical guide
What Ongoing Website Support Should Actually Include
A clear distinction between hosting, maintenance, content support and operational advice.
A launch is the start of operations
Websites need ownership after launch. Software changes, certificates expire, staff need help, content becomes outdated and customer journeys reveal new friction.
A useful support scope
- Availability and error monitoring
- Security updates and dependency maintenance
- Backup checks and recovery responsibilities
- Small content and configuration changes
- Form, booking and enquiry-flow testing
- Response targets and an escalation route
- A monthly summary of work, risks and recommended actions
Set boundaries
Support should state included hours, response times and what counts as a new project. Unlimited, undefined support creates poor expectations for both sides. A healthy agreement distinguishes incidents, routine maintenance, content requests and substantial feature development.