> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/run-your-studio/forms.md).

# Forms

Get student rosters and team lists from your accounts, with a deadline and a record of who has replied.

A form is how you get information back from an account: a roster, a team list, a head count, venue details. Instead of emailing and waiting for a spreadsheet, you send one link with a deadline and a record of who has responded.

This page is about forms on live jobs. For building them, see Form templates.

## How a form reaches someone

Forms are attached to an event template with a send date and a due date, both counted from the shoot date, and addressed to a contact role. Everyone at the account holding that role gets one.

The recipient gets an email with a link. Clicking it asks for their email address, which Schedulink checks against the contacts on that account. If it matches they're sent a one-time code, and entering it opens the form.

No login, no password, but the data is still protected: only someone already listed as a contact on that account can open it.

{% hint style="warning" %}
That means your contact records have to be right. If the person forwards the link to a colleague who isn't a contact on the account, the colleague can't get in.

If someone says the link doesn't work for them, see A form won't open.
{% endhint %}

## Reminders go out on their own

You don't have to chase. From the send date, Schedulink sends a reminder every three days until the form is submitted, up to five reminders.

Reminders stop when the form is submitted, when five have gone out, or when the due date passes, whichever comes first.

{% hint style="warning" %}
**One submission stops the reminders for everyone.**

If a form goes to five coaches and one replies, the other four stop being chased. So on a form where you need every recipient to respond, watch the submitted count rather than assuming the reminders are still working.
{% endhint %}

The first email and the reminders both carry the due date and the link, so a recipient never has to dig back through their inbox for the original.

## Filling one in over several sittings

A long roster doesn't have to be done in one go. Tell people to click **Save** as they work, and their answers are kept.

If they're away long enough for the form to time out, nothing saved is lost. They open the link from the email again, enter their address and the new code, and carry on from where they stopped.

Worth saying in your covering email: save as you go.

## Where things stand

Open an event and go to its Forms section. Each form carries a status.

| Status           | Colour | What it means                                                |
| ---------------- | ------ | ------------------------------------------------------------ |
| Waiting to send  | Amber  | The send date hasn't arrived yet                             |
| Sent             | Blue   | It's gone out and nobody has responded                       |
| X of Y submitted | Purple | Some contacts have responded, and the due date hasn't passed |
| Expired          | Red    | The due date passed with submissions still missing           |

Click the form and you'll see every contact it went to and what happened to each: when it was sent, whether it was delivered, and whether they submitted.

## Sending one by hand

Alongside the reminders, you can send a form yourself at any time. That's what you'll do when someone insists they never received it, or when the due date has passed and the link no longer works.

Open the event, find the form, and choose to send it. Pick a **role** and you'll see the contacts at that account who hold it, so you know you're sending to the right person rather than guessing from a list of everyone. Leave the role blank to see all contacts on the account.

Only contacts with an email address appear, since a form can't be sent to a phone number.

{% hint style="info" %}
Once a form expires the link stops working. Someone who left it late will need you to send it again before they can submit.
{% endhint %}

## Reading a submission

Open the event, go to the Forms section, and click the form to see everyone it went to. Click a contact who has submitted and their completed form opens, with every answer and any file they uploaded.

Whoever is set as the form's Employee to Notify gets an email each time one arrives, naming the event and the account, so nobody has to keep checking.

## Adding a form to a job

Most forms arrive with the event template. To add one to a particular job, use the Add option in the event's Forms section and pick a form template.

Adding a form template to an **event template** is different: it lands on every event using that template which isn't already complete, not just future ones.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://schedulink.io/help-center/run-your-studio/forms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
