Commissioner Managing Year-to-Year Carryover: How to Transition Between Seasons
Managing Year-to-Year Carryover
Carryover is what persists from one season into the next — rosters, settings, constitution — versus what resets (standings, points, bracket). Getting it explicit is the backbone of dynasty continuity: silent changes between years wreck the assumptions managers built their rosters on.
| Element | Carries over | Resets |
|---|---|---|
| Rosters (dynasty) | Yes — kept unless traded/dropped | No |
| Settings/scoring | Yes, unless formally amended | No |
| Constitution | Yes — last year’s is the baseline | No |
| Standings / points / bracket | No | Yes — fresh each season |
Why carryover management is critical to dynasty league continuity: dynasty leagues specifically depend on year-to-year carryover; if rosters reset between years, the league is no longer dynasty; if the commissioner changes settings between years without notice, managers make decisions based on old assumptions; clarity about what carries over prevents confusion and disputes.
Managing Year-to-Year Carryover
The carryover elements:
The structure: (1) roster carryover: in dynasty, managers keep their rosters year-to-year; existing players remain on the roster unless traded or dropped; new draft picks are added; (2) keeper carryover: in keeper formats, the subset of players marked as “keepers” remain on the roster; non-keepers are available for re-draft; (3) settings carryover: league settings (scoring, format, roster size, bench depth) should remain identical unless amended; (4) constitutional carryover: the league constitution from last season should be the baseline for this season unless amendments were voted on and approved; (5) connect carryover to constitution documentation — the constitution specifies which elements carry over year-to-year.
The carryover communication process:
The process: (1) before the new season begins, send all managers a “season carryover summary” that specifies: (a) which rosters carry over (dynasty) or are reset (redraft); (b) which settings from last season carry over unchanged; (c) any rule changes or amendments that were approved; (2) confirm manager understanding: ask managers to confirm they received the summary and understand the carryover; (3) publish the confirmed rosters and settings to the league platform; verify the platform reflects the carryover correctly; (4) the amendment process: if rule changes are proposed, use the standard constitution vote process to approve them before they take effect; (5) pair carryover management with off-season procedures — the post-season summary includes the carryover preview for the new season.
Carryover dispute scenarios:
The disputes: (1) the roster discrepancy: a manager claims their roster was not correctly carried over (a player was dropped who shouldn’t have been); (a) check the platform’s roster record; (b) if incorrect, restore the roster; (c) if correct but the manager misremembered, explain the discrepancy; (2) the setting change surprise: a manager assumed a scoring setting would carry over but it was changed; (a) check if the setting change was formally voted on and approved; (b) if yes, the change stands; (c) if no, revert the setting to maintain continuity; (3) the rule interpretation carryover: a manager claims a rule interpretation from last season should carry over; reference the constitution and prior rulings for consistency.
Worked Example: The Scoring Tweak Nobody Was Told About
Between seasons, a commissioner quietly bumps TE scoring to TE-premium because he personally likes it, and flips the platform setting without announcing it. Managers, assuming last year’s scoring carried over unchanged (as it always had), spend the offseason valuing tight ends normally and draft accordingly. When Week 1 scores post and TEs are worth 50% more than expected, the league erupts: managers who would have drafted a stud TE early feel cheated, and the commissioner is stuck defending a change he made unilaterally with no vote and no notice. The damage isn’t the rule itself — TE-premium is fine — it’s that it violated the silent contract of carryover.
The commissioner who manages carryover deliberately avoids this entirely. He treats last season’s settings and constitution as the locked baseline, and anything he wants to change goes through the amendment process — proposed, voted, approved — before it takes effect. Then, before the new season, he sends a one-page “carryover summary”: here’s what carries over unchanged, here are the amendments that passed and their effective date, here are your confirmed rosters. Managers confirm receipt, he verifies the platform matches, and no one is blindsided. When a manager later claims a player was wrongly dropped from his dynasty roster, the same discipline resolves it: check the platform record, restore if it’s wrong, explain if it’s a misremember.
Common mistake: changing settings, scoring, or rules between seasons without a vote and without explicitly communicating what carried over. Managers reasonably assume last year’s configuration persists and make roster decisions on that basis, so a silent tweak — even a good one — blindsides them and reads as the commissioner rigging the setup. Treat the prior season’s settings and constitution as the fixed baseline, route every change through a formal amendment vote before it’s live, and send a written carryover summary (what’s unchanged, what was approved and when, confirmed rosters) that managers acknowledge before the new season starts.
For how year-to-year carryover management connects to league governance, see our constitution guide and off-season procedures guide. Start at the commissioner hub for all resources.