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

# Scheduling

Staff your week, publish it, and see who has accepted and who has turned up.

The Scheduling page is your team's calendar. It shows who's available, who's on what, who has accepted, and who has checked in.

It's the view for whoever builds the schedule. If you just want to know what you're working, use your dashboard instead.

## Day and Week views

Switch between the two in the view selector at the top.

**Week** is where you build. You can see the shape of the whole week, spot the day that's overloaded, and move people around before anyone hears about it.

**Day** is where you run a shoot day. It shows one day at a time, and everything on it is ordered the way the day actually happens:

* Events are sorted by start time, earliest first
* Employee rows follow the same order, so someone's position is set by their first job
* When a job needs three photographers, all three rows sit together at that job's place in the sequence
* Anyone with nothing on that day drops to the bottom

So reading the page top to bottom walks you through the day in order.

Your choice of view is remembered, and if you leave it on Day it opens on today.

## Availability comes first

Availability shows on the calendar as colour: **red for unavailable, green for available**. **If you see no colour-coding at all, the feature is switched off for your studio.** It's off unless a studio asks us to turn it on, because some would rather build the schedule themselves without staff marking themselves unavailable. If you'd like it on, get in touch and we'll enable it.

When it is on, **everyone is available by default**. You're only ever recording the time someone can't work, so you don't have to ask around before building a week. Whatever your team has told you is already on the calendar.

### Who sets what

**Employees set their own** from the availability panel on their dashboard, where they can enter one date range. That covers a holiday or a few days off.

**You set the rest.** Anyone with access to the Employees module can open a person's employee record and set more than one range, or a recurring pattern like every Monday and Tuesday through the autumn.

Two ways to get to that record. Go to **Setup > Employees** and open the person, or click their name on the Scheduling page, which takes you to the same place.

Whatever you set shows on their dashboard, so there's one version of the truth rather than two.

{% hint style="warning" %}
**There's one set of dates per person, and the last save wins.**

Setting availability on someone's record replaces whatever was there, including a holiday they entered themselves. It works the same in reverse: they can overwrite yours.

So check what's already there before you change it, particularly mid-season when someone may have booked time off you don't know about.
{% endhint %}

## Assigning people

You assign staff **on the event**, not here. Open the job, go to its Employees section, and add people against the roles the job needs.

Nothing reaches your team while you're doing this, so take the time to look at the whole week and check the load is spread sensibly before you publish.

To change someone's role after assigning them, open the event, find them in the Employees section, and choose **Modify**. You no longer have to remove and re-add them.

## Double bookings

Schedulink doesn't stop you booking someone twice. It tells you and lets you decide.

Assign someone who's already on another job at the same time, or on a day they've marked unavailable, and a **warning icon** appears next to their name in the event's Employees Assigned section. Click it to see the job they clash with, and click that job to go straight to it.

That's deliberate. Sometimes a clash is fine, because two shoots at the same school run back to back, or the times overlap on paper but not in practice. Blocking it would get in the way more often than it would help.

### Spotting clashes across the week

The warning sits on the event, so it only tells you about the job you're looking at. For the whole picture, use the Scheduling page.

Anyone with more than one job at the same time has a **small arrow next to their name**. Click it and their row expands into two or three, one per job, so you can see exactly what overlaps.

Worth running down the page before you publish. A clash you catch now is a conversation. A clash you catch on the morning is an unstaffed school.

### Fixing one

Open the event you want to move them off, remove them from Employees Assigned, and add someone else. The warning clears once the overlap is gone.

## Publishing

Publishing is what tells your team. Do it one event at a time, or publish the whole week in one click.

Every assigned photographer gets **one email and one text** covering everything they're on that week, with links to each job.

{% hint style="warning" %}
**Someone who hasn't accepted their invite gets neither.** They're on the schedule and they'll show as assigned, but no email and no text reaches them, because they have no account to send to.

Worth a glance at **Setup > Employees** before you publish a week. Anyone whose status isn't Active won't hear from you. See Employees.
{% endhint %}

{% hint style="warning" %}
**Changing a published schedule doesn't send another notification.** If you move a time or swap a photographer after publishing, nobody is told.

The new details are correct on their dashboard, so anyone who checks will see them, but assume they won't. Tell them yourself.
{% endhint %}

## Filtering by where people are up to

The status filter narrows the page to one stage of the process. Five states:

| Status      | What it means                                       |
| ----------- | --------------------------------------------------- |
| Pending     | Assigned, but they haven't accepted or declined yet |
| Accepted    | Confirmed, not yet on site                          |
| Declined    | They've turned the job down                         |
| Checked In  | On site now, hasn't checked out                     |
| Checked Out | Finished for that shoot                             |

**Pending** is what you filter to the day after publishing, to see who still hasn't answered.

**Declined** is what you check before a shoot week, because a decline nobody noticed is an unstaffed job.

**Checked In** is the one you'll use on a shoot morning. It answers who has actually arrived, without ringing anyone.

## On the day

Photographers check in and out from their own dashboard, more than once if a shoot has several sessions.

You see it happen on the Scheduling page in **Day view**. The event card picks up a checked in or checked out icon as each person arrives and finishes, so you can tell who made it to a school without calling anyone.

## Finding check-in times after the shoot

The times are kept, but they're not on the event.

Go to the **Scheduling** page, switch to **Day view**, and navigate back to the date of the shoot. Find the event card and hover over the checked in or checked out icon. The time shows in a tooltip.

{% hint style="info" %}
That's more work than it should be, and we know it. A proper place to see who was there and when, on the event itself, is something we're working on.
{% endhint %}

## Multi-day jobs

Staff are assigned per sub-event, so a job running Tuesday and Wednesday can have a different team each day. See Sub-events and your calendar.

## Jumping to a date

Click the calendar icon next to the date on the top bar, pick a date, and the calendar jumps straight there.


---

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