A player may request to be RELEASED from a team during a given season. The objective of the player release is to allow a player who has signed on with a team he no longer wishes to play for, to join another team in the same division, or to avoid having that team limit his opportunity to join another team [due to the team maximum rule].
- The player being released AND the captain of the releasing team must both communicate the request with the league). The consent of the releasing captain is required in order to avoid situations where players leave teams without settling their financial commitments to the captain.
- The release must be validated by the league, and the current week of the season must come to an end before it is considered valid. (example: In week 3 of the season, a player plays with Team A on Saturday and is then released the following day. The release is only processed at the end of week 3/start of week 4, and not before- even if there are week 3 games held later in the week.)
Following a release, a player’s games played will no longer count towards his accumulated total with the former team, and they cannot be transferred over towards another team.
An individual can only be released once in a season. As a result, a player cannot receive a release from TEAM A, play for team B, receive a release from team B, and return to TEAM A; that would require two releases, which is not permitted.
Player releases are permitted until the end of week 6 in a ten game season and week 5 in an eight game season.
Retroactive releases are possible from Week 7 onward, but only if the player has not played with the team he is requesting the release from in week 7 or later.
The player will remain listed on the releasing team’s online roster following his departure, but his jersey number will appear as ‘R’.
Current season Player Releases, along with the release date, are listed below:
Ducks (Tier 2) release Steve Sanner (end of week 1)