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

> A copy-paste-friendly flow for going from "I have a new gig" to "the crew has been invited" in five minutes — plus the common pitfalls.

This is the fastest path through Soundcheck. Assumes you've already done first-time setup (organization, members, positions, at least one call list).

## The 5-minute flow

<Steps>
  <Step title="Create the gig (45 seconds)">
    Click **+ Create Gig**. Enter the name, date, and event type — that's all that's required. Venue not locked yet? Skip location and fill it in later. Multi-day event? Add an end date. Save. The gig is in **Draft** — only you and admins can see it.
  </Step>

  <Step title="Apply a call list (15 seconds)">
    On the gig's **Details** tab, open the **Team** section → **Apply call list** → pick the appropriate one (*A-Team*, *Wedding A*, *Tour A-Team — Leg 1*). All positions populate with the first-priority members for each role.
  </Step>

  <Step title="Spot-fix conflicts (1–2 minutes)">
    Soundcheck flags conflicts inline. For each:

    * **Hard conflict** (already booked at that time) → click the member → Replace from the call list (auto-suggests the next priority).
    * **Soft conflict** (marked unavailable) → same fix, or override if you've already cleared it with them.
  </Step>

  <Step title="Add performance fees (1 minute)">
    For paid gigs, click each position → enter the fee. Skip if your fees are baked into a template.
  </Step>

  <Step title="Publish + invite (15 seconds)">
    Flip the gig from **Draft** to **Active** in the header status picker. Invitations send to everyone on the team — they get a push (mobile) and an entry in their [Mailbox](/features/engagements/overview).
  </Step>

  <Step title="Confirm (anytime in the next 24 hours)">
    Track invitation responses from the gig page or your Home page. As members accept, their position goes green.
  </Step>
</Steps>

## Common pitfalls

<AccordionGroup>
  <Accordion title="I forgot to apply a call list and built the team manually">
    No problem — but next time, save this combination as a call list (**Teams → Call lists → New from gig**) so you don't repeat the work.
  </Accordion>

  <Accordion title="I published 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>

  <Accordion title="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>

  <Accordion title="The venue isn't in my directory yet">
    Type the new venue name and tap **Create new** — it's added to your [venue directory](/crm/venues) 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>

  <Accordion title="I don't know the venue at all yet">
    Then don't enter one. Location is optional on a gig — create the hold with just a name, date, and event type, and attach the venue when the booking firms up.
  </Accordion>

  <Accordion title="I need to change the time after publishing">
    Edit the gig → confirm the change. Confirmed members get a push notifying them of the edit. They don't need to re-accept unless the change is significant (different day, different city — Soundcheck will prompt you).
  </Accordion>
</AccordionGroup>

## Even faster: from a template

If this gig is similar to one you've done before, start from a template instead of from scratch — the position list, fees, and notes all carry over. Skip step 1 and step 4 above. See [Templates and duplication](/features/gigs/templates-and-duplication).

## Even faster: from a bulk import

If you have a spreadsheet of gigs to set up, use [Imports](/features/imports/overview) instead. The wizard does parse → map → preview → commit and creates dozens of gigs in one pass. See the [importing your season](/faq/workflows/importing-your-season) recipe.

## Related

<CardGroup cols={2}>
  <Card title="Creating gigs (full guide)" icon="calendar-plus" href="/features/gigs/creating-gigs">
    All the fields and options.
  </Card>

  <Card title="Building teams" icon="users" href="/features/gigs/team-building">
    Manual team building when call lists don't fit.
  </Card>

  <Card title="Draft vs published" icon="rocket" href="/features/gigs/draft-publish">
    The full lifecycle of a gig.
  </Card>

  <Card title="Call lists" icon="list" href="/organization/teams/call-lists">
    Build the rosters the flow above depends on.
  </Card>
</CardGroup>