> ## 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 schedule and details

> Send the gig's music schedule and details sheet as numbered versions, choose who gets what, collect confirmations, remind people, and read the send history.

The **music schedule** and the **details sheet** are PDFs Soundcheck prints from the gig itself: its run of show, music notes, venue logistics and contacts. You don't upload them. You choose who gets them, Soundcheck sends a numbered version, and each person confirms it or asks for changes.

![Send music schedule & details dialog with the documents to include, who gets them and the confirm-by date](https://mintcdn.com/soundchecklive/e-SmuOY4KzOPmXhu/images/documents/send-music-schedule-light.png?fit=max\&auto=format\&n=e-SmuOY4KzOPmXhu\&q=85\&s=b6a3d16f7388a5130aa215c7b8878ff8)

Use it when the band, vendors and planner all need the same printed plan, and you want to know who has read the latest version.

## Where to send from

On the web, any of these opens the same **Send music schedule & details** dialog:

* The gig's **Documents** tab: pick **Music schedule & details**, then choose **Send**.
* The **Sent** row in the setlist panel of the gig's **Run of Show** tab, with its **Send** button.
* **Actions → Send music schedule & details**, on gigs without a run of show section.

> [!NOTE]
>
> Sending needs permission to manage the organization's gigs and edit this gig. **Send** doesn't show on a draft, a template, or a past or archived gig. Publish the gig before you send. The dialog says **Publish the gig before sending documents.** otherwise.

## Send a version

**1. Pick the documents**

Under **Documents**, tick **Music schedule**, **Details sheet**, or both. Both start ticked. You must keep at least one.

**2. Set the printed status**

Under **Printed status**, choose **No status** (the default), **Prelim** or **Final**. It prints on the documents.

**3. Choose the options**

| Option | What it does | Starts |
| - | - | - |
| **Also text people with a phone** | Also texts crew who can get texts. Contacts, clients and people you add are never texted. With it off, crew who have no email still get a text. | Off |
| **Leave out surprise cues** | Leaves surprise cues out of this send, including its list of changes. | On when a client, gig contact or person you add gets the documents, off otherwise |
| **Treat no answer as approved** | Treats no reply by the **Confirm by** date as approval. It needs a date. | Off |
| **Confirm by** | The date you want **client** answers by. Clients see it in the portal, and it drives **Treat no answer as approved**. Crew, contacts and people you add don't see it. | Empty |
| **Message (optional)** | A short note at the top of the email, up to 1,000 characters. | Empty |

**4. Add anyone else**

Under **Also send to**, choose **Add person** and enter their **Email**, **Name** and an optional **Note**. You can add up to 50 people. Check each email: a send with a badly formed address is refused as a whole, so fix or remove that row.

When you send to someone you add, or to a gig contact, who isn't in your organization yet, Soundcheck adds them to your people list as a contact who hasn't signed up yet.

**5. Review who gets what**

The table lists each person with their **Role**, **Contact**, **Channel** (**Email**, **Text**, **Email + Text**, **Client portal** or **None**), the documents and charts they get, and a **Status**: **Will send**, **Portal only**, or **Skipped** with the reason. A line above it totals how many will send, how many are portal only, and how many are skipped. The table updates as you change anything above it.

Choose **Edit** on a row to change that person's documents, turn **Confirmation required** on or off, or add a **Note for this person**. Choose **Done** to close it.

**6. Send**

The button reads **Send to N people**, or **Share in client portal** when only portal rows are left. You see **Music schedule & details sent** and the version number when it's done.

> [!WARNING]
>
> **Sent** means the email or text provider accepted the message. It doesn't confirm delivery. If the gig or its people change while the dialog is open, Soundcheck says "The gig or its audience changed since you reviewed the plan. Review it again before sending."

After you send, Soundcheck prints the PDFs. If the gig changes before they're ready, that version fails with "The gig changed before the PDFs were ready", its history shows **PDFs failed**, and its version number is used up. Nobody is notified, so check the history after a send and send again if it failed.

Send isn't offered on a past gig on the web. You can't schedule a send for later, recall a version once it's sent, or send from the mobile app.

## Who gets what

| Person | How they get it |
| - | - |
| **Crew** on the roster or a shift | Email. Text too with **Also text people with a phone**, or when they have no email. Crew who declined, are on standby or were cancelled are skipped. |
| **Gig contacts** | Email. A contact whose role is planner or client gets the music schedule only, with no confirmation needed. |
| **Client approval** | Email to the client's portal address, or **Portal only** when there's none. Skipped when the client portal is off. Clients never get charts. |
| **People you add** | Email. |

Gig contacts and people you add get the documents by email with their own confirm link. They are saved as contacts, not added to your organization. A person you add whose email belongs to a signed-up member of your organization gets them as that member.

Someone listed twice with the same email gets it once. The second row reads **Skipped: Already listed**.

Other skip reasons you may see: **No email or phone**, **Excluded by you**, **No documents picked** and **Client portal is off**.

> [!NOTE]
>
> **Portal only** rows aren't emailed. Client contacts see these documents in the client portal. To give a planner access, invite their contact to the client portal from the client page. See [What clients see](https://docs.soundchecklive.io/features/client-portal/contracts-invoices-and-forms.md#music-schedule-and-details-sheet).

## What the details sheet includes

Crew and signed-up members of your organization get the full details sheet. Clients, gig contacts and other people you add get the client copy.

| Section | Crew | Client copy |
| - | - | - |
| Venue, parking and load-in | Yes | Yes |
| Dress and reminders | Yes | Yes |
| Day-of contacts | Name, role, company and phone | Name, role and company |
| Crew list, call times and special instructions | Yes | No |
| Gig notes | Yes | No |

The list of changes on the client copy and on the music schedule leaves out changes to the crew list and the gig notes.

## Charts

Each performer can get the charts assigned to them with the music schedule. In the **Charts** panel, pick a **Chart**, then a **Performer**, then choose **Assign**. To send a chart to someone who isn't on the gig, pick **Someone else, by email** and enter their **Email** and **Name**. Charts come from the chart files on the songs in the gig's setlist. Upload a chart to a song first if the panel says there are none.

## What people receive

**Crew, gig contacts and people you add** get an email from your organization's sending domain, with your branding. Its subject reads "\{title} · \{documents} (vN)". It carries the PDFs, your message, any note for that person, and a list headed **What changed since the last version**. Assigned charts are attached when each is 8 MB or less and the email stays under 18 MB; larger charts are listed as too large to attach, for download in the Soundcheck app. The button reads **Review and confirm** when a confirmation is needed, or **View the documents** when it isn't. The footer asks them not to forward the links. A text carries the gig, the date, the documents and the version, with links, in up to 320 characters. People with a Soundcheck account also get a push notification, "New \{documents} (vN)".

**Clients** get a different, shorter email titled **Music schedule approval** or **Details sheet approval**, with the PDF and a link to their portal. It doesn't include your message, the person's note, the list of changes, or the **Confirm by** date. If you need to tell the client something, email them yourself.

## What's in each document

Each version prints one PDF per document, and everyone who gets that document gets the same PDF. Pick per person which documents they get with **Edit** on their row. Pages are A4 and carry your organization's name, colors and logo (a PNG or JPEG logo prints; other formats are left off).

| Music schedule | Details sheet |
| - | - |
| **At a glance**: venue, status, version | **Venue** |
| **Changes since the last version** | **Parking & load-in**, with the load-in map when it's a PNG, JPEG or WebP image |
| **General information**: honorees, on-site and planner contacts, band leadership, guest count, parking, green room | **Crew**: every active crew member by day, with sound check, start and end times, position, name or company, and special instructions |
| **Sound and stage** | **Dress & reminders** |
| **Segments and times** | **Day-of contacts**: on-site and planner |
| **Run of show**, from the published run of show, with tentative cues marked | The gig's notes |
| **Requests**: must have, yes please, off-list, do not play, special songs, guidance | |
| **Reminders**, and what's still to confirm | |

The details sheet leaves out the venue's access code. To check either document before you send, open the export hub and download the **Music schedule** or **Details sheet** preview, marked "Preview (not sent)".

How people answer:

* **Crew, contacts and people you add** open the link and choose **Approve** or **Request changes**. On the gig's **Documents** tab on the web, and on the mobile card, crew can only **Confirm**; to ask for changes they use the email link or tell you. Links stop working 31 days after the gig.
* **Clients** review the version in the portal and choose **Approve** or **Request changes**. A note is required to request changes: "Tell the team what should change". They can change their answer until the version is locked.

When someone answers, your team is told by the form-response email. There's no push or in-app alert for **Changes requested**, so check the Documents tab.

## Versions and statuses

Every send is a new version. When you send again, older answers for the same document are marked **Superseded**, and the email lists what changed.

On the **Documents** tab, **Music schedule & details** has one row per person for their latest version, with a badge:

| Badge | Means |
| - | - |
| **Awaiting confirmation** | Waiting for their answer. |
| **Confirmed** | They confirmed. |
| **Deemed approved** | A client didn't answer by the **Confirm by** date and you turned on **Treat no answer as approved**. |
| **Changes requested** | They asked for changes. Their note shows on the row. |
| **Failed** | The message couldn't be sent. The error shows on the row. |
| **View only** | No confirmation was asked for. |
| **Superseded** | A newer version replaced it. |

A confirmed row also says how they answered: **Confirmed by link**, **Confirmed in app**, or **Approved in the client portal**. In the portal, clients see **Waiting for your review**, **Approved**, **Treated as approved**, **Changes requested** or **Replaced by a newer version**.

> [!NOTE]
>
> Treating no answer as approved applies to client approvals in the portal. Crew answers are never deemed approved.

## Remind people

Choose **Remind** on a row that's still waiting. Each crew member can be reminded once per version. A client can be reminded while they're waiting, and gets at most one reminder email a day. Until the PDFs are ready, **Remind** is refused with "The documents are not ready yet". Try again once the version shows **Ready**.

Soundcheck doesn't remind anyone on a schedule for the music schedule and details. Every reminder is one you send. An AI assistant [connected through MCP](https://docs.soundchecklive.io/integrations/mcp-server.md) can also send these reminders (`send_reminder`) and send a version (`send_gig_documents`). Its `hide_surprises` option works like **Leave out surprise cues** and has the same default when left out.

## Send history

The **Music schedule & details** card lists every version you sent, who confirmed, and who still needs a nudge. Each version shows its number, whether its PDFs are **Preparing PDFs**, **Ready** or **PDFs failed**, when it was sent, how many people confirmed, and, when a client was in the send, the **Confirm by** date ("Confirm by \{date}; no answer counts as approved." when you turned that on). **Show recipients** opens a table with each person's status, email and text status (**Not sent**, **Sending**, **Sent** or **Failed**), and their last activity. **Remind N unconfirmed** reminds everyone who can still be reminded.

## Related

> [card] [Run of Show](https://docs.soundchecklive.io/features/gigs/run-of-show.md)
>
> Where the music schedule's content comes from.

> [card] [Gig details acknowledgment](https://docs.soundchecklive.io/features/gigs/documents/acknowledgment.md)
>
> Ask crew to confirm the gig details in the app.


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