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

# Entertainment agencies

> Coordinate multiple acts and bookings with separate gig rosters, venue details, call times, and payouts.

Soundcheck helps entertainment agencies coordinate the people and delivery details for several bookings at once. Keep one gig per engagement, then connect its customer, venue, accepted roster, show schedule, files, and payments. Shared Teams and venue records help with repeat work; each gig keeps its own lineup and instructions.

## Before you begin

* Use the agency's organization, with permissions to manage the relevant gigs.
* Define your positions, such as lead vocals, keys, DJ, sound engineer, and stage manager.
* Add the people you regularly book, and prepare saved [Teams](/organization/teams/call-lists) if your plan includes them.
* Confirm which features are enabled. Leads, availability, and crew offers have plan and organization requirements; see the [feature comparison](/subscriptions/feature-comparison).

<Note>
  CheckAI, Chat, and E-sign are **Private Preview**, available only to the existing beta tester group. Signup, paid plans, upgrades, support contact, and public demos do not grant access. You can attach an agreed contract as a file without sending it for signature.
</Note>

## Run a weekend of bookings

<Steps>
  <Step title="Create a gig for each engagement">
    Record the customer, date, timezone, and venue. If you use [Leads](/crm/leads/overview), convert a qualified booking to a gig and customer. Otherwise create the gig directly. Keep separate engagements as separate gigs so each has its own staffing and money record.
  </Step>

  <Step title="Prepare each venue">
    Link the [venue record](/crm/venues). Confirm the production contact, stage details, house equipment, load-in, load-out, dock, elevator, and parking. Review event-specific access changes before telling the act when and where to arrive. Use the [production-company workflow](/use-cases/production-company) when the booking also requires technical production.
  </Step>

  <Step title="Check the people across all shows">
    Where enabled, use the crew calendar and staffing view to review accepted bookings and unknown availability. Send [availability requests](/features/availability/availability-requests) for the relevant days or time windows. An available answer is not a booking; confirm travel and turnaround when considering someone for two calls.
  </Step>

  <Step title="Build and send each roster">
    Apply the appropriate saved Team or build the gig manually. Review positions, call times, recipients, and fees before sending. Use invitations for a named lineup or crew offers when that is the gig's staffing mode. Track each response in [Mailbox](/features/engagements/overview) and on the gig.
  </Step>

  <Step title="Brief the people who accepted">
    Keep the [run of show](/features/gigs/run-of-show), setlist, dress notes, charts, and venue access information current on each gig. Confirm that the right people have the information they need; access to full venue contacts and specifications follows role permissions.
  </Step>

  <Step title="Close each booking and reconcile the weekend">
    After delivery, complete each gig's [closeout](/features/gigs/closeout). Owners and admins review the accepted fees and [payouts](/features/gigs/payments). Resolve outstanding money before settling the gig. A tour folder can group a related run, but it does not replace each show's roster and closeout.
  </Step>
</Steps>

## Example: one agency, three Saturday engagements

*Fictional example:* Cedar & Co. has a hotel reception, a corporate launch, and a late club show. Its regular keys player is proposed for both the reception and the launch.

| Engagement       | Staffing decision                                                              | Venue preparation                                           |
| ---------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------- |
| Hotel reception  | Send the reception lineup after confirming the full call                       | Confirm the service entrance, parking, and load-out time    |
| Corporate launch | Ask an alternate keys player about the working window, then send an invitation | Confirm house audio, stage size, and the production contact |
| Club show        | Review the later band's travel and turnaround before booking                   | Confirm the evening dock window and shared backline         |

A scheduler reviews the possible overlap instead of treating a clear calendar as proof the travel works. If a player declines, check any configured backup invitation before contacting another replacement. Each gig is covered only when its required people have accepted.

## Next steps

<CardGroup cols={2}>
  <Card title="How to staff a gig" icon="users" href="/faq/workflows/how-to-staff-a-gig">
    Build positions, send work, and track acceptance.
  </Card>

  <Card title="Production companies" icon="truck" href="/use-cases/production-company">
    Coordinate crew, equipment, venue details, and show schedules.
  </Card>

  <Card title="Corporate & private events" icon="champagne-glasses" href="/use-cases/corporate-private-events">
    Connect the booking pipeline with event delivery.
  </Card>

  <Card title="Rotating band lineups" icon="route" href="/faq/workflows/crew-scheduling-for-bands">
    Handle a substitute for one local show.
  </Card>
</CardGroup>