# Delayed-ticket delivery: test and release card

Use one card per ticket group. Record test references only; keep buyer names, addresses and full ticket codes in the ticketing system.

- **Event / ticket group:** ____________________
- **Provider and supported delivery route:** ____________________
- **Release condition, date, time and time zone:** ____________________
- **Release owner / backup:** ____________________
**Gate exception owner:** ____________________

| Checkpoint | Expected buyer or staff result | Observed result / test reference | Owner / done |
| --- | --- | --- | --- |
| Before purchase | The sales page or checkout gives the correct delivery expectation. |  |  |
| Order confirmed | The confirmation acknowledges the order without claiming that a ticket is already attached. |  |  |
| Held ticket | Check email, account, app and print routes offered by this provider. Record any usable credential or link. |  |  |
| Immediate-delivery control | An unaffected ticket type still follows its intended delivery route. |  |  |
| Alternate pickup, if offered | Buyer instructions and the desk procedure agree. |  |  |
| Release action | Authorized owner records exactly what was changed and which group was affected. |  |  |
| Post-release delivery | A controlled recipient can open the actual ticket or link; old hold wording is removed. |  |  |
| Admission check | The released credential works with the intended, controlled entrance method. |  |  |
| Missing-ticket exception | Support can find a confirmed order, identify delivery state and reach the gate owner. |  |  |

- **Release log:** group ______  action ______  local time/time zone ______  performed by ______  sample reference ______
- **Open exceptions and next owner:** ______________________________________________

Do not equate an order confirmation, ticket availability and successful check-in. Verify each state separately. Use only the controls documented for your provider.