Skip to main content

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.

The crew calendar is a denser, more powerful view than the personal calendar — it overlays every member’s availability so admins can spot coverage gaps and book quickly. This page covers the four workflows that show up most.

Workflow 1: Read the calendar at a glance

Open Calendar → Crew view (admins and gig coordinators only).
  • Green blocks are members who marked themselves available.
  • Red blocks are members who marked themselves unavailable.
  • Grey blocks are members who haven’t responded to a request for that range.
  • Filled boxes are members already booked on a gig (linked to the gig name).
Use the Position filter to show only Drummers, only FOH, etc. Use the Date range to scope to a tour leg or a single weekend.

Workflow 2: Send an availability request

You have three dates on the books and you don’t know who’s free. Don’t text everyone — send a request.
1

Open Crew view

Calendar → Crew.
2

Select dates

Click a date or drag across a range. The action sheet pops up.
3

Choose recipients

Filter by position (e.g., Drums), by call list (e.g., A-Team Tour), or pick individual members.
4

Send

Recipients get a push notification + an entry in their Engagements inbox. They respond Yes / No / Maybe per date.
Track responses in the same Crew view — green/red blocks update as members respond.

Workflow 3: Act on responses

When you’ve got enough Yeses to staff a gig:
  • Tap a green block → Book for gig → pick the gig and position.
  • Or, from the gig page → Build team → the response data preselects “available” members for that date.
Members get an invitation. Their availability response auto-converts to a confirmed booking when they accept.

Workflow 4: Book directly from the calendar

For ad-hoc gigs that aren’t yet in the system:
  1. From Crew view, click a date.
  2. Tap + Create gig.
  3. The gig form pre-fills with the date.
  4. After saving, the Build team step pre-selects members marked available for that date.

Patterns we see admins use

Send a recurring availability request every Sunday for the upcoming week. Members get used to the cadence and respond proactively.
Before each leg, send a single availability request covering the full leg’s date range. Filter by tour-leg-specific positions. Use responses to build the call sheet for each show.
When your A-team is booked but a gig drops in, filter the crew calendar to your B-team call list, see who’s open, and send a targeted request.

Permissions

ActionOwnerAdminGig CoordinatorMember
Read Crew viewYesYesYesNo (sees personal only)
Send availability requestsYesYesYesNo
Book a member from the calendarYesYesYesNo
Edit other members’ availabilityYesYesNoNo
See Roles and permissions.

Personal availability

What members see and edit.

Availability requests

The recipient side of the request flow.

Call lists

Build the rosters you filter the calendar by.

Touring lineup

Variable-lineup tours with subs.