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

# Gigs FAQ

> Common questions about creating, editing, cancelling, closing out, and organizing your gigs in Soundcheck.

Common questions about creating, managing, and organizing gigs. For questions about one part of a gig, such as Run of Show, People or Finances, open that area's FAQ from the [FAQ hub](https://docs.soundchecklive.io/faq.md).

## Creating

> [accordion] How do I create a gig?
>
> Open **Gigs** and click **+ Create Gig**. Enter the event details, save, then build the team, run of show, and attachments from the gig page. It saves as a draft; set it to **Active** when you're ready to invite the crew. [Full guide](https://docs.soundchecklive.io/features/gigs/creating-gigs.md). For the fastest path, see [Quick 5-minute gig setup](https://docs.soundchecklive.io/use-cases/playbooks/quick-gig-setup.md).

> [accordion] Do I need a venue or location to create a gig?
>
> Yes. The create form on the web and in the mobile app needs a name, a date, a gig type, and a venue. If the exact venue isn't confirmed yet, type the city or a placeholder as plain text and update it later. Gigs that arrive through an import, the API, or an AI assistant can still be created without one.

> [accordion] Can a gig span multiple days?
>
> Yes. Set an optional **end date** for multi-day runs (festival, conference, residency). Leave it empty for a single-day event; clear it later to switch back. A multi-day gig has dates only: set each day's times in the run of show and each shift's call times on the Crew board. An overnight show that crosses midnight stays single-day: use **Past midnight (next day)** when out time is earlier than start, including for a next-morning window.

> [accordion] Can I duplicate a gig?
>
> Yes. Open any gig, click the actions menu (three dots), and select **Duplicate Gig**. Modify the details for your new event and save. See [Templates and duplication](https://docs.soundchecklive.io/features/gigs/templates-and-duplication.md).

> [accordion] Is a gig the same as an event?
>
> Yes. **Event** is another word for a gig. Organizations whose business type is **Venue** see **Events** in place of **Gigs**, and clients see **Events** in the client portal. The word follows the organization's business type (**Settings → Organization → General → Business type**), not your role. You can't type your own word for gigs: **Settings → Labels → Terms** sets only what you call a group of gigs, such as a tour or series. See [Event](https://docs.soundchecklive.io/reference/glossary.md#event).

> [accordion] Can I move a gig to another organization?
>
> No. A gig stays in the organization that created it, and each organization's data is separate. To run it from another organization, create it there. To work on it with another organization, [share the gig](https://docs.soundchecklive.io/features/gigs/sharing.md#collaborators) with them where gig sharing is turned on.

> [accordion] Can I create gigs in bulk from a spreadsheet?
>
> Yes. Use the [Imports](https://docs.soundchecklive.io/features/imports/overview.md) wizard: Parse → Map → Review → Commit. Dozens of gigs in one pass. For the full migration recipe, see [Importing your season](https://docs.soundchecklive.io/use-cases/playbooks/importing-your-season.md).

## Editing & day-of

> [accordion] Can I change a gig's date after creating it?
>
> You can edit dates while preparing a gig. Once crew shifts are sent, moving the whole gig to different dates is restricted; cancel the affected shifts or create a new gig. Adding or removing days has a separate review flow. See [How shifts work](https://docs.soundchecklive.io/features/gigs/staffing-shifts.md#adding-or-removing-days-on-a-live-gig) before changing a staffed event.

> [accordion] How do I see all my upcoming gigs?
>
> The Gigs page shows your events, and the [calendar](https://docs.soundchecklive.io/features/calendar.md) provides a monthly overview. Your personalized **Home** page also shows what's coming up next when you sign in.

> [accordion] Can the team chat about a specific gig?
>
> [Chat](https://docs.soundchecklive.io/features/chat/overview.md) is **Private Preview**, available only to the existing beta tester group. The current web experience supports named text group chats within a gig, with selected participants and authorized manager oversight. Signup, paid plans, upgrades, support contact, and public demos do not grant access.

## Projects

> [accordion] What is a project?
>
> A project collects related gigs on the Gigs page: a tour, a festival season, or a residency. Bands and DJs see it called **Tour**, venues see **Series**, and you can set your own word under **Settings → Labels → Terms**. In the list, gigs sit under their project's header. In the **Projects** section above the list, expanding a project shows every gig in it plus a financial roll-up (**Revenue**, **Payouts**, **Net**). See [Projects and bulk edits](https://docs.soundchecklive.io/features/gigs/tours.md).

> [accordion] How do I add gigs to a project?
>
> In the list, check the gigs and choose **Project** in the bulk bar, then pick a project or **New project…**. In the **Projects** section, use **Add existing gigs** or **New gig in project** from a project's menu. Remove a gig anytime; it goes back to the ungrouped list unchanged.

> [accordion] What happens to the gigs if I delete a project?
>
> Deleting a project only removes the project. Its gigs return to your regular list with their data intact.

> [accordion] I don't see the Project option
>
> Only organization owners and admins can create projects and move gigs into them. In the bulk bar, **Project** also appears only when all the selected gigs belong to the same organization.

## Closing out

> [accordion] What are the gig statuses?
>
> A gig moves **Draft → Active → Completed → Settled**. **Cancelled** and **Archived** sit outside that cycle as terminal states. The status picker is in the gig header. See the [event lifecycle](https://docs.soundchecklive.io/reference/event-lifecycle.md).

> [accordion] Why can't I mark my gig Settled?
>
> Two things can block settlement:
>
> 1. **Payouts**: every crew payable must be settled first. If money is still processing, you'll see *"Settle all payouts in Finances first."* Handle payouts from the gig's **Finances** tab (Pro and above). See [payments](https://docs.soundchecklive.io/features/gigs/payments.md).
> 2. **Close-out checklist**: if your org enforces close-out gates, incomplete blocking steps (signed contract, received payment, etc.) lock **Settle**. You'll see *"Complete N close-out steps first."* When enforcement is off, money rows may still appear with a padlock as **tracked, not blocking**.
>
> See [post-event closeout](https://docs.soundchecklive.io/features/gigs/closeout.md) for the full picture, or the [closeout and payouts workflow](https://docs.soundchecklive.io/use-cases/playbooks/closeout-and-payouts.md) for the end-to-end recipe.

> [accordion] What is the close-out checklist?
>
> A six-step checklist on the gig's **Closeout** tab: **contract signed, quote approved, deposit received, invoice sent, payment received, feedback logged**. It tracks client paperwork and invoice steps, not crew payouts (those live on **Finances**, Pro and above). Money rows may show a padlock as **tracked, not blocking** when enforcement does not block settling. By default it's tracking-only. With **Enforce close-out gates** on (organization settings), incomplete blocking steps lock **Settle** and **Archive**. Enforcement applies only to gigs created after you turn it on; older gigs keep working as before.

> [accordion] Can an admin settle a gig even though the checklist isn't done?
>
> Yes. Owners and admins can use **Override & settle** with a logged reason. Payout settlement is still required; the override skips the checklist, not the money.

> [accordion] What's the difference between Cancelled and Archived?
>
> **Cancelled** means the show was called off. The gig stays in your records as never having happened. Cancelling is not blocked by the close-out checklist.
>
> **Archived** is a legacy filing state on older gigs. Current gigs finish as **Settled** or **Cancelled**; archiving is no longer part of the standard flow.

> [accordion] How do I cancel a gig?
>
> Open the gig's status menu and choose **Cancel gig**. Soundcheck shows what the cancellation affects before you confirm. **Cancelling cannot be undone.** Only Draft and Active gigs can be cancelled; Completed or Settled gigs already happened, so cancel is not offered.

> [accordion] What happens to confirmed members when I cancel?
>
> They receive a notification that the gig was cancelled. Soundcheck voids the unpaid or failed crew payables on the gig that have no payment started: shift pay, overtime, reimbursements and lines you added for a crew member. A voided line that's on a crew invoice turns that invoice **Needs update**. A payable with a payment started or recorded, including a partial payment, stays open, and the gig's **Activity** tab records it as **Crew pay kept after cancel** so you can settle it by hand.

> [accordion] I deleted a gig by mistake. Can I get it back?
>
> Yes, for 30 days. Open **⋯ → Recently deleted** on the Gigs page (in the mobile app, **Gigs → ⋯ → Recently deleted**) and choose **Restore as draft**. The gig comes back as a draft, and crew are not notified until you publish it again. After 30 days it's permanently removed. Completed and settled gigs, past gigs with accepted crew, and gigs with payment activity can't be deleted. See [Actions on a gig](https://docs.soundchecklive.io/features/gigs/overview.md#actions-on-a-gig).

## Related

* [Creating Gigs](https://docs.soundchecklive.io/features/gigs/creating-gigs.md): step-by-step guide
* [Projects and bulk edits](https://docs.soundchecklive.io/features/gigs/tours.md): group a run of gigs and edit many at once
* [Run of show](https://docs.soundchecklive.io/features/gigs/run-of-show.md): show-day rundown, exportable to PDF
* [Post-event closeout](https://docs.soundchecklive.io/features/gigs/closeout.md): Completed, Settled, and the checklist
* [Closeout and payouts workflow](https://docs.soundchecklive.io/use-cases/playbooks/closeout-and-payouts.md): end-to-end recipe


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