TATITECH

What a website care plan should include, and what to ask before you sign

A care plan should leave your website secure, current and fully yours. What it should cover, the questions worth asking before you sign and the warning signs to look out for.

· 5 min read · By Tatitech

A website is never finished. Team members join and leave, commentary needs publishing, notices change and the software around it keeps moving. Most wealth managers and family offices do not want to manage any of that in-house, so they rely on a care plan: a monthly arrangement with a supplier who looks after the site.

The difficulty is that “care plan” can mean almost anything, from a thorough service to an invoice for very little. Before you sign, it helps to know what a good plan covers and which questions bring the differences to light.

Hosting and availability

The plan should state clearly where the website is hosted, on whose account and how its availability is watched.

  • Where it runs. A reputable hosting provider or global network, with HTTPS enforced and security headers configured.
  • Monitoring. Automated checks that notice when the site is unreachable, and someone who acts on the alert rather than discovering the problem when a client mentions it.
  • Performance. Periodic checks that pages load quickly on phones as well as desktops.

Ask what happens at three in the morning on a Sunday. You do not necessarily need round-the-clock cover, but you should know what the plan offers.

Security updates and monitoring

Every website relies on software that needs updating. For a CMS such as WordPress, that means the core, the theme and every plugin. For a static website the list is shorter, but there are still build tools, form functions and third-party scripts to keep current.

A good plan says:

  • What is updated, and how often.
  • How updates are tested before they reach the live site.
  • How security settings are reviewed.
  • How you will be told when something needed attention, and what was done about it.

Backups and restore tests

A backup that has never been restored is an assumption, not a safeguard. Ask:

  • What is backed up: files, content, database, configuration?
  • How often, and how long are backups kept?
  • Where are they stored, and are they separate from the live hosting?
  • When was a restore last tested, and how long did it take?

For a static website kept under version control, every published version can usually be restored. For a CMS, the database needs its own backup schedule.

Certificates, domains and renewals

Expired certificates and lapsed domains are among the most avoidable website failures, and among the most embarrassing.

The plan should state who renews the domain name, who watches certificate expiry and who maintains the DNS records that point your domain at the website and your email service. Above all, it should be clear that the domain is registered in your firm’s name, not the supplier’s.

Content changes: turnaround and volume

For most firms, content changes are the part of the plan they use most. Make sure the plan says:

  • How changes are requested, and by whom.
  • How quickly a routine change is made, and how quickly an urgent one is.
  • How many changes, or how much time, is included each month.
  • What happens when you need more, and how it is priced.
  • How drafts are shared for your review and your compliance officer’s approval before publication.

The approval step matters. A supplier who publishes wording without sign-off creates risk, however well intentioned.

Reporting

A monthly report should be short and readable. It should tell you what changed, whether there were any incidents, how the website performed and what the supplier recommends. A dashboard you have to interpret yourself is not a report.

Who owns the accounts

This is the question most often overlooked, and the one that matters most if the relationship ends. Your firm should own, or at the very least hold administrator access to:

  • The domain name registration.
  • The DNS provider.
  • The hosting account.
  • The source code and content of the website.
  • Analytics, search console and business profile accounts.

The supplier can be granted access to work on these. They should not be the only party who can log in.

Exit and handover

Ask how the plan ends before it begins. A good answer covers the notice period, what will be handed over, in what format and within what time. That should include the website’s files and content, a list of accounts and services used, and any documentation needed for another team to take over.

A supplier confident in their service will describe this readily.

Incident response

Ask what counts as an incident, how quickly the supplier will respond and how you will be kept informed. If the website were defaced or a contact form misused, who would decide what to do, and who would talk to your clients if needed? These are questions to agree calmly in advance, not in the middle of an event.

Warning signs

Some answers should give you pause:

  • The domain or hosting is registered in the supplier’s name.
  • No one can say when a backup was last restored.
  • Updates are described as “automatic” with no testing or review.
  • Content goes live without your approval.
  • The contract has no clear exit terms, or charges heavily for handover.
  • Promises of guaranteed uptime or guaranteed security without explanation of what stands behind them.
  • Reporting that is only a list of page views.

A short checklist

Before signing a care plan, make sure you can answer each of these:

  • Where is the site hosted, and on whose account?
  • What is updated, how often and how is it tested?
  • What is backed up, where, and when was a restore last tested?
  • Who renews the domain and certificates, and in whose name is the domain?
  • How quickly are routine and urgent changes made, and how many are included?
  • What does the monthly report contain?
  • Do we hold administrator access to every account?
  • What happens, and what do we receive, if we end the plan?
  • How are incidents handled and communicated?

In closing

A good care plan is quiet. Your website stays accurate and secure, changes are made promptly with your approval, and everything that belongs to you remains in your hands. If you would like to compare your current arrangement against these questions, our own approach is set out under digital presence care.

Contact

Start a conversation

Tell us a little about your firm and what you have in mind. We will reply personally, and everything you share with us stays confidential.

Everything you share with us is treated as confidential, and we are happy to sign a non-disclosure agreement before any detailed discussion.

We use your details only to reply to you, and keep them confidential. Privacy policy