# Rollback Checklist

## Before Cutover

- [ ] Confirm previous release artifact/web root is retained.
- [ ] Take database snapshot and verify restore procedure.
- [ ] Record DNS/web server rollback owner.
- [ ] Confirm Stripe webhook endpoint can be reverted or disabled safely.
- [ ] Confirm maintenance message path.
- [ ] Confirm logs and error monitoring are active.

## Trigger Rollback If

- Checkout cannot complete.
- Signed webhook does not create ticket/QR/ledger.
- Seat holds fail or double-booking appears.
- Customers can access organiser/admin data.
- Organisers can access platform admin data.
- Media uploads execute or expose unsafe paths.
- Critical mobile booking path unusable.

## Rollback Steps

1. Put site into maintenance mode if available.
2. Stop schedulers/background jobs.
3. Restore previous web root/release artifact.
4. Restore database snapshot only if data migration caused irreversible corruption; otherwise preserve live order data and apply corrective migration.
5. Restore previous environment config if changed.
6. Repoint/reload web server.
7. Send stakeholder update.
8. Record incident notes and evidence.