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

# Quick 5-minute gig setup

> Copy-paste flow from "I have a new gig" to "the crew has been invited" in about five minutes, plus common pitfalls.

This is the fastest path through Soundcheck. You already finished first-time setup: organization, members, positions, and (on Pro+) at least one call list you can apply from **Manage Team**.&#x20;

## The 5-minute flow

**1. Create the gig (45 seconds)**

Open **Gigs** and click **New gig** or **Create Gig**. Enter the name, date, gig type, and venue. That is all that is required. Venue not locked yet? Type the city or a placeholder and update it later. Multi-day event? Add an end date. Save. New gigs save as a **Draft**. Only you and other managers see them until you publish.

![Create new gig dialog with template chips, name, gig type, date and venue fields](https://mintcdn.com/soundchecklive/YID1u3xi3y5B4ur8/images/gigs/creating-gigs-light.png?fit=max\&auto=format\&n=YID1u3xi3y5B4ur8\&q=85\&s=7de7b43004d2b500512b5898cec1d64c)

**2. Staff the team (15 seconds to 2 minutes)**

In the gig's **Team** section, open **Build team** → **Manage Team**. (If your organization staffs with crew shifts, use **Use a team** under **Crew** on the **People** tab instead; see [Building teams](https://docs.soundchecklive.io/features/gigs/team-building.md).)

* **Pro+ (Pro, Team, Enterprise):** Apply a **call list** (*A-Team*, *Wedding A*, *Tour A-Team, Leg 1*). Positions populate with first-priority members for each role.
* **Starter:** Add positions and assign members manually in **Manage Team**. Same flow, no call-list shortcut.

![Crew view on a gig with positions, shifts, pending replies and the Add position button](https://mintcdn.com/soundchecklive/YID1u3xi3y5B4ur8/images/gigs/team-building-light.png?fit=max\&auto=format\&n=YID1u3xi3y5B4ur8\&q=85\&s=2fd8beed04940ed0b8dc78fc3efba188)

**3. Spot-fix conflicts (1–2 minutes)**

Availability badges flag people who are already booked at that time or marked unavailable. A conflict is a warning, not a block, so you can still send. For each one, click the member and replace them from the saved team (Pro+) or pick someone else manually. Or keep them if you have already cleared it with them. See [Does Soundcheck prevent double-booking?](https://docs.soundchecklive.io/features/gigs/team-building.md#does-soundcheck-prevent-double-booking).

**4. Add performance fees (1 minute)**

For paid gigs, set pay for each position in **Manage Team**. Templates leave fees out by default, so set them on each new gig.

**5. Send invitations (15 seconds)**

Choose **Continue** → **Save** to hold the invitations, then set the gig to **Active** from the status pill in the gig header. Publishing sends them: everyone on the roster gets a push (mobile) and an entry in their [Mailbox](https://docs.soundchecklive.io/features/engagements/overview.md).

![Draft gig with the banner that offers to activate it and send the waiting invites](https://mintcdn.com/soundchecklive/YID1u3xi3y5B4ur8/images/gigs/draft-publish-light.png?fit=max\&auto=format\&n=YID1u3xi3y5B4ur8\&q=85\&s=a9f6f6375af232d1e06b76f2044288d2)

**6. Confirm (anytime in the next 24 hours)**

Track invitation responses from the gig page or **Home**. As members accept, their position goes green.

## Common pitfalls

> [accordion] I forgot to apply a call list and built the lineup manually
>
> No problem. On Pro+, save this combination as a **Team** preset from **Manage Team** when that option is available so you do not repeat the work. On Starter, manual **Manage Team** is the expected path.

> [accordion] I sent invitations before checking conflicts
>
> Conflicted members can still see the invitation, but the gig page keeps showing the warning. Replace them. The original invitation auto-revokes when you do.

> [accordion] Half the team hasn't responded after a day
>
> Send a one-tap nudge from the gig page → **Send reminder**. This re-pushes the invitation without creating duplicates.

> [accordion] The venue isn't in my directory yet
>
> Type the new venue name and tap **Create new**. It is added to your [venue directory](https://docs.soundchecklive.io/features/gigs/venue.md) inline. Fill in the address, contacts, and load-in logistics from the venue's own page later. Once saved there, they auto-fill every future gig at that venue.

> [accordion] I don't know the venue at all yet
>
> A new gig needs a venue, so type the city or a placeholder such as "Venue TBC" as plain text. Create the hold with a name, date, gig type, and that placeholder, and update the venue when the booking firms up.

> [accordion] I need to change the time after the crew is notified
>
> Edit the gig → confirm the change. Confirmed members get a push notifying them of the edit. They do not need to re-accept unless the change is significant (different day, different city). Soundcheck will prompt you.

> [accordion] I expected to publish the gig before inviting
>
> That's the normal flow. Every gig you create in Soundcheck starts as a **Draft**, and invitations you add are held until you click **Activate gig**. See [Draft vs published](https://docs.soundchecklive.io/features/gigs/draft-publish.md).

## Even faster: from a template

If this gig looks like one you have done before, start from a template instead of scratch. The position list carries over as roles and seat counts. Fees are left out unless you add them back when you save the template, so check pay before you send. Template gigs start as **Draft** too. Staff them from **Manage Team**, then click **Activate gig** to send the invitations. See [Templates and duplication](https://docs.soundchecklive.io/features/gigs/templates-and-duplication.md) and [Draft vs published](https://docs.soundchecklive.io/features/gigs/draft-publish.md).

## Even faster: from a bulk import

If you have a spreadsheet of gigs to set up, use [Imports](https://docs.soundchecklive.io/features/imports/overview.md) instead. The wizard runs parse → map → preview → commit and creates dozens of gigs in one pass. See the [importing your season](https://docs.soundchecklive.io/use-cases/playbooks/importing-your-season.md) recipe.

## Related

> [card] [Creating gigs (full guide)](https://docs.soundchecklive.io/features/gigs/creating-gigs.md)
>
> All the fields and options.

> [card] [Building teams](https://docs.soundchecklive.io/features/gigs/team-building.md)
>
> Manage Team flow when call lists do not fit.

> [card] [Draft vs published](https://docs.soundchecklive.io/features/gigs/draft-publish.md)
>
> When gigs start as Draft vs Active.

> [card] [Call lists](https://docs.soundchecklive.io/settings/team/call-lists.md)
>
> Call lists and call order (Pro+ apply path).


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