Skip to main content

Maintenance resources

Planning tools for keeping technology maintained

Use these templates to organise maintenance internally, brief a provider or check whether your current arrangement covers the basics. Print them or copy them into your own documents.

Template 1

Website and server maintenance schedule

A baseline schedule for a business website or store and its hosting. Higher-risk sites need tighter intervals. For a detailed task list see the website maintenance checklist.
FrequencyTasksEvidence to keep
Every dayAutomated backups run and complete successfully; uptime and SSL monitoring active; security alerts reviewedMonitoring tool, backup logs
Every weekCMS, plugin, theme and dependency updates reviewed and applied on staging; key forms and checkout tested; disk space checkedStaging site, update log
Every monthOperating system and server package patches; security scan; broken link and 404 review; performance check against Core Web Vitals; maintenance report issuedPatch log, scan report
Every quarterFull restore test from backup to a separate environment; user and access review (remove leavers, enforce MFA); review of plugins/extensions still neededRestore test record, access list
Every yearDomain and certificate renewal review; hosting and licence renewals; PHP / runtime end-of-life review; disaster recovery plan rehearsal; architecture reviewRenewal calendar, DR plan

Template 2

Technology asset inventory

You can't maintain what you haven't listed. Record these fields for every website, application, server and service your business depends on.
FieldWhat to record
AssetWebsite, store, application, server, email domain
Business ownerThe person accountable for the asset's purpose
Technical ownerWho maintains it day to day (internal or external)
Platform & versione.g. WordPress 6.x, PHP 8.x, Ubuntu 24.04 LTS
Hosting / providerProvider, plan, account owner and renewal date
Domain & DNSRegistrar, DNS host, renewal date, registrar lock status
AccessWhere credentials are stored, who has admin access, MFA status
BackupsWhat is backed up, how often, where, retention, last restore test
MonitoringUptime, SSL, security and performance monitoring in place
IntegrationsPayment gateways, CRMs, APIs and the credentials they use
CriticalityImpact if unavailable for 1 hour / 1 day (sets RTO and RPO)

Not sure what RTO and RPO mean? See the technical glossary and our guide to disaster recovery planning.

Template 3

When your website goes down: first-response checklist

Keep this somewhere your team can find it during an outage. If you need help immediately, use our emergency website support.
  1. 1Confirm the problem from outside your network (another device or a monitoring tool) and note the time it started.
  2. 2Check obvious external causes first: domain or SSL expiry, hosting provider status page, DNS changes.
  3. 3Ask what changed recently – updates, deployments, configuration or content changes – and who made them.
  4. 4If a security incident is suspected, do not delete files. Preserve logs, change administrator passwords and enable maintenance mode if customers are at risk.
  5. 5Notify the people who need to know: your maintenance provider, internal stakeholders and, if customer data may be affected, whoever handles data protection.
  6. 6Restore service using the least risky option: roll back the last change, or restore from the most recent clean, verified backup.
  7. 7Verify recovery: key pages, forms, checkout, logins, email delivery and integrations.
  8. 8Record what happened, the root cause, the fix and actions to prevent a repeat.

Would you rather hand this to someone else?

A SupportSafe maintenance plan covers every item in these templates, documented in a monthly report.