# Event parking instructions: editable page and verification worksheet

**Language:** English. Make a separate reviewed copy for every language you publish. Replace bracketed fields with facts approved by the venue or event owner; delete any line that does not apply. Keep the verification tables private.

## Public page block — copy, complete and publish

### Where to park for [event name and date]

**Choose your arrival option:** [One sentence telling each ticket or visitor group which option below applies. If parking is not provided, say so here and link to verified alternative arrival information.]

#### [Approved lot name] — for [eligible visitors]

- **Navigate to:** [Approved parking-lot address and exact vehicle entrance]. [Directions to approved lot](https://example.org/replace-with-verified-lot-link).
- **Open for event arrivals:** [Dates, times and time zone, if relevant].
- **Before you leave:** [Reservation, prepaid pass or permit action and verified link, or “No advance action required” if confirmed].
- **Cost and payment:** [Confirmed charge and payment route, or a link to the responsible operator’s current information].
- **From parking to the event entrance:** [Verified walking route, landmarks, named attendee door and opening period].
- **If this lot cannot be used:** [Confirmed alternate instruction or staffed contact; do not promise another space without approval].

#### [Second approved lot, only if needed]

[Repeat the same fields. State who should use this option and what differs.]

**Accessible arrival:** [Location, vehicle entrance, route to the attendee entrance and assistance contact approved by the venue accessibility lead. Do not label a route certified without a competent site-specific determination.]

**Other arrival choices:** [Verified public transport, drop-off or shuttle information and link, if relevant].

**Questions on event day:** [Approved public contact and hours]. **Last checked:** [date and owner].

## Private fact-source and sign-off matrix

| Fact to verify | Approved value / exact wording | Source URL or document, version and date | Venue or event approver | Checked on | Public location |
| --- | --- | --- | --- | --- | --- |
| Event edition, date and arrival window |  |  |  |  |  |
| Lot name, address and vehicle entrance |  |  |  |  |  |
| Lot eligibility by ticket, day or permit |  |  |  |  |  |
| Opening hours and reservation step |  |  |  |  |  |
| Fee and payment route, if confirmed |  |  |  |  |  |
| Walk from lot to attendee entrance |  |  |  |  |  |
| Accessible parking and arrival contact |  |  |  |  |  |
| Closure or operating-limit fallback |  |  |  |  |  |
| Approved map and booking links |  |  |  |  |  |

Do not publish an unresolved row as a provisional instruction. Keep staff-only access notes outside the public page.

## Publication and channel check

| Surface | Link or location | Same lot names, audience and hours? | Owner | Live check date | Correction needed |
| --- | --- | --- | --- | --- | --- |
| Canonical event parking page |  |  |  |  |  |
| Event information / ticket page |  |  |  |  |  |
| Confirmation or reminder message |  |  |  |  |  |
| Attendee programme or help page |  |  |  |  |  |
| Onsite signs |  |  |  |  |  |
| Front-of-house staff answer |  |  |  |  |  |

### Live-page QA

- [ ] On a phone, find parking information from the event entry page without searching the site.
- [ ] Each directions link opens the intended **lot entrance**, not only the venue building.
- [ ] Reservation and payment links, if used, open the approved destination and match the text.
- [ ] The address, route, eligibility, hours and fallback remain readable if a map or image does not load.
- [ ] Link names distinguish lots; keyboard focus reaches each link in a usable order.
- [ ] A first-time visitor can identify the right lot, required advance step and attendee door.
- [ ] Every published language uses the same approved names, dates, times and conditions.
- [ ] Page, reminders, signage and staff wording have been compared after the latest change.

## Change record

| Change and previous wording | Approved by | Effective time and audience | Page updated | Queued messages corrected | Onsite team informed | Guest notification route |
| --- | --- | --- | --- | --- | --- | --- |
|  |  |  |  |  |  |  |