OUT Friday, unpriced Sunday: the DFS ownership lag, measured in hours

A published ownership percentage looks like a live fact. It has a decimal point, it sits next to a salary, and nothing about its formatting tells you when it was actually computed. For two weeks before the Week 1 2026 main slate locked, this repository ran a daily scan against the same handful of DFS content pages — the ones a lot of players actually build from — and logged, every day, whether that day's real news had reached them yet. The slate has since played. Here is what the lag actually looked like, in hours, across four separate players.

The clean case: an OUT designation three pages didn't have at kickoff

Tua Tagovailoa suffered an oblique injury at Thursday practice. Atlanta's own Friday injury report made it official: Tagovailoa OUT, Cooper Rush the Week 1 starter, backup Michael Penix Jr. also OUT — the cleanest, most final kind of injury news a slate can produce, and it landed with a full two days before kickoff. DraftKings' own board and the consensus spread (which moved 2.5 points on the news) both reflected it almost immediately.

Three separate Stokastic properties didn't. Its flagship "NFL Week 1 DFS Picks" piece, its "First Look" show-notes page, and its DraftKings cheat sheet — the last of which was edited the same afternoon the OUT designation posted, with fresh ownership numbers for several unrelated players — all carried zero mention of Tagovailoa, Rush, Penix, or Atlanta's quarterback situation at all, checked directly and repeatedly. The last pre-lock check this file ran was Sunday morning, roughly six hours before early kickoff. All three pages were still silent. That's not a same-day miss — it's a gap that opened Friday afternoon and, as far as this scan could tell, never closed before the slate started. One outlet did catch up: DK Network's own picks piece, published Saturday, covered Rush directly and called for fading the expected Falcons chalk — a full day ahead of Stokastic, and still not fast.

GameScript's own house model, for comparison, had Rush priced correctly by Friday. That's not a claim that the house model is generally faster — see below — only that on this specific player, on this specific day, it was.

Three more cases, same shape

• Brock Bowers' meniscus trim. Ian Rapoport and Adam Schefter reported the surgery — "expected to miss a game or two" — at 7:57pm ET on a Tuesday, and fantasy media reacted within about two hours; DFS-Twitter was already naming Michael Mayer as the beneficiary that same night. The ownership tools took much longer: this scan found Bowers still listed at his pre-injury salary and ownership figure on Wednesday, Friday, and again Saturday — a fourth straight stale check — and Mayer didn't get his first exact published ownership number (29.0%, from a Stokastic cheat sheet) until the Sunday kickoff-morning check. Call it four days from surgery to a hard number for the player who actually benefited from it.
• Zay Flowers, a gap that never closed at all. GameScript's own house model held Flowers at 65% projected ownership — tied for the single highest figure on the slate — for more than eleven straight days, while Stokastic's own pages sat at 14–15% the entire time: a 4–4.5x disagreement between one site and one model, not a timing gap between two views of the same number. It narrowed to roughly 2x only two days before kickoff, and only because the house figure dropped to 30.2%. Stokastic's own number never moved. The two sides never converged.
• Alvin Kamara, where the house model was the slow one. This is the honest, less flattering data point: GameScript's own house model held Kamara flat at roughly 4.7 projected points and 0.17% ownership for more than two weeks, while the real situation cycled through three distinct states — "out at least a month" (late August), "a full-participation Friday practice and a Sunday game-time call" (per Saints beat reporter Nick Underhill), and finally "not expected to play at all," reported by Ian Rapoport and Underhill on the morning of kickoff. The house model never reacted to any of it. The lag isn't something that only happens to competitors' content.

Why this happens

None of this is a competence problem, and it isn't unique to one publisher. A DFS ownership page is built on a pipeline — projections, a simulation pass, an editorial write-up — and every stage of that pipeline runs on its own cadence, not on the news cycle. A page's byline ("Updated September 7") is telling you the truth about when the numbers underneath it were last computed; the mistake is reading the page on Sunday and unconsciously trusting Sunday's freshness for a number stamped six days earlier. The same structural gap explains why two pages from the same publisher can disagree with each other — Stokastic's own "First Look" and "Picks" pages carried different total and ownership numbers for the same game on the same day more than once this cycle — because a rewrite of one page doesn't trigger a rewrite of the other.

What to actually do with this

This isn't an argument that published ownership content is worthless; it's the best low-cost signal most players have. It's an argument for reading the byline before the number, specifically in the 48 hours before lock, which is exactly when this scan found the gaps widest:

1. Check the "updated" date before you check the percentage. A number stamped before a Friday injury report is not wrong, it's incomplete — it answers a question the news has since changed.
2. For a confirmed OUT, cross-check the primary sources directly, not a projection page. The injury report and DraftKings' own player-status field update faster than any ownership tool this scan tracked, in every case measured here.
3. A book's line move is a faster proxy than a projection page's byline. The spread moved on Tagovailoa's injury before any tracked ownership content did; a same-day line move is real-time information a weekly-cadence page structurally can't be.
4. Don't assume your own tools are exempt. The Kamara case is the reminder: an automated model is still a pipeline with a cadence, and "the number hasn't changed" is not the same claim as "the situation hasn't changed."

The field's ownership numbers are a snapshot, not a stream. Knowing when the snapshot was taken is worth more than arguing about the number in it.