Fantasy players obsess over player form and forget that the ground itself votes on every match. A batter in great form at a huge ground with long boundaries and a slow outfield will score differently from the same batter at a small ground with a flat pitch and short square boundaries. Venue records — average first-innings scores, how wickets are shared between pace and spin, and how often teams successfully chase — are the most stable data in fantasy cricket, because they are built from dozens of matches rather than one player's recent week. Learning to read a venue before you read the players gives your team a structural advantage that form alone cannot provide.

First, the average first-innings score in the format you are playing, over the last ten or so matches at the ground. This single number tells you whether to stack batters or bowlers. Second, the pace-versus-spin wicket split: at some grounds spinners take half the wickets, at others they barely feature, and that split should decide your bowling combination. Third, the chasing record: if teams batting second win most matches at a ground, dew or a flattening pitch may be helping chasers, which boosts second-innings batters and hurts second-innings spinners. Boundary size is a useful fourth number — small grounds inflate batter scores and punish economical bowlers, while large grounds reward big hitters who can clear long ropes and bowlers who force mishits.

At a high-scoring ground, pick six batters, choose bowlers only if they are proven wicket-takers, and captain a top-order batter, because economy points will be scarce and big scores will decide the contest. At a low-scoring ground, flip the structure: pick five bowlers, prefer all-rounders who contribute in both disciplines, and consider captaining a bowler or a bowling all-rounder, because wickets and economy will decide the contest. At a spin-friendly ground, carry two spinners including a wrist-spinner and favour batters who play spin well. At a seam-friendly ground, carry three seamers and favour technically sound openers. Venue first, players second — the structure follows the ground.

Venue stats have traps. A ground that was relaid, or whose pitches were changed for a new season, may not behave like its history suggests — check whether recent matches at the ground still match the long-term pattern, and weight the last five matches more than the last fifty. Day matches and day-night matches at the same ground can play very differently because of dew, so split the record by match timing when you can. And remember that venue stats describe averages, not certainties: a low-scoring ground can still produce a 200-plus total if two batters catch fire, so use venue stats to set your team structure, not to rule out every batter in a low-scoring game. Structure from the venue, picks from form.

Build a quick routine: look up the average first-innings score at the ground in this format, note the pace-spin wicket split, check the last five results including who won the toss and whether chasing succeeded, and glance at boundary dimensions if they are published. Write down one sentence — for example, low-scoring, spin-friendly, chasing wins — and let that sentence set your team structure before you look at individual players. Over a season, this routine quietly adds points to every team you build, because you stop picking batting-heavy teams for bowler-friendly grounds and bowler-heavy teams for batting paradises.

Grounds have personalities, and fantasy teams should match them. Check average scores, the pace-spin split and the chasing record, set your structure from the venue, and then pick players who fit that structure. Form picks players; venues pick teams.