# Event ticket sales pace — editable snapshot sheet

Event/date: [ ]  On-sale start/end: [ ]  Sales target (not safety capacity): [ ]  Saleable capacity source and owner: [ ]  Ticketing report/timezone: [ ]

**Counting rule:** Net valid tickets [include/exclude free RSVPs and comps: ]; refunds and voids [ ]; transfers [ ]; group orders [ ]. Track actual platform status, not page visits or carts.

| Snapshot date/time | Gross issued | Refunded/voided | Net valid tickets | Current saleable capacity | Ticket-tier change, campaign or outage | Report owner |
|---|---:|---:|---:|---:|---|---|
| | | | | | | |
| | | | | | | |

**Observed net pace:** (latest net valid tickets − prior net valid tickets) / elapsed days. Negative values are possible after refunds.

**Simple needed average:** (approved sales target − latest net valid tickets) / selling days left. This is an arithmetic scenario, not a forecast. If the target is already met or days left are zero, state that instead of dividing.

**Illustration only:** 320 net valid tickets seven days ago and 390 today gives 10 net tickets/day. A target of 600 with 21 selling days left also needs an average 10/day. It does not prove future demand will be steady.

| Ticket tier | Saleable allocation | Net valid | Remaining | On-sale status / change |
|---|---:|---:|---:|---|
| | | | | |

| Observation and context | Question to investigate | Owner | Decision | Next review |
|---|---|---|---|---|
| | | | | |

Do not exceed the approved venue or admission limits to chase a sales target. Compare other editions only at similar days-to-event and release stages, noting price and venue differences.