KEISSMEDIAGet in touch
← All resources

Launch and hand over

Hosting and support checklist

Decide who pays, monitors the service and handles failures before launch.

Fill in the template ↓Download a blank template (.md)
When to use it
When choosing hosting, preparing launch or discussing ongoing support.
What you will have
Agreed ownership, costs, checks and support boundaries.
When not to use it
This is a checklist, not a provider recommendation, support agreement or uptime guarantee.
View the worked example

The example is fictional. It demonstrates completion, not the outcome of an actual project.

Hosting needs

A static promotional site without accounts or a server database. Test access from target regions before choosing a provider.

Ownership and payment

The client owns the main account. The appointed administrator receives domain-renewal notices.

Cost and limits

Check current prices and limits with the provider on the selection date. Record what happens if a limit is exceeded.

Monitoring and recovery

Assign responsibility for checking the site. Keep source and recovery instructions separate from the sole production account.

Support boundaries

Separate defect correction, copy changes and new features. Do not promise round-the-clock support without an agreed team and terms.

Ending support and migration

Before retiring the old host, check the new build, HTTPS and required redirects. Data deletion requires an agreed decision.

Download example (.md)

Fill in the template

If an answer is unknown, say so. You do not need to complete every field before a first conversation.

Static site or server application, integrations, data storage, audience, access regions and constraints.

Whose accounts own the domain and hosting? Who has access and receives billing notices?

Price, free-tier limits, overages, third-party services, trial expiry and migration options.

Who notices a failure, where is the backup, how is recovery tested and how is a previous release restored?

What is covered: incidents, updates, content? Agree contact route, working hours, response and restoration targets separately.

How are access, data, backups and instructions transferred? Who pays for migration and retires old services?

Fields work in your browser. Your text is not sent to us or saved after the page closes. Download the document to continue later.

Sources and adaptation

Adapted from GOV.UK guidance on hosting and service monitoring. Government procurement requirements were removed; domain ownership, access transfer and the distinction between support and new work were added.

Contains public sector information licensed under the Open Government Licence v3.0.

Version 1.0 · 15 October 2026