Writing a ruleset players actually follow

The disputes that kill leagues come from ambiguity, not cheating. What to write down before your draft, and how to keep the document short enough that people actually read it.

Ask anyone whose league collapsed and you’ll hear the same story with different names in it. The villain is almost never a cheater; it’s a situation nobody wrote a rule for. Two coaches can’t schedule their match and each blames the other. A trade goes through that half the league thinks is lopsided. The season ends in a three-way tie and three people discover they’ve been assuming three different tiebreakers. None of these people did anything wrong. The league just never decided, and now every possible decision looks rigged in someone’s favor.

The whole craft of ruleset writing follows from that: a rule made before the season is policy, and the same rule made mid-season is a ruling against someone. Your job as commissioner is to move every predictable dispute into the first category while it’s still abstract and nobody’s season hangs on it. And the disputes are predictable, because every league hits the same four.

What to codify: the four load-bearing sections

1. The pool and the bans

Define exactly what can be drafted and what can’t. This means the eligible pool, anything banned outright, and (this one is easy to forget) anything restricted in combination: things legal to draft but limited in how or how often they’re used. If your game has options the group finds legal-but-miserable, decide on them now, by name. A rule like “don’t bring anything degenerate” just schedules the argument for later.

Pair the pool with its prices and the draft’s own parameters (budget, roster size, pick order rules) so the whole competitive foundation lives in one place. (Choosing those numbers is covered in running your first draft league season.)

2. Trades and free agency

Decide whether rosters are frozen after the draft or can change, and if they can, under what constraints. A workable middle ground for a first season: trades allowed until a mid-season deadline, budget totals must stay legal after the swap, and every trade is announced publicly before it takes effect. Free agency, meaning claims on undrafted pieces from the pool, needs a cost (a drop, a fee, a limited number of claims) or your draft’s scarcity quietly stops meaning anything.

Write down the veto policy too, even if the policy is “there is no veto.” Nothing generates more mid-season heat than a lopsided trade, and the heat doubles when nobody knows whether the league can undo it.

3. Deadlines and forfeits

The section your league will actually live or die by. Specify when matches are due, what counts as a good-faith scheduling attempt, and exactly what happens when a match doesn’t get played: who takes the loss, how the score is recorded, and what happens to a coach who forfeits repeatedly. The rule needs to produce a definite result without commissioner judgment. “The coach who responded to scheduling messages wins by forfeit; if neither responded, both take a loss” is mechanical enough to survive contact with real people.

Include a replacement clause while you’re here: if a coach leaves mid-season, does a substitute inherit the roster, or are their remaining matches recorded as forfeits? Deciding this in September is easy; deciding it in November, when the departed coach’s forfeits decide a playoff seed, is not.

4. Tiebreakers

Standings ties are near-certain in a short season, so publish the exact order of resolution: head-to-head record first, then a game-level differential, then whatever final resort your group prefers, as long as it’s deterministic and written down. Two sentences here prevent the ugliest argument a league can have, the one that happens after the games are over, when nothing can be replayed and someone’s playoff spot is on the line.

Keep it short

A ruleset nobody reads protects nobody. One page covers everything above; two at most. Some discipline that helps: write rules, not essays (“trades close at the end of week 4” needs no philosophy section); prefer mechanical rules over judgment calls, because every “commissioner’s discretion” clause is a future accusation of bias; and resist codifying situations that haven’t happened and plausibly won’t. A ruleset that tries to anticipate everything reads like a terms-of-service agreement, and gets read like one.

For everything genuinely unforeseen, one honest catch-all beats ten speculative clauses: “situations not covered here are decided by commissioner ruling, and the ruling becomes a written rule for the rest of the season.”

Enforce it consistently

The first time a rule is tested decides whether you have a ruleset or a suggestion box. If week two’s forfeit deadline slides “just this once,” you’ve amended the rule for everyone, permanently. The next coach to miss a deadline will cite the precedent, and they’ll be right to. The kindest enforcement style is also the most boring: apply the written rule as written, and apply it hardest to yourself. A commissioner who takes their own forfeit loss without argument buys more legitimacy in one week than a season of good rulings.

Consistency is also why mechanical rules matter so much: they let you say “the rules decided, not me.” The less a ruling depends on your judgment, the less it damages your friendships.

Version it

Your season-one ruleset will be wrong somewhere: a price that warped the draft, a trade rule with a loophole, a tiebreaker that never triggered. That’s fine; rulesets are drafts too. The discipline is to change it at season boundaries, not during play, and to keep a short changelog (“Season 2: free-agent claims limited to three per coach; S1’s unlimited claims devalued the draft”). Mid-season, the rules are frozen except for true emergencies, and any emergency change should apply from that point forward, never retroactively.

The changelog does quiet cultural work: it shows the league that rules respond to evidence and argument, not to whoever complained loudest after losing. Coaches who believe that will accept rulings they hate.

Let the software carry the rules

A written rule still depends on a human noticing the violation: a pick over budget, a roster over size, a trade that breaks the cap, a match nobody reported. Policing that arithmetic, more than making rulings, is the enforcement work that actually wears commissioners down. It’s also the part software does better. Fundrafted encodes your league’s parameters (budget, roster size, pick legality, schedule deadlines) so violations surface automatically instead of three weeks later in a heated group-chat audit. The draft room simply won’t accept an illegal pick (see snake drafts, budgets, and pick strategy for why coaches near their budget ceiling test this constantly), and unreported matches stay visibly unreported until someone deals with them. Your one-page document handles the human questions; the machine handles the math.