Pokémon Draft League Transactions and Free Agency
A transaction system should let coaches repair a roster without turning every move into a private ruling. The exact limits can vary, but everybody should know when a player is available, when a claim becomes official, how ties are resolved, and when roster movement closes. The safest rule is simple: chat can start a conversation, but only the league's official workflow changes a roster.
Separate trades from free agency
A trade moves rostered Pokémon between teams after the required managers agree. Free agency adds an undrafted or released Pokémon and usually drops another roster member. These actions have different timing and consent rules, so the rulebook should not describe them as one generic transaction.
How this works in DraftCenter
DraftCenter keeps trade proposals, responses, add/drop moves, claims, and the official transaction log together while preserving the distinct state of each action.
Choose instant moves or scheduled claims
Instant free agency rewards quick decisions and is easy to understand, but time zones can create an advantage. Scheduled claims collect requests until a published processing time, then apply the league's priority rule. Choose the method that matches how competitive and time-sensitive your group wants roster movement to be.
How this works in DraftCenter
DraftCenter can apply an eligible move immediately or queue claims for commissioner processing, according to the saved league setting. Managers see the active method before submitting.
Publish limits and deadlines before week one
State any weekly and season-long move limits, trade deadline, last free-agency week, cooldown, roster-size rule, and postseason lock. Explain whether a reversed mistake restores a transaction and who may approve an exception. Limits should be visible before a coach needs them.
How this works in DraftCenter
The Transactions view shows remaining eligibility and blocks moves that conflict with saved roster, timing, and playoff rules. Commissioners configure the operational limits in Setup.
Define what makes a transaction official
A proposed trade is not complete until every required response is accepted and the official roster is saved. A claim is not a roster spot until processing succeeds. Managers should confirm the resulting roster instead of relying on a message, reaction, or stale browser view.
How this works in DraftCenter
DraftCenter records accepted trades and completed add/drop moves in the league state. Pending, rejected, cancelled, and reversed actions remain distinguishable from active roster changes.
Use reversals for corrections, not secret exceptions
Mistakes happen: the wrong Pokémon may be dropped, a result may reveal that the deadline already passed, or a commissioner may need to undo an ineligible move. Reverse the recorded action with a visible explanation and apply the same standard to every team rather than editing history out of sight.
How this works in DraftCenter
Authorized commissioners can reverse supported transactions while DraftCenter retains the transaction history needed to understand why the roster changed.
Keep rulings and roster history in durable places
A chat server is useful for alerts and discussion, but messages can be missed or edited. Publish material deadline changes and disputed rulings where every coach can find the same version. The official roster and transaction record should remain the source of truth.
How this works in DraftCenter
Use the League Board for durable announcements, Transactions for roster movement, and optional Discord connections for selected notifications. Personal alerts remain each member's choice.
Transaction rules to publish
- Trade consent, cancellation, deadline, and reversal rules are explicit.
- Free agency is labeled instant or claim-based with a processing time and time zone.
- Weekly, seasonal, roster-size, and postseason limits match the saved settings.
- Coaches know where to confirm that a move became official.
- Material exceptions and corrections receive a durable league-wide explanation.
How this guide is maintained
DraftCenter reviews this guide against the product's current workflows. See our data methodology and editorial standards, including how to report a correction.