How to Play BatBall11 — A Step-by-Step Workflow
The complete workflow from a freshly installed app to your first paid contest, including the questions every new player asks at each step.
Five workflows inside one app
Fantasy cricket apps look complex at first because they compress five workflows into one screen: contest selection, team creation, captain choice, post-match review, and withdrawal request. This page walks through each one.
Before joining your first paid contest, run a practice contest. Every fantasy platform on the Indian market offers free practice entries — use one for at least one full match.
Workflow 1 — Contest selection
Choosing the contest that matches your budget, your team's expected score, and your appetite for risk.
Contest size matters
Smaller contests (2-50 entries) reward consistency. Larger contests (1,000+ entries) reward differentiation. Match your contest size to your team-building strategy.
Prize structure
Read the prize structure before joining. Top-heavy contests pay 1-3 places; flat structures pay more entries but smaller amounts per winner.
Entry fee vs expected value
Entry fees on Indian fantasy apps range from free practice contests to high-stakes entries. Treat each contest as an entertainment expense with a clear ceiling.
Workflow 2 — Team creation
The team-creation screen is where most losing contests are decided.
You will pick 11 players from the squads announced for the match, within a credit budget (typically 100 credits). The composition must include a defined number of batsmen, bowlers, all-rounders and wicket-keepers. Each player has a credit value that reflects their expected contribution.
The captain and vice-captain selection is the single largest decision. Captain gets 2× points and vice-captain gets 1.5×. Together those two choices usually account for 30-40% of your final score.
Open scoring referenceWorkflow 3 — Captain choice
Three signals that consistently separate a safe captain from a coin-flip one.
Overs remaining
The captain's role in the match matters. An opener in a 20-over T20 has limited time to score; a middle-order anchor or death-overs bowler has more.
Opposition match-up
A batsman against a weak bowling attack in favourable conditions is a higher-floor pick than a star player against a strong attack.
Batting position
Players batting at 4-6 in T20 typically face the most deliveries. Top-order anchors (1-3) face fewer but score more consistently.
The captain choice is a probability call
The captain is not the best player. The captain is the most predictable scorer in the conditions that favour their role. A 35-run anchor in good batting conditions often beats a 70-run boom-or-bust opener.
Read the captain selection guide for the full framework: Captain Selection Guide.
Workflow 4 — Post-match review
After every contest, the desk recommends a 5-minute review.
Where did your captain underperform?
Was the captain's role unclear, were conditions unfavourable, or was the match-up wrong? Identifying the cause sharpens next time.
Which differential pick paid off?
Differential picks (low-ownership players who outperform) are the highest-value learning signals. Note which role types paid off.
Did your team composition match the conditions?
If the pitch favoured spin and you picked three quicks, no amount of captain choice would have saved the team. Composition matters.
What would you change next time?
One concrete change is enough. Trying to fix everything at once is how rookies churn their strategy.
Workflow 5 — Withdrawal request
After KYC, withdrawals go to the bank account or UPI ID on file. Typical timelines are 24-72 hours.
Before requesting a withdrawal, confirm your KYC is on file (PAN + Aadhaar typically). Without KYC, withdrawals will be held. The Wallet & KYC page walks through the verification steps and common failure cases.
The team-creation screen — a closer look
Reading the team-creation screen is the single highest-impact skill for new fantasy-cricket players.
The credit budget
Most fantasy platforms give you 100 credits to build an 11-player team. Each player has a credit value reflecting their expected contribution. Premium players cost 10-11 credits; budget picks cost 7-8. The credit budget forces a real choice: pick all-stars and run out of budget depth, or build a balanced team with bench strength. The desk recommends balanced teams for most contests.
The composition rules
The composition rules require a defined number of batsmen, bowlers, all-rounders and wicket-keepers — typically 1-2 keepers, 3-5 batsmen, 1-3 all-rounders and 3-5 bowlers. The exact composition varies by platform. Always read the rules before picking the first player; rebuilding later costs time under the lock-in pressure.
Selecting the captain
The captain selector is the single largest decision in the team. Captain gets 2× and vice-captain 1.5× on most platforms. The selector typically sits at the top of the screen with a clear visual cue. Tap once to set as captain, twice for vice-captain. Reversing the choice after lock-in is not possible, so commit only after the rest of the team is finalised.
Time pressure — the lock-in countdown
The 15-minute countdown before toss is the most stressful window for new players.
The lock-in timer starts when the toss is announced. Most platforms give you 15 minutes to finalise your team after toss. Within those 15 minutes, the confirmed playing XIs replace the predicted XIs — your team is automatically updated if any selected player is not in the playing XI.
Common mistakes during the lock-in window: leaving players from the non-playing XI in the team, picking the wrong captain under time pressure, missing the deadline by seconds. The desk recommends completing your team at least 5 minutes before lock-in to avoid these failure modes.
If the auto-substitution logic changes the team materially (e.g. your captain is replaced), some platforms allow a quick re-selection within the lock-in window. Read your platform's substitution rules before the match.
Common beginner errors
Six mistakes the desk sees every week in new-player contests.
Pop-star captain picks
Picking the most famous player as captain regardless of conditions. Form matters, but role in the match matters more.
All-batting, no-bowling teams
Skipping bowlers to fit more batsmen in the credit budget. Bowlers earn wicket bonuses worth 25+ points per wicket — they are not optional.
Ignoring conditions
Selecting a spin-heavy attack for a green seamer, or vice versa. Conditions change the captain calculus significantly.
Skipping the practice contest
Joining paid contests before running at least one full practice contest. The UI friction is real and worth learning without a financial cost.
No post-match review
Joining the next contest without spending 5 minutes reviewing the previous one. The compounding learning is where the long-term edge comes from.
Budget over-commitment
Depositing more than the planned entertainment budget after a loss. Pause and reset the budget before the next deposit.
Next step: scoring reference
Every event your players earn points for — batting, bowling, fielding, captain multipliers, deductions, abandoned matches — is documented on the Points System page.
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.