Maintenance is a set of responsibilities. Begin with what your website runs and who relies on it, then decide which checks and changes belong in the agreement.
Keep the information useful
Review contact details, timings, services, staff information and any dated material. Remove an offer or service that no longer applies. Ask who supplies replacements and who approves them before they appear on the website.
For a small professional site, accurate information may be the most frequent change. A store also needs someone managing products, stock and order information. Those are different operating tasks, even when they happen on the same website.
Match the checks to the website
A static information site, a CMS and a custom application have different dependencies. List the services actually used: hosting, domain, editor, database, forms, payments, booking or integrations. Do not pay for a checklist of products your website does not run.
- Check important pages and links.
- Review contact or submission routes using an agreed safe method.
- Inspect the layout on representative phone and desktop sizes.
- Identify platform updates and whether they require testing.
- Confirm renewal, backup and recovery responsibilities.
Keep a small change record
Record the date, page or component, requested change, approver and result. For a technical change, note how to return to the previous working version. This can be a simple record; it does not require buying a new management platform.
The maintenance worksheet is a blank planning aid. It is not a report of checks already performed on your website.
Define the boundary
Agree whether content edits, fault diagnosis, restore work and third-party troubleshooting are included. A new store, portal or booking flow is feature development and needs its own scope. Existing technical problems may need an initial assessment before ongoing support can be defined.
Know what to do when something fails
Identify the contact route and the information needed: page address, observed problem, time and any non-sensitive screenshot. If a business depends on forms or orders, agree a manual fallback. Support hours and response arrangements should reflect the actual service, rather than a generic promise.
Read how to send a clear change request and what to record at handover.
Written by VikaSquare for business owners and office teams. Illustrations and checklists are practical planning aids. Professional permissions and sensitive-data requirements need their own review.