Support & operations · Practical guide

Compare support quotes against the whole website journey

The maintenance proposal covers website hosting, but important downloadable assets live in a separate account outside its scope.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

What to change

Compare the proposed coverage with the actual public estate. Ask the supplier to trace a representative page, download and external dependency, then mark who supports each part. The practice should understand which failure would require another supplier or account owner. Clarify response coordination as well as technical coverage, because a visitor sees one website even when several contracts sit behind it. Record exclusions plainly before comparing headline support prices.

A worked example

Illustrative example

Illustrative test: A fictional failed download is routed to the correct responsible account owner. A low-cost support proposal may cover hosting but exclude the account serving public leaflets. A fictional failed-download exercise reveals that gap. The practice assigns the storage owner and coordinator before accepting the arrangement, while comparing the quote with alternatives on equivalent coverage. The visitor journey remains the organising principle, even though its repair may involve several contracts and the cheapest headline price may describe a narrower service.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

What this means for your practice

A support price may cover the website host while excluding the separate account holding important downloads. Ask the supplier to trace a representative page, document and external tool, then mark who supports each part. Your practice should understand which fault would require another provider and who coordinates that conversation. Visitors experience one journey even when several contracts sit behind it. Clarify exclusions before comparing headline monthly prices, because a lower quote may simply cover less. A fictional failed-download scenario is a useful test: the team should be able to identify the responsible owner and next action without asking reception to work out the storage architecture.

How to check the result

The proposal explains who handles the full public journey and any excluded dependencies.

A mistake to avoid

A low monthly price may reflect a smaller estate rather than equivalent service.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore support & operations services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.