Dated answer-first
Last updated: July 11, 2026. Use this page when the intent is scenario/path logic: how a team reaches a round, what upset conditions alter the route, and which assumptions lower confidence.
Model scenario paths, upset conditions, and what-could-change triggers for each knockout round without claiming fixed results.
Last updated: July 11, 2026. Use this page when the intent is scenario/path logic: how a team reaches a round, what upset conditions alter the route, and which assumptions lower confidence.
Start with explicit group or route assumptions, compare opponent path, squad availability, rest, travel, tactical matchup, and volatility, then label the forecast as a scenario.
Confidence stays scenario-based until draw, fixture, injury, suspension, lineup, and match-result data is confirmed. Do not invent live data or exact probabilities.
| Module | What it answers | Route |
|---|---|---|
| Round-of-32 path | Document assumptions, confidence, update trigger, and data gaps for this branch. | Generate attributed report |
| Quarterfinal path | Document assumptions, confidence, update trigger, and data gaps for this branch. | Generate attributed report |
| Final matchup scenario | Document assumptions, confidence, update trigger, and data gaps for this branch. | Generate attributed report |
| Upset condition checklist | Document assumptions, confidence, update trigger, and data gaps for this branch. | Generate attributed report |
No. It is an independent scenario workflow for analysis and content planning.
No. It organizes assumptions, confidence, upset triggers, and data gaps; it should not be read as a certain outcome.
Update after the draw, fixtures, squad news, injuries, suspensions, lineup signals, group results, and knockout match results.
The main bracket predictor is the broad entry page; this page narrows the intent to scenario paths and upset conditions.