The Game of Quiet Work: An Attempt to Measure Wicketkeeping in the Domestic Season

The Game of Quiet Work: An Attempt to Measure Wicketkeeping in the Domestic Season A Rajshahi afternoon, 38 degrees, the 47th over of a domestic match. The left-arm spinner released the ball; it landed and turned to the right. The wicketkeeper was standing up to the stumps. The ball was arriving low, no more than four inches off the ground. He dropped his right hand, the glove almost brushing the soil, and took it. The scorecard said: dot ball. My notebook said: ball 47.3, turn 3.2 degrees, keeper's distance from the stumps 0.9 metres, time for the ball to reach its lowest point 0.41 seconds, the back foot still inside the crease. That evening, in the comment thread of the Rajshahi xG Circle, a member named Rafiqul asked a question: what you measure, is it the catch, or the step before the catch? That question changed the direction of my charting. Because the scorecard will never record that four-inch-low ball of the 47th over. Cricket's public accounting loves outcomes. How many catches, how many stumpings, how many byes, how many runs. A wicketkeeper is therefore judged by the number of dismissals. And that number is so tidy that it leaves little room for questions. The trouble is that in domestic cricket half the keepers never get the chance. The keeper who has held six balls in five matches and the keeper who has held thirty both look identical to the scorecard. Football filled this gap with xG, PPDA, progressive carries. Cricket has almost no such defensive accounting. I covered the Wills Cup in Dhaka for Prothom Alo in 2026. That is when the habit took hold: sitting at the ground with a notebook. After I started the Rajshahi xG Circle in 2026, the habit came back to cricket, outside football. Over the last six seasons I have charted roughly four thousand balls of domestic cricket. For each ball I log the pitch position, the bounce height, the lateral deviation, the keeper's movement time, the distance, whether he was standing up to the stumps, and most importantly, whether the ball could have beaten the batsman. That last column is the real information for me. Before the table speaks, let the sample size breathe. Six catches in five matches cannot judge anyone's keeping. Four thousand balls across six seasons is a beginning; the rest is still running. I have divided my quiet work index into four columns. Byes, catch conversion, stumping speed, and effect on spinners. None works alone, but the four together produce an image. First column, byes. How many byes per thousand balls. Keeper A: 4.1. Keeper B: 6.8. At first sight an obvious gap. But when I calculated expected byes by ball type, how many overs left-arm spinners bowled into the rough, how many times the ball stopped low, how often reverse swing appeared in front of the newer keeper, the picture changed. After adjustment, A sits at 5.2 and B at 5.9. The gap has not vanished; it has shrunk. Much of what looked like a large difference between two keepers was really a measure of the pitch and the bowling attack. Second column is exactly where that matters. I band catches by difficulty. Band one: lateral distance under half a metre, more than half a second to reach. Easy catches, conversion 99 percent. Band two: one to one and a half metres, 0.4 to 0.5 seconds, conversion 91 percent. Band three: over one and a half metres, or under 0.4 seconds, conversion 44 percent. Now look at total catches. Keeper A: 26 catches, 22 of them band one. Keeper B: 19 catches, 8 of them band three. The scorecard puts A six catches ahead. Weighted expectation puts B roughly three catches ahead. Nobody prints the second number. Third column, stumping speed. From the ball passing the bat to the stumps being broken, measured in frames. In domestic cricket the median for a good keeper is 0.62 seconds, for an average one 0.79. On a turning pitch, 0.17 seconds is about a hand's width. That is the difference between a stumping and a bye. The fourth column is the messiest and the most interesting. The same spinner, the same season, middle overs, seven to fifteen: with the keeper standing up his economy is 6.1, standing back 7.4. Ten runs across eight overs. In cricket, ten runs often decides the match. But my biggest lesson here came from football, at the 2026 World Cup in Russia. France beat Croatia 4-2 in the final. I was live-posting France's pressing data to the group: PPDA 14.3, and N'Golo Kante covering 6.9 kilometres before being substituted in the 55th minute. Three hundred comments arrived; some said Kante was overrated, some called him the engine. I understood that raw numbers do not land without a human story. Since then I attach a what-fans-saw section to every measurement. The Kante question was never about one man; it was about how we measure quiet work. Wicketkeeping is another shape of the same question. Cricket's record book belongs to Kumar Sangakkara for the most ODI dismissals, 482, as logged on ESPNcricinfo. Mahendra Singh Dhoni's number is 444. These are enormous, yet all of them count events that happened. How many balls a keeper stopped that never became a catch, the record book does not write down. The eye test and the model must sit together, or neither can see the whole match. Now to the doubts. The first is easy: correlation is not causation. The keeper with fewer byes may never have faced two left-arm spinners on a rough pitch, or the surface may have been slow. Home and away change the measure. On a spin-friendly Dhaka wicket the nature of the keeper's work is different, because the ball passes the bat slowly but irregularly. The second doubt is deeper. Selection bias. The keeper who stays in the side looks good statistically, and because he looks good statistically he stays in the side. Breaking that loop is hard. I know a board will ask for my quiet work index before picking a youngster, and if it is five percent lower over twelve matches, his career might stop there. If an index becomes an instrument of decision rather than of inquiry, it stops being a measure and becomes a punishment. The third doubt is human. Last year a keeper returned from a finger injury. In his first two matches his stumping median was 0.85 seconds, far worse than his own normal 0.66. Some said he was finished. I say demanding proof in two matches from a keeper returning with a damaged finger is cruel, and cruelty here also raises the risk of new injury. When the stadiums emptied, the numbers confessed something we had ignored. In May 2026, when play returned, it became clear that when the environment changes, the measure changes. The same applies to keepers. No crowd means silent slip catchers, means a keeper alone. That silence appears in no statistic. Let me state my own position clearly. I believe a quiet work index is necessary, but it must never decide alone. The index should be a machine for asking questions, not for answering them. If selectors use it to open an interview, why did he take that ball with the right hand, what would the left hand have done, that is the correct use. Rajshahi taught me that a circle of analysts can be a sanctuary. The group I began in 2026 with 43 members now has many who keep their own notebooks. Last week a member, Shahriar, wrote: I now watch the keeper's feet during a match, not the ball. That change is my real result. I have seen a World Cup rewrite what we thought we knew. A domestic season does the same work slowly. That is its beauty. Keep an eye on three things next round. One, on the fourth afternoon, when the pitch begins to break, does the keeper stand up to the stumps. Two, which stumpings do not happen, that is, the ball passes, the keeper reaches, and fails to arrive. Three, which spinner trusts his keeper enough to toss the ball up, and who does not. I leave you a question, which will shape the next piece: of those three, which measure will change Bangladeshi domestic cricket most next season? Vote in the comments. The table comes later; first, let the sample size breathe.