First-Team Checklist — Pre-Match in 10 Steps

A practical checklist the desk recommends for your first paid contest and every contest after.

Editorial illustration of pre-match checklist for fantasy cricket first-team contests
CHECKLIST

Pre-match, in 10 steps

A practical checklist for the 60-90 minutes before lock-in. The desk recommends running through this for every contest — paid or practice — at least for the first 10 contests.

The 10-step checklist

1. Confirm state eligibility

Verify your state allows paid fantasy contests. See the legal & availability page for the current list.

2. Confirm KYC is on file

KYC must be complete before withdrawal. Confirm it now to avoid delays after winning.

3. Confirm predicted XI

Use the predictions desk tracker to confirm the latest expected XI. Mark as "confirmed" after toss.

4. Check venue notes

Look up the chasing trend, dew forecast, and pitch behaviour for the venue. Adjust captain signal accordingly.

5. Identify captain candidates

List 3-5 candidates. Apply the captain selection framework — overs remaining, match-up, position.

6. Identify vice-captain

Pick a high role-security player. The vice-captain is your fallback if the captain doesn't play.

7. Build the team within credit budget

Standard fantasy team composition: 1-2 wicket-keepers, 3-5 batsmen, 1-3 all-rounders, 3-5 bowlers, total 11 players.

8. Pick your contest size

Smaller contests (2-50 entries) reward consistency. Larger contests (1,000+) reward differentiation. Pick the size that matches your team strategy.

9. Lock-in 5 minutes early

Lock your team 5 minutes before the official deadline. Last-minute network issues at the deadline are common.

10. Post-match: 5-minute review

After the match, spend 5 minutes reviewing your captain choice, differential hits and team composition. The learning compounds.

After the contest — the 5-minute review

The single highest-impact habit for long-term improvement.

The post-match review is where long-term fantasy edge comes from. Five minutes per contest, focused on three questions: (1) Did my captain pick pay off? Why or why not? (2) Did any of my differential picks outperform expectations? (3) Did my team composition match the conditions?

The answers compound over time. After 20 contests, you'll have 20 data points on your captain framework's accuracy. After 100 contests, you'll know which categories of picks you consistently get right and which you consistently get wrong.

The desk recommends keeping a simple spreadsheet or note: contest, captain pick, captain score, vice-captain score, top differential, condition notes. The patterns emerge within a season.

Apply the checklist to today's matches

The predictions desk publishes daily picks using a similar framework. Pair the checklist with the desk's coverage for the strongest prep.

Why this topic matters for adult fantasy-cricket readers

How this page fits into the desk's broader coverage and where it connects to other guides.

Fantasy cricket is a knowledge-intensive hobby. The desk's role is to surface verified information that helps readers make their own decisions — not to promise outcomes or push a single strategy. Each page on the desk is a building block in the larger editorial coverage of the topic.

This page in particular addresses one specific aspect of the broader topic. The desk recommends pairing it with the related coverage linked at the bottom of the page. The pairing gives readers both the narrow (this page) and the broader (the related hubs) view.

Editorial pages are not marketing pages. The desk labels unverifiable claims as such, refreshes time-sensitive facts on a 14-day cycle, and logs corrections visibly. If a fact looks out of date, the desk wants to know — send a note to the customer-care channel.

How the editorial team keeps this page current

The verification cycle and what triggers an update.

14-day refresh cycle

Time-sensitive pages (state eligibility, app version, withdrawal timelines, bonus offers) are re-checked every 14 days. The last-reviewed date at the top of the page reflects the latest cycle.

30-day refresh cycle

Reference material (glossary terms, scoring rules, role definitions) is re-checked every 30 days. Material changes are logged visibly; minor copy edits are not.

Triggered updates

If the operator announces a material change (new app version, scoring rule update, state eligibility change), the desk updates the affected pages within 48 hours of the announcement.

Reader-driven updates

Reader notes sent to the customer-care channel are read and triaged. If a note flags a discrepancy that the desk can confirm against first-party sources, the desk updates the page and credits the note (if requested).

Correction log

Material corrections are logged at the top of the affected page with the date and the change. Silent corrections are not used — if the date is silent, the correction did not happen.

Editorial verdict independence

The desk's editorial verdicts (the review, the captain framework, the venue notes) are independent of the operator's commercial interests. Where the desk disagrees with operator marketing claims, the disagreement is stated with reasoning.

Editorial framework — how the desk thinks about this topic

The structure that holds the coverage together across the desk's pages.

The editorial desk organises its coverage around a four-stage reader workflow: awareness, evaluation, decision, and review. Each page on the desk targets one stage.

The awareness stage introduces the topic — what it is, why it matters, and what readers need to know first. The evaluation stage compares options and surfaces decision criteria. The decision stage walks through the specific steps. The review stage covers post-action learning.

This page sits in the awareness and decision stages for its topic. The related coverage linked at the bottom of the page covers the evaluation and review stages. Together they form a complete picture.

The framework is intentionally simple. Fantasy cricket is entertainment with a budget; readers benefit from clear, structured information more than from clever analysis. The desk keeps the structure visible so readers can navigate the coverage efficiently.

Reader questions the desk has logged

Common questions on this topic, drawn from reader notes and search queries.

Where does the information come from?

The desk's primary sources are first-party — the operator's website, store listings, official app metadata, public corporate filings. Secondary sources are used for cross-verification. Where the desk cannot independently verify a claim, it is labelled as such.

Is the desk affiliated with the platform?

The desk is an independent editorial team. Where affiliate links are present (to the platform's app or to a related service), the desk discloses the commercial relationship on the affected page.

Does the desk have a mobile app?

The desk is a web-based publication. It works on desktop and mobile browsers. There is no separate mobile app for the editorial coverage.

Can I subscribe to updates?

The desk does not currently run an email subscription. Bookmark the predictions desk and the home page for daily coverage updates.

How do I report a fact that looks wrong?

Send a note to the customer-care channel with the page URL and the discrepancy. The desk reads every note.

Does the desk accept guest contributions?

The desk does not currently publish guest contributions. Coverage is produced by the small in-house editorial team.

Editorial perspective on this topic

Where the desk's coverage stands on the spectrum of opinion.

The desk's editorial perspective on fantasy cricket is informed by three principles. First, fantasy is entertainment with a budget — readers should treat winnings as a surprise rather than an expectation. Second, verified information matters more than marketing claims — readers deserve to know what is true, what is operator-claimed, and what is not independently verified. Third, long-term edge comes from compounding small insights over many contests — not from a single contest bet.

Where this page's coverage aligns with the operator's published material, the alignment is noted. Where the desk's view differs, the disagreement is stated with reasoning. The desk does not soften disagreements to please the operator; nor does it manufacture disagreements to seem independent.

The desk's coverage on this topic will continue to evolve as the operator updates the platform and as readers send in corrections and questions. The "last reviewed" date at the top of the page is the best signal of currency.