Asking the band 'are you free on the 14th?' without 40 messages

A client emails on Monday asking whether you can play a wedding on the 14th of June. By Wednesday the group chat has 38 messages, two of them about the date, and you still do not know if the bass player is free. Availability checks are the most frequent task in a working band, and most bands do them in the worst possible tool.

Why the group chat fails at this one job

A chat thread mixes a yes/no question with everything else the band talks about. Three things go wrong every time:

• Answers get buried. The drummer's "yes" sits between a meme and a debate about the new intro. Two days later you scroll to find it and miss it.
• Silence looks like nothing. In a chat, no answer and "I haven't seen it" are indistinguishable. You end up asking the same person three times.
• The question changes. "Is the 14th OK?" becomes "what about the 13th, the client might move it" and now half the answers refer to a different date.

The fix is not a better chat. It is separating the question from the conversation: one request per date, one place where the answers live, and one person who reads them.

The five parts of a request that gets answered

1. One request, one date, all the facts

Send the request once the client has given you enough to make it real: date, approximate times, town, type of event, and a fee range if you know it. Musicians answer faster when they can see the whole picture. "Wedding, Saturday 14 June, Tallinn, 19:00 to 01:00, around 250 EUR each, load-in 16:00" gets an answer. "Anyone free 14 June?" gets a question back.

2. A deadline, stated in the request

Give a reply-by time and make it short: 24 hours for a gig more than two months away, 12 hours if the client is waiting on you. Clients who are comparing bands book the one that answers first. A deadline also tells members that their silence has a cost.

3. A yes/no answer format

Do not ask for opinions. Ask for one of two answers: available or not. A "maybe" is useful only if it comes with a date by which it becomes a yes or a no. If someone needs to check with a partner or an employer, ask them to answer "not yet" and give you a time.

4. A reminder to non-responders only

After the deadline, chase the people who have not answered, and only them. Sending "still waiting for 2 of you" to the whole band trains the responders that answering promptly does not save them from nagging.

5. The confirmation moment

Once you have enough yeses, tell everyone that the gig is on, in a message they cannot miss: date, times, fee, line-up, and what happens next. Availability is a soft promise; confirmation is a hard one. Say the word "confirmed" so nobody thinks it is still a question.

When someone cannot make it

Plan for it in advance rather than in the moment. A five-piece band that plays 40 gigs a year will need a dep on 6 to 10 of them. Decide these things once, and write them down:

• Who is the first-call dep for each chair, and who is the second.
• What the dep gets paid (usually the same as the member they replace, sometimes 10 to 20% more for short notice).
• Who briefs the dep: the leader or the member who is absent.
• Which songs a dep must know cold, and where the charts are.

With that in place, a "no" from the keys player is a 10-minute job, not a reason to decline the gig. See deps and substitute musicians for the full system.

The quorum question

Decide before the season what counts as "enough" to take a gig. A common rule for a five-piece: the singer and at least three of the four instrumentalists, with a dep for the fourth. For a duo or trio, everyone or a named dep. Write the rule into your band agreement so nobody feels overruled when you accept a date with a dep on drums.

Timing rules that save you

• Answer the client within 24 hours, even if it is only "checking with the band, you will hear from me by Thursday".
• Hold a date for at most 7 days without a deposit. Tell the client that. It stops you turning down other work for a wedding that is still "thinking about it".
• Send the availability request the same day the enquiry arrives. Every day of delay is a day for a member to accept something else.
• Confirm to the band within 24 hours of the deposit arriving. Members plan their lives around your confirmations.

Do this today

1. Write your quorum rule and your dep list (first and second call per chair) in one document the whole band can see.
2. Pick a reply deadline you will use for every request: 24 hours is a good default.
3. Decide who sends availability requests. One person. Everyone else stops asking in the chat.
4. Draft a template for the request with the fields you always need: date, times, town, event type, fee, load-in, reply-by.
5. Draft a confirmation template that says "Confirmed" in the first line.

A worked example

Enquiry arrives Monday 10:00: corporate summer party, Friday 3 July, 20:00 to 23:30, 80 km away, budget confirmed at 1,800 EUR. You send the availability request at 11:00 with a reply deadline of Tuesday 11:00. By Monday evening four of five have answered yes; the guitarist has not opened it. Tuesday 09:00 you chase the guitarist only. He answers "no, family wedding". You message your first-call dep, who says yes by lunchtime. Tuesday 14:00 you send the client a quote and tell them the date is held for 7 days pending deposit. Deposit lands Thursday. Thursday evening the band gets "Confirmed: 3 July, corporate, 20:00 to 23:30, 300 EUR each, dep guitar: Markus". Total elapsed: 3.5 days. Messages in the group chat about it: zero.

Where expert.band helps

An availability request sends every member a personal link by email and, if they have a phone number, by SMS (50 SMS a month are included). The link shows the gig and two buttons, available or not available, with no login. The gig page shows who said yes, who said no, and who has not answered, and you can send a reminder to just the silent ones. When you have enough, change the gig from request to confirmed and the whole band sees it, and the same flow is described in availability requests explained.