# Final-week event ticket promotion — editable decision card

Copy this card for **one event edition**. Replace every bracketed field. All times must use the event's named time zone. Example rows illustrate decisions; they are not a required posting cadence.

Event / edition: [ ]  |  Date and time zone: [ ]  |  Official public page: [ ]
Promotion lead: [ ]  |  Ticket inventory owner: [ ]  |  Event-day operations owner: [ ]
Last facts verified at: [ ]  |  Next review at: [ ]

## 1. Current sale facts

| Fact | Public answer now | Source or approving owner | Checked at | Next check / change trigger |
| --- | --- | --- | --- | --- |
| Event name, edition, date, time and zone | [ ] | [ ] | [ ] | [ ] |
| Venue, arrival and access information | [ ] | [ ] | [ ] | [ ] |
| Ticket types visitors can buy now | [ ] | [ ] | [ ] | [ ] |
| Price and public conditions | [ ] | [ ] | [ ] | [ ] |
| Held allocation or waitlist release, if relevant | [ ] | [ ] | [ ] | [ ] |
| Real online sales cutoff, if any | [ ] | [ ] | [ ] | [ ] |
| Door-sale decision and capacity owner | [ ] | [ ] | [ ] | [ ] |

Do not turn a reserved allocation into a public “tickets left” number. If a count, cutoff or price has no current source, leave that claim out or mark the message Held.

## 2. Visitor path and link check

Draft message or campaign ID: [ ]  |  Exact destination URL including parameters: [ ]

| Step | What the visitor actually sees | Checked on phone by / when | Result or blocker | Retest owner |
| --- | --- | --- | --- | --- |
| Message or ad | [copy and link match current event] | [ ] | [ ] | [ ] |
| Public event page | [date, venue, price, availability] | [ ] | [ ] | [ ] |
| Ticket or registration choice | [advertised option available] | [ ] | [ ] | [ ] |
| Hosted checkout boundary, if used | [correct event and price] | [ ] | [ ] | [ ] |
| Confirmation through approved test path | [expected next step] | [ ] | [ ] | [ ] |

Use an authorized test method. Record any real test purchase and refund under the team's normal procedure. Do not expose private attendee details in this shared card.

## 3. Message and channel decisions

| Audience and permission basis | Useful answer or true deadline | Channel and draft | Owner / approver | Exact link | Planned local time | Stop or review time | State / actual URL |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [permitted subscribers] | [confirmed programme or actual cutoff] | [email draft] | [ ] | [ ] | [ ] | [ ] | Draft |
| [relevant community] | [available ticket type and event facts] | [partner copy] | [ ] | [ ] | [ ] | [ ] | In review |
| [event followers] | [verified event update] | [social draft] | [ ] | [ ] | [ ] | [ ] | Held |
| [ticket holders] | [practical arrival information; service or marketing purpose marked] | [approved channel] | [ ] | [ ] | [ ] | [ ] | Draft |

States: Draft → In review → Approved → Scheduled → Published. Use **Held** when inventory, consent, link, claim or approval is unresolved. “Scheduled” does not mean “published.” Save the actual URL or delivery evidence after sending.

## 4. Claim and offer gate

- Claim to use: [ ]
- Evidence and timestamp for remaining tickets or deadline: [ ]
- Price/offer approver and affected ticket types: [ ]
- Exact start, end and time zone: [ ]
- Fulfillment or check-in impact reviewed by: [ ]
- Person who will edit or remove old posts and ads: [ ]
- Partner posts requiring correction and contact: [ ]
- If the claim expires or changes, the replacement message is: [ ]

A discount, bundle or door price is optional. Avoid a countdown or scarcity statement unless it reflects a real, enforceable condition. Do not assume an ad click or a campaign-tagged visit is a paid order.

## 5. Stop, correction and event-day handoff

| Trigger | Immediate hold or correction | Official page owner | Direct attendee message owner, if needed | All affected channels / partners | Verified closed at |
| --- | --- | --- | --- | --- | --- |
| Ticket type sold out | [ ] | [ ] | [ ] | [ ] | [ ] |
| Link or checkout fails | [ ] | [ ] | [ ] | [ ] | [ ] |
| Price or cutoff changes | [ ] | [ ] | [ ] | [ ] | [ ] |
| Venue, access or schedule changes | [ ] | [ ] | [ ] | [ ] | [ ] |

Online sales on event day: [yes/no; actual closing time]  |  Door sales: [approved/not approved]
Door-sale location and payment owner: [ ]  |  Public status update owner: [ ]

Safety or emergency instructions follow the venue's approved plan. Promotional posts are not a reliable direct notice to every registered attendee.

## 6. Learn after the event

Reliable tickets sold in the final week: [count / unavailable]  |  Source: [ ]
Published messages and links: [ ]  |  Failures or corrections: [ ]
What the data can show: [ ]  |  What it cannot show: [ ]
One decision to keep: [ ]  |  One process to change: [ ]  |  Owner: [ ]

Compare with a genuinely similar edition before treating a late-sales pattern as a rule. Keep clicks, registrations, paid orders and attendance separate.