# Event website incident ownership plan

Complete this before an on-sale or live event. One person may cover more than one role in a small team, but name a backup and the authority to decide. Store this plan somewhere accessible if the event domain or email fails. Keep credentials in the approved secret system, not here.

**Event / edition:** [ ]  **Plan owner / last review:** [ ]  **Official alternate coordination channel:** [ ]

| Responsibility | Primary and backup | Authority or specific task | Contact route / vendor reference location | Handoff trigger |
| --- | --- | --- | --- | --- |
| Incident coordinator | [ ] | Declare, prioritize, pause changes, escalate | [ ] | [ ] |
| Technical operator | [ ] | Diagnose and make approved production changes | [ ] | [ ] |
| Hosting / DNS / CDN liaison | [ ] | Open cases, relay confirmed status | [ ] | [ ] |
| Registration / ticketing liaison | [ ] | Verify vendor boundary, reconcile pending work | [ ] | [ ] |
| Attendee communication owner | [ ] | Publish approved impact and next update | [ ] | [ ] |
| Recovery verifier | [ ] | Check journeys and record evidence | [ ] | [ ] |
| Security/privacy escalation owner | [ ] | Activate separate response if indicators appear | [ ] | [ ] |

**Declaration trigger:** [affected attendee journey / sale period / event deadline / other agreed condition].

**Incident record:** [link to current impact, known facts vs hypotheses, decisions, action owner and UTC time, vendor cases, next update].

**Alternate public channel if domain or email is down:** [URL / verified account / approval owner].

**Recovery acceptance:** public details [ ], registration [ ], official ticket path [ ], confirmations [ ], delayed queues [ ], monitoring [ ]. **Verifier and evidence:** [ ].

**Explicit handoff:** Outgoing coordinator [ ], incoming coordinator [ ], accepted at [time and zone], current impact [ ], open actions [ ], next public update due [ ].

**After-action owner and review date:** [ ]. This availability plan does not replace a security or privacy incident response procedure.

Sources: [Google SRE incident management](https://sre.google/sre-book/managing-incidents/) and [Atlassian Statuspage incident creation](https://support.atlassian.com/statuspage/docs/create-an-incident/).