Most fantasy cricket users improvise their matchday. They open the app an hour before the match, browse the contests, build a team on the fly, and lock whatever they ended up with. That habit produces teams that look fine and finish mid-table, because the work that should have happened during the day was crammed into the lock window. This piece walks through a repeatable matchday workflow that moves the thinking out of the lock window and into the morning, so the team that gets locked is the team that was already decided.
Morning: the fixture read
The first job of the day is to read the fixture. Three questions shape the read:
- Is the match worth playing? Not every match is worth a fantasy entry. Matches where team news is uncertain, where the venue history is unclear, or where the squads are likely to rotate should be skipped in favour of a practice room or the next day’s matches.
- What is the expected pitch behaviour? A pitch report is more useful than a team preview, because the pitch sets the match script. Flat pitches favour batters and death bowlers. Green pitches favour the new ball and middle-overs spinners. Dry pitches favour spin in the second half.
- What is the toss likely to do? Most captains have a preferred choice at the toss. Reading the captain’s recent toss history gives a starting point for the read, although the actual toss can always surprise.
The morning read does not need to be detailed. A short note on each match is enough to decide which one to focus on and which ones to skip.
Midday: the squad and role shortlist
Once the fixture is picked, the next job is to shortlist the squad. The squad shortlist is the list of players who are likely to be in the playing XI, separated by role:
- Batters who open, who bat in the top four, and who bat in the middle order.
- All-rounders, split into those who bowl in the powerplay and those who bowl at the death.
- Wicketkeepers, with notes on batting position and fielding role.
- Bowlers, split by phase: powerplay, middle overs and death.
The shortlist is the input to the team builder. The team builder should never produce a team that includes a player who is not on the shortlist, because off-shortlist picks are usually off-role picks.
Afternoon: the team build
The team build is where the credit budget gets spent. The Dream XI building piece walked through a sample build on a one-hundred-credit budget. The matchday version of that build follows three rules:
- The captain pick should already be decided before the team is built. Building the team around a captain pick is faster than building a team and then trying to fit a captain onto it.
- The reserve should not be empty. The reserve is what funds the late swaps that the toss news will sometimes force. A team with no reserve is a team that cannot react.
- The bench slot should cover the most likely toss-news swap. Picking a bench slot that is relevant to the alternative match script saves a credit value later.
A team built in the afternoon is rarely the team that locks. It is the starting point that the late swaps refine.
Lock window: the final read
The lock window is the hour or so before the match. Three things happen in this window:
- The toss lands. The toss is the single most useful piece of information in the matchday workflow, because it confirms the match script and the batting order.
- The XI is confirmed. The XI is the second most useful piece of information, because it removes the risk of a swap that would have lost the read.
- The lock timer ticks down. The lock timer is the budget the workflow has to make any final adjustments.
The lock window is not the time to rebuild the team. It is the time to apply the swaps that the morning read already anticipated. A useful rule is to allow no more than two swaps in the lock window, and to require that each swap maps to a pre-defined scenario from the morning read. Anything outside the pre-defined scenarios is left alone.
After the match: the review
The post-match review is the part of the workflow that most users skip, which is why most users do not improve. A short review notes four things:
- Which picks scored because of role clarity, and which picks scored because of a lucky over.
- Which picks failed because of role uncertainty, and which picks failed because of a tactical mistake.
- Whether the captain pick paid off the multiplier, and whether the vice-captain pick paid off the partial multiplier.
- Whether the room choice matched the team shape, and whether a different room would have produced a better result.
The review is short, usually five minutes, but it is the single most useful habit for long-term improvement. Skipping the review is the reason most users keep making the same mistakes across matchdays.
How this connects to the rest of the blog
The captain planner explains how to pick the multiplier. The Dream XI building piece explains how to spend the credit budget. The contest selection piece explains how to choose the room. The matchday workflow stitches those three pieces into a single day-long routine that the lock window only finishes.