> 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/events.md).

# Events

Book a job, see everything about it in one place, and move it through its statuses.

An event is one job: a picture day, a graduation, a team shoot. It holds the schedule, the staff, the tasks, the forms and the emails for that job, so everything about a shoot sits in one record.

Every event belongs to an account.

## Finding an event

Click **Events** in the top menu. Three views are available from the top left:

**List** is the default table. **Calendar** lays jobs out by date, which is the fastest way to spot an overbooked week. **Map** plots them by location, useful when you're routing photographers across a region.

Filter by date range, status, event type, location or tag. A count under the list tells you how many jobs match. Schedulink remembers the view and the filters you chose, so if a job seems to be missing, clear your filters before assuming anything is wrong.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FW6FXbTQlyvUF31BEbcDE%2Fimage.png?alt=media&#x26;token=e0bbc6ce-a147-4def-a431-9254b4603596" alt=""><figcaption></figcaption></figure>

## Creating an event

Two ways.

**From the account.** Open the account and add the event there, and it's linked automatically.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FtwwHTx6OVt5B0j0ifiHe%2Fimage.png?alt=media&#x26;token=99317307-0d68-4852-adf3-4426a98210ce" alt=""><figcaption></figcaption></figure>

**From the Events list.** Click **Add**, top right, and choose the account as you go.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FJ7ibPj34ah879dvE0oSh%2Fimage.png?alt=media&#x26;token=4df96809-4c23-4acc-967d-891bfd9e0779" alt=""><figcaption></figcaption></figure>

Either way you'll then:

1. Pick an **event template**, which decides everything the job generates
2. Choose the **account**
3. Choose the **event type**
4. Set the **start and end date**
5. Pick a **location** from the account's saved addresses, or enter a new one
6. Fill in any **custom fields** the template asks for, like setup time or expected head count

Save, and the event is created in **Planning**. Its tasks, emails and forms all generate at once from the template.

## Event statuses

Status isn't just a label. It decides whether emails go out, whether the job reaches your calendar, and whether your team hears about it.

| Status      | What it does                                                                                                  |
| ----------- | ------------------------------------------------------------------------------------------------------------- |
| Planning    | Where every event starts. Nothing sends, nothing syncs                                                        |
| Scheduled   | Automated emails begin, and the job pushes to Google Calendar or Outlook if a calendar is set on the template |
| Published   | Sends a text and an email to every assigned employee                                                          |
| In Progress | Set automatically on the day of the event                                                                     |
| Complete    | Set automatically once every task is done                                                                     |
| Cancelled   | Stops emails and removes the job from your calendar                                                           |

You can set any of them by hand. In Progress and Complete are the two that also happen on their own.

{% hint style="warning" %}
**Emails don't send from Planning.** If an account says they never got the confirmation, check the status before checking anything else.

**Publishing tells your team immediately.** Don't publish a job whose staffing might still change, or your photographers get a second message when it does.
{% endhint %}

## What's on an event

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FePyMmJfD3bQV7rByAc7a%2Fimage.png?alt=media&#x26;token=bf62bb39-7b87-4b98-8875-28b6047739fd" alt=""><figcaption></figcaption></figure>

### Event information and custom fields

The date, time, location and status, plus the answers your team gave at booking. Those custom fields aren't just for reference: anything captured here can be dropped straight into an automated email.

The account name in the header is clickable, and opens the account in a slide-in drawer so you can check a phone number or an address without losing your place.

### Tasks

Generated from the template, and editable at any time. Each shows its name, who it's assigned to, and its due date counted from the shoot date.

Click a task to see its steps or change its status. Click **Add Task** to create one that isn't in the template.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FAGDXsFXRo0F70Lb4YxBG%2Fimage.png?alt=media&#x26;token=89d23935-33a1-4c20-b650-df91c36108a1" alt="" width="563"><figcaption></figcaption></figure>

### Emails

Each email carries a status, so you can see where it stands without opening it.

| Status           | What it means                                                      |
| ---------------- | ------------------------------------------------------------------ |
| Waiting to send  | The send trigger hasn't fired yet                                  |
| Sent             | It's gone out, with no deliveries confirmed                        |
| 3 of 5 delivered | At least one has been confirmed as delivered, and this is how many |

Click **Preview** to see the drafted message with the account name, dates and custom fields already filled in. Send it early if you need to, or send yourself a test first. When you send by hand, the contact selection field lists every contact on the account, not only the ones attached to this job, so you can include someone for a one-off without editing the event.

Click an email after it's gone to see, per contact, whether it was sent and whether it was delivered.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2Fnt6BnYMtFKHcXKze3sZv%2Fimage.png?alt=media&#x26;token=361c840d-c5df-41ec-b101-b79fec106a63" alt=""><figcaption></figcaption></figure>

### Forms

Each form carries a status badge, so you can see where it stands without opening it: **Waiting to send**, **Sent**, **3 of 5 submitted**, or **Expired**.

Click a form to see every contact it went to, whether it was delivered, and who has submitted. Click a contact who has submitted to read their answers and download anything they uploaded. See Forms.

### Employees

Two halves. **Employee requirements** say how many of each role the job needs, like two photographers and a driver, and they come from the template. **Employees assigned** are the actual people.

Assigning someone puts the job on their scheduling calendar and on their dashboard.

To change someone's role, use **Modify** on their row. The dialog you used to add them reopens with their details filled in, so you don't have to remove and re-add them.

A warning icon next to someone's name means they're already booked elsewhere at that time, or the day is marked unavailable. Click it to see the clash. Schedulink warns rather than blocks, so it's yours to judge. See Scheduling.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2Fh5lpE5MwpccI5NJP3MtN%2Fimage.png?alt=media&#x26;token=97c5228a-b5b0-476f-bb24-86715e19ef14" alt="" width="563"><figcaption><p>Requirements first, then the people who meet them.</p></figcaption></figure>

### Contacts

The people at the account tied to this particular job. **Modify** works here too, so you can change a contact's details on the event without removing them.

Automated emails go to contact roles rather than to names. Whether Schedulink falls back to the account's contacts when nobody on the event holds the role depends on a setting in **Setup > Organization**, so check there if an email didn't reach anyone.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FFnfuAlVJJ8uwXcZOMrpC%2Fimage.png?alt=media&#x26;token=b37a3470-3d08-4405-b520-22c6614468ec" alt=""><figcaption></figcaption></figure>

### Attachments, notes and the activity log

Attachments hold contracts, floor plans and style guides. Notes are for your team, and you can pin the important ones or tag a colleague to notify them. The activity log records every change and who made it.

<figure><img src="https://3879395831-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHDjrFxlBUXo6RKGvSV8g%2Fuploads%2FIYaji1JXl9zR404gN8jm%2Fimage.png?alt=media&#x26;token=f06f15dc-db2e-4541-a8b2-1647e2ef664e" alt=""><figcaption></figcaption></figure>

## The job sheet

Open the event, click the **three dots** at the top of the page, and choose **Generate PDF**.

Schedulink builds a job sheet from that event: the details, the contacts, the assigned staff and the notes. That's what your photographers carry on the day, and some studios call it a job card.

The same option exists on accounts and tasks, giving you a PDF of that record rather than a job sheet.

## Multi-day jobs

A job running across several days doesn't need several events. See Sub-events and your calendar.

## Getting jobs onto Google Calendar or Outlook

Connect a calendar in **Setup > Integrations**, then choose which calendar each job type uses on its event template. Jobs sync when they reach Scheduled, not when they're created.


---

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