Skip to main content

Program & Registration Overview

Understand how Programs and Registrations work together to power your club’s offerings. This guide explains the structure behind sign-ups and how to create a clear, flexible registration experience for families.

Updated over a week ago

Every club runs seasons, camps, clinics, and teams.

But behind every successful season is a clear structure that keeps everything organized — for you and for families.

In Sprocket, that structure is built around two connected pieces:

Programs and Registrations.

They work together to help you:

  • Organize your offerings

  • Guide families through sign-up

  • Manage participants clearly

  • Keep seasons structured and scalable

When set up correctly, they create one seamless workflow from planning your season to building teams and communicating with families.


What Is a Program?

A Program is the overall bucket for a specific offering or season.

It is where you define what you are running and who it is for.

Common examples include:

  • Fall Recreational Soccer

  • Summer Camp

  • Winter Skills Clinic

  • 2026 Travel Volleyball

Inside a Program, you organize details such as:

  • Season

  • Program Type

  • Team structure

  • Age groups

  • Locations

  • Start and End Dates

The Program defines the structure of your offering.

In simple terms:

The Program is the container.

In Camps & Clinics Programs, there is an additional organizational layer called a Group. Groups sit between the Program and Registrations and allow you to organize sessions by location, format, skill type, or season block while applying shared settings across multiple registrations.

Structure in most Program Types:
Program → Registration

Structure in Camps & Clinics:
Program → Group → Registration → Event Dates


What Is a Registration?

A Registration is the sign-up experience families see.

It is the form that:

  • Collects participant information

  • Collects waivers

  • Processes payment (if required)

  • Applies eligibility rules

Each Registration is tied to one specific Program.

Anyone who signs up through that Registration is automatically connected to the correct Program.

In simple terms:

The Registration is how families enter the container.

In Camps & Clinics Programs, Registrations may be structured as:

  • Session Only

  • Session + Drop-Ins

  • Drop-In Only

Drop-in registrations are automatically generated from scheduled event dates. Capacity is enforced per event date, meaning a specific date can reach capacity even if other dates remain available.


One Program, One or Many Registrations

You can choose to have:

  • One Registration for a Program

  • Multiple Registrations inside the same Program

Many organizations use a single Registration when:

  • All participants follow the same structure

  • Pricing is the same

  • Requirements are consistent

Others use multiple Registrations when they want to:

  • Offer different options (Local, Regional, National)

  • Separate age groups into different sign-up flows

  • Use different waivers or forms by division

  • Provide different pricing for each team

  • Offer early bird vs standard pricing paths

The system supports both simple and detailed setups — so your registration flow can match how your organization actually operates.

In Camps & Clinics Programs, Registrations are organized inside Groups, and scheduling event dates supports session-based and drop-in models.


Program Types Shape How You Run Activities

There are different Program Types available, each designed to support a specific structure.

Program Type impacts:

  • How participants are placed

  • Whether teams are required

  • How seasons are organized

  • How tryouts connect to team placement

  • How scheduling and capacity are managed

For example:

Core Programs are typically used for full-season teams.
Camps & Clinics is used for session-based programming and flexible drop-ins with per-date capacity control.

You will find more details about each Program Type in the articles that follow.

Choosing the right Program Type ensures your structure matches your real-world operations.


The Typical Workflow

In day-to-day use, admins follow a simple and repeatable pattern:

  • Set up the Program

  • Create the Registration

  • Open it to families

  • Manage the participants who sign up

  • Assign teams and communicate

In Camps & Clinics Programs, scheduling event dates and generating drop-ins is part of the registration setup process.

This creates one connected workflow from planning your season through to building teams and supporting families.


Why This Structure Matters

When Programs and Registrations are structured clearly:

  • Families only see what applies to them

  • Pricing stays organized

  • Eligibility rules prevent confusion

  • Teams are built cleanly

  • Reporting stays consistent year over year

It allows you to scale without creating chaos.


Frequently Asked Questions

What is the difference between a Program and a Registration?
A Program defines the season or offering. A Registration defines how families sign up for that offering. In Camps & Clinics Programs, a Group layer sits between the Program and Registration to support session-based scheduling.

Can I have multiple Registrations in one Program?
Yes. Many clubs create separate Registrations for age groups, pricing models, or divisions within the same Program. In Camps & Clinics Programs, multiple Registrations may exist within a Group to support session and drop-in options.

Do I need multiple Programs for different age groups?
Not necessarily. You can often use one Program and create multiple Registrations inside it. In Camps & Clinics Programs, you may organize age groups within Groups rather than creating separate Programs.

What happens after families register?
Participants are connected to the Program and can then be rostered to teams, scheduled for events, and included in communication workflows. In Camps & Clinics Programs, participants are connected to scheduled event dates and attendance tracking is managed per event.

Did this answer your question?