Set Lists
Set lists organize songs into a playable sequence for rehearsal, worship, or live performance.
Each set list has:
- a name
- an ordered list of songs
- a target key per song
- a capo value per song
Creating a set list
Go to Set Lists and click New Set List.
Enter a set list name, then save it.
After that, you can begin adding songs.
Adding songs
Inside the set list editor, use Add Song to open the song selection dialog.
For each entry, you can choose:
- the song from your library
- the target key
- the capo position
This lets one chord sheet be reused in different musical contexts.
Editing songs inside a set list
Each set list item supports actions like:
- Edit
- Duplicate
- Move up
- Move down
- Delete
This makes it easy to build alternate arrangements or repeated sections.
Reordering songs
Set lists support drag-and-drop ordering.
You can also move items up and down using the provided controls.
When you save, Team Chords stores the current order.
Empty-state behavior
If a set list has no songs yet, the editor shows an empty-state prompt encouraging you to add one.
This is a good time to confirm:
- the set list name is correct
- your library has the songs you need
- you want to use transposition or capo changes per song
Sharing and previewing
Saved set lists support:
- Copy Link — copies a shareable link
- Preview — opens the live/public view of the set list
This is useful for:
- rehearsals
- sending charts to teammates
- print preparation
- live display workflows
Saving behavior
When you save a set list, Team Chords:
- saves the set list metadata
- synchronizes the set list outputs/songs
- preserves ordering and song settings
If you create a brand new set list, the app saves the set list first and then creates the related outputs.
Good set list workflow
A reliable workflow is:
- create the set list
- add all songs
- set keys and capo values
- reorder the list
- preview the final result
- share or print when ready
Tips for cleaner set lists
- use clear names like
Sunday AM - May 10 - duplicate songs when you need the same chart twice in one flow
- use target key for the actual performed key
- use preview before sending the share link