Band communication without the group-chat chaos

The gig time was in the chat. It was also changed in the chat, 140 messages later, between a video of a cat and a discussion about the drummer's new snare. Two members turned up at 18:00, three at 19:30, and the client noticed.

Group chats are not the problem. Using them for things they cannot do is the problem. A chat is a stream; logistics need a table. Here is how working bands separate the two, and what to do with the things that belong in neither.

Why the group chat fails at logistics

• It has no state. A question ("who can do the 14th?") gets four answers spread across two days, one of which is "probably". Nobody can see the current tally without scrolling.
• Edits do not propagate. When the load-in moves from 17:00 to 16:00, the old message still says 17:00 and someone will read that one.
• It punishes the busiest people. The member who checks the chat twice a day misses the poll that closed in six hours.
• It flattens importance. "Contract signed for 12 June, 2,100 €" scrolls past at the same speed as "lol".
• It turns decisions into arguments. Text has no tone. A short reply reads as blunt, a long one reads as lecturing, and by message 30 the drummer has left the group.

None of this means you should ban the chat. Keep it for what it does well: quick coordination on the day, banter, photos after the gig.

One source of truth

Pick one place where the current state of everything lives, and make the rule that if it is not there, it is not real. That place needs to hold, for every gig: date, times, address, status (request or confirmed), fee, who is playing, setlist, and what to bring. For every rehearsal: date, time, place, what is being worked on. For the band: members, roles, contact details, the split rules, the agreement.

A shared calendar plus a shared folder can do this. A band app does it with less friction. A spreadsheet does it if someone maintains it. What does not do it is a chat, a personal calendar and the leader's memory.

Three rules make the source of truth work:

1. Changes go there first. If the load-in moves, edit the gig, then post "load-in moved, see the gig page" in the chat. Never the reverse.
2. Questions about facts are answered with a link. "What time on Saturday?" gets "it's on the gig page" and nothing else. It feels curt for a fortnight and then everyone stops asking.
3. It is readable on a phone in a van. If people need a laptop, they will not look.

The decision log

A source of truth holds facts. A decision log holds choices, and it is the thing almost no band keeps. It is a single page, newest at the top, with three columns: date, decision, who decided. Examples:

2 Sept: Raise wedding base price to 2,200 € from 1 January. Majority vote at band meeting. 19 Aug: Drop "Mr Brightside" from the setlist. Musical director's call after three low audience ratings. 5 Aug: Dep fee fixed at 220 € for local gigs. All members.

Ten seconds per entry. The value shows up three months later, when someone says "we never agreed that". You open the page. Pair it with band meetings that take 30 minutes, where most of the entries are born.

What goes where

Type of message	Where it goes
Gig details, changes to gig details	Source of truth, then a one-line pointer in chat
"Are you free on the 14th?"	Availability request with a deadline, not a chat poll
Rehearsal scheduling	Availability calendar or a poll with a deadline
Decisions made	Decision log
Money: fees, splits, what is owed	Monthly summary from the treasurer, in writing, in the source of truth
Running late, lost, parking	Chat, or a call
Jokes, photos, videos	Chat
Feedback on someone's playing	In person, one to one
Anything with feelings attached	A call or a meeting

Availability requests deserve their own system

The single most common chat failure is the availability poll. The fix is a request with a personal yes/no for each member, a deadline (48 hours), and a visible tally of who has answered and who has not. Chase only the people who have not answered, individually. Confirm the gig when you have enough, and say so in the chat with one line. Asking the band "are you free on the 14th?" without 40 messages goes into the details, including what to do about the member who never answers.

Response-time expectations

Write them down once. A reasonable set for a working band:

• Availability request: 48 hours.
• Rehearsal availability: painted or filled in three weeks ahead.
• Direct question from the leader about a gig: same day.
• Chat in general: no expectation. Nobody is obliged to read 200 messages.

That last one matters. Freeing people from the chat is what makes them reliable on the things that count.

When to call

Three situations where typing makes things worse:

1. Anything that could be read as criticism. "The tempos were rushing last night" in a chat is a public accusation. On the phone, it is a conversation.
2. Anything urgent within 24 hours of a gig. A message can be unread for six hours. A call is answered or it is not, and you know which.
3. Anything that has already generated more than five replies. If a chat thread has gone past five messages and is not resolved, stop typing and call the person who disagrees. Two minutes.

For real conflict, the phone is the minimum and a meeting is better. Handling conflict in a band before it costs you a gig covers that.

A weekly rhythm

• Leader, once a week: one message in the chat that says what changed in the source of truth this week and what is coming. Five lines. "New request 21 Nov, please answer by Friday. Rehearsal Tuesday confirmed, 19:00, room B. Setlist for Saturday is up. Deposit received for the Meyer wedding."
• Everyone, once a week: look at the calendar. Two minutes.

That message replaces most of the chat noise, because the facts are already stated.

Do this today

• Decide where the source of truth is. Tell the band in one message.
• Move the next three gigs into it, completely: times, address, fee, line-up.
• Start the decision log with the last three decisions the band made.
• Pin one message in the chat: "Facts live at [place]. Availability comes by request, please answer within 48 hours. Anything with feelings: call me."

Where expert.band helps

expert.band is designed to be the source of truth rather than another chat: every gig has its times, address, fee, line-up, setlist and packing list on one page that members see on their phones, and any edit is the current version. Availability requests go to each member by email and SMS with a one-tap answer and a visible tally, rehearsals are scheduled from the band's availability heat map and reminded automatically, and the activity feed shows what changed. Your chat stays for the jokes.