RULES
Fantasy points are a translation of match events into a ledger.
Runs, boundaries, wickets, catches and economy bonuses are not equally likely, and their values can make a player with a modest real-world contribution more useful than a spectacular but isolated innings. Before selecting anyone, read the scoring rules you are using, identify which events are counted, and note whether the multiplier applies after every category is totalled. A clear ledger is more reliable than a vague feeling that a player is “involved”.
This guide uses the common IPL fantasy vocabulary of batting, bowling, fielding and milestone bonuses while avoiding platform-specific claims that can change. The examples are arithmetic illustrations, not a promise of a particular app’s final total. The important habit is to separate a player’s base contribution from bonus events, then compare the number of opportunities required for each player to reach the same target.
Read the scoring sheet in four columns
Organise every event under batting, bowling, fielding or match modifiers. This prevents a boundary bonus from being counted twice and makes omissions obvious.
Batting starts with runs and may add bonuses for fours, sixes, strike-rate bands or milestones. Bowling usually combines wickets, maiden overs and economy bands, with dismissals of certain batters sometimes carrying an extra value. Fielding includes catches, stumpings and run-outs. Match modifiers can include captain and vice-captain multipliers, but they should be applied after the ordinary score is calculated.
Write the exact rule beside each event when comparing sources. One scoring system may reward a half-century while another uses a different threshold; one may count a catch by a substitute while another treats substitutions differently. The practical question is not whether a rule sounds familiar. It is whether the rule is present in the scoring sheet attached to the contest you are entering.
Base points are about volume
A player’s base total comes from repeatable actions: balls faced, overs bowled, deliveries hitting the stumps, and fielding positions that bring them near the ball.
An opener who faces 35 balls has more chances to score runs and boundary points than a No. 7 who faces eight, even if the latter owns a higher strike rate. A four-over bowler begins with a larger wicket sample than a part-time bowler who may be used for one matchup over. Volume is not glamorous, but it is the first defence against selecting a player whose best event requires a rare script.
Use expected involvement as the denominator. If a bowler usually completes four overs, estimate wickets and economy across 24 deliveries. If a finisher normally receives ten balls, do not compare their theoretical six-hitting rate with an opener’s rate without adjusting for opportunity. The ledger lets you compare role sizes before you debate skill.
Milestones can distort a quick read
Milestone bonuses create thresholds: a batter on 48 is not the same as a batter on 52, and a bowler on three wickets may have crossed a bonus line that a two-wicket bowler has not.
Thresholds matter most when two players have similar base projections. A batter expected to face 30 balls has a meaningful chance of reaching a fifty, while a lower-order cameo may need an unusually fast innings to reach the same mark. For bowlers, a third wicket can change the score sharply, but chasing wickets can also damage economy if the bowler leaks boundaries while attacking.
Do not build an entire selection around a milestone. The player should already have a sensible role; the bonus is the extra edge. If the threshold is the only reason the player appears attractive, write down how often the required event has happened in the same batting slot or venue. A bonus that needs a perfect sequence is a ceiling note, not a floor assumption.
| Event | Typical ledger question | Why it matters |
|---|---|---|
| Runs | How many balls can the player face? | Volume creates the base |
| Boundary | Does the matchup allow clean hitting? | Adds ceiling to a run total |
| Wicket | Which phase will the bowler work? | Phase changes dismissal odds |
| Economy | How risky is the assignment? | Rate bonus needs context |
| Catch / stumping | Where will the player field? | Secondary route, high variance |
| Multiplier | Does the base score survive a miss? | Magnifies both upside and error |
Strike rate and economy are context metrics
Rate bonuses reward efficiency, but their meaning depends on the number of deliveries. A batter who scores 24 from 12 balls may clear a strike-rate band; a batter who scores 70 from 55 may fall outside it despite the larger run total.
For batting, estimate both runs and balls faced. A powerplay hitter benefits from field restrictions, while an anchor may be valuable because they preserve wickets and face the difficult middle phase. For bowling, economy must be read with role: a death specialist faces high-risk batters, whereas a spinner used in the quiet middle overs may have a safer path to an economy bonus.
The right comparison is not “who has the best rate?” but “what rate is plausible in this role, and how many events are needed to reach the bonus?” Venue dimensions, dew and opposition matchups answer that question. A rate bonus should move a close call; it should not erase a major difference in overs or batting position.
Wickets carry several layers of value
A wicket can deliver a dismissal score, a bonus for the type of batter dismissed, and an economy consequence if the rest of the spell is controlled. That makes bowling roles especially sensitive to phase.
Powerplay bowlers attack openers before the field spreads and may find edges or mistimed drives. Middle-over spinners can benefit from a batter forced to attack the matchup. Death bowlers have the highest boundary risk but also face batters who must keep scoring. The same bowler can have a different points profile depending on whether the captain uses them in overs one, two, 17 and 19.
Track overs by phase rather than accepting “four overs” as enough information. A bowler with two early overs and two at the death has a wide outcome range; a bowler used for four defensive middle overs may have a narrower range but a stronger economy path. The scoring sheet tells you the reward. The tactical role tells you whether that reward is reachable.
Fielding is a real route, not a consolation
Catches and wicketkeeping dismissals can rescue a player who contributes less with bat or ball. They should still be estimated from position and opposition patterns rather than added automatically.
A wicketkeeper behind a pace attack has more edge and glove opportunities than a keeper standing back to spin. A close-in fielder near the bat may have a sharp catch chance, while a boundary rider can collect difficult chances and occasional run-outs. The highest fielding expectation belongs to players whose team plan places them in the action for long periods.
Fielding is also noisy. A player may take two excellent catches one night and see no chance the next. Treat it as a supporting channel unless the player combines it with a secure batting or bowling role. This distinction helps avoid overvaluing a famous keeper on a match where the opposition is likely to hit cleanly over the infield.
Multipliers change the cost of mistakes
Captain and vice-captain multipliers do not create points; they magnify whatever the player produces. A quiet captain therefore hurts twice relative to an ordinary selection.
The safest multiplier candidate is not necessarily the player with the largest single-match ceiling. Look for two or more plausible routes to a useful base total. An all-rounder can reach that condition through batting, bowling and fielding, while an opener may reach it through runs, boundaries and a catch. A specialist bowler needs a credible wicket matchup or exceptional control to offer the same protection.
Apply the multiplier last in your arithmetic. First total the base estimate, then add the likely bonuses, then multiply. Keeping the order visible makes it easier to test a failure case: remove the milestone, reduce the boundary count or take away one over. If the player still has a respectable score, the selection is robust; if the total collapses, the multiplier is attached to a thin assumption.
Worked ledger: comparing two roles
Consider an opener projected for 38 runs, five boundaries and one catch against a four-over seamer projected for two wickets, one economy bonus and a chance of a catch. Their raw totals may look close even though their event paths are different.
The opener’s score depends on staying at the crease and converting balls into boundary events. The seamer depends on completing the spell, finding two moments of weakness and limiting damage. On a flat ground with a high total, the batter’s path may be wider. On a surface with seam or a top order vulnerable to swing, the bowler’s dismissal route can be more attractive.
Run three versions of the ledger: expected, favourable and failure. Do not compare only the favourable batter with the expected bowler. A fair comparison makes the same assumptions about the match script. This simple discipline is especially useful when choosing a vice-captain, because the reserve multiplier should not duplicate the same fragile event.
Questions readers ask
Scoring questions usually appear when two players contribute in different categories. Use these answers to check the ledger, the event threshold and the order in which multipliers are applied.
If an answer depends on a platform rule, venue change or late availability notice, verify that input separately. The best use of a guide is to make the next question sharper: which role is secure, which event creates value, and what would make the original view wrong?
Do all platforms use the same values?
No. Values, thresholds, substitute rules and penalty categories can differ. Read the contest scoring page before applying any example from an editorial guide.
Should I favour batters because runs are easier to predict?
Favour secure opportunity, not a category. A four-over bowler with a defined phase can be more predictable than a low-order batter who may face only a few deliveries.
Are boundary bonuses more important than runs?
They are additions to runs, not replacements. A player needs enough batting volume for boundary bonuses to become a meaningful part of the projection.
How should I treat a player who fields in the circle?
Treat fielding position as a small positive unless the player also has a dependable batting or bowling role. Catch chances remain uncertain.
When do I apply captain points?
After estimating ordinary batting, bowling and fielding points, then adding the relevant bonuses. This keeps the calculation auditable.
Related reading
The reading rail pairs the points ledger with role, price and match evidence. Choose the link that supplies the missing event estimate in your calculation.
Start with the page that answers the missing part of your current decision, then return to the confirmed XI and venue note. Internal references are editorial context; the official match announcement and scoring rules remain the final authority.
Take the next measured step
Keep a copy of the scoring ledger beside the confirmed XI, then make your final selection from events the player can actually reach.