Gigs overview
The whole gig lifecycle — pipeline, public request page, audience requests, post-show summary.
Gigs overview
A gig in Loadout is one event with one band, one date, one venue, one setlist. The same record carries you from the first lead through the post-show tip totals.
Open Gigs in the side nav. The list shows upcoming and past, filterable by status.
What a gig has
- Date, venue — when and where.
- Status — where in the pipeline this gig sits (inquiry → booked → confirmed → played, or cancelled).
- Times — load-in, start, end.
- Pay and deposit — what you're getting paid, what's been received.
- Setlist — the setlist attached to this gig.
- Public request slug — the URL the audience uses for requests.
- Notes — free-form text.
What you can do with a gig
- Move it through the booking pipeline — inquiry to confirmed.
- Turn on a public request page so the audience can request songs.
- Open the attached setlist on stage at gig time.
- Run a post-show summary — ratings, A/B comparisons, tips totals.
How gigs connect to the rest of the app
- Setlists — attach one setlist per gig. Open on stage from the gig page.
- Public band page — your band's public profile at
loadout.band/[bandSlug]lists upcoming gigs. - Audience requests — gigs with public requests enabled get a
/[bandSlug]/r/[gigSlug]URL the crowd hits with their phones. - Tips — every tip is attached to either a gig (with public requests enabled) or directly to the band.
What's next
- Booking pipeline — the status flow, finance tracking.
- Public request page — sharing the URL, slug behavior.
- Audience requests — how fans use it, how you manage the queue.
- Post-show summary — what to do after the gig.
Last updated: 2026-06-01