Move your ticket-buying group from a spreadsheet to TicketSquad

You probably built the spreadsheet because it saved you once. It has the columns your group learned to trust: who is in, whose details are checked, which ticket type they want, who can buy, who has paid, who is camping, who is travelling with whom, and what happens if someone gets through.

Do not throw that work away. Bring across the columns that actually help, let each person check their own details, and stop being the only person who knows whether the plan is up to date.

Leave the group chat where it is. That is still where the jokes, panic and "who has the stove?" messages live. Drop your TicketSquad event invite link into the chat; everybody joins from there, and you can drag and drop people into buying groups, see who has filled in their fields, and chase the exact gaps before sale day.

Click New Event and start typing the event name. If TicketSquad recognises it, pick the known event and we can configure the useful basics for you: event dates, sale timing, venue context, per-buyer limit, artwork and the required data fields we know the event needs.

That is especially powerful for events with specific checkout details. If the event needs registration numbers and postcodes, or a particular buyer limit, those should not be rediscovered from last year's spreadsheet.

After creating the event, add a squad-specific Markdown description if people need context: payment plan, meeting point, "we are aiming for Wednesday coach packages", "Alice has the camping stove from last year", or "remind Rick to book his flights to the right airport this time". Then copy the TicketSquad invite link and paste it into the chat where the group already lives.

Think of your spreadsheet columns in two piles. The first pile is checkout-critical: legal name, registration number, postcode, email, phone number, ticket type, accessibility note, payment readiness, or anything the official route may require. Those should be required fields.

The second pile is group-life useful: arrival day, car space, tent share, camping kit, day-trip vote, afters plan, Clashfinder username, personal Clashfinder link, or "who is bringing breakfast stuff because last year was a nutritional incident". Those can be optional fields or pick-list polls.

You are not rebuilding the sheet cell by cell. You are taking the bits people still use and making them easier to keep current: members check their own details, and the organiser can see what is still missing at a glance.

The spreadsheet status column is the first thing to go stale on sale day. Someone gets through, buys three of six, posts in the chat, another person keeps trying for the wrong people, and the organiser starts editing cells while everyone is shouting.

In TicketSquad, build Groups around the seller limit and report what happened when a buyer succeeds or fails. The outcome is visible to the wider squad, so the next helper knows who still needs a ticket and who can finally stop being chased.

Keep checking the official seller route for the rules. TicketSquad organises the people around the sale; it does not replace the ticket site or create a shortcut.

A move from spreadsheet to TicketSquad is a good moment to leave stale private notes behind. Do not paste raw chat logs, private commentary, old screenshots, invite tokens, card details, account passwords or anything the squad does not need for the official sale.

The best setup feels boring in the right way: the people are there, the required details are there, the useful extras are there, the Groups make sense, and nobody needs to ask which tab is the real one.