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

# Offers and confirmations

> The full life of a crew offer: drafts, sending, every status, reminders, cancelling, replacing, offering a shift again, declines, what crew receive by email, SMS and push, answering without an account, and what to do about a no-show.

An offer is how a person gets booked. You build a shift, put people on it, and send it. Each person gets their own offer, answers for themselves, and you watch the shift fill. This page follows an offer from the first draft to the day it's done, including the parts that go wrong: declines, drops, and people who don't answer.

![Crew board in the Grid view with a row per position, each shift time and fee, and confirmed, pending and declined crew](https://mintcdn.com/soundchecklive/SK0diQsPrD96SAMt/images/staffing/crew-grid-light.png?fit=max\&auto=format\&n=SK0diQsPrD96SAMt\&q=85\&s=698e009f4c8aaaa85e62c2782676e65b)

> [!NOTE]
>
> This page assumes your organization staffs gigs with crew shifts. For how shifts are built (positions, days, call times, pay, **Need** and **Spots**), see [Planning crew needs](https://docs.soundchecklive.io/features/gigs/staffing/planning-crew-needs.md) and [How shifts work](https://docs.soundchecklive.io/features/gigs/staffing-shifts.md). For every control on the web board, see [The Crew board](https://docs.soundchecklive.io/features/gigs/people/crew-board.md).

## Why it works this way

Two rules shape everything below.

* **Nobody hears anything until you send.** A draft shift is yours alone. You can park crew on it, change the days, and throw it away, and no one gets a message.
* **What someone accepted doesn't move under them.** Once a shift is sent, its pay locks. A call-time change reaches everyone and lets anyone who already accepted hand the day back. See [Call times and messages](https://docs.soundchecklive.io/features/gigs/staffing/call-times-and-messages.md).

## The life of an offer

```
Draft ──Save & Send──▶ Open ──enough people accept──▶ Filled
                        │  ▲                            │
                        │  └──── someone drops off ─────┘
                        ├── deadline passes ──▶ Expired
                        └── you cancel ───────▶ Cancelled
```

The shift has a status, and so does every person on it. A shift can be **Open** while one person is **Confirmed**, another **Needs reply** and a third **Declined**.

## Draft, then send

**1. Build the shift**

Open the gig, choose the **People** tab, then **Crew**. Add a shift for a position and fill in **Days covered**, call times and pay. The sheet is headed **Create shift**: "Choose crew, days, rate, and call times before sending."

**2. Pick the people**

Choose from your members, or use **Add someone without an account** for a freelancer who isn't on Soundcheck. See [Finding crew](https://docs.soundchecklive.io/features/gigs/staffing/finding-crew.md).

**3. Save as draft, or review**

**Save as draft** parks the crew on the board. The sheet says so: "A draft notifies nobody — it parks the crew on the board until you send it." Otherwise continue to the review step, which shows each person's fee and any **Double-booking warning**.

**4. Send**

Choose **Save & Send**. The shift becomes **Open** and every person on it is notified.

When several drafts are waiting, a bar above the board says how many people are staged. **Send all** reviews and sends them together. **Discard all** throws them away, and nobody is told.

> [!TIP]
>
> Build the whole crew as drafts while the gig is still on hold, then send everything at once when the client signs. A draft shift never notifies anyone, even on a gig that is already published.

> [!NOTE]
>
> Crew offers don't wait for the gig to be published. If you send a shift on a draft gig, the crew are notified straight away. Only the Google Calendar invite waits for the gig to be published. Keep shifts as drafts until you're ready.

### Job offer or open shift

| | **Job offer** | **Open shift** (early access) |
| - | - | - |
| Who gets it | The people you picked | The people you picked |
| How it fills | Everyone can accept. It's filled when accepted crew reach **Need** and nobody is left to answer. | The first people to accept, up to **Spots**, are booked. |
| Unanswered when it fills | Not applicable | Go to **Standby** |
| Use it for | "I want these four people." | "I need two hands from these eight. Whoever's first." |

To make an open shift, tick **Open shift — first to accept** in the shift sheet. A draft can change type with **Switch to open shift** or **Switch to job offer**. Open shifts can only be created on the web.

> [!NOTE]
>
> **Early access:** Open shifts are rolling out gradually. Contact [info@soundchecklive.io](mailto:info@soundchecklive.io) to have them turned on. An open shift goes only to the people you put on it. Soundcheck doesn't have a public shift board that anyone can claim from.

## Shift statuses

| Status | What it means |
| - | - |
| **Draft** | Not sent. Nobody has been told. Days, people and pay can all change. |
| **Open** | Sent and taking answers. Pay is locked. |
| **Filled** | A job offer has the crew it needs with nobody left to answer, or an open shift is at capacity. It goes back to **Open** by itself if someone drops off. |
| **Expired** | The response deadline passed while the shift was still open. Nobody can answer it. A filled open shift never expires. |
| **Cancelled** | You called it off. Everyone still on it is told, and their unpaid payouts are voided. |

## Each person's status

| Status | What it means |
| - | - |
| **Needs reply** (**Pending** on the board filter) | Sent, no answer yet. Mobile managers see "Waiting on a reply". |
| **Confirmed** | They accepted. A positive fee becomes a payout. |
| **Declined** | They said no, or handed back a day. The seat is open again. |
| **Standby** | An open shift filled before they accepted. They're offered a spot automatically if one opens. |
| **Cancelled** / **Removed** | You took them off, or cancelled the shift. |
| **Draft** | On a shift you haven't sent. Mobile managers see "Draft — not sent yet". |
| **Not sent** | Added to a live shift and saved without sending. They have no offer yet. |

The board also shows delivery and availability badges beside people: **Not delivered**, **SMS ready** or **SMS unavailable**, **No account yet**, and the availability chips **Available**, **Asked**, **Unavailable**, **Hold**, **Paid hold** and **Booked**.

### Multi-day answers

On a shift with several days, crew answer day by day. Someone can take Friday and Saturday and pass on Sunday. In the app they choose **Choose days** ("Unchecked days will be declined."), or open the sheet "Respond to this offer" and pick **Accept all days**, **Decline all days**, or **Confirm N of M days**. Pay follows the days they accept. See [Pay and rates](https://docs.soundchecklive.io/features/gigs/staffing/pay-and-rates.md).

### Seeing who opened it

In the organization **Mailbox** (`/org-engagements`), each person on a thread shows **Opened** with the time they opened the offer email, or **Email bounced**. Treat a missing **Opened** as "unknown", not "unseen": Apple Mail's automatic opens are left out and some mail apps block tracking. See [Mailbox](https://docs.soundchecklive.io/features/engagements/overview.md#mailbox-admin).

## Deadlines

A shift can carry an optional response deadline. When it passes, Soundcheck closes the shift within about five minutes. Soundcheck doesn't send an expiry notice today to the people who were still pending or on standby. Crew see **Reply by** with the time on the offer, and **Reply window closed** after.

> [!NOTE]
>
> The web and mobile shift sheets don't have a deadline field. Set or extend a deadline through the [Soundcheck connector](https://docs.soundchecklive.io/integrations/mcp-server.md) (`save_crew_offer` with `expires_at`) or the API. Sending a shift whose deadline has already passed is refused: "The response deadline has passed. Extend it before sending."

## Reminders

Reminders are **manual only**. Soundcheck doesn't send automatic reminders for crew offers, so a shift nobody answers stays quiet until you nudge it.

| Where | How |
| - | - |
| Web board, everyone | When anyone hasn't answered, a bar says how many. Choose **Remind all pending**, then **Remind all** in "Remind everyone pending?". |
| Web board, some shifts | Select cells, then **Remind N shifts**. One person: **Send reminder** from their cell. |
| Mobile | **Manage shift** → **Remind N waiting**, a person's **Send reminder**, or **Send reminder to everyone pending**. The roster's **⋯** menu has **Remind all pending**. |
| AI connector | `send_reminder` |

A reminder only goes to people who haven't answered, and only on an **Open** shift. Reminders and new asks are held back on gigs that are closed, archived, cancelled, completed or settled.

> [!TIP]
>
> Soundcheck has no **Resend** button. To send an offer again to someone who hasn't answered, use **Send reminder**. To offer it again to someone who declined, use **Shift again** (below).

## When someone declines

A decline frees the seat, notifies you, and does nothing else. **Soundcheck doesn't move to the next person on a crew offer automatically.** There's no first call, second call queue that advances by itself on shifts. You pick the next person.

Fast ways to refill:

* Add the next person to the live shift in **Edit shift** (web) or **Add crew** (mobile) and send. Only the new person is notified.
* Send the shift to several people at once as an open shift, so the first to say yes takes it.
* On an open shift, people on **Standby** are offered the spot automatically when it opens: "A spot opened back up on this shift — first to accept wins."

> [!NOTE]
>
> Organizations still on the older invitation flow do get automatic backups: when the primary declines, the next backup in the [call list](https://docs.soundchecklive.io/settings/team/call-lists.md) moves from standby to pending and is notified. That only happens with invitations, not crew offers.

### Offering it again

If someone declined and changes their mind, open their cell on the web board and choose **Shift again** (or **Shift again for this day**, or **Shift again for all N declined days** on a multi-day shift). On mobile, tap them and choose **Shift again** or **Shift again for every declined day**. For someone on standby, the cell menu offers **Send invite**.

Someone you removed shows as **Removed** in the shift sheet with **Re-invite**. Saving re-sends the offer to them.

## When someone accepts, then can't make it

Crew can't quietly un-accept. In the app they choose **Can't make it** on the offer, pick the days on a multi-day booking, enter a **Reason (required)**, and choose **Withdraw** (or **Keep my spot** to back out). You're notified straight away, the seat opens, a filled shift reopens, and their unpaid payout for those days is voided.

## Recording an answer for someone

When a crew member says yes on the phone, you can record it. On the web, use "Accept for this day" or "Confirm all" on their cell. On mobile, tap them and choose **Accept**, **Decline** or **Accept every day**. Owners, Admins and Gig Coordinators can do this.

## Cancelling and removing

| You want to | Web | Mobile |
| - | - | - |
| Throw away a draft | **Discard draft**. Nobody is told. | **Discard draft** |
| Take one person off one day | **Remove from this day** | **Remove from this day** |
| Take one person off the shift | **Remove from shift**, or **Cancel shift…** on their row ("Cancel \[name]'s shift for this gig?", **Cancel shift** / **Keep shift**) | **Remove from shift** |
| Cancel whole shifts | Select them, choose **Rate or delete N shifts…**, then cancel ("Cancel N sent shifts?") | **Manage shift** → **Cancel shift** |
| Drop a position and its shifts | **Remove position…** on the position | |

> [!WARNING]
>
> Only an organization **Owner**, **Admin** or **Gig Coordinator** can cancel a sent shift or take crew off one. Drafts can be discarded by anyone who can edit the board.

What happens when you cancel or remove:

* The person gets a cancellation by their usual channels.
* Their **unpaid** payout is voided. A payout that's already paid or has a payment started is left for you to settle by hand.
* Anyone who had accepted comes off the gig's **calendar** for the days they accepted, and that shift's automatic availability block is removed. A day stays on their calendar when another shift on the same gig still books them for it.
* Removing someone from a live shift re-notifies the crew who remain, because the shift is rebuilt.
* On a gig that's completed and settled, nobody can come off until you **Reopen** it: "This gig is completed and settled. Reopen it to change who was on it."

## Replacing someone

Use **Swap for...** on the person's row on the web. Pick a member, or someone without an account. Soundcheck adds the replacement first, gives them the outgoing person's days, and then removes the outgoing person, so the seat is never empty. The toast reads "Swapped. The new person has the same days."

* The replacement gets a new offer. They still have to accept it.
* The outgoing person gets a cancellation.
* Swapping out someone who already **accepted** takes them off a sent shift, so it needs an Owner, Admin or Gig Coordinator. Someone still pending or on standby can be swapped by anyone who staffs the gig.
* The mobile app has no swap. Add the replacement with **Add crew**, then remove the other person.

For a replacement on the day itself, see [Day of show](https://docs.soundchecklive.io/features/gigs/staffing/day-of-show.md#replacing-someone-at-the-last-minute).

## What crew receive

Each person hears through the channels they've chosen for crew offers: **email**, **SMS** and **push**. Their own setting wins, then your organization's default, then on. See [Call times and messages](https://docs.soundchecklive.io/features/gigs/staffing/call-times-and-messages.md#notifications).

| Moment | What they get |
| - | - |
| You send a shift | The offer, with a link to answer |
| You send a reminder | A reminder, pending people only |
| You change the name, notes or call time | An update. A call-time change names the old and new windows. |
| You remove a day they held | A notice for those days |
| They accept | The shift goes on their calendar when your organization uses calendar sync, and you're notified of the answer |
| An open shift fills | Pending people move to standby: "This shift has been filled — you're on standby. We'll let you know if a spot opens up." |
| A spot opens | Standby people: "A spot opened back up on this shift — first to accept wins." |
| The deadline passes | Nothing is sent today. Tell anyone still pending yourself |
| You cancel | A cancellation |

**Email** is titled with the shift name, and also shows the gig title when it differs. It links to the offer and carries one-tap answer links. **Accept** and **Available** links answer straight away. **Decline** and **Unavailable** ask to confirm first.

**SMS** reads like: *"\[org]: \[title]. \[details]. Tap to respond: \[link] Reply YES \[CODE] or NO \[CODE]."* Crew can answer by replying `YES` or `NO` with the code. A code works for 30 days.

**Push** shows a short label (**Offer**, **Reminder**, **Updated**, **Cancelled**, **Filled**, **Spot open** or **Confirmed**) and opens the offer in the app's **Inbox**.

In the app's **Inbox**, the offer card shows **When**, **Where** and **Pay**, "Notes from \[org]" and "Venue details" before they answer.

## Answering without an account

Freelancers don't need a Soundcheck account to take a shift.

**1. Add them by name and email**

In the picker, choose **Add someone without an account**. Enter **First name**, **Last name** and **Email**. Add **Phone (optional)** and tick **Text them at this number** only if they agreed to texts.

**2. Send the shift**

When your organization can email people without an account, they get an email with a link: "Added. They have an email with a link." Otherwise Soundcheck refuses to add them to a sent shift, and on a draft they show **Not sent**. A text goes out only when you ticked the box: "Confirm your shift. No account needed: \[link]".

**3. They answer in the browser**

The link opens a page headed "You're on \[shift]" with the gig, venue, their sound check and special instructions. They choose **Accept** or **Decline** for each day, then **Send my answers**.

The page never shows pay. Links stop working once the shift is cancelled or the gig is over. If the person later signs up with the same email, the shift attaches to their account. See [Crew experience](https://docs.soundchecklive.io/features/gigs/staffing/crew-experience.md).

## Conditional answers and counter-offers

Soundcheck doesn't support conditional accepts ("yes if I can leave by 11") or rate counter-offers today. Crew can add a note when they answer ("Add a note (optional)"), and a declined invitation can carry a reason. To agree a different rate, talk to them, then remove and re-add them at the new fee while the shift is still unsent for them, or cancel and re-issue the shift.

## No-shows

Soundcheck doesn't have a no-show status or a no-show workflow. Nothing marks a person as a no-show, and there's no penalty or automatic backfill. Here's the best way to handle one:

**1. Fill the seat**

**Swap for...** the person who didn't arrive, or add a replacement. See [Day of show](https://docs.soundchecklive.io/features/gigs/staffing/day-of-show.md#replacing-someone-at-the-last-minute).

**2. Make sure they aren't paid**

Removing them voids their unpaid payout. If you use the time clock, they have no hours to approve, and the **Not in yet** count on **Crew hours** shows who never arrived.

**3. Keep a record**

Leave a low score and a note in the gig's Closeout **Team** review, and lower their **Rating** for that position on their profile. Or add a crew record field such as "No-shows" and update it. See [Reporting](https://docs.soundchecklive.io/features/gigs/staffing/reporting.md).

## Worked example: an AV company's corporate general session

A two-day corporate meeting needs an A1, a V1 and four stagehands.

1. On Monday you build three shifts as drafts: *A1 · GS* and *V1 · GS* as job offers to your regulars, and *Stagehands · Load-in* as an open shift with 4 **Spots**, sent to eight people.
2. The client signs Wednesday. You choose **Send all**.
3. Five stagehands accept within an hour. The first four are **Confirmed**; the fifth goes to **Standby** and gets the "filled" text.
4. Thursday, a stagehand chooses **Can't make it**: "family emergency". The shift reopens and the standby stagehand is offered the spot automatically.
5. Your V1 hasn't answered. You choose **Send reminder** on their cell. They reply `YES` with the code from the text.
6. Friday, the A1 declines day two. You add a second A1 for that day only and send. Only the new person is notified.

## Questions this page answers

* Can I send one offer to five people and take the first who accepts?
* Can I keep offers unsent while a gig is a draft?
* Can crew accept or decline from a text, without an account?
* Can crew accept some days of a multi-day gig?
* Does the offer show the rate, call time and location before they accept?
* Can I see who opened, accepted or ignored an offer?
* Can I set a deadline? Are reminders automatic?
* Does the next person get the offer automatically when someone declines?
* Can I cancel an offer, and is the person told?
* Can crew counter with a different rate?
* How do I handle a no-show?

More answers in the [Staffing FAQ](https://docs.soundchecklive.io/features/gigs/staffing/faq.md).

## Related

> [card] [Finding crew](https://docs.soundchecklive.io/features/gigs/staffing/finding-crew.md)
>
> Members, freelancers, availability checks and standby.

> [card] [How shifts work](https://docs.soundchecklive.io/features/gigs/staffing-shifts.md)
>
> Pay locks, Need, per-day answers, and editing a sent shift.

> [card] [Call times and messages](https://docs.soundchecklive.io/features/gigs/staffing/call-times-and-messages.md)
>
> Changing a call and who hears about it.

> [card] [Crew experience](https://docs.soundchecklive.io/features/gigs/staffing/crew-experience.md)
>
> The offer from the freelancer's side.


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