Skip to content

How to Keep Your Whole Band on the Same Page — On Stage and Off

Every band pays a coordination tax. It is invisible until you add it up: the time spent chasing confirmations, the missed message about the setlist change, the dep who showed up for Saturday’s function not knowing “September” has a new outro, the band leader who rearranged the set on Thursday and had to text five people individually to make sure they all updated their printed sheets.

None of this is essential overhead. It is friction from using the wrong tools for the job. Group chats, personal email, shared folders, printed setlists — each one solves part of the problem and creates a different part.

This is what a properly coordinated band workflow looks like in practice.

When songs, chord sheets, and setlists live in a single shared library, the question “did you get the updated chart?” disappears. Everyone sees the same data. Changes made at 11pm the night before rehearsal are visible to every member when they walk in the door at noon.

Compare this to the typical alternative: someone exports a PDF from Chordify, sends it to the group chat, the trumpet player does not have notifications enabled, the guitarist downloaded it but has an older version saved in a folder, and nobody knows which version is canonical.

The shared library is not a better folder. It is a live database — one version, always current, visible to everyone with access, updated immediately when anyone makes a change.

Not everything should sync to everyone. Some things are genuinely personal:

  • Transpose values — the keyboard player is transposing +2 for B♭ saxophone. The guitarist does not need or want that.
  • Font size and display preferences — individual per device.
  • MIDI device configuration — your Helix preset list is yours. The drummer does not have a Helix.
  • Personal notes — annotations for your own performance that are not relevant to the rest of the band.

Shared settings (song content, chord sheets, setlists, lyrics, key and tempo metadata) sync to the whole band. Personal settings stay on your device. This separation means members can customise their experience without affecting anyone else’s view.

Band Roles: Giving the Right People the Right Access

Section titled “Band Roles: Giving the Right People the Right Access”

A four-piece with equal decision-making can share everything. A ten-piece function band with a dedicated sound tech, a booking manager, and regular deps cannot — not without creating noise and privacy problems.

Gigmeister has five roles, each scoped to what that person actually needs:

RoleWhat they can access
OwnerEverything — billing, settings, full management
ManagerSongs, setlists, calendar, bookings, mailbox
MemberSongs, setlists, calendar — no mailbox or billing
TechRider pack, patchlist, stage plan — production only
GuestOnly events they are assigned to, plus the shared song library

The Tech role is particularly useful for bands with a dedicated sound or lighting tech who needs to maintain the patchlist and rider pack without seeing the booking inbox or the band’s finances. The Guest role handles deps.

The dep problem is real. You need the dep to have the setlist, the chord charts for their instrument, the event details — but not your booking history, your internal notes, your hospitality rider, or anything else that is band-internal.

Invite the dep as a Guest. They see the events they are assigned to and the shared song library. That is it. Their access ends there.

The onboarding takes two minutes: send the invite link, assign the Guest role, assign them to the event. They arrive at the gig with the right information and no access to anything they should not have. When the gig is done, their access can be removed or left inactive — no need to chase down shared logins or revoke folder permissions.

Active practice sessions in Gigmeister broadcast the current song to all connected band members. When the music director moves to the next song, everyone’s screen jumps. Nobody is on the wrong page because they were scrolling through their notes.

For bands that track practice systematically — logging which songs were worked on and how many times each song has been rehearsed — the session data syncs across all members. Everyone sees the same session history.

This is a different kind of coordination problem than the booking or setlist problem. It does not involve communication delays or information asymmetry — it involves the real-time state of a rehearsal session, which previously required the band leader to call out “okay, next song is…” every time. The shared session handles that automatically.

Follow Leader Mode: Running the Show from One Device

Section titled “Follow Leader Mode: Running the Show from One Device”

Follow Leader is the most immediately impactful coordination feature for live performance. The leader’s device broadcasts the current song and step to all followers over the local network. When the leader swipes to the next song, every follower’s screen jumps to that song automatically.

No one is ever on the wrong song. No missed cues because someone was still looking at the previous chart. No need for a printed setlist on every stand. The leader’s navigation is the setlist for everyone.

This matters most in:

  • Large stages where shouting across to a bandmate is not practical
  • Last-minute setlist changes called from the stage — the leader skips a song, and everyone follows without a conversation
  • Function gigs with a variable order — the MC changes the plan, the leader adapts, the band adapts
  • Bands with less experienced deps who need to follow rather than anticipate

Leading requires the Gigmeister desktop app (macOS or Windows). The leader role is not available in a web browser. Followers can use the desktop app or the iOS app. All devices must be on the same local network — Follow Leader is peer-to-peer over LAN, not a cloud relay.

This is the right setup for most gig scenarios: the band leader runs the desktop app on a laptop at the stage, followers use iPhones or tablets. The connection does not require internet access beyond the local network once devices are paired.

On the leader’s desktop app: open the setlist in performance mode, click Presence, click Lead. A QR code appears on screen.

Followers open Gigmeister on their iPhone or tablet, tap Presence, scan the QR code (or select the leader from the auto-discovered list on the same network), and join. They are now synced.

From this point, any navigation on the leader’s device — next song, previous song, jump to a specific song, advance to the next step — broadcasts to all followers. Followers can navigate independently if needed but re-sync on the leader’s next action.

What Happens When Someone Loses Connection

Section titled “What Happens When Someone Loses Connection”

If a follower drops off the local network mid-show, their screen holds on the last synced song. They do not get a blank screen — just a frozen state. The leader keeps going. Reconnect by scanning the QR code again.

The sensible backup is for each member to know the setlist order anyway — Follow Leader enhances coordination, it does not replace rehearsal.

Calendar Coordination: Gigs, Rehearsals, and Attendance

Section titled “Calendar Coordination: Gigs, Rehearsals, and Attendance”

The band calendar shows every gig and rehearsal in one place, visible to all members with the appropriate role. Each event has:

  • Date, venue, load-in and soundcheck times, set time
  • Attendance tracking — confirmed, declined, tentative, no response
  • Linked setlist (even as a template that gets refined closer to the date)
  • Notes (parking, contact person, balance due)

The band leader can see at a glance who is confirmed for Saturday. Members can confirm or decline without a separate group message. When someone declines, the leader knows immediately and can line up a dep — without a round of “can everyone make it?” messages.

iCal sync pushes all band events to personal calendars (Google Calendar, Apple Calendar, Outlook) so gigs show up alongside everything else in a member’s life. One sync setup, automatically updated as events are added or changed.

Many working musicians play in more than one band. Each band is a separate workspace in Gigmeister — independent song library, setlists, calendar, and inbox. Switching between bands is a single tap in settings.

Personal MIDI device configuration carries across all bands. Your Helix setup, your MainStage program change numbers, your SPD-SX mappings — configured once, available in every workspace. You are not reconfiguring your rig when you switch from your function band to your originals project.

Band Chat provides six built-in channels scoped by role:

  • General — everyone
  • Announcements — everyone
  • Musicians — Owner, Manager, Member, and Guest (deps see this)
  • Core — Owner, Manager, and Member only (no guests)
  • Bookings — Owner and Manager only
  • Production — Owner, Manager, Member, and Tech

Scoped channels solve the noise problem. The drummer does not need to see contract negotiation threads. The touring sound tech does not need to see discussions about the rehearsal schedule. The dep does not see Bookings or Core.

Everyone sees the channels relevant to their role. The person who sets the agenda for each channel controls its audience by controlling who gets that role — without managing individual permissions per message.

Sync your entire band in real time, on stage and off. Create a free Gigmeister account or read the Band Collaboration documentation to invite your bandmates.