Docs

Named events

The Glastonbury-style flow - collect details first, form buying groups, and run sale day from static boards built for the rush.

Named tickets are tied to a person at purchase: whoever's details go into the checkout form is who gets in. That one rule shapes the whole flow - the sale is won or lost on having the right details ready and having more than one person in the queue. This is the machinery TicketSquad was originally built for.

Data first: collect what buyers need under pressure

Registration numbers, postcodes, ticket choices, accessibility needs: gathered early, checked twice. Everyone gets a clear, guided place to add the details their buyer will need at checkout, then confirm they are right before sale day. Coordinators can keep an event Open for a trusted shared sheet, or Closed so personal details stay inside each buying group.

TicketSquad member data submission screen with event-specific fields
Member data submission

Groups first: split one crowd into independent buying groups

Several smaller buying groups means several real attempts at the queue. The core tactic is simple: if one person gets through, they buy for their group. The software makes group shape, membership, and responsibility visible before the sale begins.

TicketSquad group roster showing members organised into buying groups with a waiting room
Group assignment

Readiness: spot missing details before they cost you tickets

The coordinator can see missing data, empty groups, and anything that needs chasing. The job is not to make the organiser do more admin. It is to make the last ten percent visible early enough that it can be fixed calmly.

TicketSquad coordinator readiness view showing member completion and what matters now
Coordinator readiness

Sale-day boards: built for the worst five minutes of the year

No hunting through chats. No spreadsheet panic. No dependency on the app being live at the worst possible moment. Before the rush starts, TicketSquad generates a static sale-day view for each buying group. If the main app, the database, or half the internet is struggling under load, buyers still have a fast, ready-to-open board with the details they need.

TicketSquad static sale-day board showing buyer-ready member details
Static sale-day board

After the sale: track outcomes and keep the relay moving

Real sales are messy. One group might get through while another misses out. Capture partial success, celebrate the wins, and help successful buyers keep going: once a group is covered, buyers who reach the front can try to help the next group, and anyone still unfulfilled stays visible for resale.

TicketSquad tickets-secured dialog confirming who is covered by a reported purchase
Outcome reporting

And when the whole squad gets in

When every member is confirmed, the app turns the result into a clear shared win: the moment the buying group knows the plan worked and nobody has been left wondering.

TicketSquad event brief showing sale day fully reported with every ticket confirmed
Sale day reported