Skip to main content
Common questions about creating, managing, and organizing your performances in Soundcheck.

Creating

Navigate to Gigs and click + Create Gig. Enter the event details, save, then build the team, run of show, and attachments from the gig page. Full guide. For the fastest path, see Quick 5-minute gig setup.
No. A gig only needs a name, a date, and an event type — location is optional, so you can lock in a hold or a tentative booking before the venue is confirmed and fill in the location later.
Yes. Set an optional end date on the gig to make it multi-day — a festival run, a corporate conference, a weekend residency. Leave the end date empty for a single-day event, and clear it later to switch back.
Yes. Open any gig, click the actions menu (three dots), and select Duplicate Gig. Modify the details for your new event and save. See Templates and duplication.
Yes. Use the Imports wizard — Parse → Map → Preview → Commit. Dozens of gigs in one pass. For the full migration recipe, see Importing your season.

Editing & day-of

Yes. Open the gig, click Edit, change the date, and save. Confirmed team members get a push notifying them. Significant changes (different day or city) prompt re-confirmation.
The timeline grew into the run of show — a full show-day rundown that lives at the top of the gig’s Details tab. It holds every timed item (load-in, soundcheck, sets, strike) plus songs, instructions, notes, and attachments, and it exports to PDF. See Run of show. Older gigs that used the previous timeline still display their schedule.
Yes. Open the run of show and choose Export — you get a PDF with quick views (All Items, Songs Only, Titles Only), a field picker (times, instructions, notes, attachments), and formatting controls with a live preview. See Run of show.
Yes. Upload contracts, stage plots, riders, or any other documents to the gig. Files also appear in the gig’s Files tab, and you can have CheckAI extract the schedule, crew, and money from paperwork you drop there.
Open the gig on the mobile app — the setlist caches once you’ve opened it, so it works even when reception drops. See Mobile offline and sync.
The Gigs page shows your events, and the calendar provides a monthly overview. Your personalized Home page also surfaces what’s coming up next when you sign in.
Yes — every gig has its own chat thread for show-specific discussion.

Tours

A tour is a folder that groups related gigs on the Gigs page so you can manage a run as a whole — a multi-week routing, a festival season, a recurring residency. Expanding the folder shows every gig in the run plus a financial roll-up: Revenue, Payouts, and Net across the whole tour. See Tours.
Two ways: use Add existing gigs on the tour folder to multi-select gigs you’ve already created, or New gig in tour to create a gig that starts out attached. You can remove a gig from a tour at any time — it returns to the ungrouped list, unchanged.
Nothing bad — deleting a tour only removes the folder. The gigs inside are detached and return to your regular gigs list with all their data intact.
Tours are rolling out per organization. If you don’t see the Tours section at the top of your Gigs page, contact support to enable it.

Closing out

A gig moves through a lifecycle of Draft → Active → Completed → Settled, plus two standalone terminal states — Cancelled and Archived — that sit outside that cycle. The status picker lives in the gig header. See the event lifecycle.
Two gates can hold up settlement:
  1. Payouts — every crew payable must be settled first. If money is still processing, you’ll see “Settle all payouts in Finances first.” Handle payouts from the gig’s Finances tab. See payments.
  2. The close-out checklist — if your organization enforces close-out gates, incomplete blocking steps (like a signed contract or a received payment) lock Settle. You’ll see “Complete N close-out steps first.”
See post-event closeout for the full picture, or the closeout and payouts workflow for the end-to-end recipe.
A six-step checklist on the gig’s Closeout tab that tracks the business back-half of an event: contract signed, quote approved, deposit received, invoice sent, payment received, and feedback logged. By default it’s tracking-only. If your organization turns on Enforce close-out gates (in organization settings), incomplete blocking steps lock Settle and Archive — and enforcement only applies to gigs created after it’s switched on, so existing gigs keep working as before.
Yes. Owners and admins can use Override & settle, which requires a logged reason so there’s a record of why the books closed early. Payout settlement is still required — the override skips the checklist, not the money.
Cancelled means the show was called off — the gig is preserved for your records but marked as never having happened. Cancelling is never blocked by the close-out checklist, because there’s nothing to close out on a show that didn’t happen.Archived is a legacy filing state you may still see on older gigs. Current gigs finish their life as Settled (or Cancelled); archiving is no longer part of the standard flow.
Open the gig’s status menu and choose Cancel gig. You’ll be asked to confirm — Soundcheck shows you what the cancellation affects first — and cancelling cannot be undone. Only Draft and Active gigs can be cancelled; a Completed or Settled gig has already happened, so cancel isn’t offered.
They receive a notification that the gig was cancelled. Any associated payouts that have not yet been initiated are stopped.