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

# Gig details acknowledgment

> Ask crew to confirm they've seen the current gig details, follow who has acknowledged on the Documents tab, and send again when the details change.

**Gig details acknowledgment** asks crew to confirm they have seen the current version of their gig details: call times, schedule, assigned flights, lodging, and the listed shared gig files. It's one of the kinds on the gig's [Documents](https://docs.soundchecklive.io/features/gigs/documents.md) tab.

![Gig details acknowledgment panel with the Send to crew button above the details crew confirm: dates, venue, notes and the schedule](https://mintcdn.com/soundchecklive/e-SmuOY4KzOPmXhu/images/documents/acknowledgment-light.png?fit=max\&auto=format\&n=e-SmuOY4KzOPmXhu\&q=85\&s=809ad592b03107da86e987f3644564bb)

Use it when you need proof that each person read the plan, for example before a load-in with an early call or after you changed the hotel.

## What crew acknowledge

| Included | Not included |
| - | - |
| Gig status, dates, times and call times | Other musicians' private travel details |
| The published run of show for their positions, and the schedule | Structured travel prices |
| Their assigned flights and lodging | Run of show changes not published yet, items for other positions, and surprise cues |
| Venue logistics, including the venue access code | The contents of each file. Acknowledgment covers the listed file details, not what's inside each file. |
| Gig contacts, with their contact notes | |
| Show notes, crew requirements, stage, gear and custom sections, and gig notes | |
| The list of shared gig files: name, description and when it changed | |

> [!WARNING]
>
> Keep confidential financial terms out of shared notes and files, and write gig contact notes you're happy for crew to read. Crew acknowledge what's in them.

Only crew on the gig who have a Soundcheck account can be asked. Crew without an account don't get it; use the [music schedule and details](https://docs.soundchecklive.io/features/gigs/documents/music-schedule-and-details.md), which works by email link.

## Send it

Publish the gig first. You can't send the details for a draft.

**1. Open the acknowledgment panel**

On the web, open the gig's **Documents** tab and pick **Gig details acknowledgment**, then choose **Send**. You can also open the **Crew** group of the gig's **People** tab, choose **More staffing actions** (⋯), then **Gig details acknowledgment**. Both open the same side panel. If the gig has no **Crew** group, managers find the same card on the **Overview** tab.

**2. Check each person's status**

The panel lists each crew member with a status, such as **Not sent**, **Acknowledged**, or **Details changed since they acknowledged**.

**3. Send**

Choose **Send** or **Send again** on one row, or **Send to crew** for everyone who hasn't acknowledged the current details. Soundcheck skips anyone who was sent them in the last 24 hours.

Each send puts a **Gig details** item in the crew member's Mailbox. It also goes by email ("Please review your gig details: \{title}") or push when their gig-change preferences allow it. Soundcheck confirms with "Sent. It is in their Soundcheck inbox, and they get an email or push if they have those turned on." It's never sent by text, has no due date, and isn't reminded on a schedule.

On a draft gig, Soundcheck says "Publish the gig before sending it for acknowledgment."

## Follow it on the Documents tab

Once you've sent the details to anyone, the **Gig details acknowledgment** list on the **Documents** tab has one row per crew member. Before that, it reads that the gig details haven't been sent for acknowledgment yet.

| Badge | Means |
| - | - |
| **Acknowledged** | They confirmed the current details. |
| **Awaiting review** | You sent the details and they haven't acknowledged yet. |
| **Details changed** | They acknowledged an earlier version. The details changed since then. |
| **Not sent** | Nobody sent them the details yet. |

**Open** on a row opens the same side panel. Use the **Crew & team** and **Awaiting** filters to narrow the list. See [The Documents tab](https://docs.soundchecklive.io/features/gigs/documents/documents-tab.md#filter-the-list).

## What crew do

On the web, crew choose **Review details** on the Mailbox item. They can also acknowledge from the card on the gig's **Overview** tab, or from the gig's **Documents** tab, where their row shows **Acknowledge** until they do and **View** after. In the mobile app, they tap the Mailbox item to open the review sheet. The item stays in their Mailbox until they acknowledge or the gig ends. Acknowledging needs a connection. On the web, crew confirm **I have reviewed these details and gig files**; a row they already confirmed reads **Already acknowledged**.

If the details changed while they were reading, Soundcheck says "Details have changed. Review the latest version before confirming." In the app, a lost connection shows the same **Details changed** message, so they reopen the sheet and try again once they're back online.

## When the details change

Each person's details are versioned on their own. Any change to what they acknowledge creates a new version: the gig's status or times, call times, the run of show, their flights or lodging, venue logistics, gig contacts, notes, gear, custom sections, or the list of files. The panel then shows **Details changed since they acknowledged**.

* Crew aren't asked again until a manager sends the details again.
* Earlier receipts remain on record.
* If the details return to exactly a version someone already acknowledged, that acknowledgment applies again.

> [!TIP]
>
> After a big change, filter the list to **Awaiting**, check who's left, then use **Send to crew**. People who already acknowledged the current version aren't sent it again.

## Who can do what

* **Send and follow**: people who manage the organization's gigs.
* **Acknowledge**: the crew member it was sent to.

Acknowledgment isn't available to AI assistants connected through MCP today. Acknowledging part of the details, or a section at a time, isn't available either.

## Related

> [card] [Documents](https://docs.soundchecklive.io/features/gigs/documents.md)
>
> Every kind on the gig's Documents tab.

> [card] [Music schedule and details](https://docs.soundchecklive.io/features/gigs/documents/music-schedule-and-details.md)
>
> Send the printed schedule and details sheet for confirmation.


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