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

# Forms on a gig

> Send portal forms from the gig Documents tab, follow who has answered, remind, copy a link, fill in answers for a client, change the deadline, and read responses.

Forms are the questionnaires and feedback forms you build once in your organization's library and send for a gig. The gig's **Documents** tab is where you send them and where every answer for that gig shows up.

![Send a form dialog for a gig with the forms you can pick and the Create a form option](https://mintcdn.com/soundchecklive/e-SmuOY4KzOPmXhu/images/documents/send-form-light.png?fit=max\&auto=format\&n=e-SmuOY4KzOPmXhu\&q=85\&s=48f0e743380386a1f26d05f9a221dd61)

> [!NOTE]
>
> Forms are in early access with the client portal, and rolling out to organizations now. To get them, email [info@soundchecklive.io](mailto:info@soundchecklive.io). You build them in **Documents → Forms**. See [Portal forms](https://docs.soundchecklive.io/features/gigs/documents/portal-forms.md) for building, templates, plan limits and activating a form.

Your plan sets how many forms can be active at once: 10 on Starter and Pro, 25 on Team, and no limit on Enterprise. At the limit, Soundcheck shows "Your plan includes N active forms. Hide a form or upgrade your plan to add more."

## Send a form for a gig

**1. Open the Forms list**

On the gig's **Documents** tab, pick **Forms**, then choose **Send**.

**2. Pick an activated form**

Only activated forms can be sent. **Create a form** in the same flow offers the starter templates and a blank form. The form you activate is picked for this send. Drafts can't be sent, so this path has no **Save draft**.

**3. Set a deadline (optional)**

**Deadline** sets the form's due date. Leave the default (**No deadline**, or **Until the gig is over**) to allow changes until the gig is over. The due date is the end of that day in the gig's time zone, and it's also the last day the respondent can change their answers after they submit.

**4. Set reminders (optional)**

Under **Reminders**, turn on **Remind before it is due** and set **Days before it is due** (1 to 30). Turn on **Remind when overdue** and set **Days between overdue reminders** (1 to 30) and **Most overdue reminders** (1 to 10). Reminders need a deadline. Soundcheck checks for due reminders every hour.

**5. Email the recipient**

**Email \{name}**, or **Email each recipient** when you send to several people, is ticked by default. Each row shows how it will arrive:

| Hint | Means |
| - | - |
| **Portal email** | A client contact who can use the portal gets an email whose button opens **Forms** in their portal. |
| **In their portal** | The form waits in their portal. |
| **In-app + email** | A Soundcheck user gets a **Form request** in their web inbox and a link email. |
| **Link by email** | Anyone else gets an email with a personal link to the form. |
| **No email · copy the link after** | Nothing is emailed. Use **Copy link** on the row. |

You can send a form to a client (optionally to one contact), any contact, a member of your organization, crew on the gig, or an email address. A client always needs a gig. Sending to an email address that isn't in Soundcheck yet adds them to your people list as a contact who hasn't signed up yet. One form can go to the same person once per gig.

If the client has no contact who can use the portal, the form is still assigned, no email goes out, and Soundcheck tells you so. Invite them to the portal, or use **Copy link**.

The assignment email's subject reads "\{org} sent you a form: \{title}" and says "This link is just for you, so please do not forward this email." Forms go by email only. Soundcheck doesn't text or push them.

## The Forms list

**Forms** lists every form sent for this gig, to anyone. That includes a form sent to someone not listed on the gig, and a response that reached the gig without an assignment. Each row shows the form, who it went to, whether they're a client, contact or crew, and when something last happened. Rows still waiting sit first.

| Status | Means |
| - | - |
| **Sent** | Not opened yet. |
| **Viewed** | Opened, not submitted. |
| **Overdue** | The deadline passed without a response. |
| **Submitted** | They answered. |

## Row actions

Open a row's menu for what you can do next. The menu depends on the status.

| Action | When | What it does |
| - | - | - |
| **View response** | After a response | Opens the answers. |
| **Remind** | While waiting | Emails a reminder to the same place the form went: the contact it was addressed to, the client's portal contact, or the crew member's link email. The subject reads "Reminder: \{org} is waiting on a form: \{title}". Each confirmation sends one more email. There's no cooldown. |
| **Copy link** | Any time it can be shared | Copies the personal link for that assignment. Anyone who opens it answers as that recipient. |
| **Staff fill** | While waiting | Enter answers for the client, such as a music request list taken on the phone. The client isn't notified. |
| **Edit deadline** | Before and after a response | Opens **Editable until** to change or clear how long answers can be changed. It doesn't change the due date or its reminders. |
| **Remove** | Before and after a response | Removes the assignment and turns its link off. A response already submitted stays on record. |

> [!WARNING]
>
> Share a copied link only with that recipient. Removing the assignment, or archiving the form, turns the link off. A link for a gig form stops working 31 days after the gig ends, and then reads "This form link is not valid anymore."

## How answers can change

After submitting, the client sees **Response received** and can choose **Edit answers**.

* With a deadline, they can change answers through that day.
* Without one, a form for a gig can be changed until the gig is over.
* A form sent without a gig never locks.
* Days are read in the gig's time zone.
* Your team can always change answers with **Staff fill**.

After that, the form shows **Response received** without **Edit answers**. To collect a fresh response, send the form again.

## Forms for crew

Forms sent to crew are listed here too, and they also show on each person's row in the **Crew** group of the gig's **People** tab. Crew answer through the assignment email link. On the gig's **Documents** tab on the web, their own row shows **Fill** until they answer and **View** after. Forms can't be filled in the mobile app; crew open the email link or the web.

## Your team is notified

When the first response comes in, Soundcheck emails "\{name} submitted \{title}", with a link to the gig's forms:

* to the team member who sent the form, when they can manage the organization's gigs;
* otherwise, such as when Finance sent it, to your organization's email, or the owner when there's none.

Changed answers and **Staff fill** don't send another email. Check the row for the latest answers. Each person can turn the email off with **Form responses** in the **Notifications** section of their **Settings** page.

## Where answers show up

* The form's row on the **Documents** tab (**View response**).
* The person's row in the **Crew** group of the **People** tab, for crew.
* The **Form responses** CSV in the gig's export hub.
* The **Music requests** panel on the **Run of Show** tab, for forms with a **Song list** question.

## What forms can't do today

* Show or hide questions based on earlier answers. A question can only become required when an earlier choice is picked (**Required when**).
* Let the respondent upload a file, take a payment, or save a draft.
* Prefill answers from the gig or the client.
* Run as a public or embedded form on your website.
* Be edited once published. Send a new form instead.

## With an AI assistant (MCP)

An AI assistant [connected through MCP](https://docs.soundchecklive.io/integrations/mcp-server.md) can list, create from a template, publish and delete forms, send a form for a gig (`create_form_assignment`), read and save music requests, change answers, and change **Editable until**. Apart from music requests, it can't read submitted answers. It also can't remind, remove an assignment, copy a link, or add custom questions.

## Who can do what

* **Send, remind, copy links, fill in, change deadlines, remove, read**: people who can manage clients (Owner, Admin, Gig Coordinator, Finance, or anyone given client access). Someone who leads a gig without client access doesn't see its forms.
* **Answer**: the recipient, through their portal, their link, or the **Fill** button on the web.

## Related

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

> [card] [What clients see](https://docs.soundchecklive.io/features/client-portal/contracts-invoices-and-forms.md#filling-out-forms)
>
> How clients fill out a form in the portal.


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