Fantasy Cricket Strategy: A Repeatable Matchday Decision Framework
Method scope
Use this worksheet to make each selection traceable. It organises information; it does not predict a result or guarantee points, rankings, winnings, withdrawals, or profit.
Required inputs before lock
Confirmed playing XI and substitutes
What to check: Record the team announcement and the time you checked it. Do not treat a probable XI as confirmed.
Evidence boundary: A late replacement can invalidate earlier role assumptions.
Expected role and batting or bowling opportunity
What to check: Write the expected batting band, wicketkeeping duty, powerplay role, death-over role, or all-round workload.
Evidence boundary: Roles are expectations, not promises; match state can change usage.
Toss, venue, pitch and weather
What to check: Separate confirmed toss information from forecasts and pre-match reports. Note rain, dew, wind, surface pace and boundary size only when a source states them.
Evidence boundary: A forecast or pitch reading can be wrong and may change after play starts.
Current app scoring, credits and contest rules
What to check: Read the live contest screen before lock. Record the scoring version, credit cap, role limits, entry amount and tie rules that actually apply.
Evidence boundary: This site does not define operator scoring or contest terms; in-app rules take precedence.
Written assumptions
- Every input has a source and checked-at time; an undated screenshot or copied prediction is treated as unverified.
- Comparisons use the scoring and credit rules shown for the same contest, not rules remembered from another app or season.
- A completed worksheet still contains uncertainty. Selection quality cannot remove injuries, tactical changes, weather shifts, or normal sporting variance.
Six-step decision process
1. Freeze the contest rules
Decision rule: Copy the active scoring, credits, role limits and lock time before comparing players.
Recorded output: One rules record for the selected contest.
2. Verify availability
Decision rule: Remove anyone not in the confirmed XI. Mark uncertain roles instead of filling the gap with a guess.
Recorded output: A candidate pool with confirmation status and source time.
3. Map likely opportunity
Decision rule: Describe how each candidate can participate: batting position, overs, wicketkeeping or more than one role.
Recorded output: A role-based shortlist, not a reputation-based list.
4. Stress-test the shortlist
Decision rule: Apply the rain, dew, surface and late-role scenarios below. Replace only when the new scenario changes the role evidence.
Recorded output: A base XI plus documented contingency choices.
5. Choose captain and vice-captain
Decision rule: Score only the documented criteria below. Use two players with different failure modes when their evidence is otherwise close.
Recorded output: A captain, vice-captain and one-sentence reason for each.
6. Run the final lock check
Decision rule: Recheck XI, substitutions, app rules and lock time. Stop if a critical input is still unverified.
Recorded output: A timestamped decision record or a no-entry decision.
Captain and vice-captain selection
Total = role certainty + opportunity paths + condition fit − volatility penalty. This is a comparison discipline, not projected fantasy points. Use the strongest documented case for captain; when possible, use the next strong candidate with a different failure mode for vice-captain. Break ties by fewer unresolved uncertainties.
| Criterion | 0–2 score or penalty |
|---|---|
| Role certainty | 0 unknown; 1 plausible; 2 confirmed by current team or contest information. |
| Opportunity paths | 0 narrow; 1 one stable role; 2 more than one credible way to contribute. |
| Condition fit | 0 contradicted; 1 unclear or neutral; 2 supported by the current toss, surface or weather evidence. |
| Volatility penalty | Subtract 0 when the role is stable, 1 for one material uncertainty, or 2 for multiple unresolved uncertainties. |
Scenario-based risk checks
| Trigger | Recorded response |
|---|---|
| Official XI is not available near lock | Do not label availability as confirmed. Use a no-entry decision if the contest locks before the uncertainty can be resolved. |
| Rain or a shortened-match notice | Recheck contest validity and overs. Downgrade assumptions that require a full innings or a fixed bowling allocation. |
| Toss or a credible report changes the expected dew or chase conditions | Update only the condition-fit score; do not rewrite role certainty without separate role evidence. |
| The used surface differs from the pre-match assumption | Record the new source, then rerun condition fit for the affected roles. Keep unaffected criteria unchanged. |
| A player is confirmed but their expected role changes | Recalculate opportunity paths and multiplier choices. Availability alone does not preserve the earlier ranking. |
Source policy
| Source type | Use it for |
|---|---|
| Team or tournament source | Use for confirmed squads, playing XI, substitutes and official match notices. |
| Live contest screen | Use for current scoring, credits, eligibility, lock time, fees and payout terms. |
| Named weather or venue report | Use for forecasts and surface observations, labelled as forecasts or reports rather than facts when not confirmed. |
Final record
Keep the source, checked-at time and one-sentence reason beside every selection. If a critical input remains unverified, do not fill it with a guess—a no-entry decision is valid. Check the current in-app terms and your budget before choosing a paid contest.