Your website may have a hosting company, a developer and someone in your business who updates the content. When a form stops sending, or a renewal is missed, it helps to know which person should act first.
Hosting and website maintenance can come from the same supplier, but their responsibilities still need to be agreed. Use the matrix below to identify gaps before they become urgent.
What is the difference between hosting and website maintenance?
Web hosting provides the environment that serves your website. Website maintenance looks after agreed aspects of the website itself, such as software updates and checks. Domains, DNS, email, backups and recovery may sit across several services. The names on an invoice do not establish who handles every task; the agreed scope does.
If you need an overview of routine care rather than responsibility allocation, our WordPress maintenance guide covers the types of checks to consider.
Start with the agreement, not the service label
“Managed hosting” and “maintenance included” need supporting detail. Ask what is managed, which website or account it covers, what is excluded and how support is requested.
One supplier may cover the server while another manages WordPress. Your business may still supply content, approve changes and renew a third-party subscription. Assign a lead contact for each area even when several people contribute.
For a Cyprus business working with suppliers elsewhere, record the relevant support hours and time zone. Distinguish monitoring, initial response and resolution: they describe different activities.
A practical website responsibility matrix
This matrix identifies parties to involve; it does not assign contractual responsibility automatically. Replace each role with the person or supplier who has accepted the task. If nobody has accepted it, mark the item unassigned and resolve it.
Domain registration and renewal
Parties to involve: business account owner and domain registrar.
Record: who renews, who receives notices and who can recover the account.
Evidence to keep: account ownership/contact details and renewal confirmation, without copying passwords into the matrix.
DNS records
Parties to involve: DNS account manager and the supplier requesting a change.
Record: who approves and applies changes, and who checks affected website and email services afterwards.
Evidence to keep: approved change request, previous record values and verification results.
Hosting environment
Parties to involve: hosting supplier and any separately appointed server administrator.
Record: which infrastructure and management tasks are covered, how an outage is reported and what access is available.
Evidence to keep: service scope and relevant support ticket or status information.
WordPress, themes and plugins
Parties to involve: appointed website maintainer and business decision owner.
Record: who reviews and applies updates, tests important functions and handles compatibility problems or renewal decisions.
Evidence to keep: agreed update scope and a dated change/test record.
Business email and website messages
Parties to involve: email provider, DNS manager and website maintainer as relevant.
Record: who handles mailbox issues, website sending configuration and confirmation that enquiries reach the intended recipient.
Evidence to keep: agreed delivery test and the outcome. A visible form alone does not prove delivery.
Backups
Parties to involve: appointed backup operator and business owner.
Record: what is copied, frequency, retention, storage location and who checks failures.
Evidence to keep: dated success/failure records and access arrangements. Confirm whether files, database and separate services are covered.
Restoration
Parties to involve: authorised recovery operator and business decision owner.
Record: who may request and approve a restore, any charges or limits, how recent data is protected and how the restored site is checked.
Evidence to keep: recovery procedure and test result. A backup subscription alone does not confirm every restoration service.
Content, accounts and third-party services
Parties to involve: business content owner, website editor and relevant external providers.
Record: who keeps information accurate, manages staff access and renews any required licences or integrations.
Evidence to keep: approved content changes, access review and renewal ownership.
Give each row an owner and a next step
For every area above, copy this short record into your own document:
Responsible person or supplier:
Business approver:
Service or agreement reference:
What is included:
What is excluded or still unclear:
Evidence and last check date:
First contact when something fails:
Escalation contact:
Open question, owner and target date:
Keep this record where the relevant team can find it. Store credentials separately through an appropriate secure process. Naming an account owner does not require sharing their password with everyone who reads the document.
Backups and restores need separate answers
A backup is a recovery copy, but its usefulness depends on what was captured and whether it can be restored. Ask the operator to explain the coverage, retention and recovery process in terms your business can use.
Consider how much recent information could be lost between copies. A site with frequent orders or enquiries may need different arrangements from a site that changes occasionally. Do not assume a schedule suitable for one website suits every business.
Also ask who decides when restoration is appropriate. Restoring an older copy may affect changes made afterwards, so the recovery plan should address recent information and the checks needed before normal use resumes.
Hosting support and maintenance support can overlap
A website problem is not always obvious from the first symptom. A slow page might require investigation across the website and its hosting environment. An enquiry-delivery failure can involve the form, sending service, DNS or receiving mailbox.
Agree who coordinates the investigation rather than asking your team to diagnose everything first. Suppliers can then establish the cause and explain which part of the work falls within their scope.
If you are comparing web hosting options, ask about the actual resources, management and support. For website maintenance, ask about the application tasks and checks included. A bundle can be convenient, but the responsibility record remains useful.
A hypothetical enquiry-delivery example
Imagine a customer reports submitting a form, but the team cannot find the message. This is a fictional example, not an Absolute Websites client incident.
The business records the affected page and approximate time, avoiding unnecessary customer information. The agreed website contact checks the form response and sending process. If evidence points to DNS or the receiving mailbox, the relevant provider is brought in through the named escalation contact.
After the issue is addressed, the team carries out an agreed test and verifies receipt. The ticket records the result and any ongoing action. “The form displays correctly” would not be sufficient evidence to close this particular problem.
Review the handover when responsibilities change
Revisit the matrix when you change suppliers, move hosting, add an integration or change the person managing the website. Confirm access arrangements and outstanding tasks before ending an old service.
Changing hosting does not automatically transfer the domain, DNS or email. Establish which services are moving and which remain, then agree the necessary checks. A supplier handover should preserve access to the information needed to operate the website.
Questions to ask Absolute Websites
When discussing support with us, explain where your website is hosted, who manages the relevant accounts and which tasks you want help with. We can discuss the scope rather than assume every existing service should be replaced.
Ask which responsibilities would sit with Absolute Websites, which would remain with you or another provider, and how the agreed support process would work. Confirm any schedules, inclusions, exclusions and response arrangements in the current proposal for your website.
FAQs
Does hosting include website maintenance?
Sometimes a package combines them, but hosting alone does not establish that every website maintenance task is covered. Ask specifically about WordPress updates, testing, backups, recovery and third-party services. Use the written scope to identify who handles each part, including responsibilities retained by your business.
Who is responsible for DNS and business email?
That depends on the accounts and agreements in place. DNS may be managed separately from hosting, and business email may use another provider. Identify the person authorised to manage each service and the process for approving changes. Do not assume that moving the website also moves email.
Does having a backup mean restoration is included?
Not necessarily. Confirm who can initiate recovery, what can be restored, any limits or charges and how the result will be checked. Also agree how information created after the backup will be handled. A successful backup notification and a verified recovery test provide different evidence.
Agree the responsibilities before you need them
Start with the tasks that matter to your website, then name the accepted owner, supporting evidence and escalation route for each. Resolve unassigned work and revisit the record when the setup changes.
To discuss your website support arrangements with Absolute Websites, share the services you already use and the responsibilities you want clarified.
