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

# Planning crew needs

> Decide who a gig needs before you book anyone: positions, departments, crew requirements, headcount per day, several shifts a day, multi-day gigs, and one person in several positions.

Every staffing job starts with the same question: what does this gig need? Two A1s, a V1 and six stagehands on load-in. A bass player and a sub on standby. Ten hands for the morning and four for the show. In Soundcheck you write that plan down as **positions** and **shifts** on the gig, as drafts, before you contact anyone. The plan then becomes the offers you send.

![Add position picker listing the organization's positions with their departments, to tick one or more](https://mintcdn.com/soundchecklive/SK0diQsPrD96SAMt/images/staffing/add-position-light.png?fit=max\&auto=format\&n=SK0diQsPrD96SAMt\&q=85\&s=24a09cf4417b3e0be8393d39affe786a)

## When to use this page

* You're setting up Soundcheck and need your list of positions.
* You're planning a new gig and want the crew shape in place before you know who will fill it.
* You run gigs with several calls a day, or gigs that span several days.
* You want a reusable crew shape for a show type you do often.

## Positions: the jobs you staff

A **position** is a job your organization books people for: *A1*, *V2*, *Stagehand*, *Rigger*, *Keys*, *Bartender*. You define each once and use it on every gig, in templates, in availability requests and in imports.

**1. Open Positions**

Go to **Settings → Labels → Departments → Positions**. The page reads "The jobs you staff for. Give each a short code and a default day rate".

**2. Add your positions**

Choose **Add positions**. For each, set the **Position** name, a short **Code** (such as *A1* or *SH*) and a **Default day rate**.

**3. Give people their positions and rates**

On a member's profile, the **Org Positions** card lists the positions they work, with their own **Day rate**, **Hourly rate** and a **Rating**. A blank day rate gives no fee: the position's default day rate is a reference and never sets pay. See [Pay and rates](https://docs.soundchecklive.io/features/gigs/staffing/pay-and-rates.md).

Positions have a default **day** rate only. Hourly rates are set per person, on their profile. Owners and Admins create and edit positions. Everyone in the organization can see the list. On a phone, owners and admins find **Positions** under **You → organization settings**.

See [Managing positions](https://docs.soundchecklive.io/settings/team/positions.md) for naming, imports and troubleshooting.

> [!TIP]
>
> Keep positions to the jobs you actually book and pay differently. *A1* and *A2* are two positions because they pay differently. *Audio* is a department, not a position.

## Departments: groups of people

> [!NOTE]
>
> **Early access.** Departments are rolling out. Contact [info@soundchecklive.io](mailto:info@soundchecklive.io) if you'd like them turned on.

A **department** groups your people: "Organize your roster into teams — like Audio, Video, or a house band — each with its own code, color, and lead." Each department has a name, a short code of up to five characters, a colour, a description, and at most one lead.

* Manage them under **Settings → Labels → Departments → All departments**. Owners and Admins make changes; everyone in the organization can see them.
* When you create or edit a gig, the **Department** field says which department the gig is staffed under. Choose **No department** to leave it open.
* Departments are on every plan. Adding, renaming or deleting them needs the Team plan or a free trial.

The staffing board itself is organized by position, not by department. Positions, crew records and onboarding are shared by every department. Soundcheck doesn't run a separate onboarding flow per department today.

## Crew requirements: dress and reminders

**Requirements** in Soundcheck tell crew what to wear and what to remember. They're not headcount.

* **Organization presets:** on the Positions page, set **Dress presets** (choose **Add preset**) and **Standing reminders** that apply to every gig.
* **Per gig:** on the gig's **People → Requirements**, pick a **Dress code**, add **Dress notes** and gig reminders.
* Crew see them on the gig in the mobile app, under **Crew requirements**.

See [Crew requirements](https://docs.soundchecklive.io/features/gigs/people/requirements.md).

> [!WARNING]
>
> Soundcheck doesn't let you mark a position as needing a certification, such as a rigging or forklift ticket, and it doesn't stop an unqualified person from being offered a shift. Track certifications as [crew record](https://docs.soundchecklive.io/settings/organization/crew-records.md) fields with an expiry date, and check them when you pick people. See [Paperwork and compliance](https://docs.soundchecklive.io/features/gigs/staffing/paperwork-and-compliance.md).

## Shifts: the plan on the gig

A **shift** is one position on one gig: its days, call and out times, pay, and how many people you need. You build shifts on the gig's staffing board (**People → Crew**). The gig needs a date first.

On the web, add a position to the board, then add a shift to it. The **Create shift** sheet reads "Choose crew, days, rate, and call times before sending." and asks for:

| Field | What it holds |
| - | - |
| **Position** | One of your positions. |
| **Shift name** | What this call is, such as *Load-in*, *Show* or *Strike*. Crew see it in emails and on their phones. |
| **Notes** | Anything the crew should know about this shift. |
| **Days covered** | Which of the gig's days the shift covers. |
| Call and out times | One window per day. **Copy times to all days** (or **Copy times & rate to all days**) repeats one day's window. **Use event time** fills in the gig's times. **Clear** empties a day. |
| Pay | **Flat** or **Hourly**. A flat shift is a **Flat total** or **Per day**, with a **Default per-day rate**. See [Pay and rates](https://docs.soundchecklive.io/features/gigs/staffing/pay-and-rates.md). |
| **Need** | How many people you need. Optional. |

A shift saved with **Save as draft** notifies nobody: "A draft notifies nobody — it parks the crew on the board until you send it." A draft can have blank call times and nobody on it, so you can sketch the whole crew plan first and fill it in later.

In the mobile app, choose **Add position** or add a shift to an existing role. The sheet asks for the **Role**, **Days**, **Call times**, whether it's **Hourly**, the **Seats** and the **Need per day**. The mobile app builds regular shifts only; open shifts are built on the web.

## Headcount: Need and Spots

How you set "how many" depends on the kind of shift.

| Shift kind | Field | Meaning |
| - | - | - |
| Regular shift (job offer) | **Need** | How many people you want. You can ask more than you need: ask five, need two. Leave it blank for no target. |
| Open shift *(early access)* | **Spots** | How many people get booked. The first ones to accept fill the spots. |

On a multi-day shift, each day can have its own target: "How many people this day needs. Leave blank for no target." A load-in day can need ten people while the show day needs four, all on one shift.

The board rolls each position up as filled, short, or with open seats, and the **Needs** tab on **Crew** lists every gig in the next 30 days that still has open seats.

## Several shifts a day

A position can have as many shifts on a gig as you like, including several on the same day. Use this whenever the same job has separate calls:

* *Stagehand · Load-in*, 7:00 AM to 12:00 PM, need 10
* *Stagehand · Show*, 6:00 PM to 10:00 PM, need 4
* *Stagehand · Load-out*, 10:00 PM to 2:00 AM, need 12

Each shift has its own call times, headcount and pay, and the people on it can be the same or different. Different positions on the same day each have their own call times too, so your A1 can be called at 2:00 PM while stagehands start at 7:00 AM.

A new shift starts from the call times and pay of the last shift you set up for the same position. The sheet says so, and you change what differs.

> [!TIP]
>
> An out time earlier than the call time ends the next morning. A 10:00 PM to 2:00 AM load-out stays on the show day. Only make a gig multi-day when the work really spans separate days.

## Multi-day gigs

When a gig spans several dates, one shift can cover any of its days. Each day carries its own call and out time, its own rate, and its own headcount, and a blank value falls back to the shift's. Crew accept or decline each day for themselves, so someone can take Friday and Saturday and pass on Sunday.

A shift has one call window per day. For two separate calls on the same day, use two shifts.

See [Tours and multi-day staffing](https://docs.soundchecklive.io/features/gigs/staffing/tours-and-multi-day.md) and [How shifts work](https://docs.soundchecklive.io/features/gigs/staffing-shifts.md#multiday-gigs-answer-day-by-day).

## One person, several positions

One person can hold more than one position on the same gig. Your A2 on load-in can be a stagehand on load-out, and a truck driver can also run the generator. Each position is its own shift with its own fee and call times, so pay stays correct for each role.

The only limit: a person appears once on any one shift. To book them twice on the same day, put them on two shifts.

> [!NOTE]
>
> The picker tells you when someone is already on another shift: "On \{roles}". Soundcheck shows this as a note and still lets you add them.

## Reuse a crew plan

You rarely plan a gig from nothing.

| Start from | How | What carries over |
| - | - | - |
| A team template (call list) | **Start from a template** on an empty board, or **More staffing actions → Use a team** | One draft shift per seat across the gig's days, with the people you saved. Pay doesn't carry over. Nobody is notified. |
| This gig, for next time | **More staffing actions → Save as team** | The positions, seat counts and crew on the board, saved as a template. |
| An email or spreadsheet crew call | **Paste data**, then **Map into Staffing** | One draft shift per row you keep, with roles, counts and call times. Tick rates to keep them. |
| Another shift on the gig | **Duplicate shift**, or **Duplicate with crew** | A new draft copy, with or without the people who accepted. |
| A past gig | **Duplicate Gig**, or a saved gig template | Shifts come back as drafts. A gig template keeps roles and seat counts with nobody named; duplicating keeps the crew, all pending again. |

Saved team templates need the Pro plan or higher. See [Call lists](https://docs.soundchecklive.io/settings/team/call-lists.md), [Templates and duplication](https://docs.soundchecklive.io/features/gigs/templates-and-duplication.md) and [The Crew board](https://docs.soundchecklive.io/features/gigs/people/crew-board.md).

## Plan while the gig is still a hold

Draft shifts never notify anyone, so you can plan the full crew on a gig that's still tentative. Sending is what tells people.

> [!WARNING]
>
> Sending a shift notifies crew straight away, even when the gig itself is still a draft. Keep shifts as drafts until the gig is confirmed. Only the calendar invite waits for the gig to be published.

## What Soundcheck doesn't plan for you

* **Labor cost before booking.** There's no labor estimate for crew shifts. Turn on **Show pay** in the board's view menu to see each person's fee as you build, and check the gig's [Finances](https://docs.soundchecklive.io/features/gigs/finances.md) once people accept.
* **Crew from the equipment order.** Adding gear doesn't add crew. A [Flex](https://docs.soundchecklive.io/features/gigs/staffing/switching-tools.md) quote import can create shifts from the quote's labor lines *(early access)*.
* **Stages and rooms on a shift.** A shift has no stage or room field. For a festival or conference with several rooms, put the room in the **Shift name** (*A1 · Ballroom B*), or put each room's crew on its own gig in one project.

## Worked example: corporate general session

*Fictional example.* Brightline AV is running a two-day corporate general session: build on Thursday, show on Friday.

1. They open the gig's **People → Crew** and choose **Start from a template**, picking their *Corporate GS* team. Draft shifts appear for A1, A2, V1, L1 and Stagehand, with their regulars on them.
2. They split stagehands into two shifts: *Stagehand · Build* on Thursday, need 8, hourly; and *Stagehand · Strike* on Friday from 5:00 PM to 11:00 PM, need 10.
3. The A1, A2, V1 and L1 shifts cover both days, with Thursday's call at 10:00 AM and Friday's at 6:00 AM, set per day.
4. Their V1, Dana, is also a qualified L2, so they put her on a second shift as *L2 · Show* on Friday. She'll be paid for both.
5. They set **Dress code** to *Show blacks* under **Requirements**.
6. Everything stays a draft until the client signs. Then they move on to [finding crew](https://docs.soundchecklive.io/features/gigs/staffing/finding-crew.md) and send.

## Questions this page answers

* How do I list the positions a gig needs before I know who will fill them?
* Can I build a crew template for a show type and reuse it?
* Can one person hold more than one position on the same gig?
* Can I split a gig into load-in, show and load-out, each with its own headcount and times?
* Can different positions on the same day have different call times?
* Can I plan crew while the gig is still a hold, without notifying anyone?
* Can I copy last year's crew plan?
* Can I require a certification for a position?

More answers in the [Staffing FAQ](https://docs.soundchecklive.io/features/gigs/staffing/faq.md).

## Related

> [card] [Finding crew](https://docs.soundchecklive.io/features/gigs/staffing/finding-crew.md)
>
> Fill the plan with the right people.

> [card] [How shifts work](https://docs.soundchecklive.io/features/gigs/staffing-shifts.md)
>
> Statuses, seats and per-day answers in full.

> [card] [Positions](https://docs.soundchecklive.io/settings/team/positions.md)
>
> Managing your positions catalog.


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