← All Posts

September Is a Liar: Surviving the Early-Season Overreaction Window

JVBy Jordan VossMay 12, 2026Strategy6 min read
Person holding a red and white megaphone in their lap
Photo by Gianmarco Avigni on Unsplash

The Most Dangerous Weeks on the Calendar

No stretch of the fantasy season generates more bad decisions than the first three weeks. Managers wait eight months for real football, and when it arrives they treat every box score as revealed truth: the slow-starting first-rounder is "done," the waiver-wire hero with two touchdowns is "a league winner," and rosters get torn up accordingly. Fantasy Life's guide to avoiding Week 1 overreactions states the obvious that's so hard to live: one week is one data point, and neither spectacular nor disastrous performances deserve much weight. The whole panic-or-patience genre — QB List runs a weekly column on exactly this — exists because the pull is that strong. The skill isn't suppressing all reaction; it's knowing which numbers stabilize in three weeks and which take three months.

What Stabilizes Fast — and What Never Does

The clean rule: usage is signal, scoring is noise. Snap share, route participation, target share, and red-zone role are *decisions coaches make*, and they're remarkably stable once made — three weeks of them tells you what a player's role actually is. Points are what happens when that role collides with variance: touchdowns bounce, and they regress hard, long plays cluster randomly, and three-game point totals routinely lie in both directions. A receiver running 90% of routes with a 24% target share and one touchdown is a buy, full stop; a receiver with three touchdowns on a 55% route share is a mirage wearing a good box score. The same lens governs panic: a first-rounder scoring poorly *on unchanged elite usage* is fine — the points are coming. A first-rounder whose snaps are shrinking is the real alarm, whatever last week's score said.

Weeks 1–3: what to react to, what to fade

Signal (coach-controlled usage)Noise (scoring variance)
Snap share and route participation
Weekly point totals
Target share and red-zone role
Touchdown count (bounces, then regresses)
A role that grew or shrank week over week
One monster game or one dud
Usage that contradicts the depth chart you drafted
Positional rank after two weeks
The early-season sorting test: coach-controlled usage stabilizes within weeks and predicts what's coming; scoring outcomes bounce for months. React to the left column, fade the right.

The Overreaction Window Is a Market

Here's the productive reframe: every overreaction in your league is a mispriced asset, and weeks 1–3 produce more of them than the rest of the season combined. The manager benching — or shopping — a slow-starting star is offering the classic buy-low; the one who just watched their bench player score twice is briefly holding a sell-high they think is a cornerstone. Trading into the panic and out of the euphoria is the highest-leverage move September offers, and it requires exactly one discipline: pricing players on their usage, not their last box score, while your trade partner does the opposite. The same market logic runs the waiver wire — FAAB bids in September chase last week's touchdowns, which means the usage-based claims (the quiet 8-target game, the snap-share climber) consistently go underpriced.

Not All Evidence Ripens at the Same Rate

The usage-versus-scoring split is the right first cut, but inside "usage" there is an ordering too, and knowing it tells you how much weight a given number deserves in Week 2. Roughly from fastest to slowest: whether a player is on the field at all, then how often he runs a route when his team drops back, then his share of the targets, then what he does with those targets, and last of all how often he reaches the end zone. The first item is close to a fact after one game. The last is barely meaningful after ten.

That ordering is not arbitrary — it tracks how much of each number is a coaching decision versus an outcome. Snap counts are pure decision, so they mean something immediately. Touchdown rate is almost entirely outcome, decided by field position and goal-line luck as much as by the player, so it needs a season to say anything. Anything in between is a blend, and the further right you go, the more games you should demand before you let it change a draft-day conviction.

The practical version: if the thing that changed is on the left of that list, act now, because it will still be true in Week 6. If it is on the right, wait, because it probably will not be.

Week 1 Is Its Own Category

Even inside the overreaction window, the opening week deserves its own discount. Teams have installed new schemes that nobody has seen against live competition, coaches are still finding out what their personnel groupings actually do, and a game that gets out of hand early produces a snap distribution that reflects the scoreboard rather than the plan. A rotation that looks alarming in Week 1 is frequently just a coaching staff hedging in the first real game of the year.

Which is why the honest read on a single Sunday in September is usually "I do not know yet". That is an unsatisfying thing to say when everyone in your league chat is certain, and it is correct far more often than the certainty is.

What Actually Should Change Your Mind

None of this argues for doing nothing. There are early-season developments that genuinely settle the question, and they share a feature: somebody made a decision that is hard to reverse. A starter who is publicly benched rather than rotated. A backfield where the passing-down back stops getting passing downs. A committee that resolves because the other half of it got hurt. An offense that changes play-caller. Those are structural, and waiting three weeks to act on them just means paying the waiver price after everyone else.

The test is whether you can name the decision. If you can point at a choice a coaching staff made, you are looking at a role change and you should move. If the only thing you can point at is a number that went up or down, you are looking at results, and September results are the least reliable data the season produces.

A Three-Week Operating Manual

Practically: hold your draft convictions for three weeks unless *usage* contradicts them — you spent all summer forming those opinions on more data than two games provide. Check snaps and routes before every reaction; two minutes of usage data prevents most September mistakes. Keep FAAB powder dry early — the September wire rewards patience, and the bid discipline that feels too slow in Week 2 looks brilliant by Week 6. And write down, before Week 1, the three beliefs you'd bet your season on. When September's chaos tempts you to abandon one, the note forces the question that kills most overreactions: what do I actually know now that I didn't know then? If the honest answer is "two box scores," the conviction stands — and you've just avoided joining the market you were planning to profit from.

  • Three-week rule: no dropping or panic-trading draft-capital players unless usage — not scoring — collapses
  • Check snap share, routes, and target share before reacting to any box score
  • Buy the slow-starting star from the panicking manager; sell the touchdown-fueled mirage
  • Bid on usage spikes, not scoring spikes — the market overprices touchdowns every September
  • Write your convictions down pre-season; make September argue against the document
💡 Tip:The September question that saves seasons: "Is his role different, or just his results?" Different role — act on it. Different results on the same role — the market is wrong, and being right a week or two before everyone else is the entire early-season edge.

Get waiver wire alerts built around your actual league

Connect your ESPN or Sleeper league in under a minute. Free to start.

Start for Free