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.

This is a workflow recipe for the bandleader running a multi-week tour. For a deeper conceptual treatment see Managing a touring lineup.

​
Once, at the start of the tour

1

Build a tour template

Create one gig with the canonical positions. Save as template. Don’t bake in the venue or time — those vary per show.
2

Build per-leg call lists

If the lineup differs by leg, create Tour A-Team — Leg 1 and Tour A-Team — Leg 2. Include the priority order — first-call up top.
3

Stamp out the show dates

From the template, duplicate one gig per show. Fill in venue and time. Save each as draft.
4

Apply call lists in bulk

Multi-select the leg’s gigs in the calendar → Apply call list → pick the per-leg list. All teams populate at once.

​
Per show, as things shift

Open the gig → click their name on the position → Replace → pick from the B-team call list. The original invitation is revoked; the sub gets a fresh one. Gig notes still apply.
Send an availability request for that date to a filtered list (e.g., position = Drums, call list = Tour B-Team). Book whoever responds first from the response view. See Crew calendar workflows.
Edit the Tour A-Team — Leg 2 call list to swap the drummer. Re-apply the call list to leg 2 gigs — Soundcheck only updates positions where the member changed.
Edit the gig. Confirmed members get a push notifying them. They keep their booking unless the change is significant (different day or city), in which case Soundcheck prompts you to re-confirm.

​
Payouts that vary by leg

Set the performance fee on each gig, not on the template. Two patterns:
  • Leg-uniform fees: After bulk-applying a call list, multi-select that leg’s gigs → Set fee → enter once.
  • Per-show fees: Set on each gig page when you create it.
Members see the fee on their invitation; you see the rollup on the dashboard. See Gig payments.

​
Tour-wide communication

Pick one:
  • Per-gig threads — clean per-show context. Use when most discussion is show-specific.
  • DM group thread — one persistent thread for all touring members. Use when most discussion is about the tour overall (bus times, hotel info, day-off plans).
See Chat.

​
Reporting

After the tour:
  • Dashboard → filter to the date range — counts, total fees, by-member rollup.
  • Per-member view → who played which shows — useful for payroll and 1099s.
  • Payments → status per member — sent, pending, failed.

Touring lineup (full guide)

Conceptual treatment with more patterns.

Call lists

Build the per-leg rosters.

Templates

Stamp out the show dates.

Payments

Per-gig fees and rollups.

Segment spotlight: Tour managers

Why tour managers need infrastructure built for the job — and how the patterns above address that.