The Dew Factor: A Variable at Dusk, Not a Ghost of Fortune

On an April evening, at a domestic T20 league match, I sat beside the scoreboard sketching columns into a small notebook. The home side made 162 in the first innings; after the break they took the ball. In the last five overs the visitors added 68 without losing a wicket. The commentary offered one explanation: "The dew has come down, the ball isn't gripping." But the next column in my notebook said something else: in those five overs the visitors' strike rate was 172, while the season-long average for a first-innings last-five-over strike rate at that ground was only 141. The real question is harder: if dew truly is such a large variable, why do we not measure it before the match, and instead drag it out as an explanation after a defeat?

That night I decided that for every evening match I would write three numbers beside the score — dew point, relative humidity, temperature. Because I learned long ago: the variable you do not measure becomes the most opportunistic explanation of all.

The pile of statistics built around toss decisions in T20 cricket is largely dew-centric. The Indian subcontinent, certain Australian venues, outfields in the West Indies — where the evening air is hot and humid, taking the ball in the second innings means, quite literally, bowling with a wet ball. The 2026 ICC T20 World Cup was staged in the United States and the West Indies, and at several of its evening venues dew sat at the centre of discussion throughout the tournament. But discussion and measurement are not the same thing.

How dew works is simple physics. When air temperature falls close to the dew point, moisture above the grass and outfield condenses and begins to settle. A ball landing on that wet surface gathers a film of water on its seam and cover. The seamer loses grip, the spinner's fingers lose control of the ball, and the ball skids on, reaching the bat more easily.

Here is my first caveat. From years of watching matches I have understood that a spectator remembers dew only when the result can be explained by it. Chase 160 and win, and dew was there; chase 160 and lose, and it was "second-innings pressure." That is memory bias. I built the Sylhet xG Desk for football because memory is a biased scout; in cricket the rule is exactly the same.

One more thing is worth holding on to. In the empty stadium I learned that atmosphere is a variable, not a ghost. When in 2026 I published home-advantage data drawn from fifty behind-closed-doors matches, the lesson was singular — before talking about weather or environment, give it an operational definition. The same applies to dew: not "there was dew," but "at half past six in the evening the dew point was 23 degrees Celsius and relative humidity was 84 percent."

League scheduling is a variable too. Most evening matches start at half past seven; the death overs of the second innings fall after ten at night, when the temperature is at its lowest. Dew's influence therefore grows with time; it does not stay fixed. In some competitions the fielding side may request a ball change — the rule itself concedes that dew is real. But having a rule and having a measure of the effect are not the same thing.

Now the real part of my notebook. Over the past three seasons I have logged 114 evening T20 matches — domestic league, franchise tournament and international combined. For each match I recorded the venue, the date, the toss winner's decision, the last-five-over run rate of both innings, the spinners' economy across both innings, and the dew point and relative humidity at the time.

Let me keep the method plain. For each venue I maintain a rolling baseline — the average last-five-over run rate of the previous twenty evening matches. I then set today's match against that baseline. Where a venue-specific baseline is missing for a single match, I do not wobble; as with the empty-stadium protocol, I apply no correction clause without two independent sources agreeing.

What emerged falls into three parts.

First, in the matches where the gap between dew point and temperature dropped below 3 degrees Celsius, the second innings' last-five-over run rate was on average 19 percent higher than the first innings'. Where the gap exceeded 6 degrees, that difference was only 4 percent.

Second, the effect on spinners is sharper. In high-humidity matches, the spinners' economy in the second innings rose by an average of 1.3 runs against the first; in low-humidity matches that rise was only 0.4 runs.

Third — and this matters most — the gap between the two innings cannot be explained by dew alone. At the same venue in a day match, where dew is nearly absent, the second-innings run rate still climbs; the pitch dries and batting becomes easier, and the chasing side knows precisely what it needs. Dew is a variable — probably a large one — but it is not the only one.

Here my template gained a "sterile dew" flag. When a favourite wins the toss and fields, I write it down in advance: if the first-innings score is 15 runs below the league average, and the dew point sits within 4 degrees of the temperature, then I calculate the second innings' last five overs on 20 percent more runs. The ledger does not care about your loyalties; it only asks for the sample. And 114 matches are no great sample — I concede that from the outset.

Now the section where I challenge my own story.

The relationship I see between dew and the second-innings rise in scoring may be a correlation, not a cause. The reason is plain: the decision to field after winning the toss is not random. The side with greater batting depth, the side with the better chasing record, is usually the side that chooses to field. Part of the higher second-innings scoring therefore comes from the team's quality, not from dew. That selection bias hides inside my log.

There is only one way out — a natural experiment. For instance, a day match and an evening match at the same venue two days apart; or matches where the toss winner was forced to bat first. When I isolated only those 23 "forced" matches, dew's effect fell from 19 percent to 11 percent. Dew is genuinely there, then, but it is roughly half of what we claim.

The second gap lies in post-match explanation. When a bowler concedes fours with a wet ball we say "dew." But when the same bowler misses his yorker in the first innings' death overs we say "execution." The two are really two names for one event — and the name depends on the result. That is memory's greatest deception: we choose the cause after we know the outcome.

There is another trap here. In international tournaments the dew story swells, because venues change quickly and the sample is small. A conclusion drawn from two or three matches of a World Cup is not in fact set against that venue's twenty-match baseline. Tournament folklore and venue data must be kept apart.

So what should you watch in the next round? Not the bottom of the scoreboard — the weather app. Before the match, note the gap between dew point and temperature; if the gap drops below 3 degrees, allow a little more for second-innings death-over runs and a slightly worse spinner economy. If the gap is wide, forget the dew story.

And above all — the price the market puts on dew, and the measurement my notebook gives, the gap between those two is the real information. The day I stopped betting on teams and started betting on the gap, I stopped betting on teams. Dew is no ghost; dew is a column whose value is known in advance.