# Global event website maintenance-window planner

Use for a planned change that could interrupt event information, registration or tickets. There may be no zero-impact hour for a global audience. Choose a window from observed usage and event commitments, then document the remaining impact and who accepts it.

**Event / edition:** [ ] **Change and expected disruption:** [ ] **Decision owner:** [ ] **Implementation owner:** [ ]

## Blackout and dependency inventory

| Date/time and zone | Why it matters | Journey or provider affected | Owner who confirms blackout |
| --- | --- | --- | --- |
| [ ] | [on-sale / registration deadline / live event / email send] | [ ] | [ ] |

**Affected paths:** public page [ ], sign-in [ ], registration [ ], ticket checkout [ ], confirmation mail [ ], other [ ].

**Can this change be staged or made without user-visible interruption?** [Evidence / constraints]

## Compare candidate windows

| Candidate | Start/end UTC with date | Local times for main audience regions | Recent traffic and transaction evidence | Conflict with blackout or provider | Staff available | Expected interruption | Decision |
| --- | --- | --- | --- | --- | --- | --- | --- |
| A | [ ] | [region + IANA zone + local date/time] | [ ] | [ ] | [ ] | [ ] | [ ] |
| B | [ ] | [region + IANA zone + local date/time] | [ ] | [ ] | [ ] | [ ] | [ ] |

Convert for the actual calendar date; daylight-saving offsets can change. Do not assume the organizer’s home time zone represents the audience.

## Execution and recovery budget

- **Preparation and pre-change snapshot:** [duration and owner]
- **Implementation:** [duration and owner]
- **Warm-up and real attendee-path checks:** [duration and tester]
- **Latest safe rollback decision time (UTC and zone):** [ ]
- **Abort trigger / rollback action and owner:** [ ]
- **How new registrations or sales are reconciled if reversal is needed:** [ ]

## Public notice and completion record

**Advance notice approved by:** [ ] **Published at and channels:** [ ]

“[Event/service] will undergo scheduled maintenance on [date, start and end time with time zone]. [Specific functions] may be unavailable. [Unaffected function / verified alternative] remains available at [official URL]. Updates will appear at [status URL]. We will confirm completion after checking registration and ticket access.”

**After the change:** public page [pass/fail], registration [pass/fail], official ticket path [pass/fail], affected email [pass/fail]. **Verifier / time and zone:** [ ]. **Completion or extension notice URL:** [ ].

An automatic status of “completed” at the expected end does not prove the attendee journeys work. Verify first, then communicate actual status.

Sources: [Atlassian Statuspage scheduled maintenance](https://support.atlassian.com/statuspage/docs/schedule-maintenance/) and [AWS maintenance-window timezone fields](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-maintenance-create-mw.html).