> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks

> Reusable checklist templates that get attached to your gigs

The **Tasks** page at `/tasks` is where admins build the reusable checklist templates that get attached to gigs. A template captures the recurring prep work for a kind of show — load-in steps, soundcheck items, day-of confirmations — so a coordinator doesn't have to recreate it for every event.

<Note>
  Tasks templates are admin-only. They are gated by **`canManageOrganization`** and the **`gig-checklist`** feature flag. Without both, the sidebar item is hidden and direct navigation falls back to `/gigs`.
</Note>

***

## How templates work

A template is a list of **phases** (e.g., "Pre-event", "Day-of", "Post-event"), each containing a list of **tasks**. When a gig is created, you can attach one or more templates and Soundcheck materializes the phases and tasks onto that gig's checklist. From there each task can be checked off, assigned to a member, or annotated — all without affecting the template it came from.

### The library

The Tasks page opens to the template library. From here you can:

* **Search** by template name.
* **Open** a template to edit phases and tasks.
* **Create** a new template (Soundcheck auto-names the first one and you can rename it).
* **Delete** a template that's no longer needed.

### The editor

Inside a template you can:

* Add, rename, reorder, and remove phases.
* Add tasks to a phase, with notes.
* Drag tasks between phases.
* Save the template — changes don't ripple back to checklists already attached to gigs.

<Tip>
  Attach a generic "Day-of" template to every gig as a baseline, then layer event-specific templates (Wedding, Corporate, Festival) on top to capture variations.
</Tip>

***

## Attaching a template to a gig

From the gig detail page, open the **Checklist** section and click **Attach template**. The phases and tasks copy onto the gig and become editable from there — adding a one-off task on the gig doesn't change the template.

***

## Permissions

Editing templates requires **`canManageOrganization`** plus the `gig-checklist` flag. Once tasks are on a gig, anyone with edit access to that gig can check them off and add ad-hoc items.

***

## Related

<CardGroup cols={3}>
  <Card title="Gigs overview" icon="calendar" href="/features/gigs/overview">
    How the checklist appears inside an event
  </Card>

  <Card title="Templates & duplication" icon="copy" href="/features/gigs/templates-and-duplication">
    Reusing entire events instead of just task lists
  </Card>

  <Card title="Teams" icon="users" href="/organization/teams/overview">
    Reusable team and call-list configurations
  </Card>
</CardGroup>