List what must be recoverable
Map the website code, configuration, editorial content, uploaded media, form settings and any external data sources. Not every website has a database or the same publishing workflow. Record where the current version lives in your actual setup rather than assuming a generic stack.
Separate material that can be rebuilt from version control from data that would otherwise be lost. Name the responsible provider, account owner and access recovery route without putting passwords or keys in the document.
Set recovery objectives the business can use
Ask how much content could be recreated from an older copy and how long the organisation could work through an outage. The answers help set a backup interval and a practical procedure. There is no universal interval: publishing frequency, important forms and provider options vary.
Decide which functions come first. For an information site, accurate content and a working enquiry route may be the priority. A booking or sign-in service depends on additional systems and data. Also agree which recovery point is acceptable if the latest state cannot be trusted.
Protect copies and access
Treat backups as part of the system's security. Limit who can read, change or delete them, and understand how the provider handles storage, access and retention. A copy reachable through the same account as the primary environment may be exposed to the same access problem.
Keep instructions and escalation contacts separate from credentials and recovery keys. Use the organisation's approved secret and account management. Confirm provider capabilities and contract terms directly; this guide does not claim that any particular hosting product offers a specific safeguard.
Practise recovery and check the user journey
Run a recovery exercise in a test environment with a copy you are authorised to use. Record elapsed time, required permissions and missing information. Check pages, images, forms, links, language versions and integrations afterwards. A home page that loads does not prove that the full workflow works.
Save results, issues, an owner and a date for the next exercise. Repeat relevant checks after major changes to the CMS, hosting or form delivery. If personal data is involved, the appropriate owners should also review privacy, retention and deletion requirements.
| Area | Question | Evidence from an exercise |
|---|---|---|
| Content and media | Where is the latest approved version? | A test restore returns the expected material |
| Access | Who restores it and where are instructions? | Permissions are checked without shared passwords |
| Enquiry route | Does a test message reach the agreed recipient? | A fictional enquiry arrives at the intended destination |