To limit an offering (division) to players of certain ages, set the program's Age Validation Type to Age As Of on 1 Setup, then give each offering an Age As Of Date, an age or birth-date range and an Age Restriction Action. With Prevent, families only see the offerings that fit the player's age; with Warning, they see a warning message but can still register.

Applies to: Org admins · All plans (Team Registration plus Roster programs and Update Multiple Offerings: Enhanced, Elite and Enterprise; Youth Camp: Camp & Activity module) · Youth, Adult, Youth Camp and Team Registration plus Youth Roster programs

Where: Programs > Manage Programs > (your program) > 1 Setup, then 2 Configuration > Offerings

Before you start

• Age As Of is available on Youth Registration, Adult Registration, Youth Camp Registration and Team Registration plus Youth Roster Registration programs. Team Registration, Youth & Adult Registration and Team Registration plus Adult Roster Registration programs don't have it.
• Adult programs check the adult's own birthday, so Age Validation Type only appears on an Adult Registration program when Customers > Configurations > General > Birthday is set to Yes, Required or Yes, Optional.
• Everyone you want to check needs a birth date on file. With Prevent, a person with no birth date can't register for the offering.

Step 1: Turn on Age As Of for the program

1. Go to Programs > Manage Programs.
2. Click the program's name, then open 1 Setup.
3. In Age Validation Type, select Age As Of.
4. Click Save.

A program uses one Age Validation Type. The other choices, Custom Validation (birth-date ranges you build under Custom Grade Validation) and Grade Validation (Player Grade), are covered in the related articles below. Team Registration plus Youth Roster programs offer only None and Age As Of.

Step 2: Set the age rule on each offering

1. Open 2 Configuration. For a Team Registration plus Youth Roster program, open 2b Roster Configuration.
2. Under Offerings, click Add Offering, or click the Edit icon on an existing offering.
3. In Age Restriction Action, choose None, Warning or Prevent (see the table below).
4. In Age As Of Date, enter the date ages are counted on, for example your league's August 31 cutoff.
5. In Restriction Range Type, choose Age (an age range) or Date (a range of birth dates).
6. In Age Restriction, enter From and To.
7. Click Save (or Add when you're adding a new offering).

The age fields appear on offerings only after Step 1 is saved. Each offering has its own Age As Of Date, so offerings in one program can use different cutoff dates.

Age Restriction Action

How to enter the age range

On Add Offering and Edit Offering, the range includes both numbers you enter, counted on the Age As Of Date:

Add .5 for a half year, as the hint next to the field says ("Add .5 for half year. Example 4.5"). No other decimals are accepted.

With Date, enter the earliest and latest birth dates. People born on or between those dates are eligible.

How to update many offerings at once (Update Multiple Offerings)

1. On 2 Configuration, click Update Multiple Offerings. The button shows when the program has more than one offering and your plan includes it (Enhanced, Elite and Enterprise).
2. In Step 1: Select Offerings to update, check the offerings, or check All Offerings.
3. In Step 2: Update, fill in only the fields you want to change, such as Age As Of Date. Fields you leave blank, or at Select, keep each offering's current value.
4. Click Update. You'll see "Multiple offerings have been updated."

Important: on this page, To is one more than the oldest age. For 5- and 6-year-olds, enter From 5 and To 7, as the hint on the page says. That's different from Add Offering and Edit Offering, so after a bulk update, open one offering with Edit and check the range it shows (5 To 6 in this example). The age fields on this page are available only for Youth Registration programs.

What you'll see

• On the program's details page, each offering set to Warning or Prevent shows its eligible birth dates under the offering name. For example, with an Age As Of Date of August 31, 2026 and a range of 5 To 6, it shows "DOB: 09/01/19 - 08/31/21 (5 and 6 year olds)".
• With Prevent, a family registering a player sees only the offerings that fit that player.
• On a Team Registration plus Youth Roster program, the roster offering's rule is also checked against the date of birth entered when a player is added to a team's roster.

If it doesn't work

• Families can choose any offering and no warning appears. Check that Age Validation Type on 1 Setup is Age As Of, that the offering's Age Restriction Action is Warning or Prevent, and, when Restriction Range Type is Age, that the offering has an Age As Of Date. Without that date, the age range isn't checked at all.
• A player can't see an offering they should qualify for, or the family sees "There are no available offerings to enroll in for the enrollment type and program selected." With Prevent, an offering is left out when the player's birth date is missing or outside the range. Check the birth date on the player's record and open the offering with Edit to check its range. If the range was entered on Update Multiple Offerings as 5 and 6, it covers only 5-year-olds; set it to 5 To 6 on Edit Offering.
• "Enrollee birthday is required. Navigate to the profile page and update before adding this enrollment to the cart." The offering uses Prevent and the person being enrolled has no birth date on file. The family adds it with Edit Member on the Members page of their account, or an admin adds it in the customer's account.
• "Player age does not match Offering age restrictions. Please check offering details for age restrictions. (Note: Age is calculated based on the Age As Of Date.)" The player's age on the Age As Of Date is outside the offering's range. With Warning, the family can continue. To make an exception under Prevent, an admin can enroll the player through Place Order.
• "The date of birth is not within age requirements for this Offering." Someone added or edited a player on a youth roster whose roster offering uses Prevent, and the date of birth is outside the range. With Warning, the message starts "Please note:" and the change is still saved.
• Errors when you save an offering:
  • "Age Restriction From field required when other Age Restriction fields are populated." or "Age Restriction To field required when other Age Restriction fields are populated." Enter both From and To.
  • "Invalid Age Restriction from field value." or "Invalid Age Restriction to field value." Use whole numbers or .5 only.
  • "The Age Restriction To field must be equal or greater than to the Age Restriction From field." Make To the larger number.
  • "Age Restriction" field "To" must be greater than 0 when "Age Restriction Action" field is Warning or Prevent. Enter a To age of at least 1.
  • "The Age Restriction From field cannot be greater than the Age Restriction To field." With Date, From must be the earlier birth date.

Good to know

• Ages are counted on the offering's Age As Of Date, not on the day the family registers.
• Admins aren't blocked by Prevent in Place Order or Transfer: both show a warning ("…Age is calculated based on League Age As Of Date.") and let you continue. Adding a player to a youth roster does follow Prevent.
• Imports don't check age, and changing an offering's age settings doesn't re-check or move anyone who is already enrolled. To review placements, use the Age As Of filter (Add Filter) or the League Age highlight on Assign To Roster.
• Smart Auto Assign uses each offering's Age As Of Date for its "Age as of" criterion. If an offering has no date, it counts ages on the day of the run.
• Gender Restrictions on an offering are a separate check from age.
• Age As Of settings belong to each organization's own offerings, so in a parent/child setup each child organization sets its own dates.

Related articles

• How To Set Up Grade Validation
• How To Enable Auto Grade
• How to Create an Individual Registration Program
• How to Place an Order for a Customer
• How To Assign Rosters