The Two Diaries of Cricket: How One Match Gets Written Twice, From Mymensingh to Dhaka

The first session was eleven overs long, and the daylight had not fully arrived. I sat at a domestic ground in Dhaka with a scorebook on my left and an open notebook on my right. In the same over I wrote two different realities. The scorebook recorded: 4 0 1 0 W 0. The notebook recorded: 'After the fourth ball, a direct instruction from the fielding coach at slip, short leg raised both hands in signal, the striker did not move his foot an inch.' Who would believe these were two accounts of the same delivery? Same ball, same moment, same twenty-two yards. Mymensingh taught me that every match writes two diaries. One diary is public, written in numbers, in the language of the scorecard. The other diary is private, written in rhythm, in the language of sound and skill. The first is for everyone. The second is only for the person who sits at the ground and learns to watch. This piece is an attempt to read both diaries together. A single article cannot force two narratives into one, but the gap between them sometimes tells the real story of the match. In 2026, during the Russia World Cup, I was seventeen. From a room in Mymensingh I watched all 64 matches, 169 goals, 1,024 shots, and built an expected goals model in Excel. Forty hours of re-watching set pieces, cross-checking every goal against FIFA's official match reports. My prediction that France would beat Croatia 4-2, derived from set-piece efficiency, came true. That 5,000-word data diary on a Facebook page called 'Mymensingh Football Lab' was shared 2,300 times. The interesting thing is that the numbers were probably read 2,300 times, but nobody read the real story of those forty hours, because it was never written down. In cricket, the difference between the two diaries is even sharper. In football, ninety minutes create a continuous narrative through possession, passes, xG, pressing triggers. In cricket, every ball is a separate event. Balls are not divided into hours, overs, or sessions. Before every ball the bowler starts his run-up, the batter takes his stance, and then an eight-foot sequence can change the course of an entire match in 0.5 seconds. In this irregular rhythm, writing two diaries is almost impossible: the scorecard paints an average picture, the notebook freezes on a moment. This is where my first interest took root, on domestic cricket grounds between Mymensingh and Dhaka. Before writing, I give several hours to the environment of the writing. In 2026, when the whole world shut down, I somehow got the job of remote data analyst for the Mymensingh District football team, and perhaps I will write about that another day. But that same year the Bangladesh Premier League returned to empty galleries, and I sat at the Bangabandhu National Stadium to watch Sheikh Russel KC versus Abahani Limited Dhaka. The scorebook recorded: 0 spectators, 18 fouls, Abahani's 1-0 win, a 78th-minute penalty goal by Nabib Newaj Jibon. The notebook recorded the echo of the stadium, the sound of kicks leaving the corridor, the goalkeeper's shout that was perfectly audible despite zero spectators in the gallery. That 2,000-word report was picked up by a Dhaka sports blog. The silent stadium taught me to hear the game. But silence in cricket is harder than in football, because the entire structure of cricket rests on sound. Stumps, pads, the bat's edge, the chatter of the slip cordon, the wicketkeeper's gloves, these are all small sounds, drowned out by the roar of the crowd. In 2026, while interning at a Dhaka sports outlet, I covered Euro 2026 remotely, Italy's 4-3-3, Mancini's pressing, 13 goals scored and 4 conceded. At the same time, I compiled a minute-by-minute timeline of Christian Eriksen's collapse in the Denmark-Finland match, thirteen minutes of medical response. At the Tokyo Olympics I compared emergency protocols. Several Bangladeshi coaches cited my 3,000-word tactical autopsy, and that remains a turning point in my work. Since then a 'crisis protocol' subsection has entered my tactical previews. In cricket this is even more necessary, because emergencies cannot be engineered into the game. Writing tactical analysis without verifying underlying information is impossible, especially in a club-based franchise league. After joining Bashundhara Kings as team travelling writer in 2026, that instinct deepened. In that summer's transfer window I first broke the loan move of Brazilian winger Robinho from Sheikh Russel KC. I travelled with the team to eleven away matches, including the AFC Cup group stage. The picture of the dressing room after the 2-1 win over Mohun Bagan is still vivid. At the season's end Bashundhara Kings won the 2026-24 Bangladesh Premier League. Yet the strange thing is that immediately after the league win, the most-read item was not a picture of the trophy but a small note from a physio: 'After the fielder's injury, he took four minutes twelve seconds longer than the coach's protocol to return to the dressing room, seventy seconds above normal.' That single line circulated widely, because it said something hard that the scorecard cannot say. Evidence first, conclusion after. That is the mould of all my writing. Bangladeshi domestic cricket still relies primarily on scorecard-driven analysis. There is no fault in that, because in a fifty-over match, the story of 300 balls is told most honestly by the scorecard. But the problem is that the scorecard does not know why a batter is playing slowly across forty balls. Perhaps he is playing through injury, perhaps his shot selection has shifted on a slow pitch, perhaps the opposition leg-spinner has laid a single trap customised for him. This gap is my notebook's territory. In India-Bangladesh series, the difference between the two diaries is most visible. Here the cricket structures of the two countries are different, and the structure of my writing must accept that difference. Sometimes, writing about the rationing of Bangladesh's spinners, I have had to speak with India's batting coach. Sometimes, writing about India's top-order rotation, I have had to discuss with domestic coaches in Dhaka. From outside it looks like one match, but inside it is a clash of two structures. That clash is the centre of my cricket writing. Mymensingh taught me a lesson that still applies: in cricket it is not the play but the interval of play that matters. There is some advantage in entering the ground half an hour before the match. The pitch roller is giving its final pass, two coaches stand on the sidelines giving last instructions, the wicketkeeper is slowly putting on his gloves. The information available in that half hour is nowhere written in the first over of the scorecard. From that 5,000-word data diary in 2026 to today, my method remains the same: begin with a table, then a question, then an answer. Applying this to cricket is harder than football, because in cricket the reporting of data is ball-by-ball. If someone scores 120 in twenty overs, that is success, but why two slow overs occurred in the middle is recorded by no points table. That gap is what I want to write. Yet writing two diaries carries a real cost. Keeping the scorebook and the notebook open together means splitting the mind in two places. Sometimes five deliveries out of six are lost, because the eye was on the feet of the fielder at slip. I am not alone in this mistake. This is the true value of journalism, losing the rest in exchange for focusing on one specific place. But the beauty of the two diaries is here: reading one without the other means seeing the match in half. Since that 2026 internship I have kept a separate subsection called 'crisis protocol'. In cricket this means: what happens if a match is abandoned, who is responsible if there is an injury, what the match referee does if an over takes too long. Nobody asks these questions, because in cricket emergencies are not part of entertainment. Nobody buys a ticket to see an ambulance. But this absence is the most truthful thing. The habit of hearing the game in a silent stadium is at the centre of this writing. In cricket this habit is even more necessary, because cricket's sound is more calculated. In a zero-spectator gallery, before the bat's edge reaches the hand of the fielder at slip, you can hear the wicketkeeper's glove shift slightly. That is written in no scorebook, but it can change the course of the match. The matter is clearer in cricket's setting. Cricket's structure is sound-dependent: the clatter of stumps, the bat's edge, the quick conversation between two umpires on an out decision, all small sounds, lost in the roar of thirty thousand spectators. In a silent stadium these small sounds become audible again, but their meaning is not the same as before. Then every sound becomes information, evidence. This is where the lesson of the silent stadium does not end, but begins. Over a long period I follow one player, one ground, one season. In cricket this kind of following is harder, because a cricket season is much longer than a football season, and a player's real progress can only be measured across many sessions. This long-view habit teaches me who is changing what, and why it is not showing up on the scorecard. A one-inch change in batting stance might add twenty runs over a season, a new taping by the physio might enable two more sessions of batting. None of this appears in a match report, but at the end of a season it is the real story. Still, I want to give myself one warning against my own work. There is a trap in a sky-high notebook culture. Often an analyst thinks more comments mean more depth. In cricket this is worse, because a comment can be added to every ball, but 300 comments in a 300-ball match means a zero conclusion. My rule: one central thread per match, the rest stored as tracking information. The second trap is scorecard tunnel vision. Only numbers means only pages. In cricket this risk is large. A 115 km/h yorker might be survivable, but the scorecard will not show it as a goal. So I keep one observation with every key statistic. This is not only for feeling, but for the precision of information. The silent stadium has its own trap. Emotional writing about silence is easy, but verifying how silent the silence actually was is hard. In cricket the trap of silence is subtler: a batter's breathing, the sound of the bat tapping the pitch while taking guard, these subtle sounds are the real information. This writing risks becoming lyrical, but in cricket lyrical writing means merely ringing a bell to tell a story. The last and biggest trap is my own identity. India-born, Bangladesh-based, with an ISTJ's discipline, these three things together can make the writing more cautious than necessary. In Bangladeshi cricket, as much as I write, a part of it is in another language, another rhythm. But without naming the actual structures of cricket, the writing weakens. So I try to name specific sessions, specific coaches, specific reforms. A regular problem in the Bangladesh Premier League is that the fitness tracking of fielders coming off the bench is weaker than that of the registered squad. Since my time at Islamic University I have kept a habit: after every session I write three things, how many minutes each fielder was on the ground, which foot seems to have taken more load, and after which delivery he returned to the crease fastest. This information is not in the scorecard, but in a transfer window this information is a club's biggest asset. It goes without saying that this method began in Mymensingh. There, cricket and football, the two characters of two games, are visible. In football the game flows across ninety minutes, in cricket the game takes 300 separate breaths. Between these two games my two streams of writing have formed, and both stand on the same foundation: numbers and silence. When a match ends, what remains is a scorecard. But when a match ends, much is lost. In a blockchain era, what we read is written, but what is not only ink, not only numbers, is perhaps never archived anywhere. My work is to fill that gap. No deception in any report, only connection in any result. Next season the link between the Bangladesh Premier League and India's domestic cricket will grow, especially due to franchise transfers. Who benefits from this link will be answered by a single measure: when the scorecard and the notebook come together, what emerges is the truth. The rest is the audience, the rest is the story.