Define responsibilities
List the domain, hosting, external services and people with access. Specify who receives alerts and who makes decisions. Maintenance may be handled internally or by the studio, but an implied responsibility often becomes a forgotten task. Store credentials in an appropriate tool, not in a public document.
Check essential functionality
Define a short verification journey: open main pages, use mobile navigation and check contact functionality. If the site handles purchases or bookings, provide an appropriate test environment or mode. Frequency depends on the website’s activity and the changes made. A simple routine actually performed is more useful than a long list never executed.
Review information that can become outdated
Offers, contact details, external links and documents may change even when the code remains stable. Assign review dates to pages affected by business changes. Tell the content owner when an offer changes. Avoid accumulating old announcements on the homepage merely because they already occupy a designed space.
Separate fixes from improvements
A broken form and an idea for a new section do not have the same priority. Keep two lists: problems preventing a task and improvements to explore. For each request, record the page, observed behaviour and expected outcome. This reduces back-and-forth and helps quote enhancements without confusing them with agreed maintenance.
Your checklist
- An owner for every service and alert.
- A short verification journey.
- A content review schedule.
- Fixes distinguished from new requests.
