The gig nobody put in the calendar
Half the band found out about the show from the venue's Instagram. A shared band calendar fixes the scheduling chaos that kills good bands.
By @KHeavy · Updated 26 October 2026
Every band has a version of this story. The gig got booked in a DM. The booker confirmed it in an email to one person. That person mentioned it in the group chat, somewhere between a meme and a question about strings. Three weeks later the drummer books a weekend away, and half the band finds out the show is real because the venue posted a poster.
Nobody did anything wrong. There was just no place where the gig officially existed.
The short answer: the moment a show, a rehearsal, or a studio day is real, it goes on one shared calendar as an event with a time, a place, and a description. Link the setlist. Attach the files for that day. Everyone sees the same diary, and a date change is one edit. BandVolt’s shared band calendar is that diary, on every tier.
The day the gig becomes real
“I’ll add it later” is how the weekend away happens. Later is after someone else has planned their life.
Add the event when the confirmation arrives, even if the setlist is still a guess and the rider is last year’s. A placeholder with the right date is already more useful than a perfect plan that lives in one person’s head. You can fill the rest in during the week.
On the schedule, Add Event is the button. You get a calendar view and a list view of the same dates, so “what have we got in October?” does not depend on squinting at a grid. Each event takes a date and time, a location, and a description. Use the description for the facts that otherwise turn into questions:
- Load-in
- Doors
- When you are actually on
- Where to park, if the venue told you
- The promoter’s name, if there is one person to ask on the day
The demo band’s headline at The Signal Box is a filled-in version of that. Saturday 28 November 2026, 20:30, at The Signal Box. The description is one line: doors at 7:30, on at 9, load-in at 5. Nobody has to scroll a chat to find the only three times that matter.
Gigs, rehearsals, and studio sessions are all events. There is no second calendar for “the music stuff” and a third for “the admin”. One diary, the whole band.
The setlist lives on the date
An event with a time and no songs is how you arrive and spend soundcheck arguing the running order.
Link the setlist to the event. If the set changes, you change it from Edit Event, and the gig still points at the current list. Building that list - order, keys, the version you actually play - takes about five minutes once the songs are in the library. The calendar’s job is to make that list the one attached to Friday, not a screenshot from the Tuesday rehearsal.
One setlist can be linked to more than one event. A Friday club show and a Saturday in the next town often run the same songs. Link the set once to both dates. When you drop a song because the Saturday slot is shorter, you can split them. Until then, you are not maintaining two copies of the same running order.

The night before the gig, the question “which set are we playing?” has an answer that is not a message. Open the event.
The files for that day, on that day
The setlist is one attachment. The rest of the day’s paperwork is the other.
Upload files straight onto the event. The rider, the stage plot, the parking note, the contract PDF the venue sent back. On the Signal Box show those attachments are Rider.pdf and Signal Box stage plot.pdf, with an Upload button on the event itself. The master copies can still live in the band’s shared files, so the next venue is not starting from a one-off. The show carries the copies that apply to it.
That is the whole of what to send a venue: two current PDFs, a contact, and a place the band can find them after dark. The calendar is that place for the show in question.
Rehearsals count, and so do the quiet weeks
Calendars die when they only contain the gigs. The Tuesday rehearsal is the event people actually miss, because it felt too ordinary to write down.
Put it on the same calendar. Time, room, and the setlist of songs you are working on, linked the same way as a show. The band walks in knowing what is getting played. You spend the hour on the songs, not on “what shall we run first?”
Studio days belong there too. Tracking, a mix playback, a mastering deadline if it is a date people have to be free for. If it needs a member in a place at a time, it is an event.
Filter past dates out of the main schedule when you want the next month, not the last one. The history stays. It just stops crowding the view of what is coming.
When the date moves
Promoters move doors by an hour. Support slots shift. Rehearsal rooms send you to a different night because someone else booked the usual one.
Edit the event. The description, the files, and the linked setlist stay with it. The band gets an event notification, so the change is not only in the head of the person who read the email. You are not updating a group chat, a spreadsheet, and three phone calendars and hoping they match.
That is the job people mean when they say someone has to be the band’s PA. Chase, remind, re-send, repeat. A calendar the whole band can see retires most of that. It does not retire the need for a human to read the promoter’s email. It retires the need for that human to be the only copy of the diary.
The public page reads the same diary
The shows you want the outside world to see can be flagged on the event. Flagged gigs appear as upcoming shows on the band’s Electronic Press Kit, which is free on every tier. You are not keeping a second list of dates on a press page that goes stale the moment a show is added.
Flag the public ones. Leave the rehearsal and the studio day unflagged. The band sees everything. The EPK shows the gigs.
A habit that fits in the same evening as the reply
When you answer the booker, add the event before you close the laptop. Date, venue, the times they gave you, a draft setlist if you have one. Attach the rider if it is already in the files. You can tidy the description tomorrow. You cannot recover a Saturday that somebody else gave away because the gig never became a date.
The walkthrough under this post is the same path in the app: add the event, link the setlist, attach the rider, and move the date when the plan changes.
Frequently asked questions
What should you put on a band calendar the day a gig is confirmed?
The date and start time, the venue, and a description with load-in, doors, and when you are on. Link the setlist, even a draft, and attach the rider and stage plot if you already have them. A date with no detail still gets double-booked around.
Can one setlist be used for more than one show?
Yes. Link the same setlist to several events when the run of shows uses one set. Each event can still carry its own files, so Friday and Saturday share the songs and keep their own stage plots.
Do rehearsals belong on the same calendar as gigs?
Yes. A Tuesday rehearsal is an event with a time, a room, and the setlist you are actually running. If it only lives in a chat message, half the band will have planned something else by the weekend.
How do upcoming shows get onto the EPK?
Flag the events you want listed. Those flagged gigs show up as upcoming shows on the band's Electronic Press Kit, which is the same calendar you are already keeping, not a second list to update by hand.
What happens when the promoter moves the date?
Edit the event once. The date, the description, and the linked setlist stay together, and the band gets an event notification. You do not re-send the same correction into the group chat, a spreadsheet, and three personal calendars.
Topics: band rehearsal scheduling app · shared band calendar · gig calendar