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

# Music requests

> The client's must-play, yes, off-list and do-not-play songs: the Music requests form in the client portal, requests your team enters, library matches, and do-not-play warnings in the run of show.

Music requests are what the client wants to hear, and what they never want to hear. They come in from the client portal or from your team, and they sit right below the gig's sets so the band can check one against the other.

![Music requests panel with must-play, yes, off-list and do-not-play songs, their library matches and a do-not-play warning](https://mintcdn.com/soundchecklive/DQsOfwUk5leizXB5/images/run-of-show/music-requests-light.png?fit=max\&auto=format\&n=DQsOfwUk5leizXB5\&q=85\&s=da78edf65dcd06280a7bd10fbf6433fd)

## The four categories

| Category | Means |
| - | - |
| **Must play** | Play it. |
| **Yes** | Happy to hear it. |
| **Off-list (to learn)** | Not in your repertoire yet; the band would need to learn it. |
| **Do not play** | Never play it. |

A request can be about a **Song**, an **Artist** or a **Genre**. A request can also name a moment: **First dance**, **Parent dance**, **Last dance**, **Grand entrance**, **Ceremony** or **Other**. **Do not play** requests don't take a moment.

## Where requests come from

### The client form

Send the client the **Music requests** form from the gig's **Forms** (on the gig's **Documents** tab). The client fills it in from the [client portal](https://docs.soundchecklive.io/features/client-portal/contracts-invoices-and-forms.md): a song list with must-play, yes, off-list and do-not-play rows, plus the genre and era guidance.

On the song list, each row has a category, an optional moment, and notes. The client can paste a title–artist list and check every row in a preview before it's added. A list never holds the same song twice.

When your team builds the form, **Songs the client picks from** sets where songs come from:

| Option | The client… |
| - | - |
| **Client types any song** (the default) | Types titles. |
| **Songs of the acts on the gig** | Picks from the songs tagged to the gig's acts. |
| **Songs of one act** | Picks from one act's songs. |
| **Songs I pick** | Picks from a list you choose. |
| **Whole song library** | Picks from your whole library. |

While **Let the client add a song that isn't on the list** is on (the default), the client can also choose **Something else…** and type a song. See [Portal forms](https://docs.soundchecklive.io/features/gigs/documents/portal-forms.md).

### Requests your team enters

Requests that come in by email or phone can be entered by your team. Owners, admins, finance members and gig coordinators choose **Add request** on the music requests panel, then set:

* the **Request** category,
* whether it is **About** a song, artist or genre,
* the song, picked **From your library**, or typed in under **Not in the library? Type it**,
* who it was **Asked by**: **Client**, **Planner**, **Talent** or **Our team**,
* an optional **Moment**, such as *First dance* (not offered for **Do not play**),
* notes.

They can edit a request or remove it from its row. **Remove request** takes it off the music requests and out of the setlist picker. Team-entered requests show on the panel even when your organization doesn't use client forms.

To change the client's form answers for them, such as a list taken on the phone, choose **Edit answers** on the panel and **Save on behalf of client**. The client isn't notified.

### Show packets

Soundcheck doesn't read music requests out of a planner's show packet today. When a packet arrives as a document, enter its requests on the panel yourself, or use **Edit answers** to fill in the client's form for them.

## The music requests panel

The panel sits below the sets on the gig's run of show **Setlist** view, under **Music notes**. It shows:

* counts per category, and the notes,
* each requested song's library match: **In library**, **Possible match** or **Not in library**,
* who asked, such as *Asked by planner*,
* how long the client can still change the form: *Client can edit until* a date, *Client can edit at any time*, or *Locked. Client can no longer edit.*

With no requests yet, it reads: "No music requests yet. Add requests that came by email or phone, or send the Music requests form from the gig's Forms section."

### Do-not-play warnings

When a run-of-show song matches a do-not-play request, the panel warns: "A run-of-show song matches a do-not-play request." Warnings never block a save, so you can still keep a song on purpose.

A do-not-play request about a genre can't be checked against the library, and the panel counts how many of those there are.

> [!NOTE]
>
> Library matching is unavailable when the song library holds over 5,000 songs. The panel says so.

### Requested songs in the picker

When you add songs to a set in the run of show, requested songs are pinned in the song picker with their category, such as **Must play** or **Do not play**.

## On mobile

The mobile app shows the same panel, read-only. Add and edit requests on the web.

## Related

> [card] [The Setlist view](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/setlist-view.md)
>
> Where the panel lives.

> [card] [Client portal forms](https://docs.soundchecklive.io/features/client-portal/contracts-invoices-and-forms.md)
>
> How the client fills in forms.

> [card] [Portal forms](https://docs.soundchecklive.io/features/gigs/documents/portal-forms.md)
>
> Build and send forms.


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