Guides

Sale-day guide

Sale-day checklist for ticket-buying groups

A practical sale-day checklist for ticket-buying groups: official links, buyer accounts, required details, Groups, custom planning fields, backup plans, and what happens after a successful checkout.

Before the queue

Check the official route, account, device and payment basics while everyone is calm.

Start with the event or seller page that owns the sale. Confirm the link, account requirement, queue guidance, ticket type, payment method and buyer limit before the pressure starts.

Each buyer should know which account they are using, whether they need to be logged in early, whether two-factor codes might arrive, and whether the seller has any specific instructions about tabs, refreshes or waiting rooms. Ten minutes before the sale is a horrible time to discover a forgotten password, a dead laptop, or one heroic buyer still asleep.

Do not rely on an old screenshot or some half-remembered rule from last year. Ticket sites can change instructions, and the current official route wins.

  • Open the official event or seller page before the sale window.
  • Check every buyer can log in without needing a last-minute code rescue.
  • Agree who can pay, what they can buy, and where the order confirmation goes.

Required data

Make the boring fields impossible to miss, then add the human ones.

Some events need names only. Others need registration numbers, postcodes, membership IDs, dates of birth, travel choices, ticket tiers or accessibility details. A Glastonbury-style sale is the classic reminder: a tiny detail mismatch can matter when checkout time is short.

TicketSquad helps by keeping the group data in one place, and known events can add recommended fields automatically when we know what the sale needs. For custom events, add the fields yourself and make the checkout-critical ones required.

Once the serious fields are covered, add the planning fields that stop chat confusion: who is driving, who has the camping stove, who wants the day trip, who has a Clashfinder plan, who can stay online after a successful buy.

  • Required: anything a buyer may need at checkout.
  • Optional: travel, camping, meetups, kit, Clashfinder links and group preferences.
  • Never collect passwords, one-time codes or card details.

Buyer roles

Give every helper a clear Group, product target and fallback.

Before the queue opens, each buyer should know the people they are trying for, the details they may need, the official product choice, and what to do if their first option disappears.

For a festival, that might mean "try for this Group of six, Wednesday coach first, Thursday coach fallback, then general admission if coach sells out". For an arena run, it might mean "try Manchester first, then Birmingham, cap at this price".

The plan should be simple enough to follow while tired, excited, distracted, or staring at a checkout timer doing emotional damage.

After a win

Say who you got tickets for, then go again for someone else.

When one Group gets through, press "I got tickets" and tick who you got them for. Anyone you untick stays in the mix, so another Group can still buy for them - they only move to the resale round once the coordinator says the sale is over. Nobody then wastes time trying for people who are already sorted, and the running count at the top of the page shows how the morning is going without anyone asking in the chat.

You do not have to work out who to help next. Once your own group is covered, the next group that still needs help is lifted to the top of the sale-day page with their checkout details ready, and if they get there before you do, you are handed the next one on your list instead. Several groups can be buying for the same group at once, so nobody is turned away for being second.

TicketSquad is not a queue advantage. The value is calmer coordination around the official route.

Transferable-ticket crew instead? Your Tickets board keeps a live tally through the sale window: report what you got in one tap, then sort spares and needs once the dust settles.

Example: the sale-day page
Group 1 - Amy buying

Amy

Has ticket

Ben

Has ticket

Chloe

Has ticket

Omar

Has ticket

Priya

No ticket yet

Sam

No ticket yet

Backup plan: if Wednesday coach sells out, try Thursday coach before general admission.

Groups with tickets

2 of 4

Group 1 and Group 2 are covered.

Next group to help

Group 3

If you get through again, buy for Group 3.

Pressing "I got tickets" and ticking who for is the only thing a group reports. Everything else on this page follows from it.
Official routes only

Turn the method into a real squad plan.

TicketSquad helps with the coordination around the official ticket route: people, details, Groups, reminders and outcomes. Use TicketSquad to keep required details, Groups and outcomes visible before the official sale opens.