01Define what is being hosted
Identify the website or application, expected use, data types and operational dependencies. Email, DNS, domains and external services may be separate even when visitors experience one business website. Record the provider and account owner for each component before changing the environment.
The appropriate hosting arrangement depends on the application, traffic pattern, support skills and recovery needs. A label such as managed does not by itself explain which operating-system, application or content tasks are included.
02Separate platform care from website changes
The scope should identify who handles server maintenance, application updates, certificate renewal, monitoring and incident escalation. Content editing, redesigns and integrations are different work and should not be assumed to be included in a hosting charge.
Check dependencies such as licence renewals and payment or booking services. A platform can be online while a business-critical external integration is unavailable, so the support plan needs to explain how those cases are handled.
03Plan backup and recovery
Agree which files, databases and configuration are protected and how a restore is requested. Establish the recovery objectives appropriate to the business and test restoration. An active website and an existing backup job do not prove that the required information can be recovered in time.
Keep ownership and exit arrangements clear. The business should know how to obtain its content, domain control and necessary exports if the hosting relationship changes. Do not make the only recoverable copy dependent on the same compromised access as production.
