Return2PLAi
6

S · #6 · Cincinnati Bengals · week 5 vs Miami Dolphins · Sun Oct 11 · 1:00 PM ET

Bryan Cook

  • ROLE a starter
  • CLASS 2022 · R2 P62
  • EXP 4 seasons
  • AGE 25-28
  • DEPTH FS1

As of week 5, Bryan Cook was an SAF for CIN, age 27, 4 seasons of experience, drafted in round 2. In 2026 through week 4 he was listed at depth rank 1 on his club's depth chart; he had played 3 games on 78% of snaps. Before 2026 he played 68 games (postseason included) over 4 seasons. His injury history held 10 episodes (ankle 2, arm 2, neck 2), 2 of them reaching OUT, 3 a repeat of an earlier site; the last was a shoulder injury in 2025 week 16.

The full read

In short

How our call moved in week 5

  • our call, P(plays)
  • club report (public)

73% LIKELY → 73% LIKELY

Every call we wrote for him in week 5, earliest first, as written.

In short

Bryan Cook is a starter at free safety for CIN — 100% of the snaps in his best week of 8. He has an ankle injury. His team named him inactive in week 4. In week 5 he did not practise, then practised limited, then practised in full. His team has listed him Questionable. We called him PLAY in week 4 and he did not play.

The reader concurs · grade C

P1 establishes only that Cook missed LAST week's game ("The Bengals were without starting safety Bryan Cook and backup safety Kyle Dugger last week"), which is history for the 11 Oct game, and its framing that "The Bengals defense desperately needs Cook back" cuts toward him playing.

What the read cites

What was reportedSource
1“The Bengals were without starting safety Bryan Cook and backup safety Kyle Dugger last week”source not recorded
2“The Bengals defense desperately needs Cook back.”source not recorded
3“Bryan Cook doesn’t want to hurt the Bengals defense by playing injured”source not recorded
The reader's full reasoning

The rest of the reading

The headline's "doesn’t want to hurt the Bengals defense by playing injured" (P1) is a caution flag, but the passage is truncated and does not say he is doubtful or out for 11 Oct, so it does not contradict the PLAY call. With a Friday full practice on the club's own report and no written statement of doubt for this game, the call stands, though the evidence base is a single aggregating blog post.

11versions in week 5
13average, every player
54most for one player

How the call moved

LIKELY since Sat Oct 10 · 7:01 AM ET · 30 h before kickoff · after the club said it (-5 h). Biggest move: 73% → 91%, Thu Oct 8 · 5:01 PM ET to Fri Oct 9 · 7:01 AM ET, after: practiced more (Did Not Participate In Practice → Limited Participation in Practice).

Our call

Injury report

His team's word: Questionable

This is the TEAM'S OWN ANNOUNCEMENT, not a reading of ours. His team filed him on the injury report and we are restating it so the record is complete. There is nothing early about repeating an announcement — what we say ahead of one is on the week's page. Source: his team's published inactive list, on the day.

Practice in week 5

FriThuWed
FPdated Sun Oct 11LPdated Sun Oct 11DNPdated Sun Oct 11

Shape of the week: improving. Only days the publisher dated are shown; a day we could not date is left out until the nightly sweep stamps it. The shape is a fact, not a forecast.

Head start

  • His club's word
  • Kickoff

The evidence behind his current call

We read the news; nothing was attributed.

Stats, with ranges — dot = his average, bar = his game range

  • Snap share90.3% range 34–100

    wk 1–10 · 8 games

Snaps by week — his larger of the offence and defence share

  1. 100%wk 1
  2. 100%wk 2
  3. 34%wk 3
  4. 97%wk 5
  5. 94%wk 7
  6. 99%wk 8
  7. 98%wk 9
  8. 100%wk 10

Missed while on the injury report

SeasonWeeks on the reportMissed while listed
202621

Only the weeks he was on the injury report with a recorded result — not every game of his career.

Medical history

WhenInjuryWeeks on a reportWorst status
2026 · wk 4ankle2Questionable
2025 · wk 16shoulder1—
2025 · wk 14ankle2—
2025 · wk 4neck1—
2024 · wk 12chest1—
2023 · wk 14ankle1Out
2023 · wk 13arm1—
2023 · wk 7neck1—
2023 · wk 4arm1—
2022 · wk 13wrist1—
2022 · wk 6concussion2Out

Every injury episode on file for him, as the record holds it.

Injury history by season · 11 episodes · 14 weeks on a report · same site more than once: ankle ×3

  • ruled out
  • questionable
  • listed, and played

Each bar is one episode: the week it began and how many weeks he was on a report, coloured by the worst status.

The rest of his team's report in week 5

PlayerPosPracticeWhose wordCallChance he playsBand
Jonathan AllenDTLTDoursPLAY99%EXPECTED
B.J. HillDTDNPoursPLAY94%EXPECTED
Dexter LawrenceDTDNPoursPLAY99%EXPECTED
Dalton RisnerGFULLoursPLAY96%EXPECTED
Kyle DuggerSDNPteam's wordOut
Tee HigginsWRFULLteam's wordQuestionable
Ja'Marr ChaseWRFULLteam's wordQuestionable
Jordan BattleSFULLoursPLAY94%EXPECTED
Swayze BozemanLBFULLteam's wordQuestionable
Barrett CarterLBFULLoursPLAY94%EXPECTED
Colbie YoungWRLTDteam's wordQuestionable

The model reads the room: who else is out shifts what his own designation is worth.

The evidence behind his earlier calls

The evidence behind the call made Thu Oct 8 · 7:01 AM ET

We have not read the news for this player this week.

The evidence behind the call made Thu Oct 8 · 12:01 PM ET

We have not read the news for this player this week.

The evidence behind the call made Thu Oct 8 · 5:01 PM ET

We have not read the news for this player this week.

The evidence behind the call made Fri Oct 9 · 7:01 AM ET

We have not read the news for this player this week.

The evidence behind the call made Fri Oct 9 · 12:01 PM ET

We have not read the news for this player this week.

The evidence behind the call made Fri Oct 9 · 5:01 PM ET

We have not read the news for this player this week.

The evidence behind the call made Sat Oct 10 · 7:01 AM ET

We have not read the news for this player this week.

The evidence behind the call made Sat Oct 10 · 12:01 PM ET

We have not read the news for this player this week.

The evidence behind the call made Sat Oct 10 · 5:01 PM ET

We read the news; nothing was attributed.

The evidence behind the call made Sun Oct 11 · 7:01 AM ET

We read the news; nothing was attributed.

The evidence behind the call made Sun Oct 11 · 11:41 AM ET

We read the news; nothing was attributed.

The evidence behind the call made Sun Oct 11 · 12:01 PM ET

We read the news; nothing was attributed.

The evidence behind the call made Sun Oct 11 · 12:01 PM ET

We read the news; nothing was attributed.

Role

Call history

The data behind this page — the timeline in words, every call and week on record, about him, and what this page does not show

Profile — as of week 5

RoleSAF1 · 78% snaps
Season2026 · 3 games through wk 4
Career4 seasons · 68 games before 2026
Injuries10 episodes · last: shoulder, 2025 wk 16
Bioage 27 · 4 seasons' experience · drafted round 2

Where the profile comes from

Built from: honors.db; nflverse injuries_2026.csv; medical.db; nflverse players.csv; profile.db; nflverse roster_2026.csv; nflverse roster_weekly_2026.csv; nflverse snap_counts_2026.csv; nflverse stats_player_week_2026.csv. Every number in it is one those sources hold.

nflverse injuries_2026.csv

About him

About himAs the record holds it
His rolea starter at free safety — 100% of the snaps in his best week of 8
Listed on the depth chartfirst at free safety
Snaps played90% a week on average over 8 weeks, 100% at his highest
Build6 ft 1 in · 210 lb
CollegeCincinnati; Howard
Drafted2022, round 2 pick 62, by KC
Age25-28 at the season's start
Experience4 seasons

When this call was made, and when the world knew

  1. Team reportHis team listed him Questionable.
  2. PublicHis team's word was public as soon as it was filed.
  3. KickoffKickoff.

How our call moved, earliest first

WhenLeadCallChance he playsBandOn what
Thu Oct 8 · 7:01 AM ET78 hPLAY73%LIKELYbefore his team said anything
Thu Oct 8 · 12:01 PM ET73 hPLAY73%LIKELYbefore his team said anything
Thu Oct 8 · 5:01 PM ET68 hPLAY73%LIKELYbefore his team said anything
Fri Oct 9 · 7:01 AM ET54 hPLAY91%EXPECTEDbefore his team said anything
Fri Oct 9 · 12:01 PM ET49 hPLAY91%EXPECTEDbefore his team said anything
Fri Oct 9 · 5:01 PM ET44 hPLAY91%EXPECTEDbefore his team said anything
Sat Oct 10 · 7:01 AM ET30 hPLAY73%LIKELYafter his team's announcement
Sat Oct 10 · 12:01 PM ET25 hPLAY73%LIKELYafter his team's announcement
Sat Oct 10 · 5:01 PM ET20 hPLAY73%LIKELYafter his team's announcement
Sun Oct 11 · 7:01 AM ET6 hPLAY73%LIKELYafter his team's announcement
Sun Oct 11 · 11:41 AM ET1 hhis team's word——his team's published inactive list, on the day
Sun Oct 11 · 12:01 PM ET1 hPLAY73%LIKELYafter his team's announcement
Sun Oct 11 · 12:01 PM ET1 hhis team's word——his team's published inactive list, on the day

11 calls in week 5, and the call never flipped between PLAY and SIT. Each lead time is the one that call actually had when it was written — never recounted from now. A call that changes is the record working: new evidence arrived and we said so, in public, before the game.

What would change this read

What would change this read
Official Sunday 11 Oct inactive list or final game status for Cook (Questionable -> Active/Out)
Zac Taylor's Friday 09 Oct or Saturday 10 Oct press conference remarks naming Cook's ankle and Sunday availability
Full text of the 09 Oct Cincy Jungle piece: is the 'doesn't want to hurt the defense by playing injured' framing about last week's absence or about doubt for 11 Oct?
Whether backup safety Kyle Dugger has returned, which would reduce pressure on Cook to play through the ankle
Beat-reporter confirmation of the Friday full practice and whether Cook was listed as limited in any capacity on Sat 10 Oct

We went and found out more

Rank 1 (listed first on his depth chart), 12 documents deep, because: llm_unsure. Fetched 12 of 12.

Named inactive in week 4

The team's own list. We held it after kickoff, so it could NOT have informed a call. Matched to him by his player id.