Know which account controls each part
A business website may depend on a domain registrar, DNS service, hosting, application, email provider and external booking or payment tools. Make a simple inventory of the accounts your site actually uses, the business owner responsible for each and the renewal contact. Confirm how access is granted and revoked. Avoid collecting every password in a single ordinary document. Administrative access should be given only to the people who need it and removed when their work ends.
Define what care includes
Ongoing care can mean very different things. Ask whether it covers hosting, application updates, compatibility checks, uptime checks, small content edits or response to failures. Identify the parts supplied by another provider. Agree on support channels, working hours and how urgent incidents are handled. Response time and resolution time describe different things; a reply does not prove a fault is repaired. Record the actual service commitment in the accepted scope rather than relying on an informal label such as fully managed.
Treat recovery as a process
A backup is useful only if the necessary files and data can be recovered. Ask what is included, how often copies are taken, how long they are retained and where they are kept. Determine who can restore them and when restoration was last demonstrated in a separate environment. An older recovery point may lose recent changes, while a failed restore can prolong an outage. Decide which loss and interruption your business can tolerate before choosing the backup arrangement.
Agree how updates and edits reach production
Decide who approves changes and which changes need a test or rollback plan. A routine text edit and a payment integration change do not carry the same operational risk. For content editing, ask for a demonstration of the exact tasks staff need: changing a service description, replacing an image, updating a link or publishing a guide. Check that a failed save retains the draft and that permissions keep unrelated customer or staff information private. Define how larger requests are estimated separately.
Include a practical handover
Request the agreed access, an account inventory, renewal responsibilities and a short explanation of the supported editing workflow. Test the main contact and booking journeys after handover. Clarify how to request support and how to retrieve the business’s files or data if the service ends. Review which third-party subscriptions or licensed assets cannot simply be transferred. Document any agreed export format or transition assistance so neither side has to infer it during a later move.
Review when the business changes
Revisit the arrangement when the site gains a new integration, collects different information or becomes more important to daily operations. More traffic is only one reason to change a plan; a booking workflow or new staff access can also alter the work required. Venoxis Digital offers ongoing website care, but the specific hosting, backup, support and editing commitments should always be stated in your accepted proposal. This checklist helps define those commitments rather than replacing them.