What's new
A practical changelog for coordinators, buyers, members, and squads deciding whether it is worth getting organised before the queue opens.
See how the app grew from event setup into readiness, sale-day boards, outcomes, and rich event context.
Follow the journey from invite links and data submission through confirmation, updates, privacy controls, and post-sale clarity.
The short version: TicketSquad continues to enhance its methodology for replacing checkout panic with calmer, more structured buying attempts.
Coming soon
A short public preview of what we expect to work on next, written as outcomes for squads rather than internal delivery notes.
Not every event is a Glastonbury-style registration sale. For gigs and club shows where tickets can change hands, a new mode will swap buying groups and the sale-day board for a simple distribution grid: say what you are holding, what is spare, and what you still need, then claim and confirm hand-overs within your crew.
The disabled autofill-profile button is a preview of a planned export that will let prepared buyers load member details into a browser autofill tool before sale day.
Latest product updates
These notes are distilled from our delivery history and rewritten for humans who care what the app can do for their squad.
Navigation
Browser tabs and history now name the page, event, or community you are viewing instead of all looking like the TicketSquad homepage.
Move between your dashboard, an event, its sale-day tools, or community settings and the browser tab now follows you. History entries are clearer too, so finding the right page again takes less guesswork.
Event knowledge
Whether tickets can be passed to a mate is one of the first things a group needs to know - and one of the easiest to get stung by. Your event's guide tab now says it plainly, with our confidence and the official sources behind it.
Events linked to our catalogue now show a "Passing tickets on" section: whether tickets are named or transferable, how a hand-over actually works (app transfer, name change and its fee, or a plain e-ticket forward), and the official pages we read to check it - complete with a confidence rating. Over 150 events researched so far, so a group of 20 finds out about a GBP 20-per-ticket name change before buying, not after.
Field privacy
Field privacy is now its own switch, separate from whether a field is required to buy: a coach pickup can be required AND visible to your organisers, while a registration number stays required and private.
Our whole event catalogue — over 400 events — now carries per-field privacy recommendations, painstakingly reviewed by our founder. Create a Glastonbury event and the registration number and postcode fields arrive protected while the coach pickup fields stay visible to your organisers, before you touch a single setting.
Until now, marking a field required in a closed event automatically kept it private — which protected registration numbers nicely, but also hid the coach pickup point from the organisers trying to group travellers. Those are different questions, so privacy is now its own setting. Every field in a closed event now has its own "Sensitive, personal or confidential" setting in the field editor, with capsules on each field row so you can see required, sensitive and type at a glance. Anything that was protected before stays protected.
When you switch an event to Closed, a new step lists every field and asks which ones should become private, with sensible suggestions pre-ticked. And if you ever make a sensitive field visible again, we ask you to confirm first — answers people gave privately are worth a second thought before the whole event can see them.
Pin & sort
Star an event to pin it to the top of your lists, and sort any list both ways with a second tap.
Every event card on your dashboard and on a community page now has a star. Tap it to pin that event to the top of the list, ahead of whatever sort you have chosen. Tap it again to unpin. Your pins are yours alone — nobody else in the squad sees them.
Tap a sort button a second time to flip the order, shown by a small arrow. It works on dashboard events, community events, your communities, and both member lists. Events without a date stay at the bottom either way, rather than jumping to the top when you reverse.
Event notifications
Known-event updates and coordinator description changes now have opt-in email notifications with per-event stop and snooze links.
When we groom important known-event changes such as sale dates, registration deadlines, resales, event-date changes, cancellations or lineup availability, admins can now notify members of linked TicketSquad events. If you are in more than one linked event, we group that into one email instead of sending duplicates.
These event-update emails are non-essential. Each one includes a link to stop or snooze future updates for that specific event, while Account still lets you pause all non-essential emails in one place.
Event coordinators now have an opt-in checkbox when saving the event description, so genuinely important squad notes can be emailed to eligible members without making every edit noisy.
Accounts
If TicketSquad learns that account emails are bouncing, the affected person now gets a dashboard and account prompt to update their address.
When an account email starts bouncing, TicketSquad now shows that person a clear prompt on Dashboard and Account so they can update the address themselves. Other members do not see the warning, and it disappears once the email is corrected or verified.
Privacy modes
New Open and Closed privacy modes for events and communities — keep your personal details inside your own buying group when you don’t know everyone, without losing the group-buying magic.
A lot of you asked the same question: “who can actually see my details?” TicketSquad works best for groups who know and trust each other — but some of you run big communities where you don’t know everyone, and you’d rather not hand your home address to a few hundred strangers months before a sale. So every event and community now has a privacy setting. Open is how it works today — everyone in the event sees everyone’s details, perfect for a group of mates. Closed keeps your personal details — address, postcode, phone, registration and email — visible only to the small buying group you’re actually in. Other groups can’t see them.
Closed mode never gets in the way of buying together: your own buying group still sees everything it needs to book each other’s tickets. And everyone — in any group — can still see who has filled in their details, so you can chase the one person who hasn’t the night before the sale. You just can’t see what other groups typed.
A community or event admin can see everyone’s email — so they can nudge people — and who’s ready, but not everyone’s home address and personal details. Being an admin doesn’t turn into a licence to browse everyone’s private info.
Flip an event or community to Closed and everyone’s details are hidden straight away. Going the other way — back to Open — asks each person to confirm first, because it’s their data to share.
The magic of buying-groups is helping each other get in. In a closed event, if your group lands its tickets and another group hasn’t, you’ll be matched to help them — you get just that group’s details, only during the sale, and it disappears again afterwards. You keep the “we all get in together” part without everyone seeing everyone all year round.
Lists
Busy dashboards, community pages and rosters now have search controls so long lists are easier to work through.
You can now search events by name or location on dashboard and community event lists, filter your communities by name, and find people faster in community rosters and event waiting rooms. Member rosters also get Role, Name and Joined sorting so bigger groups stay easier to scan.
Hype Squad
Hype Squad members now have a private brand kit with TicketSquad logos, Dash marks, hero videos and poster artwork gathered in one place.
Hype Squad members can now open Brand kit from the app nav to review and download TicketSquad marks, Dash mascot assets, landing-page videos and poster masters for social posts, merch ideas and community hype.
If you open the private Brand kit while signed out, signing in now brings you straight back to the kit instead of dropping you on Welcome.
Communities
Community owners can now archive events in their community, and we warn you before adding the same event twice.
If you own a community, you can now archive any event in it — handy for clearing out a duplicate someone added — even if you did not create it yourself. Archiving is reversible and nothing is deleted. (Community admins keep their own events; only the owner can tidy everyone’s.)
Adding an event that is already in your community now shows a gentle heads-up, so two copies of the same event do not appear by accident. It is only a warning — if you really do want a second one, just choose “Add anyway”. Adding the same event to a different community is unaffected.
Profile polish
The account profile form now explains where your display name appears, with the same allyship note we show during onboarding.
Editing your profile now shows the same display-name guidance as onboarding: where your name appears, why friends need to recognise it, and that pronouns are optional but appreciated.
New
TicketSquad’s event catalogue keeps growing — and now you can grow it too. If the event you’re organising around isn’t in our list, request it in a couple of taps.
Requested an event and carried on building your squad? The two now join up on their own. While we research and add it, your event shows an “official details pending our discovery” note — and the moment it’s in our catalogue, we link yours to it, unlocking dates, the guide and reviews with nothing more for you to do. Want to do it yourself, or link an older event? Open your event’s Settings and pick it from the new “Known event” list.
Creating an event and ours isn’t on the list? Tap “Request that we add it”, tell us the name (venue, dates and a link help too), and carry on setting up your squad — once the official event is in our catalogue we can link yours to it, unlocking dates, guides and reviews. The same goes for reviews: if the event you went to isn’t listed yet, ask for it right from the review picker. Every request is checked by a human before it goes live.
Communities refresh
Communities now look the part, your dashboard keeps everything you’re in one place, and you can look before you leap into a community event.
Your community’s invite link and its chat and playlist links — WhatsApp, Discord, Signal, Telegram and Spotify — now sit together in one clear card, each with its own icon and a line telling you where it goes. It’s the same clean layout as an event’s invite links, and the invite link itself reads more easily too.
Opened a community invite link, then got pulled away before joining? Your dashboard now remembers. If you looked at a community invite but didn’t finish joining, it shows up as a “Community invite” card so you can pick up right where you left off — one tap to join. It disappears the moment you join, or you can dismiss it.
Your communities went from a plain list to proper cards — cover art, a glimpse of who’s in, and what’s coming up. Thinking about a community event? Open it first to see the details, the venue, and who’s already going, then decide whether to join — no more committing blind. And you can tap anyone’s avatar, here and on the roster, to open their profile.
Your events page now brings your own events and the events across your communities together — grouped by community, collapsible, and sortable by sale date, event date, or name. Less hopping between screens to find what’s next.
Your communities now always show on your dashboard — even the ones you haven’t joined an event in yet. When there’s nothing on your list for one, we point you to browse what’s on, so it’s easier to find your next thing to do. And when you share a community invite link, it now gets a proper preview card in the chat.
Reviews launch
Festival and event reviews have arrived: editorial deep-dives from our team plus honest reviews from people who actually went — with verified-attendee badges, star ratings, and photos. Find them in the new Reviews section.
You can now see what an event was really like before you commit to the next sale. Our team writes editorial reviews of the big events, and anyone who went can add their own — with star ratings, practical intel (toilets, bar queues, getting in and out…), and photos. People we can confirm attended get a verified-attendee badge. Browse everything in the new Reviews section, or open any event guide to see its rating. And your privacy stays yours: if you delete your account, your reviews and photos are permanently removed with it.
A calmer screen
Our on-screen helper, Dash, has retired from following you around the app. The first squads told us the always-on character took up room and chimed in more than it helped — so the screen is quieter now, on mobile and desktop alike. Dash stays on as our logo and mascot.
Early squads told us our on-screen helper, Dash, took up room and chimed in more than it helped. So we have retired Dash as an always-on companion: the app is quieter and you get the screen space back, on mobile and desktop alike. Dash sticks around as our logo and mascot — just no longer following you around the page. Nothing about your events, squads, or data changes.
Squad Pro launch
Squad Pro is now available — and with it, Squad Communities: one umbrella across all the events your crew goes to, so members self-add to each new sale without a fresh invite link every time.
Squad Pro (£79/yr, or £7.99/mo) unlocks Squad Communities — create a community, bring your regular crew in once, and they self-add to every community event with no fresh invite link each time. Already on Squad Crew? Upgrade any time without losing a thing; First Hundred backers get a discount on their first Pro year.
Adopter feedback pass
The loudest feedback from our first adopters was about pricing. We listened, and the biggest change has followed: the people you bring along never pay, and joining squads is unlimited. This chapter collects the refinements that have come from real squads kicking the tyres.
Squad Crew, Squad Pro, and Hype Squad members now have a dedicated calendar for the future known-events catalogue. Browse upcoming festivals and gigs, filter by location and planning details, preview the data we already know, and start a squad from the event you choose.
We added four practical TicketSquad tutorials for organisers: how to use TicketSquad for your next event, how to move from a spreadsheet, what to check on sale day, and why we stay official-routes-only. They are written for real buying groups who want calmer planning before the official ticket route opens.
When a public TicketSquad guide is tied to a known event, its planning CTA can now take you straight into event setup with that event already selected. If you need to sign in first, we bring you back to the same setup path afterwards, so you can move from reading the guide to building the squad without searching for the event again.
The launch pieces are now in place for TicketSquad to move from early access into a real paid product. Squad stays free for members and casual organisers, Squad Crew unlocks the paid organiser tier, and the first hundred annual Crew subscribers get the early-supporter price while spaces remain. Existing early users are protected with Hype Squad status before the free-tier cap goes live, and the whole launch can be rolled back quickly with kill-switches if anything looks off.
When you send a reminder or a data-freshness prompt to your squad, we now show you up front who hasn’t confirmed their email address yet — because unconfirmed addresses won’t receive it. You can nudge anyone to verify in a single click right from that screen, and the member roster quietly flags unverified squadmates so coordinators always know who to chase. Fewer people slip through the cracks before sale day.
Finished with an event, or had one fall through? You can now archive it from the event’s settings. Archived events drop out of your active list to keep your dashboard tidy, and they stop sending sale-day reminders and notifications — but everything stays safe and readable, so you can look back anytime. Changed your mind? Unarchive it whenever you like and pick up right where you left off. If you’re coordinating someone else’s event and want to bow out, you can now step down to a regular member from that event’s settings too.
We added a public guide hub plus full Glastonbury, Coachella, Boomtown, Download, Tomorrowland, Roskilde, Reading, Isle of Wight, and Rock Werchter ticket guides, turning TicketSquad’s buying-group method into practical, searchable advice for squads preparing before they ever create an event.
You’re now in charge of your own account settings. Pause non-essential emails when your inbox needs a breather — we’ll still send the things that matter, like sale-day links and outcome updates. Manage which sign-in methods are linked to your account and unlink the ones you don’t use (we always keep at least one, so you’re never locked out). And if you ever want to leave, you can permanently delete your account and personal data yourself — no need to email anyone. If you’re running an event with other members, we hand it over to a fellow member so the group can carry on.
We tuned the red used for warnings, errors, and delete actions so it stays comfortably legible in both light and dark mode. In dark mode especially, a few error messages had been hard to read — now they are crisp wherever you are double-checking something that matters.
You can now create an account or sign in with Google. Your Google name is offered as a friendly suggestion at sign-up, but the display name your squad sees is always yours to choose. If you already have a TicketSquad account, signing in with Google using the same email links the two together — one account, two ways in, no duplicates. You can also link Google to an existing account anytime from your account settings.
If your event has an artist pre-sale, venue pre-sale, and general sale, you can add that schedule without turning setup into admin soup. Event pages now highlight the next sale still ahead of you, then switch to already-on-sale once the listed dates have passed. Custom event imagery is simpler too: one strong event artwork image, plus a lineup image if you have one.
We added a way to grant Hype Squad membership — our earliest-adopter recognition — via shareable invite links. Hype Squad members get the badge, an ad-free experience, and every Pro feature, as our thank-you for showing up early.
On phones, the top bar now keeps to the TicketSquad brand and a single menu button. Page links, account actions, and theme controls live in that menu, while the landing page gets a clearer Jump to control for moving between sections.
Member profiles now show each person’s TicketSquad membership and any badges they’ve earned — including the First Hundred badge for the earliest backers and the Hype Squad mark for friends-and-family supporters. Your membership travels with you across every event, and you can see your own tier on your account page too.
We added email verification so the people getting your squad’s invites are real — not typo’d addresses, not bots — without making signup any slower. New accounts get a one-click verify email; the rest of the app keeps working while you confirm. Coordinators see who hasn’t verified yet before sending out reminders or sale-day URLs, with a one-click nudge for any squadmate who needs a friendly chase.
The people you bring along should never have to think about pricing. Joining a squad and being part of someone else’s event is permanently free, with no per-seat fee and no cap on how many events you can be a member of. Paid plans are there for the power organisers among us — and one active event you organise yourself is always on the house.
TicketSquad now sits behind a proper observability stack — production error tracking, alerts on the failure modes that matter, and an internal view of activity across the platform. Mostly invisible to your squad, which is the point: the kinds of failures that should never reach a coordinator or a buyer get caught and fixed first.
Early adopter polish
The current polish pass makes the product easier to understand at a glance, more personal to your event, and more comfortable to use across phones, tablets, and desktop.
Event coordinators can now create a fresh TicketSquad invite link from the event page. The old link stops working, and anyone opening it gets a clearer nudge to ask for the latest invite.
Profile and event image cropping now gives larger source images more room, so faces, logos, and posters are easier to fit cleanly before saving.
People who create an account directly now get the same lightweight setup moment as invite joiners: they can set the name their squad will see, pick their preferred theme, or skip straight to the dashboard.
Dash now resyncs during page scroll as well as browser viewport changes, so the mobile bar stays tucked to the bottom of the visible screen even on long pages with the footer in view.
Dash now stays pinned more reliably at the bottom of the screen on iPhone Chrome when the browser controls hide and reappear while scrolling.
The known-event picker now covers more of the 2026 festival calendar, including Green Man, Truck, Tramlines, End of the Road, FORWARDS, WOMAD, LIDO, and BST Hyde Park. Coordinators get a better starting point for dates, ticket routes, venue details, and the questions their group should answer before buying.
Event pages now keep the story of the event up top, give groups more breathing room, and make invite links, member data, and sale-day actions easier to find. Shared invite links also get proper invite preview cards. Coordinators can collect richer answers such as dates, weekdays, URLs, ranges, and yes/no fields; open an all-groups sale-day snapshot; and let people stay in the squad as helpers when they are not attending.
Demo events now keep post-sale outcome actions in showcase mode, so curious visitors can explore the flow without changing the shared demo data. Deep app 404s also keep the mobile nav tidy instead of squeezing raw route crumbs into the header.
Coordinators can now add a Spotify playlist alongside chat links on an event. It gives each squad one more shared place to collect the soundtrack, hype tracks, and planning mood before ticket day.
Once your group has tickets, you can keep trying for groups that are still waiting. If you get through again, report a success for that pending group and confirm who is covered from there.
Members can now mark whether they already have a ticket from the event page, even if they created the event or skipped that choice during joining. Coordinators can also update an event sale date from settings, clear it back to the known-event default, or leave it TBC for custom events.
Coordinators can now add WhatsApp, Discord, Signal, and Telegram links to an event. The TicketSquad invite stays first, while extra chat links sit alongside it so members can find the right place to coordinate.
Invite, sign-in, sign-up, and create-event pages now do a better job of explaining TicketSquad while people are taking action. Event setup also pre-fills known sale dates, while still letting coordinators override them when they know better.
Visitors can now see how TicketSquad has grown, story by story, in product language. It makes recent polish, reliability work, and user-facing capabilities easier to understand before signing up or trying the demo.
Event detail pages now put the most useful member data closer to the invite and readiness context, while touch devices get cleaner group-management controls that avoid awkward drag-and-drop affordances on small screens.
TicketSquad can detect your timezone, let you override it in profile, and show important dates in the timezone that makes sense to you. This is especially helpful for squads spread across countries.
Event pages now show clearer countdowns for sale and event dates, including more urgent timing as the moment gets close. Everyone can see what is coming without doing timezone maths in the group chat.
Coordinators can export sale-day data as a spreadsheet, giving experienced buyers another familiar way to work. The board stays the main flow, but Excel is there for the squads who want a belt-and-braces backup.
Sale-day board notes now render links more reliably in the generated HTML. If your coordinator adds useful ticketing, queue, travel, or venue links, buyers can actually use them when the clock is ticking.
Profile and event images are easier to make look right before upload. Coordinators can frame event artwork properly, and members can avoid awkward centre-crops on avatars.
The public methodology page now shows the product flow with real app screenshots. People who are still deciding whether to try TicketSquad can see what the experience actually looks like before signing up.
Custom questions can now be fixed-option fields, which is perfect for choices like camping type, entry day, coach location, or ticket tier. Cleaner answers make sale-day boards and post-sale summaries much easier to scan.
Known events can now show more useful review content on the event page. For unfamiliar events, that gives you a quicker way to sense the venue, vibe, logistics, and lessons from previous years.
Coordinators can browse known events and see a richer preview before creating one. That means less typing, fewer setup mistakes, and more confidence that the right festival or show has been selected.
Dash now appears more consistently on mobile, tablet, and desktop surfaces, with small interactions where they help rather than distract. It gives the app a bit more companionship when people are working through sale prep.
Dash can now reflect the state of an event, from calm preparation through anticipation, readiness, worry, and celebration. The app feels less static and gives squads a warmer read on what is happening.
Dark mode picked up a deeper club and disco feel, with better contrast and more character. It keeps late-night planning sessions readable while giving the app a clearer identity.
Light mode now feels much more like the world TicketSquad serves: open-air, event-first, and upbeat. It gives you a stronger sense that this was built for real ticket-buying squads, not generic project management.
We gave the app a cleaner visual foundation so new ideas can land faster and the whole experience can keep improving without feeling patched together.
Outcome tracking
Outcome tracking turns the messy aftermath of a high-demand sale into a shared source of truth: who got through, who is covered, and who still needs a plan.
Coordinators get a high-level outcome view for the whole event, pulling together group results and the members still waiting for tickets. It is the post-sale command centre for deciding what happens next.
Coordinators can see who still needs help after the main sale. That makes resale planning and second-wave coordination far easier than scrolling through days of messages.
Successful groups get a proper celebration moment, and members receive clearer updates about what happened. It brings a bit of joy to the win while keeping the admin side tidy.
Buyers can confirm which members were covered, including partial wins. That keeps everyone honest and avoids the classic group-chat confusion of "wait, am I actually sorted?"
Any member of a buying group can report whether they got through. That gives your group a clear buyer when there is a success, and gives the wider event a reliable post-sale signal.
Demo readiness
This chapter made TicketSquad easier to understand before login, richer during event setup, and more credible in demos with real event context and better profile surfaces.
TicketSquad gained a proper public landing surface that explains the problem, shows the method, and gives curious squads a reason to try the demo or start their first event.
A focused polish pass tightened the rough edges that could distract first-time visitors, making the app feel more deliberate before broader early-adopter exposure.
Reusable motion and illustration primitives gave the app a smoother, more expressive feel without rebuilding one-off visuals every time.
The app adopted a clearer design direction so future UI work had a shared target. The result was less visual drift and a more coherent first impression.
Profile details now respect role and relationship rules, so helpful identity appears where it belongs without turning private member data into decoration.
Members can have a clearer profile identity, including display names and avatars. That helps squads feel more human and makes rosters easier to scan.
Known-event pages can show venue facts, entry requirements, sale timelines, ticket types, lineup details, and review videos. The event page became a useful planning hub, not just a settings screen.
Popular events moved from a simple helper list into a richer event knowledge layer. That opened the door to venue details, ticketing notes, images, AI-assisted grooming from reputable sources, and future event intelligence.
Demo data became much more realistic, with portfolio-ready events and people that show how the app behaves when a squad is actually in motion.
Roles and ownership
Ticket-buying groups have more nuance than one admin and everyone else. This work made roles safer, clearer, and much more flexible.
Demo examples and automated journey checks were brought into line with the richer role model, so the product is tested against the way people actually organise.
Events can have multiple coordinators, with ownership transferable when someone else needs to take the lead. It is a better fit for long-running or high-stakes events.
Groups can support a more realistic admin model, so responsibility does not have to sit with a single person when a squad needs help organising itself.
Event creators are now properly represented as participants, which keeps rosters, group counts, and ownership behaviour aligned with how real squads work.
Permission checks moved into a clearer shared layer, making sensitive actions easier to reason about and harder to accidentally expose.
The underlying participant model was reshaped so someone can be a member, coordinator, owner, or group admin without those ideas fighting each other.
Sale-day tools
This is the core TicketSquad promise: when the queue opens, buyers should already have the right people, the right details, and a fast view that does not depend on everyone clicking around the app.
Members can receive reminders before the sale and sale-day links when it matters. Delivery is designed to avoid duplicate sends and keep sensitive data out of logs.
The app introduced a clear coming-soon path for autofill export, so power users can see where the workflow is heading without us overpromising before it is ready.
Buyers get a dedicated sale-day board with the details they need to buy for their group. It is built for quick scanning, copying, and staying calm under pressure.
TicketSquad can pre-generate sale-day data snapshots before the big moment. That means the most important screen is designed to be fast and resilient when everyone is trying to buy at once.
The app gained deterministic fixture data so sale-day flows could be tested and demonstrated with realistic groups instead of fragile one-off setup.
Squad management
Coordinators got the visibility and controls needed to move from "I hope everyone is ready" to "I can see exactly what still needs doing."
Coordinators can prompt members who still need to submit details. It is a practical nudge system for the people who always mean to do it later.
Trusted members can help manage their own buying group, reducing the bottleneck on the main coordinator.
Coordinators can form buying groups and assign responsibility, turning a loose crowd into practical sale-day teams.
Coordinators can see every member, their group, and whether their required details are complete. It replaces the spreadsheet-style audit with something built into the event.
Event pages gained a readiness banner and high-level status view, so coordinators can spot missing details before they become sale-day problems.
Member joining
The member experience moved from invite link to confirmation, including privacy-conscious data collection, group choice, updates, and returning-member convenience.
People who come back for another event get a smoother path, with prior context reused where it helps. Repeat squads should feel easier every time.
Members can update submitted details and opt out where needed. That keeps the group data accurate while giving people control over their participation.
After joining, members get a clear confirmation and next-step summary. No more wondering whether the form worked or what happens next.
Members can choose an available buying group and see capacity before joining. It reduces coordinator admin and helps friends cluster together naturally.
Members can submit the event-specific details their coordinator needs, with privacy consent captured as part of the flow.
Invite links now explain the event before asking people to continue. Members can understand what they are joining and why their details are needed.
Event setup
The earliest product loop gave coordinators enough structure to create an event, define the details they need, invite people, and manage basic access.
TicketSquad can suggest known events while a coordinator types, making setup faster for popular festivals and shows.
Coordinators can manage admin access without handing over the whole event. It is a safer way to share responsibility.
Events get shareable invite links, making it easy to move a squad from group chat into a structured flow.
Coordinators can set the maximum buying group size so the plan matches the rules of the ticket sale.
Every event can ask for the details it actually needs, from registration numbers to postcodes or other purchase requirements.
Coordinators can create a new event with the core details needed to start organising a ticket-buying squad.
Foundations
Before the visible workflows, the app needed account access, a secure data model, dashboard shell, testing, deployment, and a basic brand system.
TicketSquad got its first real visual identity, setting the brand and tone for a product that should feel useful, honest, and made for real ticket sales.
Automated checks, simulated user journeys, smoke tests, and performance-minded testing arrived early, helping the app stay dependable as more workflows were added.
Once you sign in, the dashboard gives you a stable place to see your events and move into the main app experience.
You can create an account and sign in, giving coordinators and returning members a stable home for their events.
The core event, member, group, invite, and sale-day data model was designed around security and privacy from the start, so sensitive coordination details only appear where they belong.
TicketSquad started with a modern, scalable product foundation, wired for fast iteration and automated checks from day one. The goal was simple: move quickly without becoming fragile.
Trust and reliability
Alongside feature stories, we shipped targeted hardening around privacy, security, production reliability, previews, mobile testing, and diagnostics.
The public landing page now behaves more cleanly on iPhone-sized screens, dashboard event cards stay inside the viewport, and image crop actions remain reachable when editing photos.
Production analytics were added in a privacy-friendly way so we can learn which pages help people without turning the app into a surveillance machine.
Our end-to-end testing became faster and more diagnostic, with stronger simulated user journeys, transaction checks, smoke coverage, and failure traces. That means safer future releases for the product your squad depends on.
We tuned and hardened database connection behaviour so the app stays more resilient under real-world traffic spikes.
Success timing logs were added around timeout-protected work, making future reliability tuning easier without exposing sensitive member details.
Several slow-loading event views gained safer time bounds and graceful fallbacks. Visitors should see useful page content instead of waiting indefinitely on one slow section.
Event cover uploads became more resilient, so large or repeated uploads are less likely to leave you stuck halfway through making an event look right.
Login redirects were tightened so people are sent only where the app expects. It is a small security detail that matters for user trust.
TicketSquad is built around the way real squads already try to get tickets: more prepared attempts, cleaner handoffs, better visibility, and fewer last-minute surprises. Join free.
What's new
A practical changelog for coordinators, buyers, members, and squads deciding whether it is worth getting organised before the queue opens.
See how the app grew from event setup into readiness, sale-day boards, outcomes, and rich event context.
Follow the journey from invite links and data submission through confirmation, updates, privacy controls, and post-sale clarity.
The short version: TicketSquad continues to enhance its methodology for replacing checkout panic with calmer, more structured buying attempts.
Coming soon
A short public preview of what we expect to work on next, written as outcomes for squads rather than internal delivery notes.
Not every event is a Glastonbury-style registration sale. For gigs and club shows where tickets can change hands, a new mode will swap buying groups and the sale-day board for a simple distribution grid: say what you are holding, what is spare, and what you still need, then claim and confirm hand-overs within your crew.
The disabled autofill-profile button is a preview of a planned export that will let prepared buyers load member details into a browser autofill tool before sale day.
Latest product updates
These notes are distilled from our delivery history and rewritten for humans who care what the app can do for their squad.
TicketSquad is built around the way real squads already try to get tickets: more prepared attempts, cleaner handoffs, better visibility, and fewer last-minute surprises. Join free.
Navigation
Browser tabs and history now name the page, event, or community you are viewing instead of all looking like the TicketSquad homepage.
Move between your dashboard, an event, its sale-day tools, or community settings and the browser tab now follows you. History entries are clearer too, so finding the right page again takes less guesswork.
Event knowledge
Whether tickets can be passed to a mate is one of the first things a group needs to know - and one of the easiest to get stung by. Your event's guide tab now says it plainly, with our confidence and the official sources behind it.
Events linked to our catalogue now show a "Passing tickets on" section: whether tickets are named or transferable, how a hand-over actually works (app transfer, name change and its fee, or a plain e-ticket forward), and the official pages we read to check it - complete with a confidence rating. Over 150 events researched so far, so a group of 20 finds out about a GBP 20-per-ticket name change before buying, not after.
Field privacy
Field privacy is now its own switch, separate from whether a field is required to buy: a coach pickup can be required AND visible to your organisers, while a registration number stays required and private.
Our whole event catalogue — over 400 events — now carries per-field privacy recommendations, painstakingly reviewed by our founder. Create a Glastonbury event and the registration number and postcode fields arrive protected while the coach pickup fields stay visible to your organisers, before you touch a single setting.
Until now, marking a field required in a closed event automatically kept it private — which protected registration numbers nicely, but also hid the coach pickup point from the organisers trying to group travellers. Those are different questions, so privacy is now its own setting. Every field in a closed event now has its own "Sensitive, personal or confidential" setting in the field editor, with capsules on each field row so you can see required, sensitive and type at a glance. Anything that was protected before stays protected.
Pin & sort
Star an event to pin it to the top of your lists, and sort any list both ways with a second tap.
Every event card on your dashboard and on a community page now has a star. Tap it to pin that event to the top of the list, ahead of whatever sort you have chosen. Tap it again to unpin. Your pins are yours alone — nobody else in the squad sees them.
Tap a sort button a second time to flip the order, shown by a small arrow. It works on dashboard events, community events, your communities, and both member lists. Events without a date stay at the bottom either way, rather than jumping to the top when you reverse.
Event notifications
Known-event updates and coordinator description changes now have opt-in email notifications with per-event stop and snooze links.
When we groom important known-event changes such as sale dates, registration deadlines, resales, event-date changes, cancellations or lineup availability, admins can now notify members of linked TicketSquad events. If you are in more than one linked event, we group that into one email instead of sending duplicates.
These event-update emails are non-essential. Each one includes a link to stop or snooze future updates for that specific event, while Account still lets you pause all non-essential emails in one place.
Accounts
If TicketSquad learns that account emails are bouncing, the affected person now gets a dashboard and account prompt to update their address.
When an account email starts bouncing, TicketSquad now shows that person a clear prompt on Dashboard and Account so they can update the address themselves. Other members do not see the warning, and it disappears once the email is corrected or verified.
Privacy modes
New Open and Closed privacy modes for events and communities — keep your personal details inside your own buying group when you don’t know everyone, without losing the group-buying magic.
A lot of you asked the same question: “who can actually see my details?” TicketSquad works best for groups who know and trust each other — but some of you run big communities where you don’t know everyone, and you’d rather not hand your home address to a few hundred strangers months before a sale. So every event and community now has a privacy setting. Open is how it works today — everyone in the event sees everyone’s details, perfect for a group of mates. Closed keeps your personal details — address, postcode, phone, registration and email — visible only to the small buying group you’re actually in. Other groups can’t see them.
Lists
Busy dashboards, community pages and rosters now have search controls so long lists are easier to work through.
You can now search events by name or location on dashboard and community event lists, filter your communities by name, and find people faster in community rosters and event waiting rooms. Member rosters also get Role, Name and Joined sorting so bigger groups stay easier to scan.
Hype Squad
Hype Squad members now have a private brand kit with TicketSquad logos, Dash marks, hero videos and poster artwork gathered in one place.
Hype Squad members can now open Brand kit from the app nav to review and download TicketSquad marks, Dash mascot assets, landing-page videos and poster masters for social posts, merch ideas and community hype.
If you open the private Brand kit while signed out, signing in now brings you straight back to the kit instead of dropping you on Welcome.
Communities
Community owners can now archive events in their community, and we warn you before adding the same event twice.
If you own a community, you can now archive any event in it — handy for clearing out a duplicate someone added — even if you did not create it yourself. Archiving is reversible and nothing is deleted. (Community admins keep their own events; only the owner can tidy everyone’s.)
Adding an event that is already in your community now shows a gentle heads-up, so two copies of the same event do not appear by accident. It is only a warning — if you really do want a second one, just choose “Add anyway”. Adding the same event to a different community is unaffected.
Profile polish
The account profile form now explains where your display name appears, with the same allyship note we show during onboarding.
Editing your profile now shows the same display-name guidance as onboarding: where your name appears, why friends need to recognise it, and that pronouns are optional but appreciated.
New
TicketSquad’s event catalogue keeps growing — and now you can grow it too. If the event you’re organising around isn’t in our list, request it in a couple of taps.
Requested an event and carried on building your squad? The two now join up on their own. While we research and add it, your event shows an “official details pending our discovery” note — and the moment it’s in our catalogue, we link yours to it, unlocking dates, the guide and reviews with nothing more for you to do. Want to do it yourself, or link an older event? Open your event’s Settings and pick it from the new “Known event” list.
Creating an event and ours isn’t on the list? Tap “Request that we add it”, tell us the name (venue, dates and a link help too), and carry on setting up your squad — once the official event is in our catalogue we can link yours to it, unlocking dates, guides and reviews. The same goes for reviews: if the event you went to isn’t listed yet, ask for it right from the review picker. Every request is checked by a human before it goes live.
Communities refresh
Communities now look the part, your dashboard keeps everything you’re in one place, and you can look before you leap into a community event.
Your community’s invite link and its chat and playlist links — WhatsApp, Discord, Signal, Telegram and Spotify — now sit together in one clear card, each with its own icon and a line telling you where it goes. It’s the same clean layout as an event’s invite links, and the invite link itself reads more easily too.
Opened a community invite link, then got pulled away before joining? Your dashboard now remembers. If you looked at a community invite but didn’t finish joining, it shows up as a “Community invite” card so you can pick up right where you left off — one tap to join. It disappears the moment you join, or you can dismiss it.
Reviews launch
Festival and event reviews have arrived: editorial deep-dives from our team plus honest reviews from people who actually went — with verified-attendee badges, star ratings, and photos. Find them in the new Reviews section.
You can now see what an event was really like before you commit to the next sale. Our team writes editorial reviews of the big events, and anyone who went can add their own — with star ratings, practical intel (toilets, bar queues, getting in and out…), and photos. People we can confirm attended get a verified-attendee badge. Browse everything in the new Reviews section, or open any event guide to see its rating. And your privacy stays yours: if you delete your account, your reviews and photos are permanently removed with it.
A calmer screen
Our on-screen helper, Dash, has retired from following you around the app. The first squads told us the always-on character took up room and chimed in more than it helped — so the screen is quieter now, on mobile and desktop alike. Dash stays on as our logo and mascot.
Early squads told us our on-screen helper, Dash, took up room and chimed in more than it helped. So we have retired Dash as an always-on companion: the app is quieter and you get the screen space back, on mobile and desktop alike. Dash sticks around as our logo and mascot — just no longer following you around the page. Nothing about your events, squads, or data changes.
Squad Pro launch
Squad Pro is now available — and with it, Squad Communities: one umbrella across all the events your crew goes to, so members self-add to each new sale without a fresh invite link every time.
Squad Pro (£79/yr, or £7.99/mo) unlocks Squad Communities — create a community, bring your regular crew in once, and they self-add to every community event with no fresh invite link each time. Already on Squad Crew? Upgrade any time without losing a thing; First Hundred backers get a discount on their first Pro year.
Adopter feedback pass
The loudest feedback from our first adopters was about pricing. We listened, and the biggest change has followed: the people you bring along never pay, and joining squads is unlimited. This chapter collects the refinements that have come from real squads kicking the tyres.
Squad Crew, Squad Pro, and Hype Squad members now have a dedicated calendar for the future known-events catalogue. Browse upcoming festivals and gigs, filter by location and planning details, preview the data we already know, and start a squad from the event you choose.
Early adopter polish
The current polish pass makes the product easier to understand at a glance, more personal to your event, and more comfortable to use across phones, tablets, and desktop.
Event coordinators can now create a fresh TicketSquad invite link from the event page. The old link stops working, and anyone opening it gets a clearer nudge to ask for the latest invite.
Profile and event image cropping now gives larger source images more room, so faces, logos, and posters are easier to fit cleanly before saving.
Outcome tracking
Outcome tracking turns the messy aftermath of a high-demand sale into a shared source of truth: who got through, who is covered, and who still needs a plan.
Coordinators get a high-level outcome view for the whole event, pulling together group results and the members still waiting for tickets. It is the post-sale command centre for deciding what happens next.
Coordinators can see who still needs help after the main sale. That makes resale planning and second-wave coordination far easier than scrolling through days of messages.
Demo readiness
This chapter made TicketSquad easier to understand before login, richer during event setup, and more credible in demos with real event context and better profile surfaces.
TicketSquad gained a proper public landing surface that explains the problem, shows the method, and gives curious squads a reason to try the demo or start their first event.
A focused polish pass tightened the rough edges that could distract first-time visitors, making the app feel more deliberate before broader early-adopter exposure.
Roles and ownership
Ticket-buying groups have more nuance than one admin and everyone else. This work made roles safer, clearer, and much more flexible.
Demo examples and automated journey checks were brought into line with the richer role model, so the product is tested against the way people actually organise.
Events can have multiple coordinators, with ownership transferable when someone else needs to take the lead. It is a better fit for long-running or high-stakes events.
Sale-day tools
This is the core TicketSquad promise: when the queue opens, buyers should already have the right people, the right details, and a fast view that does not depend on everyone clicking around the app.
Members can receive reminders before the sale and sale-day links when it matters. Delivery is designed to avoid duplicate sends and keep sensitive data out of logs.
The app introduced a clear coming-soon path for autofill export, so power users can see where the workflow is heading without us overpromising before it is ready.
Squad management
Coordinators got the visibility and controls needed to move from "I hope everyone is ready" to "I can see exactly what still needs doing."
Coordinators can prompt members who still need to submit details. It is a practical nudge system for the people who always mean to do it later.
Trusted members can help manage their own buying group, reducing the bottleneck on the main coordinator.
Member joining
The member experience moved from invite link to confirmation, including privacy-conscious data collection, group choice, updates, and returning-member convenience.
People who come back for another event get a smoother path, with prior context reused where it helps. Repeat squads should feel easier every time.
Members can update submitted details and opt out where needed. That keeps the group data accurate while giving people control over their participation.
Event setup
The earliest product loop gave coordinators enough structure to create an event, define the details they need, invite people, and manage basic access.
TicketSquad can suggest known events while a coordinator types, making setup faster for popular festivals and shows.
Coordinators can manage admin access without handing over the whole event. It is a safer way to share responsibility.
Foundations
Before the visible workflows, the app needed account access, a secure data model, dashboard shell, testing, deployment, and a basic brand system.
TicketSquad got its first real visual identity, setting the brand and tone for a product that should feel useful, honest, and made for real ticket sales.
Automated checks, simulated user journeys, smoke tests, and performance-minded testing arrived early, helping the app stay dependable as more workflows were added.
Trust and reliability
Alongside feature stories, we shipped targeted hardening around privacy, security, production reliability, previews, mobile testing, and diagnostics.
The public landing page now behaves more cleanly on iPhone-sized screens, dashboard event cards stay inside the viewport, and image crop actions remain reachable when editing photos.
Production analytics were added in a privacy-friendly way so we can learn which pages help people without turning the app into a surveillance machine.
When you switch an event to Closed, a new step lists every field and asks which ones should become private, with sensible suggestions pre-ticked. And if you ever make a sensitive field visible again, we ask you to confirm first — answers people gave privately are worth a second thought before the whole event can see them.
Event coordinators now have an opt-in checkbox when saving the event description, so genuinely important squad notes can be emailed to eligible members without making every edit noisy.
Closed mode never gets in the way of buying together: your own buying group still sees everything it needs to book each other’s tickets. And everyone — in any group — can still see who has filled in their details, so you can chase the one person who hasn’t the night before the sale. You just can’t see what other groups typed.
A community or event admin can see everyone’s email — so they can nudge people — and who’s ready, but not everyone’s home address and personal details. Being an admin doesn’t turn into a licence to browse everyone’s private info.
Flip an event or community to Closed and everyone’s details are hidden straight away. Going the other way — back to Open — asks each person to confirm first, because it’s their data to share.
The magic of buying-groups is helping each other get in. In a closed event, if your group lands its tickets and another group hasn’t, you’ll be matched to help them — you get just that group’s details, only during the sale, and it disappears again afterwards. You keep the “we all get in together” part without everyone seeing everyone all year round.
Your communities went from a plain list to proper cards — cover art, a glimpse of who’s in, and what’s coming up. Thinking about a community event? Open it first to see the details, the venue, and who’s already going, then decide whether to join — no more committing blind. And you can tap anyone’s avatar, here and on the roster, to open their profile.
Your events page now brings your own events and the events across your communities together — grouped by community, collapsible, and sortable by sale date, event date, or name. Less hopping between screens to find what’s next.
Your communities now always show on your dashboard — even the ones you haven’t joined an event in yet. When there’s nothing on your list for one, we point you to browse what’s on, so it’s easier to find your next thing to do. And when you share a community invite link, it now gets a proper preview card in the chat.
We added four practical TicketSquad tutorials for organisers: how to use TicketSquad for your next event, how to move from a spreadsheet, what to check on sale day, and why we stay official-routes-only. They are written for real buying groups who want calmer planning before the official ticket route opens.
When a public TicketSquad guide is tied to a known event, its planning CTA can now take you straight into event setup with that event already selected. If you need to sign in first, we bring you back to the same setup path afterwards, so you can move from reading the guide to building the squad without searching for the event again.
The launch pieces are now in place for TicketSquad to move from early access into a real paid product. Squad stays free for members and casual organisers, Squad Crew unlocks the paid organiser tier, and the first hundred annual Crew subscribers get the early-supporter price while spaces remain. Existing early users are protected with Hype Squad status before the free-tier cap goes live, and the whole launch can be rolled back quickly with kill-switches if anything looks off.
When you send a reminder or a data-freshness prompt to your squad, we now show you up front who hasn’t confirmed their email address yet — because unconfirmed addresses won’t receive it. You can nudge anyone to verify in a single click right from that screen, and the member roster quietly flags unverified squadmates so coordinators always know who to chase. Fewer people slip through the cracks before sale day.
Finished with an event, or had one fall through? You can now archive it from the event’s settings. Archived events drop out of your active list to keep your dashboard tidy, and they stop sending sale-day reminders and notifications — but everything stays safe and readable, so you can look back anytime. Changed your mind? Unarchive it whenever you like and pick up right where you left off. If you’re coordinating someone else’s event and want to bow out, you can now step down to a regular member from that event’s settings too.
We added a public guide hub plus full Glastonbury, Coachella, Boomtown, Download, Tomorrowland, Roskilde, Reading, Isle of Wight, and Rock Werchter ticket guides, turning TicketSquad’s buying-group method into practical, searchable advice for squads preparing before they ever create an event.
You’re now in charge of your own account settings. Pause non-essential emails when your inbox needs a breather — we’ll still send the things that matter, like sale-day links and outcome updates. Manage which sign-in methods are linked to your account and unlink the ones you don’t use (we always keep at least one, so you’re never locked out). And if you ever want to leave, you can permanently delete your account and personal data yourself — no need to email anyone. If you’re running an event with other members, we hand it over to a fellow member so the group can carry on.
We tuned the red used for warnings, errors, and delete actions so it stays comfortably legible in both light and dark mode. In dark mode especially, a few error messages had been hard to read — now they are crisp wherever you are double-checking something that matters.
You can now create an account or sign in with Google. Your Google name is offered as a friendly suggestion at sign-up, but the display name your squad sees is always yours to choose. If you already have a TicketSquad account, signing in with Google using the same email links the two together — one account, two ways in, no duplicates. You can also link Google to an existing account anytime from your account settings.
If your event has an artist pre-sale, venue pre-sale, and general sale, you can add that schedule without turning setup into admin soup. Event pages now highlight the next sale still ahead of you, then switch to already-on-sale once the listed dates have passed. Custom event imagery is simpler too: one strong event artwork image, plus a lineup image if you have one.
We added a way to grant Hype Squad membership — our earliest-adopter recognition — via shareable invite links. Hype Squad members get the badge, an ad-free experience, and every Pro feature, as our thank-you for showing up early.
On phones, the top bar now keeps to the TicketSquad brand and a single menu button. Page links, account actions, and theme controls live in that menu, while the landing page gets a clearer Jump to control for moving between sections.
Member profiles now show each person’s TicketSquad membership and any badges they’ve earned — including the First Hundred badge for the earliest backers and the Hype Squad mark for friends-and-family supporters. Your membership travels with you across every event, and you can see your own tier on your account page too.
We added email verification so the people getting your squad’s invites are real — not typo’d addresses, not bots — without making signup any slower. New accounts get a one-click verify email; the rest of the app keeps working while you confirm. Coordinators see who hasn’t verified yet before sending out reminders or sale-day URLs, with a one-click nudge for any squadmate who needs a friendly chase.
The people you bring along should never have to think about pricing. Joining a squad and being part of someone else’s event is permanently free, with no per-seat fee and no cap on how many events you can be a member of. Paid plans are there for the power organisers among us — and one active event you organise yourself is always on the house.
TicketSquad now sits behind a proper observability stack — production error tracking, alerts on the failure modes that matter, and an internal view of activity across the platform. Mostly invisible to your squad, which is the point: the kinds of failures that should never reach a coordinator or a buyer get caught and fixed first.
People who create an account directly now get the same lightweight setup moment as invite joiners: they can set the name their squad will see, pick their preferred theme, or skip straight to the dashboard.
Dash now resyncs during page scroll as well as browser viewport changes, so the mobile bar stays tucked to the bottom of the visible screen even on long pages with the footer in view.
Dash now stays pinned more reliably at the bottom of the screen on iPhone Chrome when the browser controls hide and reappear while scrolling.
The known-event picker now covers more of the 2026 festival calendar, including Green Man, Truck, Tramlines, End of the Road, FORWARDS, WOMAD, LIDO, and BST Hyde Park. Coordinators get a better starting point for dates, ticket routes, venue details, and the questions their group should answer before buying.
Event pages now keep the story of the event up top, give groups more breathing room, and make invite links, member data, and sale-day actions easier to find. Shared invite links also get proper invite preview cards. Coordinators can collect richer answers such as dates, weekdays, URLs, ranges, and yes/no fields; open an all-groups sale-day snapshot; and let people stay in the squad as helpers when they are not attending.
Demo events now keep post-sale outcome actions in showcase mode, so curious visitors can explore the flow without changing the shared demo data. Deep app 404s also keep the mobile nav tidy instead of squeezing raw route crumbs into the header.
Coordinators can now add a Spotify playlist alongside chat links on an event. It gives each squad one more shared place to collect the soundtrack, hype tracks, and planning mood before ticket day.
Once your group has tickets, you can keep trying for groups that are still waiting. If you get through again, report a success for that pending group and confirm who is covered from there.
Members can now mark whether they already have a ticket from the event page, even if they created the event or skipped that choice during joining. Coordinators can also update an event sale date from settings, clear it back to the known-event default, or leave it TBC for custom events.
Coordinators can now add WhatsApp, Discord, Signal, and Telegram links to an event. The TicketSquad invite stays first, while extra chat links sit alongside it so members can find the right place to coordinate.
Invite, sign-in, sign-up, and create-event pages now do a better job of explaining TicketSquad while people are taking action. Event setup also pre-fills known sale dates, while still letting coordinators override them when they know better.
Visitors can now see how TicketSquad has grown, story by story, in product language. It makes recent polish, reliability work, and user-facing capabilities easier to understand before signing up or trying the demo.
Event detail pages now put the most useful member data closer to the invite and readiness context, while touch devices get cleaner group-management controls that avoid awkward drag-and-drop affordances on small screens.
TicketSquad can detect your timezone, let you override it in profile, and show important dates in the timezone that makes sense to you. This is especially helpful for squads spread across countries.
Event pages now show clearer countdowns for sale and event dates, including more urgent timing as the moment gets close. Everyone can see what is coming without doing timezone maths in the group chat.
Coordinators can export sale-day data as a spreadsheet, giving experienced buyers another familiar way to work. The board stays the main flow, but Excel is there for the squads who want a belt-and-braces backup.
Sale-day board notes now render links more reliably in the generated HTML. If your coordinator adds useful ticketing, queue, travel, or venue links, buyers can actually use them when the clock is ticking.
Profile and event images are easier to make look right before upload. Coordinators can frame event artwork properly, and members can avoid awkward centre-crops on avatars.
The public methodology page now shows the product flow with real app screenshots. People who are still deciding whether to try TicketSquad can see what the experience actually looks like before signing up.
Custom questions can now be fixed-option fields, which is perfect for choices like camping type, entry day, coach location, or ticket tier. Cleaner answers make sale-day boards and post-sale summaries much easier to scan.
Known events can now show more useful review content on the event page. For unfamiliar events, that gives you a quicker way to sense the venue, vibe, logistics, and lessons from previous years.
Coordinators can browse known events and see a richer preview before creating one. That means less typing, fewer setup mistakes, and more confidence that the right festival or show has been selected.
Dash now appears more consistently on mobile, tablet, and desktop surfaces, with small interactions where they help rather than distract. It gives the app a bit more companionship when people are working through sale prep.
Dash can now reflect the state of an event, from calm preparation through anticipation, readiness, worry, and celebration. The app feels less static and gives squads a warmer read on what is happening.
Dark mode picked up a deeper club and disco feel, with better contrast and more character. It keeps late-night planning sessions readable while giving the app a clearer identity.
Light mode now feels much more like the world TicketSquad serves: open-air, event-first, and upbeat. It gives you a stronger sense that this was built for real ticket-buying squads, not generic project management.
We gave the app a cleaner visual foundation so new ideas can land faster and the whole experience can keep improving without feeling patched together.
Successful groups get a proper celebration moment, and members receive clearer updates about what happened. It brings a bit of joy to the win while keeping the admin side tidy.
Buyers can confirm which members were covered, including partial wins. That keeps everyone honest and avoids the classic group-chat confusion of "wait, am I actually sorted?"
Any member of a buying group can report whether they got through. That gives your group a clear buyer when there is a success, and gives the wider event a reliable post-sale signal.
Reusable motion and illustration primitives gave the app a smoother, more expressive feel without rebuilding one-off visuals every time.
The app adopted a clearer design direction so future UI work had a shared target. The result was less visual drift and a more coherent first impression.
Profile details now respect role and relationship rules, so helpful identity appears where it belongs without turning private member data into decoration.
Members can have a clearer profile identity, including display names and avatars. That helps squads feel more human and makes rosters easier to scan.
Known-event pages can show venue facts, entry requirements, sale timelines, ticket types, lineup details, and review videos. The event page became a useful planning hub, not just a settings screen.
Popular events moved from a simple helper list into a richer event knowledge layer. That opened the door to venue details, ticketing notes, images, AI-assisted grooming from reputable sources, and future event intelligence.
Demo data became much more realistic, with portfolio-ready events and people that show how the app behaves when a squad is actually in motion.
Groups can support a more realistic admin model, so responsibility does not have to sit with a single person when a squad needs help organising itself.
Event creators are now properly represented as participants, which keeps rosters, group counts, and ownership behaviour aligned with how real squads work.
Permission checks moved into a clearer shared layer, making sensitive actions easier to reason about and harder to accidentally expose.
The underlying participant model was reshaped so someone can be a member, coordinator, owner, or group admin without those ideas fighting each other.
Buyers get a dedicated sale-day board with the details they need to buy for their group. It is built for quick scanning, copying, and staying calm under pressure.
TicketSquad can pre-generate sale-day data snapshots before the big moment. That means the most important screen is designed to be fast and resilient when everyone is trying to buy at once.
The app gained deterministic fixture data so sale-day flows could be tested and demonstrated with realistic groups instead of fragile one-off setup.
Coordinators can form buying groups and assign responsibility, turning a loose crowd into practical sale-day teams.
Coordinators can see every member, their group, and whether their required details are complete. It replaces the spreadsheet-style audit with something built into the event.
Event pages gained a readiness banner and high-level status view, so coordinators can spot missing details before they become sale-day problems.
After joining, members get a clear confirmation and next-step summary. No more wondering whether the form worked or what happens next.
Members can choose an available buying group and see capacity before joining. It reduces coordinator admin and helps friends cluster together naturally.
Members can submit the event-specific details their coordinator needs, with privacy consent captured as part of the flow.
Invite links now explain the event before asking people to continue. Members can understand what they are joining and why their details are needed.
Events get shareable invite links, making it easy to move a squad from group chat into a structured flow.
Coordinators can set the maximum buying group size so the plan matches the rules of the ticket sale.
Every event can ask for the details it actually needs, from registration numbers to postcodes or other purchase requirements.
Coordinators can create a new event with the core details needed to start organising a ticket-buying squad.
Once you sign in, the dashboard gives you a stable place to see your events and move into the main app experience.
You can create an account and sign in, giving coordinators and returning members a stable home for their events.
The core event, member, group, invite, and sale-day data model was designed around security and privacy from the start, so sensitive coordination details only appear where they belong.
TicketSquad started with a modern, scalable product foundation, wired for fast iteration and automated checks from day one. The goal was simple: move quickly without becoming fragile.
Our end-to-end testing became faster and more diagnostic, with stronger simulated user journeys, transaction checks, smoke coverage, and failure traces. That means safer future releases for the product your squad depends on.
We tuned and hardened database connection behaviour so the app stays more resilient under real-world traffic spikes.
Success timing logs were added around timeout-protected work, making future reliability tuning easier without exposing sensitive member details.
Several slow-loading event views gained safer time bounds and graceful fallbacks. Visitors should see useful page content instead of waiting indefinitely on one slow section.
Event cover uploads became more resilient, so large or repeated uploads are less likely to leave you stuck halfway through making an event look right.
Login redirects were tightened so people are sent only where the app expects. It is a small security detail that matters for user trust.