Skip to main content
This is a workflow recipe for the bandleader running a multi-week tour. For a deeper conceptual treatment see Managing a touring lineup, and for what tours themselves do, see Tours.

​
Once, at the start of the tour

1

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

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

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

Check availability before you route

Before committing a leg, send an availability request 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.
5

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.

​
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.
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.
  • 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.
Either way, everything lands in each person’s Mailbox and they respond from their phone.
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.
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.

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

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

​
On the road

The mobile app carries the run: crew answer offers and invitations from their Mailbox, read tonight’s details, and get pushed when anything changes. Give everyone a private calendar feed so the tour shows up in their personal calendar too.

Tours

Folders, roll-ups, and managing the run as a whole.

Touring lineup (full guide)

Conceptual treatment with more patterns.

Call lists

Build the per-leg rosters.

Payments

Per-gig fees and payout runs.

Segment spotlight: Tour managers

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