> ## 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. # Post-event closeout > Close a gig out after the show — work the close-out checklist, settle the money behind a gate, and capture reviews. A gig's life doesn't end when the show does. **Closeout** is the back half of the [event lifecycle](/reference/event-lifecycle): the gig completes on its own once the date passes, you work a short **close-out checklist**, you **settle** the money once every payout has cleared, and you capture **reviews** of how it went. This is what makes Soundcheck a system of record for the whole gig, not just the booking. Closeout lives on the **Closeout** tab of the gig detail, which appears for managers on gigs that have taken place (or are closing out). Settling itself happens from the **status pill** in the gig header. ## How a gig completes You never mark a gig *Completed* by hand. Once the event date passes, Soundcheck moves the gig into the Completed phase automatically — the status pill reads **Completed** and the gig drops out of active operations into closeout. From there, the remaining work is settling and reviewing. ## The close-out checklist The Closeout tab shows a checklist of the steps that finish a gig financially — typically: * **Contract signed** * **Quote approved** * **Deposit received** * **Invoice sent** * **Payment received** Each row shows its state on the right: | State | What it means | | ------------------------- | ---------------------------------------------------------------------------------- | | **done** | Checked off. | | **blocking** | Incomplete and holding up close-out (when your org enforces the checklist). | | **blocks settle** | Incomplete and holding up settlement specifically — e.g. payment not yet received. | | **tracked, not blocking** | Incomplete, recorded for visibility, but not stopping anything. | | **optional** | Never blocks. | Above the list, a **stage chip** tells you where the gig sits — for example *Delivered · awaiting payment* or *Ready to settle* — and a **days-in-stage** counter flags a gig that's been stuck (it turns red once a blocked gig sits in the same stage for a week). This is your at-a-glance "which finished gigs still need attention" view. Whether the checklist actually **blocks** anything is an organization setting. When enforcement is off, the same steps still appear and track your progress — they just don't gate settling. When it's on, the settle-blocking steps must be complete before you can settle. ## Settling a gig Settling closes the gig on the books. You do it from the **status pill** in the gig header, not the Closeout tab. Choosing **Settled** only succeeds when every gate is clear: Settlement is a post-event action — the gig has to be Completed first. All crew payouts must be settled. If any are still processing, the option reads *"Settle all payouts in Finances first."* See [payments](/features/gigs/payments) for how payouts clear. When your org enforces the checklist, the settle-blocking steps must be checked. Until then, the option reads *"Complete N close-out step(s) first."* Once it settles, the gig is **Settled** — the final, fully-closed state. If you settle by mistake, an admin or coordinator can **un-settle** it back to Completed. ### Admin override Sometimes you need to settle a gig before the paperwork is fully caught up. Organization **owners and admins** can override a blocked checklist: The override dialog opens instead of settling directly. Settling early requires a written reason — this is logged, not optional. The gig settles, and the override is recorded on the Closeout tab: *"Settled with override by \[name] — '\[reason]'"* with a date. An override skips the checklist, **not** the money. Payouts still have to be settled first — the override only forgives incomplete close-out steps. Coordinators without override permission see the settle option disabled with the number of steps still outstanding. ## Reviews Closeout is also where you record how the gig went. The Closeout tab has a **Reviews** section with a star rating and notes for: * **The overall event** * **The venue** (when the gig has one) * **Each team member** who accepted and worked the gig Captured here, these become part of the gig's permanent history and feed the reputation signal that follows people and venues into future gigs. ## Cancelled and archived gigs Not every gig reaches Settled. A gig that gets **called off** is **Cancelled** — a status you set from the header pill while the gig is still a Draft or Active. Cancelling is **never gated** by the close-out checklist and shows you what it will affect before you confirm. That's different from **Archived**, a legacy filing state for delivered gigs. See [Cancelled vs. Archived](/reference/event-lifecycle#cancelled-vs-archived) for the full distinction. ## Why closeout matters Every gig coordinated in Soundcheck becomes a verified record of who did what, with whom, and whether they were paid. Closeout is the step that makes that record complete — turning a finished show into trustworthy history rather than a stale "active" gig nobody updated. ## Related Every state a gig moves through, and what gates each. How crew payouts are funded and cleared before you settle. Closeout status that flows back to your CRM.