> ## 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 lineup > Keep a run of shows staffed when the lineup changes leg to leg — subs, rotations, and conflict detection, built on availability and the Tours feature. 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 how to keep a run staffed as the lineup shifts, without re-staffing every show by hand. To organize a run of shows as a single unit — a folder of gigs with a shared financial roll-up — use the **Tours** feature under Gigs. This page focuses on the lineup side: who plays which show. Group a run of shows into a tour folder and see the run's finances in one place. ## Staffing a run The building blocks are the same ones you use for any gig, applied across a set of dates: 1. Create the shows for the run (a [gig template](/features/gigs/templates-and-duplication) with your canonical positions makes this quick), and group them into a [tour](/features/gigs/tours). 2. Send one [availability request](/features/availability/availability-requests) covering the whole date range, filtered to the positions you need. 3. Staff each show from the responses on the **People → Staffing** tab. As members accept, the crew calendar auto-blocks their time so no one gets double-booked. ## Handling subs For a show your regular can't make: 1. Open that show's gig. 2. On the position they can't cover, replace them — invite a sub instead. 3. The original invitation is withdrawn; the sub gets a fresh one. Attach the relevant setlist and any charts to the show so the sub sees exactly what they need. ## Per-leg variation If the back half of the run features a different rhythm section, you don't need one fixed lineup: * Send availability requests per leg, filtered to that leg's positions, and staff each leg from its own responses. * Keep a running bench: every time you sub someone in, note them for next time. By the next run you've got a known-good list of subs to call. ## Rotating lineups For shows where you alternate two players across the run, don't pre-pick a default. Send an availability request to both for the full date range, then staff each show against who's actually free — the crew calendar surfaces it. ## Conflict detection When you go to staff a member, Soundcheck flags two kinds of collision inline: * **Booked elsewhere** — the member has already accepted another show at an overlapping time (a conflict block on the crew calendar). * **Marked unavailable** — the member set themselves off for that date. Click the flag to see the colliding show or the availability note before you commit. ## Per-leg payouts If legs pay different rates, set the **performance fee** per show rather than baking a number into the template. The template carries the position list; the dollar amounts live on each gig. See [Gig payments](/features/gigs/payments). ## What's next Organize the run and roll up its finances. Send availability requests across the run and staff from responses. Stamp out per-show gigs without re-entering positions. Build your first-call and sub rosters.