Current methodology · SR-2026.4

ScoutRank Methodology

Millions of fantasy football recommendations are made every season. Very few are ever measured.

ScoutRank exists to measure what actually happened.

We don't predict football. We measure credibility.

Every rating is built from verified calls and real outcomes — not reputation, not follower count, not opinion. Every rating can be independently verified by reviewing the underlying receipts.

Fantasy ratings and betting records are separate systems, graded by separate rules. The fantasy score is never reused as a betting rating.

On this page
01 / Fantasy

Fantasy start/sit ratings

  1. 1.1

    What we score

    A scoreable start/sit call requires (1) a specific player, (2) a specific week, and (3) a lineup-actionable stance — a statement a listener could set their lineup on.

    Analysts rarely say the literal words "start him." They say "I like him this week," "he's the play," "I'd go with him." Those are calls, and we score them.

    We capture (not yet scored):

    • Rankings without a decision ("he's my RB12")
    • DFS pricing and salary talk
    • Betting props
    • Season-long or timeless praise with no week attached
    • Observations that recommend nothing (schedule notes, injury news, teammate commentary)

    A call enters the scored record only when it clearly resolves to a start-or-sit stance for a specific week. A credibility rating is only as trustworthy as the calls underneath it — so we keep the scored scope narrow on purpose, and show everything else honestly as captured-but-unscored rather than counting calls a publisher didn't clearly make.

  2. 1.2

    Receipts

    Every rating is backed by receipts: the individual calls that produced it, each showing the player, the week, the recommendation, the actual points, and the result — and the source: the exact words as spoken, the show, the air date, and a link to the episode audio.

    Nothing is hidden behind the score. If you want to know why a publisher is rated the way they are, the calls are right there to check — down to the tape. This is the whole point: a rating you can audit, call by call, quote by quote.

  3. 1.3

    How a rating is built

    Each rating follows the same chain, from what was said to the number:

    Episode → Start/sit call → Player outcome → Verified receipt → Publisher accuracy → ScoutRank
  4. 1.4

    How a call is scored

    Every scored call is checked against the player's actual half-PPR fantasy points for that week, against a bar set for his position — and that bar is recomputed fresh every week from that week's real results, not a fixed number that stays still all season:

    • A start call is a hit if the player finished among the top-N startable players at his position that week — the same cutoff a standard 12-team league uses to fill its starting lineups: top-12 for QB and TE, top-24 for RB and WR.
    • A sit call is a hit if he finished outside that group.
    • Otherwise, it's a miss.

    Concretely: the bar for each position, each week, is the half-PPR score of the Nth-ranked player at that position across the full NFL player population that week (not just the players podcasts happen to discuss) — the 12th-best QB or TE, the 24th-best RB or WR. Whoever cleared that line that week was startable; whoever didn't, wasn't. A representative sample:

    WeekQB lineRB lineWR lineTE line
    122.610.710.59.4
    922.29.012.110.0
    1817.38.38.58.8

    The line moves — week 1's QB bar (22.6) is meaningfully higher than week 18's (17.3), because scoring environments shift over a season. A flat, fixed number can't track that; a bar recomputed from that week's actual results does. Every claim's receipt shows the exact line that applied to it, not a season-average approximation.

    The check that keeps it honest: under these per-week lines, a skill-less caller — one making random start/sit calls on real players in real weeks — scores almost exactly 50%. We simulate this directly: 200 trials, mean 49.63%, tightly banded around the coin-flip line. That's what makes "50 = coin flip" a validated claim rather than an assumption: the only way to score above 50 is to beat random, against the same bar a real fantasy manager is judged by.

    Voids. Some calls can't be scored — the player didn't play, there's no game data, the position isn't covered by a startable-lineup slot (e.g. kicker), or the recommendation wasn't a clean start/sit. These are marked void and excluded from accuracy. A void isn't a hit or a miss; it's a call that couldn't be verified, and it never counts for or against a publisher.

    “Verified call” — the definition. Every count on this site labeled a “verified call” (the site-wide total, each publisher's record, every article) means the same thing: a claim with a hit or miss outcome. Voided claims are excluded from that count entirely — not scored as a loss, not scored at all. This is the same figure the leaderboard's own “verified calls” total is built from, so the number you see on the board and the number cited in any ScoutRank analysis will always match.

  5. 1.5

    How ScoutRank is calculated

    ScoutRank combines three things:

    • Verified Accuracy — how often were they right?
    • Evidence — how many verified predictions support that accuracy?
    • Confidence — how stable is the rating?

    Why not just use raw accuracy?

    Because accuracy alone is misleading on small samples. Consider two publishers:

    PublisherRecordRaw Accuracy
    Publisher A18 of 2475%
    Publisher B321 of 50064%

    Raw accuracy says Publisher A is better. ScoutRank says Publisher B — because 24 predictions don't prove as much as 500. A great record on a handful of calls hasn't yet earned the same trust as a strong record across hundreds.

  6. 1.6

    Evidence adjustment

    This is the correction that makes that possible. ScoutRank pulls small-sample ratings toward the middle until enough evidence accumulates. A high accuracy on a few calls produces a strong raw number but a more cautious rating — because the rating reflects what's been proven, not just what's been observed. (Statistically, it's a shrinkage adjustment; in plain terms, it's evidence.)

  7. 1.7

    The scale

    ScoutRank is normalized to 0–100, where 50 is a coin flip — the line between better and worse than chance. Higher is better. Because real start/sit accuracy clusters in a relatively narrow band, the ratings are intentionally compressed: the differences between publishers are real, but not dramatic, and we don't inflate the spread to make them look bigger than they are.

  8. 1.8

    Confidence

    Every rating shows a confidence level alongside it — Provisional, Low, Moderate, High, or Very High — reflecting how much verified evidence stands behind it. A high ScoutRank with low confidence means "promising, but not yet proven." Confidence never changes the rating itself; it tells you how much to trust its stability.

  9. 1.9

    Position coverage

    A full rating requires a full record. Publishers whose scored calls are concentrated in a single position carry a limited position coverage note and are listed with the developing publishers rather than the main board — excellence at one position is real, but it isn't yet a complete credibility record. This is a statement about evidence breadth, not quality.

  10. 1.10

    Start accuracy vs. sit accuracy

    Each publisher's record is also shown split by direction — accuracy on start calls and on sit calls separately. The two are genuinely different skills, and across the whole corpus, publishers are markedly better at start calls than sit calls. The split is shown so you can see which half of a record does the work.

  11. 1.11

    What ScoutRank doesn't measure (yet)

    A credibility rating should be transparent about its own limits.

    • Start/sit only. Today's rating reflects start/sit accuracy and nothing else. A publisher who excels at rankings or trades but makes few start/sit calls is rated only on the calls we score.
    • Shows are rated as a whole. Many publishers are multi-host shows. When different hosts disagree on the same player in the same week, the show didn't take a single position — so we don't score that call rather than count both sides of a disagreement.
    • Player matching. We resolve spoken player names to real players using a maintained matching layer. It's accurate but not perfect; when a name can't be confidently matched, the call is set aside rather than guessed.
    • It's a measurement, not a verdict on the people. ScoutRank measures the accuracy of public start/sit calls. It isn't a judgment of a publisher's overall expertise, entertainment value, or worth — only of how their tracked start/sit predictions held up against outcomes.
  12. 1.12

    Promotional opt-out

    Listing is not optional — public predictions get public review, and no publisher can be removed from the record. Publishers may opt out of promotional use: on request, we won't feature their show in our marketing, social posts, or highlighted content. Their scores, receipts, and profile remain public and identical to every other publisher's.

  13. 1.13

    Publisher Identity Policy (Beta Phase)

    Publishers may elect anonymized display on ScoutRank. On request, the publisher's name, logo, and outbound links are replaced with a stable anonymous label on all public-facing display.

    Electing anonymized display changes nothing about the research record. All underlying claim data, timestamps, direction labels, and resolved outcomes remain permanently in the corpus and in all aggregate analyses. No claims are removed, voided, or altered. The publisher's accuracy and ranking are still computed from the same data under the same methodology.

    This policy is in beta. The standard display — real name, full profile, public receipts — remains the default. Display-layer anonymization standardizes with SR-2027 before the next season begins.

  14. 1.14

    How the methodology evolves

    ScoutRank evolves through versioned methodology updates. The current version is SR-2026.4.

    When we improve it, we publish a new version and document what changed. We don't silently rewrite past ratings — every recomputation is logged, and prior versions remain auditable.

    The scoring bar is frozen for the 2026 season — corrections to data will continue; the bar itself will not change again until season's end.

    2025 season backfill in progress — publisher scores update as full-season coverage completes per show.

    A defect in the 2026 season start date used for week boundaries put the Week 1/Week 2 cutoff in the middle of the real Week 1 window, mistagging some late-week claims as Week 2. Corrected 2026-09-17: 378 claims across ten publishers were re-tagged to Week 1 and re-graded under the exact same rules as every other claim (166 hit, 187 miss, 22 void; 3 defense claims remain held under the existing defense-scoring gate). Publishers with heavier late-week volume — including The Fantasy Footballers and The Ringer Fantasy Football Show, who previously showed no Week 1 record at all — now have real Week 1 data.

    An earlier defect let some Week 1 2026 claims get resolved before that week's scoring thresholds existed, incorrectly marking them void instead of leaving them pending. 194 such claims across nine publishers were re-resolved on 2026-09-16 under the exact same rules as every other claim (114 hit, 80 miss) — the ordering defect itself was fixed so it can't recur. Net effect on the board was modest: the most-affected publisher's accuracy moved from 58.8% to 59.2%, with the rest small-sample additions.

    An earlier version of the Late-Round Fantasy Football audit page stated that graded claims came only from mainline start/sit episodes. A follow-up audit found sleeper-format episodes account for a majority of this publisher's graded starts, graded under the same rules applied to every show. The audit page was corrected with a permanent notice; the scan was fixed.

    A content source meant to stay excluded from extraction briefly entered the pipeline due to a code gap. We caught it, quarantined the affected claims immediately, verified them for genre accuracy (100% genuine start/sit fantasy football content, no cross-sport bleed) and for duplication against the publisher's existing record (no meaningful overlap found), then reinstated and scored them normally. FantasyPros' rank moved from 9 to 10 as a result — more verified data, not a ratings adjustment. That source remains excluded from future extraction.

    Four publishers' records were split across duplicate identities on the leaderboard — the duplicates weren't hidden, they showed under the same name at real ranks (one at rank 2). Merged 2026-07-28: episodes double-counted under both ids were resolved (the older extraction voided, not deleted — its permalink still resolves honestly), the rest reassigned to the real identity, and the duplicate rows removed. Two of the four publishers' combined scores came out worse than their duplicate-alone scores had shown — the merge is honest, not a ratings boost.

    Added a promotional opt-out policy — publishers may request exclusion from Scout's marketing, social posts, and highlighted content while remaining fully listed with public scores, receipts, and profile. Applied to one publisher on request.

    Routine claim-validity audit of a newly ingested publisher; 10 claims voided for scope/genre misclassification (season-long, retrospective, or availability takes misread as weekly start/sit stances), 1 corrected for a week-assignment error. Full methodology unchanged.

    SR-2026.2 → SR-2026.3 — Corpus Integrity Release. Before the 2026 season, we audited our entire corpus — every claim, every quote, every verdict — against the source recordings. We found and fixed four defects: duplicate ingestion, mislabeled claim types, and attribution errors. Every affected claim was voided or corrected — voids never count for or against a publisher. Net effect: rankings essentially unchanged. The #1 publisher didn't move, no publisher moved more than a few positions, and most accuracy figures ticked slightly up, because what we removed was noise, not signal. The verified-call total decreased from 2,610 to 2,404 — the corpus got smaller and truer. We also added two publishers with full 2025 records: The Audible (Footballguys) and the Fantasy Life Show. Every quote on ScoutRank is now verified word-for-word against the source recording before publication.

    SR-2026.1 → SR-2026.2. The original methodology used a single flat 10-point bar for every position. Community review after launch identified what our own audit confirmed: the flat bar was position-biased — near-automatic for quarterback starts, structurally harsh on tight ends — which meant ratings partly reflected position mix rather than skill. SR-2026.2 replaced it with position-calibrated median thresholds, validated by naive-caller simulation, and added the position-coverage rule and the start/sit split. Some ratings changed materially under the correction, including findings we had featured prominently. We published the changes ourselves, in full. That is what the versioning is for.

  15. 1.15

    Open methodology questions (SR-2027)

    Some questions are still open. We have not decided them yet. Any change we make here will apply to every show at once. It will happen after a season ends, not in the middle of one. We will never rewrite past results.

    Should speculative segments be scored in a separate tier? Some shows run segments built around long-shot picks: sleepers, deep stashes, low-confidence dart throws. Today we score these the same way we score every other start/sit call. Whether they belong in a separate tier is an open question. If we make this change, it applies to every show on the site, not one. It takes effect after a season ends, and it does not touch calls already scored.

    How do we decide what a call means? Analysts rarely say the literal words "start him" or "sit him." We read the analyst's stated stance in context: what they actually said about a specific player for a specific week. Every graded claim links to the source audio, so you can hear the exact words and judge whether we read the stance correctly.

Interactive example

One receipt, end to end

Step 1 · The call

A publisher makes a specific start/sit recommendation

On their Week — (—) episode, The Fantasy Footballers explicitly recommended starting —. The recommendation is captured verbatim and timestamped before kickoff.

The Fantasy Footballers · Week — · —
—
—
awaiting game…
1 of 5
02 / Betting

Betting records

ScoutRank does not recommend bets. The fantasy score is never reused as a betting rating.

We grade the picks betting shows make on air. Every graded pick is checked against the market line when the episode posted and against Pinnacle's last price before kickoff. These rules say which line, which book and which timestamp.

The rulebook

  1. 2.1

    A pick is gradeable when it names a side and a market, is the speaker's own call, and is a play or best bet for an event that has not started. Strength comes from what is said, never from the segment: a stated top tier ("five-star", "level five", "my one best bet") is a best bet; "I'm on", "give me", "play" are plays. For live shows, call_ts is the hour's scheduled start plus the transcript offset plus break time, the latest the pick could have been said. (Oct 22, 2026.)

  2. 2.2

    The reference line is the market consensus at the snapshot nearest before call_ts, because that is the number a listener could get. The line the host stated appears on every receipt as the host's claim, with the gap between stated and available shown. (Changed Oct 16, 2026 from stated-line-first after the first 64 graded picks showed 17 of 50 stated lines better than the market.)

  3. 2.3

    The closing line is the last Pinnacle price before start, de-vigged; if Pinnacle is missing, the consensus close, flagged.

  4. 2.4

    CLV depends on the market. Moneylines: de-vigged closing probability of the pick times its entry decimal odds, minus 1 (SharpAPI's formula). Spreads and totals: headline CLV in points, signed by the selection so that positive always means the pick beat the market (spreads: selected team's handicap at call minus at close; Over: close minus call; Under: call minus close), plus a beat-the-close flag; price CLV is a secondary column, because at -110 both ways it measures only the vig.

  5. 2.5

    Reports of past bets ("I had it at -2.5 Tuesday") are not new calls. Conditional calls ("if it gets to 7") grade only if the condition occurred before start.

  6. 2.6

    One pick per host per event per market; a later reversal supersedes. In multi-sport segments, a bare city or a nickname shared across sports (Giants, Cardinals, Jets, Panthers, Hawks) is held unless the segment is sport-tagged.

  7. 2.7

    Pushes are pushes; units won at the stated or default odds.

  8. 2.8

    Rated status needs n ≥ 100 graded picks; below that, counts only, no rank, no percentage.

  9. 2.9

    Receipts link to the episode and the transcript span; no hosted audio. The quote on a receipt is always the transcript's own words. Extraction accepts a model quote that differs only in case, punctuation, a team-name prefix, number words or a transcription word split (flagged quote_normalized); reordered or joined sentences are rejected. (Oct 22, 2026.)

  10. 2.10

    Shows cannot pay to be graded, removed, or featured.

Changelog

Changes from Oct 16 to Oct 22, 2026, as recorded at the time.

  • Oct 22, 2026 · Rule 1
    call_ts for live shows. VSiN Follow the Money posts each broadcast hour as "Hour N", about 45 of its 60 minutes with breaks cut. call_ts is the hour's scheduled start (4pm ET plus N-1 hours) plus the transcript offset plus the cut break time: the late end of the window in which the pick was said, and never after the episode posted. A later call time can only make the market at call harder to beat, so the approximation never flatters a host. This settles the open question above.
  • Oct 22, 2026 · Rule 1
    show notes vs audio. Eval row 6 (Chad, Week 6) was built from the show notes as "Packers PK". On air he says "I'm going to take the Packers on the money line for my level one." The notes were wrong; the row is now a moneyline. Show notes can disagree with what was said, and the eval set follows the audio.
  • Oct 16, 2026 · Rule 2
    Rule 2: reference line changed from the stated line to the market consensus at call. Why: on the 64 graded picks, 20 stated lines were better than any line a listener could get when the episode posted (2 were worse), 17 of them in the Confidence Cup, which appears to post its own lines. Measured from the stated line, those numbers counted as beating the close even when the market never offered them; it doubled the headline (+0.34 vs +0.17 mean points, 31 vs 23 picks beating the close). The spec's own answer to the bettor objection is that we grade the moment a listener could act; the reference line now says the same. The stated line stays on every receipt as the host's claim, with the `stated_vs_available` delta. Grading at stated or -110 odds (rule 7) is unchanged.
  • Oct 16, 2026 · Rule 4
    Rule 4: CLV split by market. Moneylines keep price CLV. Spreads and totals lead with CLV in points plus `beat_close`; price CLV moves to a secondary column, because measured at the closing line it ignores line movement (row 39 beat the close by a point and showed -1.7%).
  • Oct 16, 2026 · Rule 3
    Rule 3: "last Pinnacle price before start", with a live T-0 pull added beside T-5.
  • Oct 16, 2026 · Rule 6
    Resolver rule added (Session 2 inherits it): outside a single-league segment, a bare city or a nickname another sport shares (Giants, Cardinals, Jets, Panthers, Hawks) is held. The daily cards have no sport markers, and without the rule "Pittsburgh ML (-160)" (next to "Ottawa ML": the Penguins), "Las Vegas +1.5" (a WNBA card: the Aces) and "Cleveland ML (+104)" (MLB playoff week: the Guardians) would have entered the NFL set. Confidence Cup episodes are single-league, so their bare cities resolve. Held rows stay in the fixture with the reason, as row 15 did.

ScoutRank is independent. We rate predictions, not personalities.

ScoutRank · SR-2026.4