> 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/sub-events-and-your-calendar.md).

# Sub-events and your calendar

You need sub-events to put photographers on a multi-day job. How they work, and why the parent leaves your calendar.

**A job that runs across more than one day can't have photographers assigned to it.** Not until you add sub-events.

If you've booked a two-day shoot and you're trying to work out why you can't put anyone on it, that's the answer. The event itself has no Employees section to use. Staff go on the days, and the days are sub-events.

So the sequence is:

1. Create one event for the job
2. Add a sub-event for each day
3. Assign photographers on each sub-event

That holds even when the same photographer works every day. Sub-events aren't only for splitting a team, they're how a multi-day job gets staffed at all.

## What a sub-event is

One day of a multi-day job. Shooting a school on Tuesday and Wednesday means one event with two sub-events: the event holds the job, the sub-events hold the days.

Tuesday's crew and Wednesday's can be completely different, which is the reason most studios reach for them.

## What happens when you add one

Adding a sub-event changes the parent. It becomes a **group event**, which means it's now a container for its days rather than a job in its own right.

The consequence catches everyone out: **the parent stops appearing on your calendar, and only the sub-events show.** So a two-day shoot gives you two calendar entries, not three.

That's deliberate. The parent has no single date to sit on once it spans several days, and showing it alongside its own sub-events would double-book the week.

{% hint style="info" %}
If a job vanished from your calendar after you added a sub-event, this is why. Look for the sub-events instead, and the parent is still there in your Events list.
{% endhint %}

## Assigning staff

Open the sub-event for the day you're staffing and assign people in its Employees section.

Assigned days show on the Scheduling page and on each photographer's dashboard as separate entries, so someone working both Tuesday and Wednesday sees two jobs rather than one long one.

## Three ways to create sub-events

### Build them into the template

Attach sub-event templates inside an event template, choosing which event template each one uses. Then every job created from that parent template generates its sub-events automatically.

Worth doing when a job type always runs the same shape, like a three-day fall picture week you shoot at every large school.

### Add them to a job

Open any event, go to the Sub-events section and click **Add**, then choose the event template the sub-event should use.

This is what you'll do for a school that unexpectedly needs a second day, or when the number of days differs each time.

### A week in one go

In the Sub-events section click **Add** and choose **Multiple**. Set a start and end date, pick a template, and Schedulink creates one sub-event per day. They inherit the parent's status.

That replaces duplicating an event three times.

## Every sub-event is a full event

A sub-event isn't a stripped-down thing. It's built from an event template of its own, so it can carry its own tasks, emails, forms, contacts and staff.

That flexibility is the reason the concept confuses people, so here's what most studios actually do.

## How most studios use them

**Keep the work on the parent. Use sub-events for staffing.**

The tasks and emails for the whole job sit on the parent event, because chasing a roster or sending a confirmation happens once for the school, not once per day. The sub-events exist so you can put people on each day.

So your sub-event template is usually a light one: little more than a date and a place to put people.

You can put tasks and emails on sub-events if a day genuinely needs its own, but start simple. It's easier to add a task to one day later than to work out why a school got the same email three times.

## Statuses

Sub-events created with the Multiple option inherit the parent's status. After that they carry their own, so one day can be complete while another is still in progress.


---

# 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/sub-events-and-your-calendar.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.
