Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt

Use this file to discover all available pages before exploring further.

Touring lineups rarely stay fixed. Someone has a wedding on date 4, your regular sax player can’t make the back half, the drummer’s flight changes. This page covers the patterns Soundcheck supports for handling that without re-staffing every show by hand.

​
Set up once: the tour shell

1

Create a gig template for the tour

Build one gig with the canonical positions for this tour — Lead Vocals, Guitar 1, Guitar 2, Bass, Drums, FOH, Tour Manager. Save as template. See Templates and duplication.
2

Duplicate per show date

From the template, duplicate one gig per show date. Each gig inherits the position list — you only fill in venue and time.
3

Build a tour call list

From Teams → Call lists, build Tour A-Team — your default lineup in priority order. Optionally a Tour B-Team for known subs.

​
Per-show variation

For each show, the gig page has the same position grid. To handle a sub:
  1. Open the show’s gig.
  2. On the position the regular can’t play, click their name → Replace.
  3. Pick from the B-team call list, or invite an outside player.
The original member’s invitation is revoked; the sub gets a fresh invitation.

​
Per-leg call lists

If your back-half features a different rhythm section, create Tour A-Team — Leg 1 and Tour A-Team — Leg 2 call lists. Apply the right one to each leg’s gigs in bulk by selecting multiple gigs and using Apply call list.

​
Multi-week patterns

For one or two shows where your regular can’t make it: create the invitation, mark the sub’s role explicitly in the gig notes, and attach the relevant setlist plus any chord charts. The sub’s gig page shows them only what they need.
For shows where you alternate two drummers across a tour: don’t pick a default. Instead, send an availability request to both for the tour’s date range, then book each show against the responses. The crew calendar will surface who’s free.
Build the call list iteratively — every time you sub someone in, add them to the B-team call list with the appropriate priority. By the time the next tour starts, you’ve got a known-good bench.

​
Conflict detection

Soundcheck flags two kinds of conflicts on the gig page:
  • Hard conflict: the member is already booked on another gig at an overlapping time.
  • Soft conflict: the member marked themselves unavailable for that date.
Both appear inline next to the member’s name when you go to book them. Click the conflict to see the colliding gig or the availability note.

​
Per-leg payouts

If different legs pay different rates, set the performance fee per gig rather than baking it into the template. The template should have the position list but not the dollar amounts. See Gig payments.

​
Communication

A tour-wide chat thread is useful for “the bus leaves at 9, not 8:30” announcements. Two ways to do it:
  • Per-gig threads — clean, but you re-post to each one. Best when tour communication is genuinely per-show.
  • DM group thread — one thread, all touring members. Best for general tour logistics. Pin in your DM inbox.
See Chat.

​
What’s next

Call lists

Build your A-team / B-team / per-leg rosters.

Crew calendar workflows

Send availability requests across the tour range.

Gig templates

Stamp out per-show gigs without re-entering positions.

Segment spotlight: Tour managers

Why tour managers need infrastructure built for the job.

Touring band lineup workflow

The condensed recipe version.