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

# Checklist glossary

> Event checklist, task, advancing, production and safety terms, each with a one-line definition and what it maps to in Soundcheck's Checklist, or a plain note when Soundcheck has no equivalent.

Planners, producers, venues and tours use different words for the same few ideas. This glossary gives each term a one-line meaning and says what it is in Soundcheck. Where Soundcheck has no equivalent, it says so plainly, so you can plan around it.

![A gig's Checklist tab with sections, their completion rings, and each task's owner, due date and status](https://mintcdn.com/soundchecklive/e-SmuOY4KzOPmXhu/images/checklist/gig-checklist-light.png?fit=max\&auto=format\&n=e-SmuOY4KzOPmXhu\&q=85\&s=4dee1a3fbecaa1a5166e6bc59b92d534)

> [!TIP]
>
> Want straight answers instead of definitions? The [Checklist FAQ](https://docs.soundchecklive.io/features/gigs/checklist/faq.md) answers the questions buyers and coordinators ask most. New to the Checklist? Start at the [Checklist overview](https://docs.soundchecklive.io/features/gigs/checklist.md).

## Soundcheck's own terms

These are the words you'll see in Soundcheck itself.

| Term | What it means | In Soundcheck |
| - | - | - |
| Checklist | The list of tasks on one gig. A gig has one checklist. | The gig's **Checklist** tab. See [Working a gig's checklist](https://docs.soundchecklive.io/features/gigs/checklist/gig-checklist.md). |
| Task | One job on a checklist, with a title, notes, one assignee, a due date and a status. | A row on the **Checklist** tab. See [Tasks](https://docs.soundchecklive.io/features/gigs/checklist/gig-checklist.md#tasks). |
| Section | A named group of tasks, such as *Pre-event*, *Day-of* or *Post-event*. Older pages call it a phase. | Added with **Add a section to group tasks together**. See [Sections](https://docs.soundchecklive.io/features/gigs/checklist/gig-checklist.md#sections). |
| Other / Uncategorized | The catch-all section for tasks with no named section. Exports call it *Other tasks*. | Can't be renamed or deleted. See [The Other (Uncategorized) section](https://docs.soundchecklive.io/features/gigs/checklist/gig-checklist.md#the-other-uncategorized-section). |
| Status | Where a task is. | **Not started**, **In progress** or **Complete**. Ticking the checkbox marks it **Complete**. |
| Assignee | The one member of your organization who owns a task. | The assignee control on the row. Assigning sends them a push. See [Assign a task](https://docs.soundchecklive.io/features/gigs/checklist/gig-checklist.md#assign-a-task). |
| Owner (template) | The position a template task goes to, such as *Production manager*. | **Owner** in the template editor. On a gig, the task goes to whoever accepted that position earliest. See [Due dates and owners](https://docs.soundchecklive.io/features/gigs/checklist/templates.md#due-dates-and-owners). |
| Relative due date | A template task's due date, written as days or weeks before or after the gig's first day. | **Due** in the template editor, such as **1 week before** or **Day of show**. It turns into a real date when the template is applied. |
| Template | A reusable checklist your organization copies onto new gigs. | The **Checklist** page, under **Show prep → Checklist**. See [Checklist templates](https://docs.soundchecklive.io/features/gigs/checklist/templates.md). |
| Default template | The template new gigs get when nothing else is picked. | Marked **Default** in the library. You can't change which template is the default in the app today. |
| Starter pack | A ready-made checklist template, by business type or event type. | **Starter packs** on the **Checklist** page. Packs carry task titles only, with no dates or owners. See [Starter packs](https://docs.soundchecklive.io/features/gigs/checklist/templates.md#starter-packs). |
| Automatic task | A task Soundcheck writes for you because another part of the app knows the work exists. | Badged **Auto** on the web. It comes from the run of show, act seats, collaborator requests or close-out. See [Automatic tasks](https://docs.soundchecklive.io/features/gigs/checklist/automatic-tasks.md). |
| My tasks | Every task assigned to you, across every gig and organization. | The **Tasks** tab of your mailbox on the web, and **My checklist** in the mobile app. See [Your tasks](https://docs.soundchecklive.io/features/gigs/checklist/your-tasks.md). |
| Checklist assignment | A gig assignment that lets a member manage that gig's tasks. | **Checklist** under the gig's assignees. **Lead** includes it. See [Assigning people to run a gig](https://docs.soundchecklive.io/features/gigs/assignees.md). |
| Checklist on every gig | Extra access that lets one member manage the checklist on every gig. | Given under **Manage access…** on the member. See [Extra access for one member](https://docs.soundchecklive.io/settings/team/roles-permissions.md#extra-access-for-one-member). |
| Open item | Something on a gig that still needs doing. An overdue task is one. | The count on the **Checklist** tab and **Overdue tasks** on Home. See [Open items](https://docs.soundchecklive.io/features/gigs/open-items.md). |
| Act seat task | One task per seat in an act's team, so an empty seat shows up. | The **Acts** section. See [Act seat tasks](https://docs.soundchecklive.io/features/gigs/checklist/automatic-tasks.md#act-seat-tasks). |
| Collaborator request | A task an outside collaborator owes you, such as *Send your rider*. | Added to **Uncategorized** when you share a role. See [Collaborator request tasks](https://docs.soundchecklive.io/features/gigs/checklist/automatic-tasks.md#collaborator-request-tasks). |

## Tasks and planning

| Term | What it means | In Soundcheck |
| - | - | - |
| Checklist / task list | The list of things that must be done for an event, each with an owner and a due date. | The gig's [Checklist](https://docs.soundchecklive.io/features/gigs/checklist.md). |
| Task / to-do | One item on a checklist. | A task. See [Tasks](https://docs.soundchecklive.io/features/gigs/checklist/gig-checklist.md#tasks). |
| Sub-task | A smaller task inside a task. | No equivalent. Use a section for the group, with one task per step, or list the steps in the task's notes. |
| Template | A saved checklist applied to new events so tasks aren't rebuilt each time. | A [checklist template](https://docs.soundchecklive.io/features/gigs/checklist/templates.md). A [gig template](https://docs.soundchecklive.io/features/gigs/templates-and-duplication.md) also carries tasks, without due dates. |
| Relative due date / offset | A due date set as a number of days before or after an anchor, such as the event date. | **Due** on a template task, counted from the gig's first day. Dates are set once when the template is applied and don't move if the gig is rescheduled; shift them with [bulk edit](https://docs.soundchecklive.io/features/gigs/checklist/bulk-edit.md). |
| Anchor date | The date relative due dates are counted from, usually the event date. | Always the gig's first day. You can't anchor to another date, such as the contract date or the last day. |
| Owner / assignee | The person responsible for completing a task. | The task's assignee: one member of your organization. Clients, contacts and outside collaborators can't be assignees. |
| Role assignment | Assigning a task to a role (such as Production Manager) rather than a named person. | Only in templates: **Owner** names a position, and the task goes to the person in it when the template is applied. On a gig, a task is assigned to a person. Crew who accept the position later aren't assigned automatically. |
| Milestone | A key checkpoint, such as contract signed or final payment. | No milestone type. Use a task with a due date, or a section named for the stage. The [Closeout](https://docs.soundchecklive.io/features/gigs/closeout.md) tab tracks contract, deposit, invoice and payment steps after the show. |
| Dependency | A task that can't start until another is finished. | No equivalent. Order tasks by due date and section. |
| Critical path | The chain of dependent tasks that sets the earliest finish date. | No equivalent. |
| Recurring task | A task that repeats on a schedule. | No equivalent. Put repeat jobs in a template so every gig gets them. |
| Sign-off | A recorded approval that a task or inspection is complete. | No sign-off step. **Complete** is the only record, and the checklist doesn't show who completed a task or when. |
| Punch list | A list of items still to fix before something is finished. | A section such as *Punch list* on the gig's checklist, with one task per fix. |

## Advancing and production

| Term | What it means | In Soundcheck |
| - | - | - |
| Advance / advancing | Confirming every show detail with the venue or promoter before arrival. | Advance tasks on the checklist; several starter packs have an **Advance** section. The venue's [Crew advance](https://docs.soundchecklive.io/features/gigs/venue/venue-record.md#crew-advance) holds reusable answers. A collaborator can confirm their part through [request tasks](https://docs.soundchecklive.io/features/gigs/checklist/automatic-tasks.md#collaborator-request-tasks). |
| Venue advance | The advance with a specific venue: production specs, hospitality, schedule, parking and contacts. | The venue record's **Crew advance**, with per-show changes on the gig's **Venue** tab. A venue collaborator gets *Confirm load-in, specs and curfew* as a request task. |
| Production advance | The technical part of the advance, handled by the production manager. | Tasks in an advance section, assigned to the production manager. A production collaborator gets *Send your crew and gear list*. |
| Advance sheet | The form or document that records advance questions and answers. | No advance form. Send a [form](https://docs.soundchecklive.io/features/gigs/documents/forms.md) from the gig's **Documents** tab, or keep the answers in task notes. |
| Day sheet | One day's schedule and details pulled from the tour itinerary. | The **Day sheet** PDF from the run of show export. Tasks don't print on it. See [Exporting](https://docs.soundchecklive.io/features/gigs/run-of-show/exporting.md). |
| Itinerary | The full schedule of a tour, day by day. | No single tour itinerary. Each gig has its own checklist; group gigs in [projects](https://docs.soundchecklive.io/features/gigs/tours.md). |
| Routing | The order of cities and venues on a tour. | No equivalent on the checklist. Gigs in a [project](https://docs.soundchecklive.io/features/gigs/tours.md) show the run. |
| Tech pack / venue specs | A venue's document of stage, power, rigging, house gear and access. | A file on the venue record or the gig's **Documents** tab. A task can't hold files; name the file in the task's notes. |
| Load-in / load-out | Bringing gear into the venue and setting up; packing up and leaving. | The **Load in** and **Load out** [key times](https://docs.soundchecklive.io/features/gigs/run-of-show/key-times.md), plus load-in or load-out sections on the checklist. |
| Strike | Taking down the set and gear after the show. | A task or a *Strike* section on the checklist, or a row on the run of show. |
| Line check | A quick check that every audio input works before the show. | A run of show item; people on it get a timed task in the **Run of show** section. Tasks can't hold a reading or value. |
| Changeover | The time to swap one act's setup for the next on a shared stage. | A run of show item. Crew on it get a timed task. |
| Backline | The amps, drum kits and keyboards on stage, often shared at festivals. | Gear in your [inventory](https://docs.soundchecklive.io/features/gigs/gear/inventory.md), or [outside gear](https://docs.soundchecklive.io/features/gigs/gear/outside-gear.md). Tasks aren't linked to gear. |
| Curfew | The time the show must end, usually set by the venue or the licence. | The **Curfew** key time. Tasks have no due time, so a task can't be due at curfew. |
| Camlock / distro | High-current power connectors and the power distribution box that feeds a stage. | No equivalent. Write power needs in task notes or attach the plan to the gig. |
| Dead case storage | The space where empty road cases are kept during the show. | No equivalent. Note it in the venue's **Crew advance** or a task. |
| Settlement | The post-show reconciliation of money with the promoter or venue. | Soundcheck doesn't offer show settlement today. See [Show settlement](https://docs.soundchecklive.io/features/gigs/finances/show-settlement.md). [Close-out tasks](https://docs.soundchecklive.io/features/gigs/checklist/automatic-tasks.md#close-out-tasks) chase the paperwork steps after a show. |

## Safety

| Term | What it means | In Soundcheck |
| - | - | - |
| Risk assessment | A written review of hazards and the controls for each. | No built-in risk assessment. Attach the document on the gig's **Documents** tab and add a task to review it. |
| Pre-event inspection / walk-through | A safety check of the site after setup and before doors. | A section of tasks, one per check, assigned to the inspector. There's no signature, photo or sign-off step. |
| Crowd manager | A trained person responsible for crowd safety in an area. | No dedicated role. Add a [position](https://docs.soundchecklive.io/settings/team/positions.md) and assign their tasks to the person in it. |
| Event safety plan / ESMP | The document that covers safety arrangements for an event. | A file on the gig's **Documents** tab. No structured safety plan. |
| Permit | Official permission for something like noise, fire effects, alcohol or a road closure. | A task with a due date, one per permit. Check the requirements with the issuing authority. |

## Worked example: a corporate conference

A producer runs a two-day product launch for a client. Here's how their words map to Soundcheck.

1. Their **planning timeline** is the *Corporate* starter pack, saved as a template with **Advance**, **Event day** and **Wrap** sections. They set each task's **Due** relative to the first day, such as **3 weeks before**, and **Owner** to *Production manager*. Starter packs come with titles only, so this step matters.
2. Creating the gig applies the template. The **anchor date** is the first day, so *Send final run of show to client* lands three weeks before day one. The task goes to the person who accepted Production manager on the gig.
3. Their **production advance** is a set of tasks in **Advance**. The venue is shared as a collaborator, so *Confirm load-in, specs and curfew* appears as a **collaborator request** in **Uncategorized**.
4. Their **line check** is a run of show item. The A1 and A2 on it each get an **automatic task** in the **Run of show** section, timed to the item.
5. The client moves the launch a week later. **Due dates don't move by themselves**, so the producer selects every dated task and shifts them **+7 days**.
6. There's no **sign-off** or **dependency** in Soundcheck, so the walk-through before doors is one task per check, assigned to the stage manager, who ticks each one on their phone.

## Questions this page answers

* [What does Soundcheck call a section, an owner and a relative due date?](https://docs.soundchecklive.io/features/gigs/checklist/faq.md)
* [Can a task have sub-tasks or depend on another task?](https://docs.soundchecklive.io/features/gigs/checklist/faq.md)
* [Do due dates move when the event date changes?](https://docs.soundchecklive.io/features/gigs/checklist/faq.md)
* [Can I assign a task to a role instead of a person?](https://docs.soundchecklive.io/features/gigs/checklist/faq.md)
* [Is there a sign-off step for safety inspections?](https://docs.soundchecklive.io/features/gigs/checklist/faq.md)
* [How do I run an advance with the Checklist?](https://docs.soundchecklive.io/features/gigs/checklist/faq.md)

## Related

> [card] [Checklist](https://docs.soundchecklive.io/features/gigs/checklist.md)
>
> Start here.

> [card] [Checklist FAQ](https://docs.soundchecklive.io/features/gigs/checklist/faq.md)
>
> Straight answers, including what Soundcheck doesn't do.

> [card] [Checklist templates](https://docs.soundchecklive.io/features/gigs/checklist/templates.md)
>
> Relative due dates, owners and starter packs.

> [card] [Run of show glossary](https://docs.soundchecklive.io/features/gigs/run-of-show/glossary.md)
>
> Show-calling and production terms on the schedule side.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.