> 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/set-up-your-studio/templates.md).

# Templates

Templates are how Schedulink knows what a job looks like. Build them well and the rest of the app runs itself.

Every record in Schedulink is built from a template. When you create an event, you pick one, and Schedulink builds the job from it: the fields you fill in, the tasks that need doing, the emails that go out and when.

A picture day at one client should generate the same fifteen tasks and the same four emails as a picture day at every other client. Built by hand each time, they won't, and the ones that get missed are the ones nobody notices until a parent calls.

This is the part most studios underestimate at the start, and the part that decides whether the rest of the app saves you time or costs you time.

## Build them in this order

Each one depends on the last.

1. [Task templates — one per piece of work you repeat](https://schedulink.io/help-center/set-up-your-studio/templates/task-templates.md)
2. [Email templates — one per message you send](https://schedulink.io/help-center/set-up-your-studio/templates/email-templates.md)
3. [Form templates — if you collect rosters or data from clients](https://schedulink.io/help-center/set-up-your-studio/templates/form-templates.md)
4. [Event templates — assembling the above into each job type you run](https://schedulink.io/help-center/set-up-your-studio/templates/event-templates.md)
5. [Account, contact and employee templates — the extra fields your records carry](https://schedulink.io/help-center/set-up-your-studio/templates/account-contact-and-employee-templates.md)

The first four nest: task, email and form templates are attached inside an event template, so applying it to a job generates all of them at once. The fifth is separate, and most studios set it up once and never think about it again.

## How many event templates

Most studios have between three and six. Fall Picture Day, Spring, Sports, Graduation, Dance.

If you find yourself building more than ten, the extras are usually variations that belong in custom fields instead.

## One-off work

Some jobs don't repeat. A yearbook composite a client asked for once, a reshoot, a favour. For those, use a blank task template and fill in the detail on the task itself. Give it a clear name so nobody picks it by mistake.


---

# 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/set-up-your-studio/templates.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.
