Website maintenance: agree tasks, response times and scope

When comparing “monthly website maintenance” quotations, the same label may cover very different work: content editing, technical updates or both. You need the actual tasks and the fault-response arrangement before the prices become comparable.

For your operation, regular checks and responding to a reported failure serve different needs. If an important flow fails between scheduled checks, you need to know how to report it and what response is agreed; the word “maintenance” alone implies neither daily checks nor immediate repair.

Define the ongoing work

Ask which parts are covered. Does the scope include content only, or also the CMS, extensions, hosting and external connections? A clear list shows which issues must be passed to another contact.

For a time allowance, establish what counts towards it. Discussion, checking, documentation and implementation can all use time. Ask how priorities are set and what happens to unused or excess time.

A shared task list helps you allocate the available time to the most important changes. With a priority and the necessary approval on each item, the supplier can act without piecing requests together from separate messages. You also need an agreed decision-maker when the allowance will not cover everything.

Separate response from resolution

An acknowledgement confirms that a report arrived. It does not establish when the cause will be found or the fault fixed. Agree what feedback you expect for each type of problem and when support is available.

The affected task communicates urgency better than a general “it does not work”: “The form stores no enquiries” differs from “Please change this image caption”. A named person responsible for temporary alternatives can approve another contact route when needed.

For a promised response time, agree when timing starts, which reporting channel applies and which hours are covered. Also ask whether the deadline means a first reply from a person or the start of work on the fault.

Agree how live changes are approved

Establish which work can proceed under an agreed procedure and which needs your approval. The distinction may depend on impact: correcting a typo differs from adding a booking rule.

Technical updates also need preparation. WordPress recommends a backup before updating. Ask how changes are checked and who performs recovery if problems arise. The details depend on the system.

A status report should distinguish completed work from open issues. “Maintained” is not particularly useful if you cannot tell which version was checked or which connection still fails.

Plan the end of the arrangement too

An agreed handover of documents, accounts and unresolved tasks keeps a later supplier change possible. Available files, necessary usage rights and ongoing third-party contracts are different things. Keeping them separately traceable prevents support from becoming the only place where knowledge of your website exists.

Our website and shop content maintenance covers editorial work; technical operations support has a separate scope. The guide to website and application maintenance complements this quotation review with technical tasks.