# Event website backup responsibility matrix

This worksheet turns “the host handles backups” into named duties and evidence. Complete it with the organizer, developer, host and ticketing provider. It is an operational record, not a legal interpretation of your contract. Do not store credentials or attendee records in this file.

**Event / edition:** [ ]  **Review date:** [ ]  **Organizer decision owner:** [ ]  **Next review trigger:** [renewal, migration, platform change, launch]

## Recoverable components and owners

| Component and source of truth | Copy/export/rebuild method | Backup operator | Storage account and location | Frequency/trigger | Retention | Failure monitor | Restore operator | Organizer approver | Evidence link |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Deployed code and configuration | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| CMS pages and structured content | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| Media and original assets | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| Registration submissions | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| Ticketing/payment records held by provider | [confirm provider boundary] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| DNS zone and domain configuration | [export or reconstruct] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

A host snapshot may not contain third-party ticket orders, external media or separate DNS. Confirm the provider's current service terms and backup scope rather than filling a row with an assumption.

## Questions to settle with each provider

1. What exactly is included and excluded? Can you provide a dated inventory of the latest recoverable copy?
2. Who owns the storage account and can access it if the hosting account or agency contract ends?
3. Who receives an alert when a backup fails, and who must act on it?
4. What backup or export is created immediately before a high-risk site change?
5. Who authorizes a production restore, who performs it, and how are new registrations and sales reconciled?
6. Where may a test restore run without contacting real attendees or charging real payments?
7. What are the agreed recovery-time and data-loss objectives, and what has a rehearsal actually demonstrated?
8. What are the restoration fee, notice requirement and handover format at contract exit?

## Evidence and agreement log

| Date | System | Latest backup/export observed | Restore test and content check | Gap and owner | Written agreement or ticket |
| --- | --- | --- | --- | --- | --- |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

A successful backup job is weaker evidence than a safe restore with the expected content. For a rehearsal procedure, use the separate [event website backup restore test checklist](/en/blog/event-website-backup-restore-test-checklist).

Sources: [AWS Well-Architected backup guidance](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/back-up-data.html), [AWS restore-test guidance](https://docs.aws.amazon.com/wellarchitected/2024-06-27/framework/rel_backing_up_data_periodic_recovery_testing_data.html), [WordPress backups](https://developer.wordpress.org/advanced-administration/security/backup/).