CourtEdge · NFL Builder · Subscribe

NOVEMBER 1, 2026 · NFL MAIN SLATE · PRE-LOCK RESEARCH

CourtEdge Official Breakdown

Cash candidates, tournament stacks, upside plays and contest construction. Extended premium game-theory and portfolio guide. These are provisional research rankings, not injury-cleared locks or guaranteed outcomes.

Choose a contest & build lineups

1. The slate at a glance

Start with the tournament's rules and payout ladder. In a huge-field GPP, ceiling and correlation matter more than chasing median projection alone. The 23 supplied tournament profiles are available in the November 1 contest dataset, subject to verification against the current DraftKings lobby. In double-ups, emphasize reliable opportunity and cash probability. In single-entry, avoid forcing extreme leverage at the expense of projection.

2. Top cash candidates — ranked

RankPlayerPositionWhy
1CeeDee LambWRTarget volume and red-zone role
2Trey McBrideTEConcentrated target share
3Jahmyr GibbsRBReceiving and TD paths
4Josh AllenQBDual-threat scoring
5Amon-Ra St. BrownWRHigh-volume receiving role
6Bijan RobinsonRBDual-threat workload
7Dak PrescottQBStrong passing stack environment
8Puka NacuaWRTarget and reception upside

Salary-adjusted candidates to compare in cash builds: Chase Brown, Dak Prescott and Zay Flowers. Final rankings depend on price, status and role.

3. Tournament stacks — ranked

RankCorrelation corePortfolio use
1Jacoby Brissett + Trey McBride; CeeDee Lamb run-backLarge-field GPP
2Dak Prescott + CeeDee Lamb; Trey McBride run-backSE / GPP
3Josh Allen + Buffalo pass-catcher; Baltimore bring-backHigh-upside GPP
4Joe Burrow + Ja'Marr ChaseSE / 20-Max
5Jared Goff + Amon-Ra St. Brown + Jameson Williams; Minnesota bring-backContrarian GPP
6Drake Maye + Hunter Henry + DeMario DouglasLeverage double stack

4. High-upside GPP extensions

Jameson Williams: a volatility-friendly partner for Detroit game stacks. Dalton Kincaid: tight-end correlation with an Allen build when cleared. Brock Bowers: concentrated position ceiling when target share supports it. Omar Cooper Jr.: a salary-based candidate to verify carefully against official slate and role data. Never use outdated player-team associations.

5. Build by contest

Massive Huddle / Play-Action: generate thousands of unique candidates, mix single and double QB stacks, and use legitimate opposing run-backs in favorable game environments. Prioritize simulated Top 1% finish probability, then first-place chances and expected profit after accounting for duplication. SPY SE: retain projection strength with intentional correlation, and avoid overleveraging every roster spot. Cash: prioritize high-confidence roles, price efficiency and cash probability. Qualifiers: where prize is a ticket rather than cash, don't report invented monetary ROI; use appropriate advancement metrics.

6. QB stack construction

Use QB + WR, QB + WR + WR, QB + WR + TE, or selected QB + RB combinations. A run-back must come from the actual opponent in the quarterback's game, not another unrelated team. A same-team RB offers correlation in some game scripts but is not interchangeable with a receiving teammate. Avoid forcing runs of identical game stacks across every lineup.

7. Ownership and duplicates

Show the sum of each lineup's nine individual projected ownership percentages. This is not duplication probability. Diversify portfolio quarterback allocation, game environments and secondary pieces. When selecting a 20-Max portfolio, favor complementary outcomes rather than twenty nearly identical rosters.

8. Simulation and export checklist

Verify correct contest payout structure and entry cap; load a current official DraftKings salary file; reconcile each DK player ID, eligibility and team; exclude inactive or out-of-slate players; test nine unique roster slots and salary cap; confirm every exported row matches the selected contest format. Simulations are model estimates and are not a promise of future returns.

This playbook uses earlier supplied analysis, not a verified live injury feed. Update for final inactives before kickoff.

Open today's NFL builder

9. The objective: build for the payout, not for a projection leaderboard

The most common tournament-building error is treating every contest as though it awards the same prize to every high-scoring lineup. It does not. A double-up is a threshold problem: the payout is usually the same whether a lineup narrowly clears the cut or finishes first. A winner-take-all qualifier is the opposite: finishing second may return nothing. A large-field GPP rewards the extreme right tail of results, and a single-entry tournament often rewards a strong median-to-ceiling balance without demanding the same aggressive uniqueness as a 150-Max. Begin with the actual entry fee, total entries, maximum entries per person, complete prize ladder and eligibility rules. Model cashing, high finishes and first-place outcomes separately. Never label a lineup profitable merely because its raw projected points are high. A lineup can have attractive projections but be substantially duplicated, reducing the value of its best outcomes.

For a contest with cash prizes, the most useful primary output is expected net profit per entry. In each simulated slate outcome, determine the lineup's rank in the contest field, apply the payout ladder, account for any split prize caused by ties and duplicate rosters, then subtract the entry fee. Average that result over scenarios. ROI is the same expected net profit divided by entry cost. A ticket satellite requires a different calculation: model qualification probability and, if reporting dollar value, distinguish the ticket's stated face value from any realizable cash value. Model uncertainty is a reason to report ranges and confidence warnings, not a reason to invent precision.

10. How CourtEdge should simulate lineups

Candidate generation and game simulation are different operations. Generate a large, legal candidate pool first. Each candidate must use precisely the permitted roster slots, player eligibility, official player IDs and salary cap. Then run many plausible football outcomes against those candidates and a representative field of opposing lineups. One outcome should preserve game-level correlations: quarterback touchdowns must flow through eligible receivers, a trailing team may throw more, rushing attempts can suppress pass volume and a pass-heavy shootout may lift players on both sides. Simulating each player independently creates impossible or misleading stack outcomes.

The amount you plan to enter controls final portfolio size; it must not automatically limit the number of candidates or the number of simulation trials. If you plan to enter 175 lineups, generate meaningfully more than 175 legal candidates so the portfolio has alternatives. The actual candidate count and trial count should be reported in the interface, along with computation limits. Running 2,000 candidate lineups through a large set of scenarios is fundamentally different from simulating only 175 lineups and calling them the best. Deduplicate candidates before scoring; never rank identical roster combinations as independent ideas. Use the same scenario draws across all candidate lineups so their relative merits are comparable.

11. Ranking: points, win rate, cash rate, ROI and profit

Projected fantasy points predict an average score. Ceiling estimates indicate the upper part of the score distribution. Cash probability is the frequency a lineup crosses the contest's payout cut in the field simulation. Top-1% probability counts scenarios in which a lineup finishes in the top one percent of entries; it is not a direct estimate of first-place chance. First-place probability counts outright wins or appropriate fractional tie credit. Expected gross payout is the simulated average prize, including zero-prize outcomes. Expected profit equals gross payout minus entry fee. Sim ROI equals expected profit divided by entry fee. All should be displayed independently, with unambiguous labels.

For equally priced lineups in one contest, expected profit and Sim ROI produce the same order. Across contests with different buy-ins, they can disagree: a low-fee lineup could have higher percentage ROI but lower expected dollars. Profit maximization across the entire portfolio needs a budget, contest caps and an explicit treatment of risk. A practical default is to compare opportunities by expected profit and ROI side by side, then select the portfolio with limits on downside exposure. Do not simply chase a high displayed ROI from very few simulations or from an incorrect prize table. Display the date and version of the salary, projection and ownership inputs so the ranking has an audit trail.

12. The difference between a good lineup and a good portfolio

Suppose 175 individually high-ranked entries all rely on the same quarterback, two receivers and an opposing runback. Each lineup might score well in the same favorable game environment; however, the portfolio can fail together when that game disappoints. Portfolio optimization should track overlap and jointly simulated profit, not only sort the standalone entries and select the first 175. In every simulated scenario, sum the actual modeled payouts of all selected entries, minus all their entry fees. Choose the set that offers the best portfolio objective subject to user-defined exposure, uniqueness and budget constraints.

Set player, team, game and quarterback stack exposure bounds. Enforce minimum roster differences where the contest rewards diversity, and avoid filling the portfolio with lineups that differ only by a low-impact defense. If a candidate adds little incremental value because it overlaps heavily with already-selected builds, the optimizer should be willing to choose a slightly lower standalone-ROI candidate with a different ceiling path. Show the reason for the selection: incremental expected profit, additional scenario coverage and changes to concentration risk. Re-evaluate exposures after every swap or export exclusion. The displayed portfolio counts must equal the requested number of actual entries.

13. Contest presets: cash, single-entry and small-field

Cash contests are about exceeding a threshold, not maximizing first-place equity. Favor role stability, salary efficiency and realistic workload. A running back with reliable touches can be more appropriate than a highly volatile deep-threat receiver, even when the latter has the more exciting theoretical ceiling. Ownership is not automatically an enemy in cash: fading a popular, efficient play merely to be different adds unnecessary risk. A single-entry GPP merits a more balanced structure. Stack intentionally, but do not sacrifice several quality plays just to create a contrarian lineup.

For three-max and five-max contests, construct a small set of differentiated stories. One lineup can express the strongest median-plus-ceiling game environment, another can pivot to a competing quarterback stack, and a third can express an alternative game script. The distinction must be meaningful rather than cosmetic. A lower-owned player should earn inclusion through plausible upside, role and salary—not ownership alone. Even if three lineups have similar projected scores, the better set may have more distinct ways to reach a high finish. Use the actual contest size and payout concentration to determine how much variance is worth accepting.

14. Twenty-Max strategy: complementary bets with intentional leverage

A twenty-entry portfolio is a collection of twenty tournament bets, not one core lineup with nineteen tiny changes. Start by deciding how many quarterback/game environments deserve exposure. Then allocate entries across strong base constructions, leverage alternatives and carefully selected secondary stacks. A top quarterback can appear often without consuming all twenty slots; equally, equal quarterback exposure is not required if projections and contest conditions are asymmetric. The target is a diversified exposure plan anchored to expected value, not diversity for its own sake.

Compare popular one-off receivers with lower-rostered teammates or opponents who benefit under alternate scoring distributions. Measure leverage at the lineup level: ownership percentage totals are easy to display but are not estimates of duplication, and multiplying ownership percentages naively assumes independence that football lineups rarely satisfy. A more realistic field model considers common stack constructions, salary usage, positional correlations and the tendency to roster obvious values together. Test whether lineup ceilings remain attractive after accounting for shared winning outcomes and likely prize splits. Finish by reviewing the full twenty-lineup exposure report before exporting.

15. 150-Max, 175+ entries and large-field portfolio design

For a 150-Max contest, the legal entry cap is 150 in that particular contest; 175 total entries means allocation across one or more contests whose combined limits permit that number. The builder should never bypass a contest's stated maximum. In mass-entry play, maintain two distinct counts in the header: simulated candidates and entries selected. It should be possible to simulate thousands of candidates, then export exactly 150 for one contest and another 25 for a different eligible contest. For every contest, select against its own prize ladder and field model; do not pretend a cash lineup and a top-heavy GPP lineup are interchangeable.

Use an optimization pass over the candidate pool to maximize combined simulated expected profit, with user-editable player maximum exposure, team and game allocations, lineup overlap restrictions and selected variance tolerance. Recalculate expected portfolio profit after choosing the set; the sum of standalone lineups' expected profits may be a helpful diagnostic, but it does not describe portfolio risk or correlated downside. Show both. Preserve alternative lineup candidates so late injury news can trigger targeted replacements instead of rebuilding everything from zero. Generate a readable audit summary: contest, selected lineup count, total entry fees, player exposure, stack exposure, mean modeled payout, profit, ROI and worst-case scenario range.

16. Quarterback stacks and game correlation

Quarterback stacks are a tool for concentrating on plausible high-scoring game scripts. A QB-plus-one construction leaves more roster flexibility and can be appropriate when an offense spreads scoring widely. QB-plus-two narrows the required success path but may raise ceiling when multiple teammates can share strong passing production. A QB-plus-three build is an aggressive bet on a concentrated, pass-heavy ceiling; it should not be a mechanical default in every tournament. Use a same-team running back only where the modeled game script actually supports the combination, such as receiving involvement or a particularly prolific overall offensive outcome.

Runbacks must belong to the quarterback team's actual opponent on the selected slate. They are neither compulsory in every lineup nor automatically good. In a tightly contested, fast-paced game, one opposing receiver can raise lineup upside when both offenses score. In a blowout, a successful quarterback stack may not need an expensive opposing piece. Compare no-runback, one-runback and selected two-runback builds in simulations. A tight end and a wide receiver can be strong correlation partners but their target competition matters. Stack rules should constrain candidate generation itself; a validation warning after lineup creation is not enough.

17. Value plays: role first, price second and ownership third

Value is not synonymous with cheap. A low-cost player is useful if the salary discount purchases meaningful expected workload and allows higher-upside spending elsewhere. Inspect routes, target participation, red-zone opportunities, rush share, playing time, game script sensitivity and replacement competition. Cheap one-off plays can be essential, but filling multiple roster positions with fragile punt plays may destroy the lineup's chance of posting the extreme score needed for a large-field win. Every value candidate should have a concrete path to a scoring outcome that beats salary-based expectations.

Consider Chase Brown as a conditional running-back example: receiving work and goal-line usage could create a valuable combination if confirmed by current projections and role news. Zay Flowers is attractive where targets and after-catch opportunity support volume, but his ceiling is not guaranteed simply because his team has a strong offensive environment. Jameson Williams profiles as a more volatile downfield and big-play candidate whose best tournament uses may differ from his cash suitability. Dalton Kincaid offers a potential tight-end correlation route in Buffalo passing stacks, conditional on his active status and expected role. These are candidates to reassess, not declarations of today's locks. Any player listed out, inactive, traded off the slate or without an official player ID must be removed before builds are finalized.

18. Premium-player opportunity cost and ceiling paths

Paying up for a premium receiver or running back only makes sense relative to the alternatives at that roster position and the total lineup construction. A high-priced target hog with an excellent median may be the right foundation in cash; a more volatile but lower-owned comparable may deserve a stronger tournament share if the ceiling scenarios justify it. Examine whether the salary savings unlock a meaningful upgrade at another position, not just whether the cheap player is projected for sufficient points in isolation. Compare realistic two-for-two or three-for-three roster swaps instead of evaluating each player in a vacuum.

For quarterback selection, rushing is valuable because it creates fantasy scoring without relying on a particular receiver. But high-priced dual-threat quarterbacks can crowd out premium pass-catchers elsewhere, so compare the full stacked roster's expected tournament value. A pocket passer in a pass-heavy, high-total game can outscore a rushing quarterback in some outcome clusters and may be less popular. At tight end, identify whether paying up reduces lineup fragility or merely sacrifices ceiling at a higher-impact position. At defense, consider sacks, pressure, turnovers and scoring variance without assuming a cheap defense cannot contribute to a winning lineup.

19. Ownership, duplication and sensible leverage

Projected ownership reflects how frequently a player is expected to be used by the field; it does not by itself say whether the player is a good or bad selection. A player can be both popular and underpriced. The right question is how that player changes the chance the entire lineup wins or cashes, including the possibility that many opponents share the same combination. Make roster-level leverage explicit: compare the performance distribution and expected payout of otherwise similar lineups built around chalk, a credible pivot and a mixed construction.

A sum of nine projected ownership percentages is an easy descriptive stat, but it does not predict exact duplicates. Duplication depends on joint ownership patterns, salaries left on the table, quarterback stack habits, positional constraints and field composition. Model expected duplicates only when the field-generation process actually does so. If the model has no reliable duplicate data, label the result an approximate uniqueness score instead. Never state an invented duplicate count. A strong portfolio can include several popular players while still remaining structurally distinctive through secondary correlations, off-the-board game environments or alternative roster allocations.

20. Game-by-game method: what to ask before ranking a matchup

Every game review should begin with four questions. First, is the game likely to produce enough total plays and touchdowns to sustain multiple tournament-winning players? Second, where will fantasy production concentrate—quarterback rushing, one lead receiver, multiple wideouts, or the running game? Third, what script would make the market's expectations wrong? Fourth, are the relevant players priced and owned as if that script is already certain? A game can carry an appealing total but still be a poor stacking opportunity if touchdowns are widely distributed or if field ownership captures nearly all of the upside.

Classify the matchup in the playbook as a primary stack candidate, secondary mini-stack, one-off target or fade unless late news changes the picture. State the specific catalysts: offensive line absences, defensive personnel, pace changes, red-zone concentration, weather and injury news. Do not invent game totals, injury designations or snap shares. For today's slate, use the official November 1 game list and verified updates to fill an 11-game matrix in the site's data feed. The procedure is actionable even before the latest numbers arrive; fabricated numerical certainty is not.

21. The portfolio learning loop: measure decisions against results

Learning from previous contest results should improve future model calibration, not encourage chasing a single winning lineup. Store pre-lock projections, ownership estimates, injury assumptions, simulation seeds, contest payout ladders and chosen lineups. After games finish, compare actual fantasy points and ownership with what was predicted. Track calibration by position, salary tier, game total, ownership bucket and contest type; measure whether estimated cash and top-finish probabilities were accurate over many slates. Winners are useful examples of possible successful constructions but are a selected, unusually lucky sample. Training only on winners can bias the builder toward extreme, misleading conclusions.

Use out-of-sample dates when checking whether a new rule improves ROI or ranking quality. For each proposed adjustment, compare the old and new model on the same historical contests without leaking actual results into the pre-lock projections. Count the number of entries and total fees, not just gross winnings. Compare candidate-level and portfolio-level performance. A rule should be retained when it has repeatable evidence across enough contests, is operationally robust and does not merely fit yesterday's outcome. Display model version, data freshness and the size of the backtest sample to readers who want transparency.

22. Late injury news and swap discipline

Late-breaking inactive news should trigger targeted, auditable revisions. First remove ruled-out players and those excluded from the actual slate. Then reassess teammates for routes, snaps, carries and red-zone roles; a replacement player's projected value may rise while the offense's overall efficiency falls. Re-run simulations with the updated role distribution rather than simply adding an arbitrary projection bonus. Update ownership estimates because the field may react to the same news. A player who appears under-owned at noon may become popular minutes before lock.

Never rewrite already locked lineup slots in an unauthorized way. For late swap, consider only eligible unlocked players and roster positions under the site's contest and platform rules. Protect salary, eligibility, position slots and the user's preferred risk profile while reacting to new information. Log which lineups changed and why. The replacement process should preserve portfolio diversification: if an injury suddenly increases one value player's appeal, avoid assigning him to every entry without evaluating ownership, ceiling, correlation and concentration. Any automatic adjustment must be tested against a valid official export file before it is used for real entries.

23. Final build and export quality gate

Before presenting a build as ready for entry, check the selected sport, date, slate and contest; official entry cap; valid nine-player roster composition; salary cap; every player's current team and official platform ID; no duplicate player in a lineup; correct quarterback-opponent mapping; ownership and exposures; and that the exact requested number of unique lineups exists. The displayed ranking metric must match the contest type. Re-simulate after final candidate selection so the portfolio total reflects the actual exported entries. The exported CSV should be opened in a parser and compared row-for-row with the selected player IDs and roster slots.

If any of these checks fails, block the export or display a prominent warning rather than silently assuming success. Do not say that the optimizer enforces a stack rule just because a page contains a validator for it. Nor should a preview deployment count as proof the underlying game simulator ran. The user should be able to see counts for candidates generated, valid candidates, simulations completed and unique entries exported. These operational details protect the quality of the picks and the credibility of the analysis just as much as player rankings do.

24. Decision board and practical last look

The final reader-facing board should separate core plays, strong pivots, role-driven values and high-variance tournament darts. For each recommendation, give a concise positive case, the failure case, the contest formats where it fits and a conditional exposure range that depends on slate size and news. A value play can be a strong salary saver and still be a poor fit in a winner-take-all lineup if he has little chance to exceed his modest ceiling. Conversely, a boom-bust receiver can make a large-field lineup worthwhile without being reliable enough for a double-up.

Review the portfolio as if every lineup expressed a game thesis. Can a reader explain why this particular nine-man combination would beat the field? What needs to go right? Which popular constructions does it beat when its thesis succeeds? How much of the portfolio is exposed to the same fragile assumption? If the answers are vague, more simulations alone will not rescue the strategy. Strong builds come from plausible football outcomes, price-aware roster construction, defensible risk-taking and rankings that follow the real payout table. That is the standard the CourtEdge NFL builder should aim to make repeatable.

Analysis is educational and conditional on verified slate data. No simulated result guarantees profit.