# Sponsor ticket allotment and handoff worksheet

Use one row per sponsor **and** event/date/ticket type/access zone. Use sponsor and event references, not attendee names, live codes, account credentials or private agreement text. This sheet is a count and handoff aid; keep the authoritative ticket records in the chosen system.

## 1. Confirm the approved units

| Sponsor ref | Event/date ref | Ticket type and access zone | Approved units | Approval ref | Inventory owner | Sponsor contact role | Distribution due date, if set |
| --- | --- | --- | ---: | --- | --- | --- | --- |
| ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ |

- [ ] The approved units fit the event's actual capacity and category/zone allocation.
- [ ] The sponsor's distribution route and permitted ticket categories are clear.
- [ ] A promise is recorded separately from a platform allotment and a valid guest ticket.

## 2. Record the provider allotment and representative handoff

| Sponsor + event row ref | Provider model observed | Units allocated in provider | Stock/count checked at | Representative role and access checked? | Handoff complete? | Unresolved issue / owner |
| --- | --- | ---: | --- | --- | --- | --- |
| ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| ______ | ______ | ______ | ______ | ______ | ______ | ______ |

- [ ] Test one authorized assignment or invitation without placing a real guest's personal details on this sheet.
- [ ] Inspect the delivered ticket's event, date, category, zone and validity in the provider record.
- [ ] Confirm that a changed sponsor allotment produces the expected event inventory result; do not infer it from a sponsor-facing screen alone.

## 3. Reconcile before doors and after the event

Enter each **state as the provider defines it**. Some counts overlap: checked-in tickets may also be included in valid-issued tickets. Do not add the columns together as if they were separate pools.

| Sponsor + event row ref | Approved | Provider allocated | Invitations/assignments observed | Valid guest tickets issued | Voided/returned | Unresolved balance and reason | Owner | Checked in after event |
| --- | ---: | ---: | ---: | ---: | ---: | --- | --- | ---: |
| ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ |

- [ ] Explain any issued ticket without an approved sponsor unit and any approved unit without a working admission path.
- [ ] Investigate failed invitations, duplicate assignments, changes and returns in the authoritative ticket record.
- [ ] Give the entrance team the current category rules and named exception owner.
- [ ] After the event, compare valid issued tickets with recorded admissions; unused sponsor units are not assumed to have been returned to public sale.

## If a sponsor quantity changes

| Change ref | Approved number updated by | Provider allotment checked by | Affected guest tickets reviewed by | Event stock checked by | Sponsor and gate teams told by | Closed on |
| --- | --- | --- | --- | --- | --- | --- |
| ______ | ______ | ______ | ______ | ______ | ______ | ______ |

Provider examples, not universal features: [run.events](https://community.run.events/knowledge-base/article/how-to-give-complementary-tickets-to-sponsors) documents sponsor-level labels, deal-specific quantities and a representative who can assign sponsor tickets. [InEvent](https://faq.inevent.com/l/en/in-event-registration/ticket-quotas) documents sponsor ticket-type allotments and distinguishes available sponsor tickets from attendee-assigned or invited tickets. Verify the behavior and count definitions in your provider.