Shared Calendar for Bands: Manage Availability Without Endless Group Chats
How a band can answer a date request within 24 to 48 hours: one single source, four date statuses, unavailability collected in advance, one booking contact and an availability indication for promoters.
A promoter offers you a date: Saturday, April 18. They want an answer by the end of the week.
You post in the band group chat: "Is everyone free on the 18th?"
The bassist replies within a minute. The guitarist "thinks so" but needs to check. The singer doesn't reply. The drummer is free… unless the gig the night before with his other project gets confirmed.
Two days later, still no firm answer. Meanwhile, the promoter is waiting. And they may have already messaged three other bands.
The real problem isn't knowing who's available. It's being able to give a promoter a reliable answer within 24 to 48 hours, without tying up the whole band for days.
This guide focuses on that exact moment: between the date request and your reply. For general band organization (roles, files, rehearsals), see Organize a Music Band Effectively.
Why "is everyone free?" stops working once you play regularly
Four or five musicians means four or five schedules: day jobs, holidays, family, often a second musical project. And unlike rehearsals, gig offers show up without warning, for a date three weeks or six months away.
The same three blockers come up almost every time.
Scattered information. One member's holiday is in the group chat, another's constraint was mentioned at rehearsal, a third sent a private message. Nobody has the full picture.
Unclear statuses. One date is confirmed, another is waiting on the promoter, a third is just an idea. Without a clear distinction, you can't tell what's actually blocked.
Slow replies. Every request means checking with everyone. Meanwhile, the promoter fills their lineup with another band.
One single source for the band's dates
A group chat is great for discussing and deciding quickly. But a chat thread isn't a calendar: an unavailability mentioned in March is impossible to find in June.
The band needs one place to check dates. Several options work:
- A Google Calendar dedicated to the band, shared with every member.
- A shared spreadsheet to track gig offers.
- A booking tool that connects incoming requests, dates and the lineup.
The criterion isn't how sophisticated the tool is. It's whether everyone actually uses it. A basic calendar kept up to date beats a full-featured app nobody opens.
Simple test: if a member has to scroll through a conversation to find out whether the band is playing on June 12, you don't have a single source yet.
Four statuses so you never confuse a hold with a confirmed gig
Mixing offers, holds and confirmed gigs in the same calendar creates exactly the confusion you're trying to avoid. Four statuses are enough.
Available No known constraint for the band.
To check One or more members still need to confirm.
On hold A serious offer is under discussion, but nothing is signed.
Confirmed The band and the promoter have both validated the date.
A concrete example. A bar offers you June 12. Everyone is free, but the fee isn't agreed yet. The date is on hold, not confirmed.
If another promoter contacts you for the same night, you know right away that a discussion is already in progress. You can follow up with the first one before making a new commitment, instead of discovering the double booking three weeks later.
A hold with no deadline ends up blocking other offers. Put it in writing with the promoter: "We'll hold the date for you until Friday. If we don't hear back by then, we'll reopen it."
Collect unavailability before requests come in
This is the habit change with the biggest payoff. In most bands, availability is only checked when an offer lands. Flip it around: each member flags their main constraints in advance.
- Holidays and trips
- Known work commitments
- Gigs with other projects
- Important family events
- Periods when they'd rather not commit
Nobody needs to justify their absences or share details of their private life. The goal is simply to have a picture reliable enough to reply quickly.
The ten-minute monthly check-in
Once a month, say the first Monday, each member adds their new constraints for the next three months. This small ritual avoids asking the same questions with every request, and turns most "to check" dates into "available" dates before a promoter even reaches out.
One person answers the promoter, everyone sees the answer
A shared calendar isn't enough if nobody knows who should reply. Appoint a booking contact (role allocation is covered in our band organization guide) and give them a clear process:
- Log the request and mark the date as "to check."
- Check the calendar to see who is already available.
- Ask only the members whose availability is still uncertain, with a precise deadline.
- Reply to the promoter: confirmation, hold or decline.
- Update the date's status for the whole band.
For step 3, a short, specific message gets answers much faster than "are you free?":
"Request for Sat 4/18 at Café des Arts, 90-minute set. According to the calendar, we're still missing confirmation from Julie and Mark. Please reply by 8pm tomorrow, thanks."
One contact for the promoter, shared information for the musicians. It's also what prevents two members from replying separately to the same offer.
Give promoters an availability indication
So far, we've talked about internal organization. But part of the back-and-forth comes from the outside.
A promoter discovers your band on Instagram and is looking for someone for an event in July. With no indication of availability, they start by asking. You check with the band, get back to them, and only then talk about venue, budget and tech. Three exchanges before getting to the point.
There's no need to publish a detailed schedule: it would be hard to maintain and misleading as soon as a date moves. An indication by period is enough to point the promoter toward workable dates.
An availability indication makes first contact easier. It isn't a booking: every date is confirmed with the band before you commit.
Centralize requests on a Booking Page
That's the role of a Yelinka Booking Page. Instead of hunting for your phone number or email across several posts, the promoter finds in one place your presentation, your availability indications and a way to send you a structured date request: event, venue, requested date.
On the band's side, the request doesn't end up buried in a group chat: you ask the members concerned, track their replies and build the lineup for the date in the same tool.
A few examples of band Booking Pages showing their availability:
What happens once the date is confirmed?
The date switches to "confirmed" and moves into concert planning. On Yelinka, lineup members receive a calendar invitation (.ics) to add to their own calendar: everyone has the date on their side, without copying anything.
For everything that follows (address, soundcheck times, on-site contacts, gear), use the logistics checklist for a successful concert.
The mistakes that cost you a date
- Treating silence as a yes. A musician who doesn't reply isn't available. Set an explicit rule: no reply by the deadline, no confirmation.
- Confirming too early. An assumed availability announced as firm sooner or later leads to a cancellation, the worst possible look with a promoter.
- Using too many tools. One calendar for rehearsals, a spreadsheet for gigs, the group chat for absences: three sources, so none of them reliable.
- Forgetting updates. A dropped hold left in the calendar blocks a date for nothing. Change the status as soon as things move.
Your action plan for this week
You don't need to change everything at once. Five decisions are enough to remove most of the back-and-forth:
- Pick one shared calendar or space for the band's dates
- Adopt the four statuses: available, to check, on hold, confirmed
- Ask each member for their unavailability over the next three months
- Appoint the person who replies to promoters
- Give promoters a single point of contact for their requests
Frequently Asked Questions
The one every member actually checks. A dedicated Google Calendar is often enough when you play occasionally. Once gig requests start piling up, it becomes more useful to connect the calendar to request tracking and to the lineup of each date, so you don't have to maintain two systems side by side.
Collect known unavailability in advance (holidays, other projects, work constraints), route requests to a single person, and agree on a validation rule. For each new date, check the calendar first, then only ask the members whose availability still needs confirming — with a clear reply deadline.
No. A per-period indication is enough to make first contact easier, without exposing each musician's personal schedule. It isn't a booking commitment: every date is confirmed precisely with the band before you commit.
For discussion, yes. For storing dates, no: an unavailability mentioned three months ago becomes impossible to find in the thread. Keep WhatsApp for quick exchanges and record dates and their status in one place everyone can check.
Give every date a status (to check, on hold, confirmed) and let a single person handle confirmations. A date is only booked once the band and the promoter have clearly validated it, and any existing hold must be checked before replying to a new request for the same night.
There's no universal rule: what matters is setting the deadline explicitly with the promoter — for example, "we'll hold the date until Friday." If there's no answer by then, the date becomes available again. An open-ended hold ends up blocking other offers.
Conclusion
Managing availability is nobody's favorite part of being in a band. But it's often where a date is won or lost: a band that replies within 24 hours with reliable information inspires more confidence than a more talented band that takes a week to decide.
Start with the single calendar and the four statuses this week. The next time a promoter gets in touch, you'll know within minutes what you can tell them.
Ready to launch your Booking Page?