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

# Tasks

Create, assign and complete the work behind every job.

A task is a piece of work someone has to do: cull the images, print the ID cards, chase a roster, pack an order.

Most tasks arrive on their own. Creating an event generates every task its template defines, already timed and often already assigned. The Tasks page is where you see all of it in one place.

## Finding your tasks

Click **Tasks** in the top menu, then filter by due date, assignee or status.

For just your own work, your dashboard is quicker: switch the tasks panel to **My tasks** and you see what's ready for you, with overdue and due-today called out.

{% hint style="info" %}
You can filter by who a task is **assigned to**, but not by who created it. So there's no single view of everything you've handed out to other people. Filter to each person in turn, or assign yourself alongside them on the ones you want to keep an eye on.
{% endhint %}

## Task statuses

| Status      | What it means                                                                                             |
| ----------- | --------------------------------------------------------------------------------------------------------- |
| Not Started | The task exists but its start trigger hasn't been met. Nobody has been told about it                      |
| Ready       | The trigger has been met. This is the moment the assigned person gets an email and an in-app notification |
| In Progress | Set it yourself, or start any step on the task and it moves here                                          |
| On Hold     | Yours to set, for when you're waiting on something outside your control                                   |
| Completed   | Set it yourself, or complete every step and it moves here                                                 |

**Ready is the one that matters.** It's when the assigned person is actually told. If someone says they never heard about a task, the question is whether it ever reached Ready.

When every task on an event is completed, the event moves to Complete automatically.

## Creating a task

Click **Add** on the Tasks page, or use **Add Task** inside an event.

You'll be asked to pick a **task template** first, because a task always comes from one. If this is genuinely one-off work, use a blank task template and fill in the detail yourself.

Then attach it to an **event** if it belongs to a job, or to an **account** if it doesn't. Account-level tasks suit work that isn't tied to a shoot, like preparing a quote or chasing an unpaid invoice.

You can add a task to a job at any point, including one that's already in progress.

## Adding a task to every job at once

If you've realised mid-season that every picture day needs a step you didn't build in, you don't have to open each event.

Add the task to the **event template** instead. It lands on every event using that template which isn't already complete, not just on jobs you book from now on.

So a task added to your Fall Picture Day template in October appears on the November shoots you booked back in August, already timed from each one's event date.

{% hint style="info" %}
It reaches incomplete events only. Jobs already marked Complete are left as they were, which is usually what you want, since you're not asking anyone to go back and redo finished work.
{% endhint %}

If you run several event templates and the task applies to all of them, add it to each one. There's no way to push a task across every template at once.

## When a task becomes Ready

Every task has a **start trigger**, which decides when it wakes up and tells the assigned person. Which triggers you can choose depends on where the task lives.

### On a task you create yourself

Three options:

| Trigger    | What happens                                                                 |
| ---------- | ---------------------------------------------------------------------------- |
| Manual     | The task never becomes Ready on its own. You move it along when you're ready |
| Date       | The task becomes Ready at a date and time you set                            |
| Dependency | The task becomes Ready when another task you choose is completed             |

**Date** takes a time as well as a day, so a task that has to happen at 2pm can say so. That turns a task into a timed reminder, for you or for whoever it's assigned to.

If the task is attached to an event, a fourth option appears: **Days from Event**, counted from the shoot date, which is the same trigger event templates use.

### On a task inside an event template

Three options, and they apply to every job built from that template:

| Trigger         | What happens                                                                  |
| --------------- | ----------------------------------------------------------------------------- |
| No Trigger      | The task never becomes Ready on its own. Same as Manual on an individual task |
| Days from Event | The task becomes Ready a set number of days before or after the shoot date    |
| Dependency      | The task becomes Ready when another task on the job is completed              |

There's no Date option here, because a template has no single date to work from. A fixed date only makes sense on a task you create by hand.

See Event templates for setting these up.

{% hint style="warning" %}
**A dependency can only point at a task on the same event.**

That matters on multi-day jobs. If your editing tasks sit on the sub-events and your final check sits on the parent, the final check can't wait for them, because they're on different events.

The usual answer is to give the parent task a Days from Event trigger timed for a few days after the shoot, so it arrives on its own rather than waiting for something it can't see.
{% endhint %}

## Assigning a task

Open the task and set **Assigned To**.

That person gets an email and an in-app notification, but not immediately: the alert goes out when the task reaches Ready, which is the point at which they can actually do it.

A task assigned inside a template arrives already assigned. Reassigning it by hand sticks, and editing the template afterwards won't overwrite your change.

## Due dates

**Due dates on event tasks are counted from the event date, never from another task.**

That catches nearly everyone. If a task is set to start when the one before it finishes, its deadline still counts backwards or forwards from the shoot, not from the moment that other task was completed. Finishing early makes the next task available sooner; it doesn't move the deadline.

You can change a due date on an individual task whenever you need to. That affects only that task, not the template it came from.

Times follow your studio's timezone, set in **Setup > Organization**, so a task due at 2pm is 2pm for everyone regardless of where they're working.

## Steps

Steps are the checklist inside a task: generate the layouts, verify the data, export the files, print, pack.

They're defined on the **task template**, so you add them there rather than on an individual task. Each step records who started it and when, and who completed it and when, which gives you a history of the work without anyone writing it down.

Steps guide rather than gate. A task can be marked complete with steps outstanding, which is what you want when a step didn't apply to that particular job. Complete all of them and the task closes itself.

## Custom fields

Tasks carry custom fields from their template, and they do two jobs: telling the person what they need to know, like which ID design to use, and giving them somewhere to record what happened, like a tracking number.

## Notes and attachments

Notes are for your team. Pin the important ones, and tag a colleague to notify them.

An attachment added to a note can't be taken off again, so check you've picked the right file before saving.

## Downloading a task

Open the task, click the **three dots** at the top of the page, and choose **Generate PDF**. You get the task's details and its custom fields as a document.

The same option exists on accounts and events.

## Not seeing a task you expect?

Three things to check, in order.

Your **filters**, which persist between visits and are the most common reason something appears to be missing.

The task's **status**, because one sitting at Not Started hasn't reached anyone yet.

Who it's **assigned to**, since My tasks shows only your own.


---

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