Skip to main content

Commissioner Guide: How to Handle Mid-Season Emergencies

You’ve written the rules, set up the draft, started the season — and then something unexpected happens. A manager ghosts the league. A scoring error affects a playoff race. A platform has a bug. A rule has a gap when it matters most.

These situations don’t happen every season, but every long-running league eventually faces them. How you respond defines your reputation as a commissioner.

Emergency Quick Reference

Emergency Time window to act First action What NOT to do
Inactive / ghosted manager 72 hours after missed lineup Try all contact channels; set a deadline Remove mid-season without exhausting contact options
Scoring error changes game outcome Wait for 48–72 hour NFL correction window Let platform auto-correct; announce if outcome changes Manually adjust scores before platform correction
Rules gap or ambiguity 24 hours of dispute Read the constitution; make call consistent with existing intent Leave the dispute unresolved for more than a day
Platform outage / waiver bug Immediately Contact platform support with screenshots Make manual roster adjustments without platform confirmation
Commissioner becomes unavailable Before going offline Brief co-commissioner explicitly; notify league Go silent without any league communication

Emergency 1: Inactive or Ghosted Manager

The problem: This damages competitive integrity — every team that plays the inactive manager gets an easy win; every team that doesn’t gets shortchanged.

Response protocol:

  1. Try multiple contact channels — text, email, league chat, direct message. Try all of them. Some managers are dealing with real-life issues and want to return.

  2. Set a 72-hour deadline: “If I don’t hear from you by [date], I’ll look at options for the team.”

  3. If no response:

    • Option A: Set the lineup automatically using highest-projected available players — least invasive, preserves competitive integrity
    • Option B: Find a replacement manager immediately — post to the league’s friend group or the waiting list
    • Option C: If the season is far enough along and no one wants the team, orphan the roster for the remainder of the season — last resort only

  4. Set an offseason policy: an inactive mid-season manager almost never comes back without a conversation first (“If you go inactive mid-season, you’re out unless you give two weeks notice”).

Emergency 2: Scoring Error That Changes Game Outcomes

Response protocol:

  1. Wait for the official NFL correction window. Most platforms auto-update within 48–72 hours of the game.
  2. Check if the platform automatically adjusted the game outcome:
    • If yes: announce it in league chat and explain what happened
    • If no: contact platform support with the stat correction documentation
  3. If the outcome reversal changes playoff seeding or eliminates a team: be transparent and document everything in league chat, then apply the corrected outcome consistently

What NOT to do: Don’t manually adjust scores unless you have incontrovertible evidence and the platform confirms they won’t auto-correct it. Manual adjustments create trust problems and are hard to audit.

Emergency 3: Rules Gap or Ambiguity

Response protocol:

  1. Read the existing constitution carefully. What is the closest applicable rule? What was clearly intended?
  2. Make the call most consistent with existing rules — apply the spirit of the rules even if the specific scenario wasn’t anticipated.
  3. Document the ruling in league chat: the situation, the closest relevant rule, your interpretation, the ruling.
  4. Add the clarification to the constitution immediately — turn a dispute into an improvement.
  5. If the ruling is genuinely 50/50: run a quick manager vote in league chat (poll). Take the majority position and move on.

Emergency 4: Platform Outage or Bug During Waiver Processing

Response protocol:

  1. Contact platform support immediately with the specific error and screenshots/documentation.
  2. Do not make manual roster adjustments until you have a response from support.
  3. Notify affected managers that you’re aware of the issue and investigating.
  4. If platform confirms an error: ask them to correct it directly if possible; if they can’t, implement the corrected result manually and document everything in league chat.
  5. If platform says “no error”: get their explanation in writing. Sometimes managers misremember bid amounts or waiver priority order.

Emergency 5: Unexpected Commissioner Absence

This is the argument for having a co-commissioner. If you have one, hand off explicitly before you go offline — give them a clear scope of what to handle.

If you don’t have a co-commissioner:

  1. Notify the league that you’ll be unavailable and for roughly how long
  2. Ask if a trusted manager can handle time-sensitive decisions (waiver disputes, scoring questions)
  3. When you return, make decisions quickly so the league doesn’t stall

The Commissioner Credibility Principle

In every emergency, the worst thing you can do is be slow and silent. Managers can accept a wrong call that gets corrected. What kills league trust is a commissioner who goes quiet, delays, and lets the situation fester.

The rule: Within 24 hours of any reported emergency, you should have either resolved it or posted an update explaining what you’re investigating and when you expect a resolution.

Speed and transparency matter more than being right on the first try.

For the dispute resolution process, see: Commissioner Guide: How to Handle Disputes and Complaints Fairly. For setting up a co-commissioner to handle emergencies in your absence, see: Commissioner: How to Set Up a Co-Commissioner.