> ## 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. # Building teams for gigs > Staff a gig from org-scoped positions — build invitations as a draft and send them together, or post crew offers each recipient responds to individually. Staffing a gig means filling its **positions** with people. Soundcheck gives you two ways to do that — classic **invitations** you build and send, or per-recipient **crew offers** — and a cross-gig **staffing grid** for seeing your whole upcoming schedule at once. Invitations and crew offers both land in each recipient's [**My Mailbox**](/features/engagements/overview). Accepting on Soundcheck also auto-RSVPs the matching Google Calendar invite, so the team doesn't confirm twice. ## Positions are defined at the org level Every seat you staff is one of your organization's **positions** — Lead Vocals, Guitar, Sound Engineer, and so on. You manage that catalog once in [**Teams → Positions**](/organization/teams/positions), and every gig, invitation, and offer references the same org positions. That consistency is what makes staffing history and the [staffing grid](#the-staffing-grid) work across gigs. Set up your standard positions before you staff your first gig. Positions can be organized into sections and marked active/inactive at the org level. ## Two ways to staff: invitations and crew offers A gig staffs in **one mode at a time**, depending on what your organization has enabled: | | **Invitations** | **Crew offers** | | ----------------- | ---------------------------------- | ---------------------------------------------------- | | Section is called | **Team** | **Crew** | | You assign | A specific person to each position | A shift several eligible people can respond to | | Best for | A known lineup | Filling open shifts, or offering work to a shortlist | | Enabled by | The **draft team invites** feature | The **crew availability & offers** feature | The sections below cover each. If you're not sure which your org uses, look at the section heading on the gig — **Team** or **Crew**. ## Invitations: build as a draft, then send The invitation flow lets you assemble the whole team quietly and send it all at once — nobody gets paged while you're still deciding. In the gig's **Team** section, add each position and assign a person — an organization member, or an external contact by name and email. Set each one's **performance fee**, currency, and any position or fee notes. Save the team as a **draft**. A **Draft** badge shows on the Team section while any invitations are still unsent, so it's clear nothing has gone out yet. When the lineup is right, choose **Activate Invites** (or **Save & Send**). Soundcheck confirms — *"Send N invite(s)?"* — then sends exactly the unsent drafts. The draft stage is an all-or-nothing staging state for the whole team, and it's available only until the first invitation goes out. Once anything has been sent, the gig's team is live and you send new invitations directly as you add people. ### Call order and backups For a critical position, add more than one person in **call order** — a primary (call order 1) and backups (2, 3…). If the primary declines, the backup is next in line. ### Tracking responses Each invitation moves through **Pending → Accepted / Declined** (with a tentative/standby option). The Team section shows every person's status at a glance, and you're notified as people respond. ## Crew offers: one shift, many recipients Crew offers staff work as an offer that recipients respond to individually — useful when you don't yet know exactly who's taking a shift. ### Two offer types | Type | What it does | | -------------- | --------------------------------------------------------------------------------------------- | | **Open shift** | A role posted to several eligible people; it fills as they accept, up to the number of slots. | | **Job offer** | A targeted offer sent to a specific shortlist — every recipient can accept. | From the **Crew** section, create an offer with the position, date and time, fee, recipients, and an expiration. Choose **Save as draft** to attach recipients without notifying them yet, or **Send Offer** to notify them now. A drafted offer can be sent later, and you can **Send to more crew members** at any point. Every recipient is tracked individually — **Pending, Accepted, Declined, or Standby** — with their own response time. ### One roster, however seats were filled A gig's roster is the **union of its accepted invitations and its accepted crew-offer recipients**, de-duplicated by position and person. So whether a seat was filled by a direct invitation or an accepted offer, it shows up in one place and shares one response model. Crew offers can create financial obligations: an accepted offer with a positive fee becomes a payable on the gig. Owners and admins manage offer payouts; gig coordinators run operational staffing without P\&L or payout access. ## Fees become payouts The **performance fee** on an accepted invitation or offer becomes a payable item in the gig's **Finances**. Accepted, unpaid people can then be paid out — by direct deposit or card, or recorded as paid manually. How performance fees become crew payouts. ## The staffing grid When crew availability & offers is enabled, managers get a cross-gig **staffing grid** on the **Staffing** tab of the People/availability area. It's a matrix of your **org positions (rows)** against your **upcoming events (columns)**: * Each cell shows who's staffed for that position on that event — accepted, pending, and declined, with backups tagged **BU**. * Cells also surface the **available** members who said they're free that date and hold that position, so you can fill a gap without leaving the grid. * Each position row shows a **"N working"** count. This is the "who's covering what across the next few weeks" view — the place to spot an unstaffed position across every upcoming gig at once, rather than opening each gig one by one. ## Making changes * **Replace someone** — assign a new person to the position; the previous assignee is notified. * **Update fee or notes** — edit the assignment and save. * **Remove someone** — remove them from the gig; they get a cancellation notice. ## Troubleshooting Check the email address, look in spam, and confirm they haven't unsubscribed from notifications. Confirm they're part of your organization and that you have permission to staff gigs. Try searching by email. Positions come from your org catalog — add it in [Teams → Positions](/organization/teams/positions) first. ## Next steps Set up your organization's position catalog. Reusable lineups with backup call order. Where invitations and offers reach the crew. Turn accepted fees into payouts.