Website Maintenance, Hosting and Content Updates: What to Put in the Scope

A useful website support scope explains what will be maintained, which changes are included, how requests are handled and what happens when something goes wrong. Separate technical upkeep, hosting and content work so the proposal can be compared against the website’s actual needs.

Start with an inventory and a few examples of expected requests. The number of pages alone says little about the support required by a site with forms, customer accounts, integrations or frequent bilingual updates.

Separate the main kinds of work

Ask the proposal to describe these areas individually:

• Technical maintenance: agreed software updates, checks and repairs
• Hosting: the environment that serves the website and the specified operational support
• Content updates: approved changes to text, images, documents or listings
• Development changes: new features, redesigned layouts or integration work

Identify where tasks overlap. Uploading a new report may be an editorial change; building a searchable report archive may require development. A broken form may involve the website, an email service or a third-party integration.

Include examples beside each category. That gives both sides a clearer basis for deciding how a future request will be handled.

Inventory the website and its dependencies

Record the CMS, custom components, forms, integrations and services the website relies on. Note which team is responsible for each part.

Include the domain, hosting, certificate arrangements, analytics setup and any paid software licences. Confirm who owns the accounts, pays renewals and receives expiry notices.

For an existing site, ask whether the provider needs an initial assessment before accepting maintenance. The proposal should identify known issues and assumptions, especially where another team built custom functionality.

Provide representative tasks such as submitting an enquiry, logging in or updating a language edition. These become useful checks after technical changes.

Agree how updates will be checked

Specify which software the provider updates and how changes will be reviewed. A website can contain CMS software, extensions, themes and custom code with different support responsibilities.

For WordPress sites, the official updating guidance recommends backing up the website before an update. Ask how the proposed service carries out that precaution and what it checks afterward.

Where the agreed setup includes a test environment, define how an update moves from testing to the live site. Include the important user tasks in the review, rather than checking only whether the homepage opens.

Record how failed updates are handled and who decides when a change can proceed. Avoid assuming that a general maintenance label covers every compatibility problem.

Describe backups and recovery clearly

Ask what is backed up, how often copies are created, how long they are kept and who can request a restoration.

For a typical WordPress site, the official backup handbook explains that a full restoration needs both files and the database. Confirm that the proposed coverage matches the actual website.

Ask the provider to explain what changes could be lost if an older copy is restored. Also agree how restoration is tested and how long recovery is expected to take under the specified conditions.

For sites receiving orders or other live submissions, discuss how those records will be handled during recovery. A restored page and a reconciled set of business records are separate checks to include in the plan.

Make content-update allowances practical

Describe the editorial work you expect: replacing images, publishing news, uploading approved files, updating staff details or adding a language version.

If a proposal includes a time or request allowance, ask how it is measured and what happens when it is used. Define whether unused allowances carry forward and how additional work is approved.

State who supplies and checks the content. Copywriting, translation, design and data verification may require their own scope.

For example, “upload an approved PDF with its title and language label” is easier to estimate than “update the annual report section”. The latter could also involve new artwork, archive changes and layout adjustments.

Define support arrangements using real incidents

Agree the contact channel, support hours and the information needed to assess a request. Specify how urgent problems are distinguished from ordinary changes.

Use scenarios to test the arrangement:

• The entire site is unavailable
• An enquiry form stops sending messages
• An editor cannot publish an update
• A new page layout is requested before a campaign

For each scenario, clarify who investigates, who authorises work and how progress is communicated. A response target should say whether it covers acknowledgement, investigation or resolution.

If another provider controls an affected service, identify the coordination route. The website team needs the relevant contact and permission to work within the agreed scope.

Ask for support evidence you can use

Choose a reporting format that helps the company understand what happened. It might include completed updates, reported incidents, backup checks, unresolved issues and decisions needed.

Ensure the responsible person can open the records. A report stored in an inaccessible system is difficult to use during a review or renewal discussion.

Keep technical completion and user acceptance distinct. When an issue is repaired, test the operation that failed and record the result. For a CMS problem, that may mean selecting an image, saving a draft and publishing it in the relevant browser.

Plan renewal and handover at the start

Record the contract period, renewal process, payment responsibilities and the point at which the scope will be reviewed. Confirm commercial terms directly with the provider.

Agree what the company receives if support changes hands: website files, relevant configuration, an account register, documentation and any transferable materials covered by the agreement.

Handle credentials through an approved secure process. Identify company-controlled ownership early so access does not depend on one person’s private account.

Miracle’s published Alcatel Mobile case includes website development, WordPress, hosting and maintenance alongside the UX and UI work. It is a useful reference for discussing design delivery and ongoing operation together.

What to include in your support brief

Share the website address, platform, current providers and the tasks your team performs. Include known problems, typical content requests and any fixed reporting or campaign dates.

Ask for a proposal that identifies included work, additional-work approval, dependencies and handover materials. Compare those details across quotations before comparing headline prices.

Miracle’s website design and development services can be discussed together with the ongoing support your site requires. Send your website brief with the available information and the responsibilities you want clarified.