Player-Registration.md

@@ -65,9 +65,61 @@ Registration fees are maintained by inLeague but may be updated with two busines
 * Whether the player has registered siblings
 * The value of a question on the registration form (core or custom)
 
-### Scholarship and Coupon Discounts
+To review or update your fee schedule, please send a request to **support@inleague.io**. 
 
-## Division Placement and Division Caps
+### Scholarship
+
+The [legacy Scholarship System](https://gitlab.inleague.io/content/guides-and-documents/-/wikis/inLeague-Community-Guide) is supported by the 20th Anniversary Edition registration platform. Scholarships may be assigned to individual players or to families. The mechanism for doing so will migrate to the new player and user editors, but until it does, the legacy functions will continue to work.
+
+### Coupons
+
+inLeague has added support for registration coupons to our fee processor. We anticipate that administrative tools to manage available coupons should be completed by the Fall of 2022.
+
+## Division Placement, Age Calculation, and Division Caps
+
+### Age Calculation
+
+For every season, players are assigned an **AYSO Age** that is their "effective age" for a given membership year based on the cutoff used by the league.
+
+**Cutoff Dates** are one of:
+
+1. (Most leagues) **Full Year Calendar**: December 31st of the Registration Year (e.g. 12/31/22 for Fall 2022). This is the AYSO "standard" (as of 2016).
+2. **School Year Calendar**: July 31st of the Registration Year. This makes players born on or after August 1st effectively "younger" by one year.
+3. **Season Start Date**. For the youngest divisions (playground), it is possible to use the season's start date, e.g. "any player who turns 3 by the time the season starts." This requires additional configuration on the inLeague side; please contact inLeague support.
+
+### Division Placement
+
+Division placement is determined by the active, gender-appropriate division whose age cutoff is greater than the player's age as of the cutoff date for the registration year.
+
+Division gender configurations currently supported by AYSO and inLeague:
+
+1. (B)oy Divisions (B Division, **Force Co-Ed** is false)
+2. (G)irl Divisions (G Division, **Force Co-Ed** is false)
+3. (C)o-ed Divisions (B Division, **Force Co-Ed** is true)
+
+**Example**: If a boy born on December 1, 2017 registers for the Fall 2022 program with a December 31 cutoff, inLeague will determine their **AYSO Age** as **5** (2022 - 2017) and look for the first division whose age cutoff is greater than 5 that admits boys (typically **U6B**). 
+
+**Example 2**: If a girl born on December 1, 2015 registers for the Fall 2022 program with a December 1 cutoff, inLeague will determine their **AYSO Age** as **7** (2022 - 2015) and look for the first division whose age cutoff is greater than 7 that admits girls.
+
+* If a **U8G** division exists, inLeague will use that;
+* If no **U8G** division exists, inLeague will first look for a **co-ed U8** division
+* If no co-ed U8 division exists, inLeague will look for a **U9G** division (and so on: U9 co-ed, U10G...) until it finds one. If no division is found, the player will not be permitted to register.  
+
+### Division Caps
+
+Every division in every program may have a cap placed on the number of players that may register for that program, and then an action to be taken when the cap is reached:
+
+**1. Close Division** - no players may register once the limit is reached 
+**2. Waitlist** - registrations will be accepted but their status will be set to waitlisted once the cap is reached
+**3. No Action** - Nothing happens when the cap is reached.
+
+**Division caps are unique to each program in each season**. Fall 2022 Core registration may have different caps than Spring 2023 Core registration, which may have different caps than Spring 2023 Travel registration, and so on.
+
+Division caps are configured in the **Competition Administrator** under **Division Settings**:
+
+![image](uploads/1e6701209a121bbd3da780179fbed5c8/image.png)
+
+Note that the caps are enforced prior to the payment phase in the registration process, but only paid registrations are counted against the cap. It is possible, but unlikely that multiple players may "pass" the cap simultaneously and be permitted to register.
 
 ## Registration Form - Core Questions