Run a Team Season Without Three Group Chats

By October most coaches are running three group chats without ever having decided to.

There is the parents' one, which is where the actual information goes. There is the players' one, which is where the information should go but where nothing is read. And there is the smaller one with the two other adults who help, which exists because the first two are unusable for anything requiring a decision.

Then there is the spreadsheet nobody but you opens, and a pinned message from August that is now wrong.

What actually goes wrong across a season

A single fixture is easy. A season is not, and the reason is repetition.

Every week you need roughly the same four answers, and the fact that they are the same four is precisely what makes a season different from a fixture. Who is available on Saturday. Who is short of a lift. Who has the away kit. Whether subs have been paid. None of those questions is hard. Asking them thirty times, reading the replies, and holding the current answer in your head is what burns coaches out by half term.

The failure is not that people are unhelpful. It is that each week's answers have nowhere to live except a chat that scrolls — last Saturday's availability is now four hundred messages up. So you ask again, and the asking is the work.

The four things a season needs

Availability that counts itself. Not twelve thumbs-up emoji you have to tally. A number you can look at on Thursday night.

Lifts sorted in public. Carpooling collapses when it happens in private replies, because only you know the state of it, and if you are away nobody else can.

Jobs with a name on them. Someone brings the balls. Someone does the teas. Someone chases the two who have not paid.

Nothing to install for the parents. A squad of fifteen means fifteen households, and roughly three of them will not download anything for a Sunday league. If your system needs all fifteen, your system has already failed.

How this runs in Blinko

One group chat for the team, with plans living inside the conversation instead of beside it.

Each fixture is a Plan: opponent, place, kick-off. It lands in the chat as a card with RSVP buttons, and people tap Going or Maybe on the card rather than typing a reply that you then have to count. Your availability for Saturday is a glance, not an arithmetic exercise, and it updates through the week as replies arrive.

Anyone who is not on Blinko gets a link. It opens in a browser, shows what and when and where, and takes a first-name RSVP in about ten seconds. No account, no app, no password to reset in a car park.

Invitations go out from your own number, using text the share sheet writes for you. Blinko never messages the parents itself and never collects their numbers. Nobody gets a notification from a platform they have never heard of.

Lifts, kit and subs

A shared list in the chat handles the things that need ticking rather than deciding. Away kit, corner flags, the first aid bag, who is bringing oranges. Everyone sees the same list and ticks their own line, so the state of it is public and you are not the only person who knows what is missing.

Lifts work the same way, and this is the part that is genuinely better in public than in your inbox. Three seats offered, two taken, one still going. Another parent can fill the gap without asking you first, which is the entire point.

Tasks with owners take the jobs that need a name. Chase the subs. Book the pitch. Confirm the referee. Assign it, nudge it, mark it done.

When kick-off moves an hour, you change it once, and the card and everyone's calendar entry move with it. No pinned message to rewrite. No parent arriving at the old time.

Honest sizing

A Plan holds up to 25 people, which comfortably covers a squad, and usually a squad plus the parents who need to know.

If your club is running an age group of eighty across four teams, a Plan is the wrong shape for the whole thing. Use one per team, which is how people think about it anyway, and use a Beacon for the open club-wide occasions where there is no guest list to hold: the end-of-season presentation, the club fun day, the fundraiser in the park.

Nobody needs a hard headcount for a fun day. Plenty of people need one for a minibus.

What this replaces, and what it does not

It replaces the second and third group chat, the spreadsheet, and the pinned message. It replaces the Sunday-night tally.

It does not do league tables, registrations, or match reports. Team management platforms do those — they charge for them, and if you need them you should pay for them. What most volunteer coaches actually need is not a management platform. It is one place where asking a question and counting the answer are the same action.

The bit nobody plans for

A season ends, and everything that happened in it is inside a chat that will be muted by December.

The plans, the places, the photos from the cup run stay together instead. Which is worth something in three years, when one of them is playing somewhere else and the parents' chat has long since gone quiet.

More on the mechanics: RSVP links that need no app, a group chat that makes plans, and inviting people without social media. Organising a one-off rather than a season? Getting parents to reply about a school trip.

---

Blinko Spots is free. Every feature, no tiers, no adverts.

See what Blinko Spots does →