> ## 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.

# Call lists

> Saved team configurations with priority ordering for efficient gig staffing

> [!WARNING]
>
> There is **no** dedicated Call Lists page in the current web app. Do not look for a Call Lists tab or **+ Create Call List** control.

Roster templates live on the **Teams** tab or page (**+ New template**), for example **House Crew** and **Festival A-Team** with position rows. Saved teams come with Pro and above. To staff a gig from a saved roster, apply a **saved Team** from **Manage Team** (organizations on gig invitations), or use **Use a team** under **Crew** on the gig's **People** tab (organizations on crew staffing, including every new organization). On an empty Crew board the same action reads **Start from a template**.

![Team template editor with positions and the people who fill them](https://mintcdn.com/soundchecklive/EpuwxNqbqHAHt986/images/teams/call-lists-light.png?fit=max\&auto=format\&n=EpuwxNqbqHAHt986\&q=85\&s=327200ca44588a430227a895cb568001)

***

## What is a call list?

A **call list** (saved team) is a reusable lineup: which members to contact for each position, and in what order. **Call order** sets a primary assignee and backups, so if your first choice declines, you already know who's next.

**Example:**

```
Saved team: "Full Band - 5 Piece"
├── Lead Vocals
│   ├── Call Order 0 (Primary): Sarah
│   └── Call Order 1 (Backup): Jessica
├── Lead Guitar
│   ├── Call Order 0 (Primary): John
│   └── Call Order 1 (Backup): Marcus
├── Bass → Mike (Primary)
├── Drums → Dave (Primary)
└── Keys → Lisa (Primary)
```

When you apply a saved team to a gig, every list member not already on the gig is added: primaries land Invited, backups land Standby. Standby backups are not messaged at apply time. If a primary later declines, Soundcheck promotes the next standby to pending and notifies them.&#x20;

> [!NOTE]
>
> Call order and automatic promotion work for organizations on gig invitations (**Manage Team**). On crew staffing, **Use a team** creates **draft** shifts on the gig's Crew board, one per seat, covering every day of the gig. Nobody is notified until you send them, and nothing is promoted automatically: there's no call-order queue on crew offers. See [Finding crew](https://docs.soundchecklive.io/features/gigs/staffing/finding-crew.md).

***

## Why use saved teams?

Saved teams cut repeat work on gigs that use the same lineup shape.

**Priority order.** Call order 0 is your first choice; 1, 2, and so on are backups if someone declines.

**Speed.** Apply a saved team instead of rebuilding the same lineup by hand every time.

**Consistency.** Regular lineups keep the same positions and people across gigs.

**Less scramble.** When the primary can't make it, you already know who to try next.

***

## Two ways to apply a saved team

**From Manage Team**, applying a saved team populates the invitation flow, but you still choose who to invite and when to send:

**1. Open Manage Team**

On the gig, choose **Build team** (or **Manage Team**).

**2. Pick a saved Team**

Apply a saved **Team** preset from inside **Manage Team**. Positions and members populate from that preset.

**3. Adjust fees and details**

Set performance fees, fee notes, and any gig-specific instructions. Saved teams do not carry pay rates.

**4. Continue and send**

Choose **Continue** → **Review & send invites** → **Save & Send** when the lineup is ready.

> [!NOTE]
>
> On an active gig, **Save & Send** on **Review & send invites** is the step that notifies the crew. On a draft gig, invites go out when you publish it.

**From the Crew group of a gig's People tab**, choose **Use a team** to drop the whole roster onto the board as draft shifts instead. Nobody is notified. Review the roster, set fees, and send offers when you're ready. See [Staffing and shifts](https://docs.soundchecklive.io/features/gigs/staffing-shifts.md) for promoting a draft to a sent offer.

***

## Save a gig's staffing as a team

You do not have to build a saved team from scratch. On a gig whose Crew board already has shifts, choose **Save as team** in the Crew header. The team form opens pre-filled with one seat per position and whoever is on each shift (accepted first, then pending). See [Staffing and shifts](https://docs.soundchecklive.io/features/gigs/staffing-shifts.md#save-the-board-as-a-team-template).

## Understanding call order

### How call order works

| Call Order | Meaning | When to Contact |
| - | - | - |
| **0** | Primary choice | Always contact first |
| **1** | First backup | If primary declines |
| **2** | Second backup | If first backup declines |
| **3+** | Additional backups | Continue down the list |

### Example scenario

**Position: Lead Guitar**

* Call Order 0: John (Primary)
* Call Order 1: Marcus (Backup)
* Call Order 2: Chris (Second Backup)

**What happens:**

1. On apply, John is added as Invited (primary) and gets the invitation flow
2. Marcus and Chris are added as Standby (backups). They are on the gig; they are not messaged at apply time
3. If John declines, Soundcheck promotes the next standby (Marcus) to pending and notifies them. You do not have to promote by hand for that decline path&#x20;

***

## What gets applied

When you apply a saved team from **Manage Team** (organizations on gig invitations):

* All positions are added to the gig
* Every list member not already on the gig is added
* Primaries (Call Order 0) land **Invited** and get the invitation flow
* Backups (Call Order 1+) land **Standby**. They are not messaged at apply time. If a primary declines, the next standby is promoted to pending and notified
* Re-apply does not duplicate people already on the roster
* Positions appear in the saved team's order

The same apply path powers [MCP](https://docs.soundchecklive.io/integrations/mcp-server.md) `apply_calllist_to_event` (primaries `INVITED`, backups `STANDBY`).

### What you still need to set

Saved teams don't include (set per gig):

* Performance fees
* Fee notes or payment terms
* Gig-specific instructions

### Making adjustments

After applying a saved team, you can:

* Change individual assignments
* Add or remove positions
* Set performance fees
* Swap in a backup if needed
* Add notes and details

***

## Saved team examples

### Standard band configurations

**5-Piece Rock Band**

| Position | Primary | Backup 1 | Backup 2 |
| - | - | - | - |
| Lead Vocals | Sarah | Jessica | - |
| Lead Guitar | John | Marcus | Chris |
| Rhythm Guitar | Alex | John | - |
| Bass | Mike | Alex | - |
| Drums | Dave | Tyler | - |

**Jazz Quartet**

* Saxophone → Primary + 1 backup
* Piano → Primary + 1 backup
* Bass → Primary + 1 backup
* Drums → Primary + 1 backup

**Acoustic Duo**

* Vocals/Guitar 1 → Primary only
* Vocals/Guitar 2 → Primary + 1 backup

### Event-specific configurations

**Wedding Full Production**

| Position | Primary | Backups |
| - | - | - |
| Lead Vocals | Sarah | 2 backups |
| Guitar | John | 1 backup |
| Bass | Mike | 1 backup |
| Drums | Dave | 1 backup |
| Keys | Lisa | 1 backup |
| Sound Engineer | Tom | 2 backups |
| DJ | Chris | 1 backup |

**Festival Set**

* Full band positions with 2 backups each
* Full crew positions with 2 backups each
* Critical roles (Sound, Stage Manager) with 3 backups

### Crew-only saved teams

**Full Production Crew**

* Sound Engineer (FOH) → Primary + 2 backups
* Monitor Engineer → Primary + 1 backup
* Lighting Tech → Primary + 1 backup
* Stage Manager → Primary + 2 backups
* Backline Tech → Primary + 1 backup

***

## Best practices

### Create saved teams for common scenarios

Match presets to the gig types you run often:

* Weekly residency lineup
* Typical wedding configuration
* Festival full band + crew
* Stripped-down acoustic setup

### Set realistic backup depth

How many backups do you need?

| Position Criticality | Recommended Backups |
| - | - |
| Essential (vocals, drums) | 2-3 backups |
| Important (guitar, keys) | 1-2 backups |
| Flexible roles | 0-1 backups |

### Keep saved teams updated

When team members change:

* Update saved teams with new members
* Adjust call orders based on availability patterns
* Remove members who've left
* Add new reliable collaborators

### Use clear naming

Name saved teams so anyone in your organization understands:

* Include the configuration type
* Note the size or style
* Be specific enough to differentiate

**Good names:**

* "Wedding - 6 Piece with Horns"
* "Club - Standard Trio"
* "Corporate - Background Music Duo"

***

## Troubleshooting

### Saved team not showing members?

* Members must be part of your organization
* Removed members won't appear
* Re-open **Manage Team** and pick the preset again with current members

### Can't apply a saved team to a gig?

* Verify you have edit access to the gig
* Check that positions exist in your organization catalog under **Settings → Labels → Departments → Positions**

### Applied the wrong saved team?

* Remove assignments from the gig team
* Apply the correct saved team from **Manage Team**
* Or manually adjust as needed

### Backups not being contacted automatically?

Apply puts backups on the gig as **Standby**, so they are not messaged at apply time. That is expected. When an invited primary **declines**, Soundcheck promotes the next standby to pending and notifies them. You only need to promote by hand if you want a standby invited before anyone declines (or if there is no standby left).&#x20;

***

## Saved teams vs. manual assignment

| Scenario | Recommended Approach |
| - | - |
| Regular weekly gig | Saved team |
| One-time unique event | Manual |
| Similar events with same team | Saved team |
| Events needing many substitutes | Saved team (use backups) |
| New organization (few gigs) | Manual to start |
| Established operation (many gigs) | Saved teams for efficiency |

***

## Related guides

* [Positions](https://docs.soundchecklive.io/settings/team/positions.md): defining roles
* [Building Teams for Gigs](https://docs.soundchecklive.io/features/gigs/team-building.md): staffing events
* [Staffing and shifts](https://docs.soundchecklive.io/features/gigs/staffing-shifts.md): draft shifts, promoting to open, and offers


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.