One Sign-Up Link for the Whole Season: Event Series for Games, Concerts, and Market Days

A Season Is Not a Weekly Schedule

Here's the volunteer sheet every athletic director and booster parent knows: a column of dates, a column of matchups — MS Soccer vs St. Mark, game at 4:00 — and the same two jobs next to every one of them. Gate needs two people. Concessions needs two people. Twelve games, maybe thirty.

Scheduling tools have historically given you two bad ways to run it:

• A recurring roster assumes every occurrence is identical — same name, same time, every week. But Monday's game is at 4:00 against St. Mark and Thursday's is at 6:00 against Central, and some weeks there's a double-header. A repeating "Game Day" row tells volunteers nothing about which game they just signed up for.
• One sheet per game gets the details right and drowns you in links. Thirty games means thirty sheets to create, thirty URLs to share, and a group chat full of "which link is this week's?"

The season is its own shape: many distinct events that share one set of jobs. So we built a roster type for exactly that.

Event Series: The Season on One Link

Creating one takes two steps. First, define the roles once — Gate, 2 spots; Concessions, 2 spots. They repeat for every event automatically. Then list the events: each with its own name, date, time window, and location. New rows copy the previous row's time and location, because seasons repeat their patterns even when the details differ. Two games on the same day is fine — a middle school match at 3:30 and a varsity game at 6:30 each get their own card with their own spots.

You get one public link for the entire season. Volunteers open it and see every game grouped by date, with a jump strip across the top showing which days still need people ("Mon, Aug 31 · 3 open"). They claim a spot with just a name and email — no account — and the system enforces first come, first served. One parent can absolutely work the gate at the 3:30 game and concessions at the 6:30 game; the sheet treats each event separately.

Every confirmation email names the specific event, not just a date, and so does the reminder that goes out the day before. Nobody shows up for the wrong game.

Seasons Change. The Sheet Keeps Up.

The reason paper season sheets die by October isn't signups — it's changes:

• A game gets rescheduled. Edit the event's date or time, and everyone signed up for it gets an email with the new details automatically. Their spot moves with the game, and their day-before reminder re-arms for the new date.
• A game gets rained out. Cancel it and every volunteer with a spot is emailed once. The game disappears from the signup page, reminders stop, and their calendar feeds drop it. If it gets rescheduled after all, restoring the event brings every signup back exactly as it was.
• A playoff game gets added. New event, thirty seconds, same link everyone already has.

Who's Working the Gate?

By default, filled spots show an anonymous "Filled" — volunteers see what's taken without seeing who took it. But for a lot of teams, names are the point: parents sign up because they see a friend already did. So there's a per-link toggle to show volunteer names — first name and last initial only ("Linda D."), built so full names and emails never appear on a public page. Signups that still need your approval stay anonymous until you approve them.

Which Roster Type Do You Actually Need?

An honest decision guide, because we now have several and picking wrong is annoying:

• Same shifts, same time, repeating on a schedule (Sunday services, weekly practice snacks) → a recurring roster.
• One day, one event (bake sale, working bee) → a quick event.
• A run of different events sharing the same jobs (a sports season, a concert run, weekly market days with changing themes) → an Event Series.

If you've been maintaining a season sheet in SignUpGenius, this is the use case we built the series type against — here's the honest comparison, and the booster club guide covers the concession-stand side in depth.

The Bottom Line

A season of games is thirty different events wearing one uniform. Tools that force it into a weekly repeat lose the details; tools that force one sheet per game lose the parents. One link that knows every matchup, every start time, and every open spot — and emails people when their game moves — is the version that survives to the last whistle.