|
|
# Table of Contents
|
|
|
|
|
|
1. [Introduction to Player Registration](#introduction-to-player-registration)
|
|
|
2. [Which Programs Need Registration](#which-programs-need-registration)
|
|
|
3. [Who May Register](#who-may-register)
|
|
|
4. [Registration Fees and Discounts](#registration-fees-and-discounts)
|
|
|
5. [Division Placement and Division Caps](#division-placement-and-division-caps)
|
|
|
5. [Registration Form - Core Questions](#registration-form---core-questions)
|
|
|
6. [Registration Form - Custom Questions](#registration-form---custom-questions)
|
|
|
|
|
|
## Introduction to Player Registration
|
|
|
![Player_Registration_Flow.drawio](uploads/c18c7ba4e68b09926c0c558da2ce7ebd/Player_Registration_Flow.drawio.png)
|
|
|
|
|
|
Once a player record is added to inLeague, they can be registered for one or more programs (also called competitions) every season.
|
|
|
|
|
|
A player registered for at least one program is considered "registered" for the season and all non-waitlisted record are sent to the AYSO Association Management platform.
|
|
|
|
|
|
Players may be registered in any program(s) for which they are eligible each season. There is no limit to the number of programs that may have registration running concurrently. Programs may register players for multiple seasons concurrently, if desired.
|
|
|
|
|
|
## Which Programs Need Registration
|
|
|
|
|
|
By default, players may only be assigned to teams in a program for which they are registered, but programs may be configured to draw their "player pool" from several places. Consider an example league that has a Core Program and a Tournament Program. The Tournament Program may be configured to draw players from:
|
|
|
|
|
|
* (Default) Players explicitly registered for the Tournament Program
|
|
|
* Players registered for any program
|
|
|
* Players registered for the Core Program
|
|
|
* Players who satisfy a custom eligibility rule
|
|
|
|
|
|
If our Tournament Program is a season-long (or longer) program with a player pool distinct from the Core Program, it might have its own program registration and fee structure. If it's just a one-off Thanksgiving Week Tournament and not a whole separate program, it might not have a standalone registration form and simply draw from players registered for the Core Program.
|
|
|
|
|
|
The "correct" solution is the one that collects the information you need with the fewest barriers to registration. [inLeague support](mailto:support@inleague.io) is happy to assist with registration setup!
|
|
|
|
|
|
## Who May Register
|
|
|
|
|
|
Eligibility for Program Registration is governed by a combination of registration dates, invitation lists, and/or eligibility rules.
|
|
|
|
|
|
![Screenshot_2022-03-27_113711](uploads/4474221aaeca0f58da1ad0d35e31cd5e/Screenshot_2022-03-27_113711.png)
|
|
|
|
|
|
### Default Configuration: All Players Eligible when Registration is Open
|
|
|
|
|
|
The default configuration for all programs is that every age-eligible player may register once registration opens on the designated date and time. **Every Program has separate Registration Start and End dates**. (Prior to 2022, these dates were global for each season rather than per-program).
|
|
|
|
|
|
Registration may be restricted by disabling the **Default Eligibility** option in the Competition Administrator.
|
|
|
|
|
|
### Restricted Registration: Invitations, Name/DOB, or Eligibility Rules
|
|
|
|
|
|
Programs that do not have **default eligibility** have three mechanisms to designate eligible players. Any player satisfying ANY of these three mechanisms will be eligible to register.
|
|
|
|
|
|
1. **Name and DOB**: Each program maintains a list of last names and dates of birth. Any player whose last name and date of birth matches an entry on this list may register. This is the recommended mechanism for any program that has new players, since the player record does not have to exist in inLeague at the time
|
|
|
2. **Explicit Invitation**: You may search for a player and select a specific record. The only reason to prefer this method over Name & DOB is that you can easily look up a player that already exists in the system whose name you know but whose date of birth you do not.
|
|
|
3. **Eligibility Rule**: Any player in the result set of any child-based (not registration-based) report in the Report Center may register. If eligibility is determined by numerous factors and maintaining a list of every individual isn't practical, an eligibility rule is a great way to catch a lot of players all at once. Exceptions can then be made using one of the other two mechanisms. **Eligibility rules auto-update every three hours.**
|
|
|
|
|
|
#### Restricted Registration: Ignore Dates if Eligible
|
|
|
|
|
|
Every competition has an option to ignore registration dates for players who are eligible via one of the three above mechanisms. This option can allow player-based (rather than family-based) "priority registration", or to permit individual players to register outside of the usual registration window without having to re-open registration for everyone.
|
|
|
|
|
|
## Registration Fees and Discounts
|
|
|
|
|
|
Registration fees are maintained by inLeague but may be updated with two business days' notice. Fees can be modified based on a number of factors:
|
|
|
|
|
|
* The program being registered for
|
|
|
* The date of registration ("Early Bird")
|
|
|
* The age of the player being registered
|
|
|
* Whether the player is new or returning
|
|
|
* Whether the player has registered siblings
|
|
|
* The value of a question on the registration form (core or custom)
|
|
|
|
|
|
### Scholarship and Coupon Discounts
|
|
|
|
|
|
## Division Placement and Division Caps
|
|
|
|
|
|
## Registration Form - Core Questions
|
|
|
|
|
|
## Registration Form - Custom Questions
|
|
|
|