Analysis
DFS research and lineup-construction notes from the team building GameScript: game environment, correlation, ownership, and what the numbers do and do not support.
-
McCaffrey's IR story was real — in September 2024: three weeks of catching contaminated DFS research
A daily research scan spent three weeks doing what any DFS player does before a slate — searching for injury and depth-chart news — and kept finding real articles about the wrong year, the wrong opponent, or the wrong team. Cross-referencing every player-team claim against the actual slate pool caught most of it, produced one false alarm of its own, and still missed things a human reading quickly would miss too. The failure modes, the catches, the one retraction, and the checklist that's left.
-
-3.5 to -10: the Week 2 spread that got less settled the more sources checked it
Seattle at Arizona has carried a real spread disagreement for four straight days — and the newest number, GameScript's own house line, is now the outlier on the opposite end from DraftKings. What the gap means for reading this specific game, and why a total agrees across sources when a spread doesn't.
-
OUT Friday, unpriced Sunday: the DFS ownership lag, measured in hours
A daily research scan tracked the same DFS ownership pages, from the same publishers, every day for two weeks before Week 1 2026 locked. The gap between an injury becoming official and that injury reaching a published ownership number wasn't occasional — it was structural, and in one case it never closed before kickoff. What the lag actually looked like, and how to read a projection page's byline instead of trusting its number.
-
50%, 50%, 29%, 58%: four days inside a forecast that never settled
One Week 1 game's second-half storm chance was checked daily for four days and never stabilized — it dropped, then jumped past its own starting point, with no event explaining either move. What that means for how long a weather-driven read is actually good for.
-
Showdown captain leverage: five slots are forced, one is a decision
A Showdown entry spends 600% of ownership across six slots — 500% on five flex spots the field fills the same way, and 100% on the captain. Here is the conserved-quantity arithmetic, the proof that points-per-dollar is mathematically useless in the captain slot, what GameScript's model actually assumes about captains, and why nobody here can tell you what real captain ownership looks like.
-
Six days out, the board settles — except for one number that won't move
Atlanta named its Week 1 starter and six outdoor stadiums got their first real forecasts on the same day. What that resolves, what still doesn't, and the one line dispute that has now outlasted everything else on the board.
-
Ten days out, four Week 1 numbers still don't agree with themselves
A full environment ranking for the Week 1 2026 Sunday main slate, plus an honest account of which totals are settled, which are genuinely still in dispute, and what two teams' offensive-line and quarterback situations mean for reading them.
-
Stacking is a variance decision, not a points decision
A QB-WR stack does not raise your expected score by a single point. It widens the distribution around the same mean, which is the entire reason to do it in a tournament and the entire reason not to in cash. With the arithmetic, what a bring-back really buys, and when a naked running back is fine.
-
The Week 1 line freeze: why a total from May isn't a total from September
A Week 1 number looks exactly like a Week 8 number, but it hasn't been priced the same way. It opens at schedule release, sits largely frozen for months, and moves only at a handful of calendar events. Here's how to tell a real move from three books mirroring the same stale line.
-
Game environment first: how implied totals should shape a DFS lineup
Implied team totals tell you which games are worth playing before you argue about which players are worth rostering. Here is how to read them, where they mislead, and how to turn one into a lineup rule.
-
Cash and GPP are different constraint problems, not different moods
The same player pool and the same projections produce two different rosters because the objective function and the feasible set are different. Here is what each optimizer knob actually changes, with the arithmetic, and why one lineup cannot serve both contests.
-
Leverage is a difference, not a low number
Low ownership and leverage are not synonyms, and the industry's usual leverage ratio ranks the wrong players first. Here is the arithmetic of a field-relative edge, why a good leverage measure has to be bounded, and when the chalk is simply correct.