# Event website staging boundary and release worksheet (English editable template)

Complete this before cloning or testing a live WordPress event site. Record the actual host/plugin behavior; a staging name does not disable payments, email or external integrations by itself.

## 1. Environment and owner

| Item | Record |
| --- | --- |
| Production URL and last verified time |  |
| Staging URL and access-control method |  |
| Host, staging tool and documentation link |  |
| Technical owner, content approver and public verifier |  |
| Recovery point and who can use it |  |
| Planned release window |  |

## 2. Clone and outbound-effect boundary

| Dependency | Copied? | Staging control or substitute | Owner / evidence |
| --- | --- | --- | --- |
| Pages, posts and media |  |  |  |
| Event/calendar records |  |  |  |
| Registration or ticket records |  |  |  |
| Site users and administrator access |  |  |  |
| API keys and webhook destinations |  |  |  |
| Attendee and staff email |  |  |  |
| Payment gateway and test mode |  |  |  |
| Inventory or capacity synchronization |  |  |  |
| Analytics and external automations |  |  |  |

Never use real attendee identities or real payment details for a rehearsal unless the responsible operator has approved a specific controlled process.

## 3. Representative visitor tests

| Test ID | Page/flow and approved fact | Test identity or mode | Staging result and URL | Reviewer | Ready? |
| --- | --- | --- | --- | --- | --- |
| 1 | Current event date, time zone and venue | Signed out |  |  |  |
| 2 | Future event or changed calendar record | Signed out |  |  |  |
| 3 | Registration form acknowledgement and staff route | Test identity |  |  |  |
| 4 | Ticket label, capacity and checkout destination | Provider test route |  |  |  |
| 5 | Phone navigation and embed fallback | Phone/signed out |  |  |  |

Known differences between staging and production: ______

## 4. Promotion and public verification

| Item | Record |
| --- | --- |
| Exact files, settings or content records to promote |  |
| Production changes since the clone (registrations/orders/content) |  |
| Will any database sync replace production data? Evidence |  |
| Approver and release decision |  |
| Recovery trigger and operator |  |
| Production event URL and signed-out result |  |
| Registration/ticket path and acknowledgement result |  |
| Unaffected page check |  |
| Test settings/placeholders absent from production? |  |
| Released by / verified by / time |  |

Staging copy retained or retired, with owner and next review date: ______