How our daily fantasy predictions shortlist is built, updated and audited.

A note on how this desk note is built

Why this note exists

The fantasy cricket reading audience has grown faster than the editorial coverage that serves it. New readers arrive through search, through referrals from older readers, and through the platform’s own marketing, and they reach a predictions chapter that promises a captain pick, a vice-captain pick, three differentials and one contrarian for every match day. The promise is real, but the method behind it is rarely visible. This desk note is the method, written in the same register as the shortlists themselves.

The reason to publish the method is simple: a reader who understands the inputs can audit the calls, can disagree with the reasoning when the evidence pulls the other way, and can decide which calls to follow into a paid contest. A reader who does not see the method has to take the shortlist on faith, and the desk has no interest in asking for that. Faith is a bad input for a captaincy call.

This note is written for the parent who plays one head-to-head each week, the returning reader who runs two or three shortlists in parallel, and the new reader who has never built a team and wants to see the working before they start. None of them should have to take the desk’s calls on trust. The method, the inputs, and the audit are all in public. The rest of this note is a tour.

The morning routine, in order

The desk opens roughly three hours before the toss, because three hours is the smallest window in which the captain pick, the vice-captain pick, the three differentials and the contrarian can all be written, cross-checked against the squad announcement and the pitch note, and laid out as a published shortlist. The window is short on a double-header day and longer on a single-fixture day, but the order of operations does not change.

The first job is the squad read. The published eleven is the only signal that cannot be substituted, because the salary cap is set against the published eleven, not against rumoured line-ups. The desk does not publish a captain pick until the squad is final. If a squad is delayed past the team lock, the shortlist is shelved rather than guessed. Guessing a captain is the single most common cause of a bad shortlist, and the desk treats it as a release-blocker.

The second job is the venue read. The venue decides which roles are scarce, which roles are common, and which split between batters, allrounders and bowlers fits the surface. A high-scoring venue rewards batters and death-overs pace; a slow-turning venue rewards spinners and anchors. The venue read is a thirty-second look at the last five matches at the ground, plus the pitch note if the broadcaster has published one. The read is short, but it is decisive. A captaincy call made without a venue read is a coin flip.

The third job is the weather read. Dew, crosswind, and the chance of a shortened innings all shape the captain call. A wet outfield usually tilts the surface towards the side batting second. A crosswind tilts the bowling plan away from the short-ball barrage. The weather read is not always decisive, but it is the difference between a captain pick that survives the toss and one that does not.

The fourth job is the form read. The form read is the cumulative points scored over the last six completed matches, filtered by role and venue. A batter averaging fifty on a slow surface is a stronger captaincy case at a slow-turning venue than on a flat-batting one. The filter matters more than the raw average. The desk applies the same filter to the differentials, because a differential is only a differential if its form is recent.

The fifth job is the public shortlist read. The public shortlist is the list published by the most-followed fantasy writers, by the platform’s own recommendation engine, and by the consensus among the largest paid contests. The desk does not copy the public shortlist; it reads it for two reasons. First, to know what the captaincy pool is, so the differentials are genuinely below fifteen per cent selection. Second, to know which way the public is leaning, so the contrarian is genuinely against the grain rather than against a strawman.

The morning routine closes with a draft shortlist, a draft captain case, a draft vice-captain case, three draft differentials, and one draft contrarian. The draft sits in the editor’s notebook for roughly thirty minutes. The pause is intentional. A captaincy call made in haste is a captaincy call made under the influence of the most recent match, not the most relevant match. The pause is the desk’s cheapest input.

The five inputs that decide the captain pick

The captain pick is the single most important call on the shortlist, because it carries the largest points multiplier and sets the floor for the rest of the XI. The desk applies five inputs in order. Each input can rule out a player as a captain even when the player is a strong vice-captain case.

Input one is role scarcity. If the role is scarce on the squad sheet, the captaincy case is stronger, because the player is more likely to face the right number of overs and the right match-ups. A leg-spinner in a spin-trap squad is a scarce role. A middle-order batter in a four-batter squad is not. The scarcity input is the first filter, because it is the one most often missed by readers who copy the public shortlist.

Input two is venue fit. The captain should be a player whose role the venue rewards. A top-order batter on a slow surface is a weak captain case, even if the batter is in form, because the surface will compress the strike rate and the points. A death-overs bowler on a high-scoring venue is a stronger captain case than the same bowler on a low-scoring venue, because the wickets and the dot balls are worth more points at the death. The venue fit input is the second filter.

Input three is recent form, weighted by venue and role. A batter averaging fifty on slow surfaces over the last six matches is a stronger captain case at a slow-turning venue than the same batter averaging fifty on flat surfaces. The filter is a five-line spreadsheet, not a model. The desk does not publish the model, because the model is not the product. The product is the captaincy call.

Input four is the match-up. The captain should be a player whose match-up against the opposition is favourable. A right-arm pace bowler against a left-handed top order is a strong match-up. A leg-spinner against a right-handed middle order that reads leg-spin well is a weak match-up. The match-up input is the fourth filter, and the one most often missed by readers who rely on points averages alone.

Input five is the salary cost. A captain pick that costs eleven credits forces a trade-off in the XI. A captain pick that costs nine credits leaves room for a stronger differential. The salary cost input is the fifth filter, but it is the one that decides whether the captaincy call survives the cap. The desk never picks a captain that breaks the cap, even if the captaincy case is the strongest of the season.

The five inputs are applied in order. A player who fails any one of them is removed from the captaincy shortlist. A player who passes all five is the captain pick. The vice-captain pick is the next-strongest case, with the floor weighted above the ceiling. The three differentials are players who pass the form and match-up filters but fail the public-shortlist filter; that is, they are below fifteen per cent selection in the largest paid contests. The contrarian is one player who passes the form and match-up filters but is the strongest opposite of the public shortlist, weighted by ceiling rather than floor.

How the case is written

The case for each pick is written in four sentences. The four sentences are the case for, the case against, the role filter, and the salary cost. Each sentence is a single clause. Each clause is auditable. The desk does not write a fifth sentence, because a fifth sentence is the sentence where filler lives.

The case for is the strongest piece of evidence supporting the pick. The evidence is named. The case for a captain pick might be the venue average; the case for a differential might be the match-up against the opposition’s weak link. The case for is the sentence the desk will defend in the audit the next morning, so it has to be specific. A vague case for is a case for that cannot be audited, and the desk does not publish calls that cannot be audited.

The case against is the strongest piece of evidence against the pick. A captaincy call without a case against is a captaincy call made under confirmation bias. The case against is the reason the pick could miss, and the reason a reader might skip it. Publishing the case against is not the same as hedging; it is the desk telling the reader what would change the call.

The role filter is the role scarcity input translated into a single clause. The clause names the role, the count of players in that role on the squad sheet, and the reason the role is scarce or common. The clause is short. A reader who needs more detail can read the squad analysis for the franchise; the shortlist is the call, not the dossier.

The salary cost is the credit cost of the pick, the credits left in the cap after the pick, and the next upgrade the credits left can buy. The desk does not promise the reader will follow the same trade. The desk publishes the trade so the reader can decide whether the captaincy call is worth the cap pressure it creates.

The four sentences are written into the shortlist page as soon as the squad is final. The desk does not edit the shortlist after the team lock, because the editor cannot see the actual XI after the lock and therefore cannot re-write the case without new evidence. A shortlist published at the lock is the same shortlist the reader sees the next morning. The audit is the only place the desk writes a different version.

The audit, the morning after

The audit is published on the shortlist page the morning after the match, before the next squad announcement. The audit is a five-line note: the pick, the actual points, the expected points, the delta, and the reason. The reason is the single most important line. The reason is what the desk would change if the match were played again with the same squad and the same surface.

The expected points are the median of the points scored by the player in the role and the venue over the last six matches, not the points the desk hopes for. A pick that lands at the expected points is a neutral result, not a win. A pick that beats the expected points is a win. A pick that misses the expected points is a loss. The desk tracks the win/loss ratio at the season end, and publishes the running number in the chapter’s footer.

The audit is not an apology column. The desk does not write the audit to explain why the captain pick missed; the desk writes the audit to log the evidence. The evidence is what the desk will use the next time a similar captaincy case appears. A captaincy call that misses on a slow surface at Chepauk is a captaincy call that informs the next captaincy call at Chepauk. The audit is the input to the next call.

The audit also records the misses. A captaincy call that lands at the expected points is not a miss. A captaincy call that beats the expected points is not necessarily a hit; the desk reads the call against the public shortlist, not against the player’s median. A differential that lands at sixty points when the public differential at the same role lands at eighty is a miss for the differential call, even though the player did not score zero. The audit tracks the call, not the player.

The desk publishes the running audit at the end of every month. The running audit is the count of calls, the win/loss split, the median delta, and the largest miss of the month. The running audit is the most honest number on the chapter, and the one the desk would point a sceptical reader to first.

Where the method stops

The method above is built for the kind of match day where the squad is final, the venue is known, the weather is forecast, the form is recent, and the public shortlist is published. Most match days are like that. A few are not, and the desk treats those cases as limits to the method.

The first limit is the late squad. If a franchise announces the XI past the team lock, the shortlist is shelved. The desk does not publish a captaincy call against a squad that has not been seen, because the cap math and the role math are not knowable. A shelved shortlist is logged on the chapter the next morning, with the reason. The desk does not pretend a shelved shortlist is a missed shortlist; it is the method being honest about a match day it cannot call.

The second limit is the rain-affected match. If the match is shortened, the points matrix changes, the captain multiplier changes, and the role scarcity shifts. The desk does not publish a captaincy call for a rain-affected match after the rain arrives; the published shortlist stands, but the audit notes the rain. The reader who followed the shortlist into a rain-affected match should know whether the miss was the call or the weather.

The third limit is the injury-time call. If a player named in the shortlist is ruled out at the toss, the shortlist is republished with the replacement named and the case re-written. The republished case is shorter, because the desk has ten minutes between the toss and the team lock, not the three hours of the morning routine. The republished case is audited the same way as the original. The republished case is logged separately so the season-end numbers are not distorted by injury-time rewrites.

The fourth limit is the platform change. If a platform changes the points matrix, the salary cap, or the contest format between the morning routine and the team lock, the desk does not publish a shortlist for that match. The desk publishes a short note on the change, links to the platform’s own announcement, and resumes the shortlist the next match. The desk does not try to call a match whose rules it has not read.

The fifth limit is the data outage. If the desk’s data feed is down at the morning routine, the desk publishes a captaincy call only on the evidence that survived the outage. A captaincy call made on partial evidence is logged as a partial call. The desk does not pretend the call is full when the data is partial. A reader who follows a partial call is told the call is partial.

What readers can do with the chapter

The chapter is built for readers who want to make their own call and want the desk’s call as one input, not as a verdict. The first thing a reader can do is read the morning routine above and run it themselves before the desk publishes. If the reader’s captain pick matches the desk’s captain pick, the desk’s call is the reader’s confirmation. If the two picks diverge, the divergence is the start of the reader’s own case, not the end of the desk’s authority.

The second thing a reader can do is use the four-sentence case as a template for the reader’s own shortlist. The template is public. The reader can copy the four-sentence structure into a notebook and run it for every match day. The reader does not need to follow the desk’s picks. The reader can use the desk’s picks as the public shortlist against which the reader writes their own contrarian.

The third thing a reader can do is read the running audit at the end of the month and decide whether the desk’s win rate justifies the reader’s subscription or the reader’s follow. The running audit is the most honest number on the chapter. A reader who disagrees with the running audit is free to unsubscribe, to unfollow, or to write their own chapter. The desk does not argue with readers who leave on the basis of the audit. The audit is the answer.

The fourth thing a reader can do is send the desk a counter-case. The desk reads every counter-case that arrives by email or in the comment thread. The counter-case that names a piece of evidence the desk missed is logged on the next shortlist. The counter-case that does not name new evidence is logged in the desk’s own notebook, but not in public. The desk does not publish counter-cases it cannot verify.

The fifth thing a reader can do is use the chapter as the input to a longer read. The wagon-wheel method, the salary-cap math, the captain-vs-vice-captain math, and the rest of the long-form coverage all use the shortlist as the empirical record. The long-form pieces are the place where the desk writes the case in full; the shortlist is the place where the desk writes the call. The two serve different readers and should not be confused.

What we are watching next

The next squad announcement, the next venue change, the next injury update, the next platform-side amendment. Each item is added to the chapter within an hour of the announcement, and the shortlist is republished before the next match. The chapter’s changelog is in the footer, and the changelog records every substantive change. The chapter’s last-refresh date is on the same page. Readers who want a stricter update cadence can subscribe to the chapter’s RSS feed at /feed.xml; the feed is updated the moment a new shortlist is published.

The desk’s working target for the next month is to publish the morning routine as a downloadable checklist, so a reader can run it without a notebook. The checklist will be on the predictions chapter, with the same five inputs and the same four-sentence case, formatted for a single A4 page. The release date will be logged on the chapter the moment the checklist is live.