Transferable events

For gigs where whoever holds the ticket gets in, most of the named-event machinery simply isn't needed. Nobody's registration number decides anything, so there's far less data to pre-fill - the form only asks what buyers genuinely need. The centre of gravity moves to one place instead: the tickets board.

The board: held, spare, needed

Everyone buys what they can, and the board keeps one live tally for the whole event:

• Held - tickets a member currently holds, whoever they end up with;
• Spare - the part of someone's held count they're offering onward;
• Needed - how many tickets members are still short.

A spare is always part of someone's held count - offering one doesn't change how many tickets exist, just who can see it's available. Members who aren't attending can hold and offer spares too. During the sale window the board adds a demand tally: needed broken down by ticket type so buyers in the queue know exactly what's still worth grabbing, with the event's total spare count alongside.

Hand-overs confirmed by both sides

A swap only counts when both people say it happened - and either side can start it. A member who needs a ticket claims someone's spare, or a holder records a hand-off to a named recipient; the other person then confirms it, and only that confirmation moves the counts. A coordinator can cancel a pending swap that's gone stale, but never confirm one on someone's behalf.

No "I thought you had it" the week before the gig - the board is the shared memory of who holds what: every hand-over, pending and confirmed, stays on the record.

Less admin, same visibility

The squad still gets the shared place to join, the chat links, the travel-and-accommodation context, and the calm dashboard - everything in the overall process - just without the data-collection ceremony a named sale demands. Create the event as transferable and the workspace shows the board instead of the buying-group machinery.