Compare the operating models
A fictional standing talk sells capacity-only admission. A dinner assigns seat B4. A workshop reserves station T2 with equipment. All sell attendance, but only the latter two promise an identifiable place.
| Business requirement | General admission | Assigned place |
|---|---|---|
| Standing talk | Ticket quantity reduces capacity | Invented seat map unnecessary |
| Dinner B4 | Cannot fulfil a named-seat promise | Seat identity on ticket |
| Workshop T2 | Headcount hides station equipment | Station identity and supplied setup |
Work through the chosen model
Capacity-only tickets link attendee/quantity to event. Assigned tickets also link seat or station inventory. Keep station attributes separate from marketing ticket types; a ticket labelled Premium is not a place identity.
- Customer selects admission or place
- Reserve quantity or the actual seat
- Staff admit using matching ticket detail
Assigned places make seating promises precise but require layouts and change handling. General admission stays simpler; it cannot guarantee adjacency or a particular workstation.
Two talk tickets reserve two places without seat IDs. One dinner ticket names B4; one workshop ticket names T2. T2 cannot be sold again while allocated.
When the other model fits
Dinner guests choose any free table on arrival. Must every ticket have a seat ID?
Show the worked answer
No. Use capacity admission and any actual table-arrival process separately.