Glossary
What TicketSquad means by Squad, Group, sale plan, named and known events, the roles, and the tiers.
A short translation table for the words TicketSquad uses everywhere else.
Squad
Everyone trying to get to the same event together. There are 30 of you trying to go to Glastonbury 2027? That's 30 Squad members.
Group (buying group)
The Squad's sale-day checkout team, sized for the maximum tickets per transaction. If the ticket seller allows 6 per purchase, a 30-person Squad plays best as 5 Groups of 6 - five real attempts at the queue instead of one. For known events, TicketSquad works the group size out for you from the seller's real limits.
Sale plan
One sale's arrangement on an event that runs more than one sale: its Groups, who's placed in which, its group admins, who's buying in that sale, and which sale date it's for. The squad, everyone's answers and their privacy choices are shared across every plan, and only the arrangement is per plan. The plan running the sale is marked Operating, one you're preparing alongside it is provisional, and one with no announced date is Date TBC. People sometimes call a plan a board too, which isn't the swap board on a transferable event and isn't a group's sale-day board either. Covered in Sale plans.
The handover between sales turns people who already have a ticket into helpers for the next sale, with Make ticket holders helpers. It's a different thing from the ticket hand-over on a transferable event, where a spare ticket passes from one member to another.
Named event vs transferable event
The two ticket modes - a question about the tickets, not the event:
- A named event sells tickets tied to a person's details at purchase (the Glastonbury model). Passing one on is usually impossible or costs a fee, so the flow is data-first and groups-first - see Named events.
- A transferable event sells tickets anyone can use: whoever holds it gets in. The centre of gravity is the swap board - see Transferable events.
Known event vs custom event
A known event is an entry in the TicketSquad catalogue. Linking your event to one prefills dates, venue, the per-transaction ticket limit, timezone, recommended data fields, and the right ticket mode from checked ticket rules. A known event can be either ticket mode - known is about the catalogue, named is about the tickets. Don't see yours? There's a "Request that we add it" button in event creation.
A custom event is one you build yourself, with full control over every detail.
Roles
Roles shape what you see and do in an event:
- Event owner - there's exactly one per event. Can transfer ownership, rename, archive, or delete the event. Owners are coordinators too.
- Coordinator - organises the Squad: edits event details, sale dates, imagery, invite links, group size and data fields; creates and renames Groups; sends reminders; generates the offline sale-day backup files, and rebuilds any that have gone missing; closes each sale when it's over and, on an event with sale plans, decides which sale runs next.
- Group admin - steers one Group on one plan: manages its roster (when the coordinator allows it), says who in it is buying or helping in that sale, and generates its offline sale-day backup file. A helper docked to a Group can be its admin as well.
- Member - coming along: submits their ticket-buyer details and sees their group's roster and readiness. On an event with sale plans, they can be in a Group on each sale.
- Helper - a participation state rather than a role, and on an event with sale plans it's per sale: somebody buying for others in that sale, who takes no buyer place in it. It says nothing about whether they're coming to the event. Somebody who joined because they're not attending is a helper on every sale, and somebody with a ticket becomes a helper once the handover or a late ticket moves them. Helpers sit on the "helper bench" until an organiser docks them to a Group, aren't counted in readiness or capacity, and can report a sale-day success for the group they're helping.
Communities have their own pair: a community owner (exactly one; can transfer ownership, change the privacy setting, archive) and community admins who help run the roster and settings.
Tiers
- Squad Solo - the free tier, forever. Join unlimited Squads and create one of your own - it counts as used once someone else joins it.
- Squad Crew - unlimited squads for coordinators running more than one, plus the events calendar and calendar sync.
- Squad Pro - adds the ability to create communities (joining is free on every tier, and an existing community keeps running whatever happens to the subscription).
- Hype Squad - a granted thank-you tier for people helping TicketSquad get good: every Squad Pro feature, free.
Open and Closed
The two privacy modes for events and communities - who can see members' personal details. Covered properly in Privacy.