Fantasy cricket points are built from more than runs and wickets. This guide explains how batting, bowling, fielding, milestone, strike-rate and economy rules usually work, then gives you a practical checklist for verifying captain, substitute and playing-XI settings before entering a contest. Because scoring systems vary by platform and format, use the reference below as a framework and confirm the live rules shown in your selected contest.
Overview
A fantasy cricket scoring system converts events in a real match into points for selected players. A batter may score through runs, boundaries and milestones; a bowler may earn points for wickets, maidens and economical spells; fielders usually gain points for catches, stumpings and run-outs. Some contests also apply bonuses or deductions for strike rate, economy rate, ducks, dropped catches or other defined events.
The exact values are not universal. A platform can change its scoring table, apply different rules to Test, ODI, T20, domestic, women’s or league contests, or exclude certain bonus categories altogether. The safest approach is to treat the contest’s own rules page as the final authority. Do not rely on a points table copied from an old article, a previous season or another fantasy service.
Platform-neutral scoring reference
The following table shows the main categories to check. It is a checklist of scoring events, not a claim that every platform awards the same number of points.
| Category | Events to check | Selection implication |
|---|---|---|
| Batting | Runs, boundaries, sixes, milestones and dismissal for a duck | Prioritise players likely to face enough deliveries and contribute consistently. |
| Bowling | Wickets, bowled or leg-before-wicket bonuses, maidens, runs conceded and wickets taken in a spell | Review role, overs allocation and conditions rather than choosing only by reputation. |
| Fielding | Catches, stumpings, direct-hit run-outs and assisted run-outs | Wicketkeepers and active close fielders can have additional routes to points. |
| Strike rate | Threshold-based bonuses or deductions, often dependent on a minimum number of balls faced | Check whether the rule applies to the match format and whether a minimum-ball condition exists. |
| Economy rate | Threshold-based bonuses or deductions, usually dependent on a minimum number of overs bowled | Confirm how partial spells, shortened innings and super overs are handled. |
| Captain multiplier | A multiplier applied to the captain’s earned points | Choose a player with several realistic scoring routes, not only a high ceiling. |
| Vice-captain multiplier | A separate multiplier applied to the vice-captain’s earned points | Use a dependable second option and confirm what happens if that player does not play. |
To understand the underlying match data, see Cricfizz’s guide to reading a cricket scorecard. It can help you connect fantasy events with runs, overs, strike rate and bowling figures.
Checklist by scenario
Before building a lineup
- Open the exact contest rules, not a general help page.
- Confirm the match format: T20, ODI, Test or another competition-specific format.
- Check the squad list, player credits or selection limits, roster composition and maximum players from one team.
- Review whether a player must be named in the playing XI to earn points.
- Identify scoring categories that reward your intended player types, such as all-rounders, opening batters or bowling all-rounders.
After the toss and team announcement
- Replace probable selections who are not in the confirmed playing XI.
- Check batting position, wicketkeeping duties and expected bowling quota.
- Review late injury news, workload management and any team squad update.
- Use the pitch report and toss update as context, not as a guarantee of performance. Surface, weather and innings conditions may affect opportunity, but they do not remove match uncertainty.
- Recheck captain and vice-captain choices after confirmed roles are available.
Cricfizz’s probable playing XI guide and pitch report and toss update hub can support this final review.
If your captain or vice-captain is absent
- Find out whether the platform automatically transfers the multiplier, removes it or applies a substitute rule.
- Check whether a player who is selected but does not take the field receives points.
- Confirm whether substitutions are automatic, manual, limited by time or unavailable after the deadline.
- Do not assume that a reserve player becomes eligible simply because the original selection did not play.
When comparing player options
Estimate opportunity before attempting to predict an exact score. For a batter, consider likely position, recent role, innings length and boundary potential. For a bowler, consider whether the player is expected to complete a full spell, bowl at the death or operate with the new ball. For an all-rounder, verify that the player is genuinely likely to contribute in both disciplines. A player with multiple routes to points may be more resilient than a specialist whose value depends on one event.
What to double-check
Format-specific conditions
Strike-rate and economy bonuses need particular care. A T20 rule may use different thresholds from an ODI rule, while a Test contest may treat innings, overs and milestone bonuses differently. Shortened matches can also change how minimum balls faced or overs bowled are interpreted. Before joining, look for clauses covering rain-affected matches, abandoned games, super overs, tie-breakers and matches reduced by the playing conditions.
Dismissals and fielding events
Check how the platform treats catches completed by more than one fielder, stumpings, run-outs involving two players and catches later overturned by a review. Also verify whether points are awarded for a catch when a batter is dismissed through a special match event. These details are easy to overlook because the scorecard may show one dismissal while the fantasy rules divide credit differently.
Bonuses and deductions
Read the definitions, not just the headline point values. A boundary bonus may require the shot to be recorded as a four or six. A duck deduction may exclude certain batting positions or apply only to recognised batters. Economy and strike-rate adjustments may require a minimum workload. If the rules use abbreviations, open the platform glossary before making assumptions.
Scoring updates
Live points can change when a scorecard is corrected, a wicket is reassigned or a match event is reviewed. Compare the fantasy scoreboard with the official match scorecard where possible, but allow for processing delays. Final rankings should be based on the platform’s completed scoring process and published settlement rules.
Common mistakes
- Using an old points table: Scoring values and eligibility settings can change between seasons, formats or contests.
- Picking a player before checking the playing XI: A probable selection is not the same as a confirmed selection.
- Choosing a captain only for reputation: The multiplier increases both the benefit of a good performance and the cost of a quiet one. Assess role and opportunity first.
- Ignoring workload requirements: A strike-rate or economy bonus may not apply unless the player faces enough balls or delivers enough overs.
- Confusing fantasy points with real match impact: A player can make a tactically important contribution without triggering a large fantasy score, while one brief event can produce many points.
- Assuming every platform handles substitutes identically: Automatic replacements, bench players and non-starters may be treated differently.
- Overreacting to one recent score: Use role, opportunity, conditions and opposition context alongside recent form. Fantasy selection remains uncertain.
For a wider pre-match process, read the cricket match preview guide, which covers pitch, toss, form and playing-XI checks.
When to revisit
Return to this checklist before each contest rather than treating it as a one-time reference. Recheck the rules at the start of a new season, when a platform redesigns its contest format, when a new tournament or league is added, and whenever the match type changes from T20 to ODI or Test cricket. Also revisit it after a scoring dispute, an unexpected substitute result or a change to captain and vice-captain handling.
A practical match-day audit takes only a few minutes:
- Open the exact contest rules and note any format-specific exceptions.
- Confirm the toss, playing XI, player roles and late injury updates.
- Check roster limits, substitutes and deadline settings.
- Review batting, bowling, fielding, strike-rate and economy conditions.
- Set the captain and vice-captain only after confirming both players are expected to play.
- Save or record the final lineup and the rules used for that contest.
Use fantasy cricket as an analytical and entertainment activity, set personal limits and avoid treating projections or multipliers as guarantees. The strongest process is not a promise of a result; it is a repeatable way to make informed selections from the information available before play begins.
