Setlists overview

A setlist is an ordered list of songs (and breaks) for a specific gig. The stage view runs from a setlist, audience requests attach to a setlist, the post-show summary scores a setlist.

The setlists grid

Open Setlists in the side nav. The grid shows everything your band has built, filterable by:

• All — everything.
• Regular — actual gig setlists.
• Templates — saved patterns you clone for new gigs (see Setlist templates).

Each row shows the setlist name, song count, total duration, and a Template badge when applicable. Click a row to open the builder.

[screenshot: setlists grid with filter chips]

What a setlist contains

• Name — the gig name works well (Saturday at The Press Box).
• Target duration — optional. Drives the over/under indicator in the builder.
• Items — ordered list of songs and breaks. Each song row supports per-gig overrides (key, notes).
• Template flag — marks the setlist as a reusable pattern.

Lifecycle

A typical setlist lives through three states:

1. Draft — you're still adding/reordering. Autosaves as you work.
2. Ready — you've sent the link to bandmates, they've reviewed it.
3. Live — opened on stage at the gig.

Loadout doesn't enforce these states — there's no draft/ready/live flag. The "states" are just where you are in your workflow. The builder is the same screen the whole way through.

Where setlists connect

• Songs — pulled from your library. You can't add a song to a setlist unless it's in the library first.
• Gigs — attach a setlist to a gig so the audience-request page can show "tonight's set."
• Stage view — hit Open on stage to start a live session against this setlist.

What's next

• The setlist builder — drag, drop, search, the per-gig overrides.
• AI setlist generator — describe the gig, draft a list.
• Set breaks — break rows between sets.