Skip to main content

Understanding Registrations

Learn how Registrations work inside Programs, how visibility and eligibility are controlled, and how pricing and payment options are managed at the registration level.

Updated over 2 weeks ago

Registrations are where the actual sign up experience for families lives. Programs give you the structure for a season or offering. Registrations decide who can join, what they pay, and what the sign up flow looks like.

This article explains how Registrations relate to Programs, the main types of Registrations, and how visibility, eligibility, and pricing work at the registration level.

How Registrations relate to Programs

Registrations are always created inside a Program.

A Program defines the overall offering, such as Fall Core Teams, Winter Break Camp, or Spring League.

A Registration defines the specific way a family signs up or individual options like separate camps, including price, eligibility, and questions.

Key points:

  • Every Program needs at least one Registration for families to register.

  • If a Program does not have any Registrations, it will not show to parents and players as something they can register in.

  • You can have as many Registrations as you need within a single Program.

  • For example, different age groups, different locations, or different packages can each have their own Registration.

  • Registrations can be:

    • Created from scratch using a blank setup, or

    • Created by duplicating an existing Registration and then adjusting the details, or

    • Created by using the Registration Import Template.

Most of your decisions about pricing and who is allowed to register are made at the registration level, not at the Program level.

Types of Registrations

There are two main types of Registrations that drive the default form and behavior:

Player Registrations

Player Registrations are the most common type.

  • A parent or guardian registers a single player into a Program.

  • This is used in all Program types, such as:

    • Core Programs

    • Supplemental Programs

    • Tryout Programs

    • Tournament Programs

    • League Programs

    • Other Programs

    • Training Sessions

    • Subscription Programs

Training Sessions have additional options that sit on top of Player registrations:

  • A la carte registrations

    • Families choose individual training times or options.

    • Often used when each timeslot or coach has its own price.

  • Bundle registrations

    • Families purchase a package of sessions, such as a 5 session pack.

    • They can often use those sessions over time rather than all at once.

Both of these are still Player registrations. They are just specialized patterns that are only available in Training Session Programs.

Team Registrations

Team Registrations are less common.

  • A coach, manager, or team captain registers an entire team into a Program.

  • This is most often used for:

    • League Programs, where teams join a league.

Technically, most Program types except Training Sessions and Subscription Programs can support Team Registrations, but in practice it is mainly Leagues that rely on them. Most Programs use Player Registrations only.

Payment plans

Payment plans are not created directly inside a Registration. They live in a separate area of the platform and can be connected to one or more Registrations.

  • A single payment plan can be tied to multiple Registrations.

  • Details of setting up payment plans are covered in a separate article.

Open vs Invitational and how Registrations fit in

Open vs Invitational is defined at the Program level, not the Registration level.

  • An Open Program means eligible families can see and register for available Registrations without an invitation, as long as their player meets the registration’s eligibility criteria.

  • An Invitational Program means families need to be invited to register and accept a spot.

At the registration level, there is no separate Open or Invitational toggle. Instead, there is one important connection for Invitational Programs:

  • For Invitational Programs, teams must be linked to specific Registrations. If no teams are selected on a Registration, then all teams are eligible for that Registration.

This tells the platform which Registration to show to a parent when they log in to accept a spot on a given team.

In other words, the Program controls whether a player needs an invitation. The team-to-registration link controls which Registration they see when they accept.

Registration-level visibility

Registration visibility is controlled by both the Program and the Registration.

A Registration will only appear to a family if:

  • The Program Start Date and End Date include today, and

  • The Registration Start Date and End Date also include today.

This allows clubs to:

  • Build out an entire season’s worth of Registrations in advance.

  • Open only the Registrations that should be available right now.

  • Keep later Registrations hidden until their Registration Start Date arrives.

Additional visibility controls:

  • Hide in Open Programs checkbox

    • If checked, the Registration will not appear in the standard Open Programs list.

    • It can still be used by sending a direct registration link to specific players or families.

    • This is often used in Open Programs when you want a more targeted flow without using invitations.

  • Max Capacity and waitlist

    • At the registration level, admins can set a maximum capacity.

    • Once that capacity is reached, a waitlist can be opened.

    • This lets you control how many players can sign up for each option while still collecting interest beyond that limit.

There are no separate “states” such as Draft or Archived exposed as labels to admins. Instead, dates, capacity, and hide options are how you control whether a Registration acts as open or closed.

Eligibility rules for Registrations

Eligibility is configured at the registration level and determines which players can see and use each Registration.

There are five main types of eligibility rules:

  • Birth Date Range

    • Only players whose date of birth falls within a defined range can register.

  • Grade Range

    • Only players in certain school grades can register.

  • Age Group Range

    • Age group is calculated at the player level using a defined start date, such as a school year cutoff.

  • Graduation Year Range

    • Only players with certain graduation years can register.

  • Gender

    • Registrations can be limited by gender when needed.

Typical best practice:

  • Use Gender plus one of the age related rules (Birth Date Range, Grade Range, Age Group Range, or Graduation Year Range).

  • Avoid stacking multiple different age related ranges on the same Registration, as that can make eligibility over-restrict players.

Beyond these main rules, you can also use registration history:

  • Pre-Conditions

    • Only show the Registration if the player has previously registered in a specific Program, Registration, or Team.

    • Useful for returners or advanced programs that require a prior step.

  • Exclusions

    • Prevent registration if the player has registered in certain Registrations before.

    • Prevent a player from registering in this option if they are already registered in another registration within the same program during an overlapping season.

    • Useful when you want to guard against duplicate enrollment.

Eligibility is checked when the User Dashboard loads after someone logs in. The system uses these rules to decide which Registrations to show in Open Programs and related views.

Pricing at the registration level

Pricing is defined on each Registration.

Key concepts:

  • List price

    • Every Registration has a base price set at the registration level.

  • Price overrides

    • Admins can set updated pricing that becomes effective on specific dates.

    • For example, an early bird price that changes to a standard price after a certain date.

  • Promo codes

    • A Registration can allow promo codes by enabling a checkbox in the registration configuration.

    • Details about discounts, credits, and promo code setup are covered in separate articles.

  • Payment plans

    • Payment plans are created outside of the Registration setup, in their own sub-navigation of the platform.

    • Once created, payment plans can be attached to one or more Registrations.

    • Families then choose between pay-in-full and any available payment plan options (if the club forces a selection, as described in Program settings).

Because pricing is handled at the registration level, Programs can host multiple Registrations with different prices, payment options, and effective dates, even though they all belong to the same overall offering.

How this fits with Programs

Putting it all together:

  • Programs give you the overall framework for a season, camp, league, or other offering.

  • Registrations inside those Programs control:

    • Who can register

    • What they pay

    • When registration opens and closes

    • Whether they sign up as a player or as a team

If something is not appearing for a family the way you expect, it usually helps to check:

  • Program Start and End Dates

  • Registration Start and End Dates

  • Registration eligibility rules

  • Whether the Registration is hidden from Open Programs or at capacity

Related articles

For more context and step by step guidance, see:

  • Programs Overview

  • Program Lifecycle & Visibility

  • Program Management for Admins

  • The Types of Programs articles, which explain how different Program types commonly use Registrations and teams

FAQs

Why isn’t my Registration visible to families?

A Registration only appears if both the Program Start/End Dates and the Registration Start/End Dates include today, and the player meets the eligibility rules.

Can I have multiple Registrations inside one Program?

Yes. You can create as many Registrations as needed within a single Program for different age groups, locations, sessions, or pricing structures.

Where are eligibility rules configured?

Eligibility rules are configured at the registration level, including age, grade, graduation year, gender, pre-conditions, and exclusions.

Are payment plans created inside the Registration?

No. Payment plans are created in a separate area of the platform and then attached to one or more Registrations.

Did this answer your question?