Festival Volunteer Shifts: A Three-Day Station Roster That Keeps Up With Changes

Three days, nine stations and sign-ups that keep changing

A weekend festival runs on volunteers. Each station, from the main gate to the recycling point to the kids tent, needs a minimum number of people for every shift from Friday afternoon to Sunday evening. Volunteers pick shifts through a Calendly link, then swap, cancel and book again, and the roster still has to show who is where at every hour.

Sign-ups live in Calendly, the roster the station leads use is in Airtable, the shift calendar that volunteers and leads see is in Google Calendar, the station map and coverage minimums are in Google Drive, and during the festival everything runs through Slack. When a volunteer reschedules, Calendly records a new booking. If the roster adds a new row and the calendar a new event, that person now counts twice, and the gap it hides is real.

Who works in the room

Everything for the festival happens in one Kylon room. Ryan is the default agent, so any question about who is on a shift reaches it. The room guidelines send anything addressed to volunteers to Fin. When Ryan finds a gap, it mentions Fin with the station, the shift and the volunteers who offered extra time, and Fin drafts the ask. Ryan reads Calendly and writes to Airtable and Google Calendar through a grant the coordinator approved for this room, and each write still waits for the coordinator's approval.

Building the roster and keeping it true

The roster covers Friday through Sunday only, and the room guidelines say so, which leaves Thursday load-in and Monday teardown to their own crews.

When the brief is one line and the weekend keeps moving

The request to build the roster is often one line in Slack. Ryan reads the scope from the coverage plan in Drive and, where the plan is silent, asks the coordinator in the thread before it writes anything. Bookings that fall outside Friday to Sunday are set aside with a note, never added or dropped without a word.

Through the week, every change arrives as a Calendly event: a swap, a cancellation, a new sign-up. Ryan matches each one to the volunteer's existing row and event before proposing anything, so a reschedule moves one record instead of creating two. After each batch the thread shows the roster and the calendar side by side, and the coordinator approves both together.

What the checks catch

• A Thursday or Monday booking from an old link that falls outside the festival window
• A rescheduled volunteer who appears on both the old shift and the new one
• A roster row with no matching calendar event, or an event with no row behind it
• A station that looks covered because a canceled volunteer still counts

What stays with people

• Approving every roster and calendar change before it is written
• Sending confirmations, reminders and requests for extra shifts, which Fin drafts
• Deciding which station goes short when there are not enough volunteers
• Accepting replacements at each station during the festival

Integrations in this workflow

Kylon is not a volunteer management platform and it does not replace a sign-up tool. It works across the tools the festival team already runs and keeps the coordination in one room.

• Airtable
• Calendly
• Gmail
• Google Calendar
• Google Drive
• Slack

• Calendly is where volunteers book, reschedule and cancel their shifts
• Airtable holds the roster the station leads work from
• Google Calendar carries one event per shift assignment, created or updated after the coordinator approves
• Google Drive keeps the station map, the coverage minimums and the volunteer guide
• Gmail sends confirmations and requests through drafts the coordinator sends
• Slack is where station leads post no-shows and early finishes during the festival

Where to start

Try it on one weekend with a handful of stations. Connect Calendly and the Airtable roster, and set one rule in the room guidelines: every booking is matched to an existing volunteer row before anything new is created, and the coordinator approves the roster and the calendar together.

“A roster is right when the base, the calendar and the people at the gate all agree.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.