What you'll find on this hub
Watch in the warm-up, not the broadcast.
The scouting-session photographs on this page show what LetsGame editors look for in the warm-up: footwork, grip, and the way a player moves between overs.
LetsGame does not publish scouting notes it has not verified. The scouting-session observation page holds the ones LetsGame editors have stood and watched.
If a scouting note is older than six weeks, it is folded back into the long-form guide rather than the news page. LetsGame prefers dated references to fresh guesses.
Read the workload, not the talk.
Training-load references are the most under-used part of a fantasy squad. A player who has been in the nets for three days often produces a different match than the broadcasters expect.
The training-load recovery page on this hub holds the workload references LetsGame editors cross-check before publishing a match preview.
If the workload data is not available, LetsGame says so on the preview. LetsGame does not invent a workload story to fill a column.
Wicketkeeper workflow, and the small things in between.
The wicketkeeper role is the smallest section of a squad but the most rule-heavy. The wicketkeeper role detail page on this hub holds the workflow LetsGame editors follow.
LetsGame does not publish role detail that has not been verified against a current rule sheet. The role detail page is updated when the rules change.
If a role detail is not yet verified, it stays off the page. LetsGame would rather have a quiet page than a wrong one.
Related pages
- Fantasy cricket — Format explainers and captain strategy.
- Predictions — Batter vs bowler matchups and risk notes.
- Matches — Toss, pitch and weather checks.
