> ## 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.

# Managing a touring band's lineup

> Set up a tour folder once, check availability across the run, rotate the lineup per show with call lists and offers, and settle each leg.

This is a workflow recipe for the bandleader running a multi-week tour. For a deeper conceptual treatment see [Managing a touring lineup](/features/availability/managing-touring-lineup), and for what tours themselves do, see [Tours](/features/gigs/tours).

## Once, at the start of the tour

<Steps>
  <Step title="Create the tour folder">
    On the Gigs page, click **New tour** and name the run (*Spring Run 2026*). The tour is a folder: every show you add rolls up into one view with tour-wide **Revenue**, **Payouts**, and **Net**. See [Tours](/features/gigs/tours).
  </Step>

  <Step title="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.
  </Step>

  <Step title="Stamp out the show dates into the tour">
    Use **New gig in tour** for each date (or duplicate from the template and **Add existing gigs** to pull them into the folder). Location is optional, so unconfirmed venues don't block you — add them as the routing firms up. Save each as draft.
  </Step>

  <Step title="Check availability before you route">
    Before committing a leg, send an [availability request](/features/availability/availability-requests) for the date range to the people you'd call — responses reconcile into the crew calendar, so you see who's actually free before a single invitation goes out.
  </Step>

  <Step title="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. Apply the right list to each leg's gigs. See [call lists](/organization/teams/call-lists).
  </Step>
</Steps>

## Per show, as things shift

<AccordionGroup>
  <Accordion title="Regular can't make one show">
    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.
  </Accordion>

  <Accordion title="You don't know yet who can sub">
    Two tools, by how targeted you want to be:

    * **Availability request** — ask a filtered list (position = *Drums*, call list = *Tour B-Team*) whether they're free, then book from the responses. See [crew calendar workflows](/features/availability/crew-calendar-workflows).
    * **Crew offer** — post the open seat itself and let eligible people claim it. The first accept fills the position, and the accepted fee flows into the gig's payables. See [team building](/features/gigs/team-building).

    Either way, everything lands in each person's [Mailbox](/features/engagements/overview) and they respond from their phone.
  </Accordion>

  <Accordion title="A whole leg's drummer changes">
    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.
  </Accordion>

  <Accordion title="Time / venue change for one show">
    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.
  </Accordion>

  <Accordion title="A show falls through">
    Use **Cancel gig** on that date — members are notified, uninitiated payouts stop, and the show stays in the tour folder for your records without counting as delivered. Cancelling can't be undone, so confirm the date is truly dead first.
  </Accordion>
</AccordionGroup>

## Money across the run

Set the **performance fee** on each gig, not on the template, so different legs can pay different rates. Then let the tour folder do the accounting:

* **Tour roll-up** — expand the folder to see **Revenue**, **Payouts**, and **Net** across the whole run, updating as shows settle.
* **Per-show payouts** — after members accept, fees become payables you send as [gig payouts](/features/gigs/payments) from each gig's Finances tab.
* **Close each show out** — mark shows **Completed** as the run progresses, then **Settled** once payouts clear, so the tour's net is real money, not projections. See the [closeout workflow](/faq/workflows/closeout-and-payouts).

## 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](/features/chat/overview).

## On the road

The [mobile app](/features/mobile/overview) carries the run: crew answer offers and invitations from their [Mailbox](/features/engagements/overview), read tonight's details, and get pushed when anything changes. Give everyone a private [calendar feed](/features/calendar-feed-subscription) so the tour shows up in their personal calendar too.

## Related

<CardGroup cols={2}>
  <Card title="Tours" icon="route" href="/features/gigs/tours">
    Folders, roll-ups, and managing the run as a whole.
  </Card>

  <Card title="Touring lineup (full guide)" icon="users" href="/features/availability/managing-touring-lineup">
    Conceptual treatment with more patterns.
  </Card>

  <Card title="Call lists" icon="list" href="/organization/teams/call-lists">
    Build the per-leg rosters.
  </Card>

  <Card title="Payments" icon="money-check-dollar" href="/features/gigs/payments">
    Per-gig fees and payout runs.
  </Card>
</CardGroup>

## Related reading

<Card title="Segment spotlight: Tour managers" icon="newspaper" href="https://soundchecklive.io/blog/blog/segment-spotlight-tour-managers">
  Why tour managers need infrastructure built for the job — and how the patterns above address that.
</Card>