Research guide · Matchup context

A practical matchup-research checklist

A matchup view is strongest when each layer answers a different question. Start with what the player or team normally does, update that baseline for the current role, then examine how the opponent and environment can change the opportunity.

1. Establish the baseline

Begin with a sample broad enough to describe the current player and team. Season averages are a useful default, but they may blend different roles. If a player changed teams, entered the starting lineup, returned from injury, or gained a new tactical assignment, create a second baseline for the current role and retain the larger sample as a stability check.

Record both the average and the distribution. Two players can share the same average while producing very different ranges. Note how often results cluster near the average, how often extreme games occur, and whether zero or low-opportunity outcomes are common.

2. Confirm the current opportunity

Check the schedule and expected participation before studying the opponent. Opportunity measures should fit the sport: plate appearances and lineup slot; minutes and attempts; snaps, routes, targets, and carries; ice time, line assignment, power-play time, and shots.

Do not skip the denominatorA receiver’s catches can fall because target rate declined, because routes declined, or because catch conversion declined. Those explanations have different implications for the next matchup.

3. Describe the opponent without using one ranking

An overall defensive rank compresses many conditions. Break the opponent into the factors that connect to the question. For baseball, that may include pitcher handedness, pitch mix, bullpen quality, park, and expected weather. For basketball, consider pace, shot profile allowed, positional matchups, rebounding environment, and transition frequency. For football, consider coverage, pressure, run fronts, pace, and likely game script. For hockey, consider goaltending, shot suppression, penalties, special teams, and line matching.

Use opponent information that has a plausible path to the opportunity or result. A broad ranking with no connection to the measured statistic can create a confident-sounding but weak argument.

4. Account for schedule and environment

Rest, travel, altitude, weather, park dimensions, back-to-backs, overtime in the prior event, and dense schedule periods can change performance or workload. These factors are usually modifiers rather than standalone predictions. Avoid assuming every player responds identically.

Game environment can also affect volume. Pace and overtime create more possessions. A likely low-possession game reduces the number of chances available to everyone. A baseball game with weather risk can reduce expected innings or plate appearances even if it starts.

5. Build scenarios instead of one fragile answer

Create a base case using the most likely lineup and role. Then identify the one or two uncertainties that would materially change it. If a questionable teammate is active, usage may stay near baseline; if inactive, opportunity may shift. If a projected goalie or pitcher changes, the opponent context may need to be rebuilt.

Do not create dozens of scenarios for trivial changes. Focus on decisions that alter playing time, opportunity, or the quality of the direct matchup.

6. Avoid double counting

Several statistics may describe the same cause. A fast-paced opponent can increase possessions, attempts, and counting stats. Treating all three as separate positive signals exaggerates the evidence. Write the causal chain once: faster pace → more possessions → more opportunities. Then add only genuinely independent information.

Correlation is also common among teammates. An injury can raise one player’s minutes, another’s ball-handling, and a third player’s rebounding position. Those are connected outcomes of one roster change, not unrelated discoveries.

7. Write a balanced conclusion

A useful conclusion states the baseline, the current role adjustment, the opponent or environment modifier, and the largest uncertainty. It should also say what new information would change the view.

Example structure: “The season baseline is stable, and the current starting role has added opportunity across the last ten games. The opponent plays at a slower pace, which offsets part of that increase. Confirm the questionable teammate’s status before treating the role as unchanged.”

The full checklist

Statly is an informational research tool. Historical results and contextual comparisons do not guarantee a future outcome, and time-sensitive information should be confirmed through official league and team sources.