The Notebook With Nothing Written in It Is Still a Record

Last night I opened a file at my desk. Eight columns, all eight blank. Beside every field, the same sentence: "insufficient information." No match type, no venue, no player names, no numbers, no date, no source. My first instinct was to fill the columns with imagination — because blank boxes itch the hand, and the mind starts building stories on its own. My second instinct was to close the file and go make tea.

I did neither. Instead I opened my notebook, wrote the date at the top, and beneath it wrote: "Input empty. That, too, is worth recording." A white page is never truly white. The ink of the previous page bleeds onto it; behind it lies the history of someone who wanted to write but couldn't. The blank fields in the file that reached me are not a description of any cricket match. They are themselves information. The question is what we do with that empty space. Some fill it with imagination. Some print imagination and call it reporting. I don't. I trust the notebook more than the noise.

1. A District League training session for Khulna Abahani. Twenty-two years old, a university student, an ordinary notebook and an old pen in hand. Forty-seven sessions, three hundred and twelve set-piece repetitions — all logged. I didn't know why. I only knew that writing it down would matter later. The coach would laugh and say, "What will all this scribbling do? The ball is right there on the field." He was right. But the field erases itself; the ink in the notebook stays.

The next year, 2026, the Russia World Cup. I was an economics student then, but my eyes were on cricket and football — the data of both. Sixty-four matches, one hundred and sixty-nine goals, thirty-two teams' pressing triggers — all watched through the lens of my degree. I built an enormous spreadsheet. I waited until the quarter-finals. Then I wrote a cautious thread on France's set-piece efficiency — four goals from dead balls. I refused to hype xG without watching the video. The result? Twelve hundred reads, and an internship offer from a local editor. That day I learned that slow writing has a reward; it just doesn't arrive quickly.

That habit later saved me. Because cricket is now soaked in data. Ball tracking, live feeds, pressing maps, fielding charts, recovery data — all streaming every moment, on the corner of the screen, on the phone, on the stadium board. But data and evidence are not the same thing. Data is raw material. Evidence is verified material — material with a tape, a date, a name behind it. That gap between the two is where my work lives. Standing there, I must make a decision every day: which number to print, and which to leave out.

My economics degree gave me a habit: keeping the ledger of cost and benefit on a separate page. In cricket this habit sounds strange, but it works. Because every selection is a cost — play one man and another is dropped; rest one man and another carries extra load. Nobody writes down that cost, but the account always exists, on a hidden page.

I follow one rule, made for myself, not for me by any institution. The rule: before any tactical claim, I need at least two hundred and seventy minutes of tape. In cricket, that means three matches. I call it the three-match evidence threshold. Some crown a hero on one night; some bury a villain in one over. I wait. Because the flash of an innings and the arc of a season are entirely different things. The flash is beautiful to watch; the arc is painful to watch, but it is true.

I write a player as a five-year curve. Workload in overs per season, injury intervals in days, selection gaps in months, and how small trust compounds — across these four columns. The story is not the spike, it is the trend line. Because anyone can write the spike; the trend takes patience.

The most concrete form of this verification discipline shows up in load accounting. I read every fixture list as a bill — how much is owed, and who will pay it. The fast bowler's knee, the spinner's shoulder, the keeper's finger, the middle order's back. One match means twenty-four deliveries for a fast bowler. Before that, yesterday's twenty. Before that, six hours of travel, before that the morning warm-up, before that the midnight ice bath. On paper it is only a number. In the body it is sleeping pills, an ice bucket, a phone call home at midnight, an absent birthday.

The biggest question in the schedule, for me, is never "who will win"; it is "who will pay, and how much."

Suppose a fast bowler plays six matches in a row, averaging eighteen overs a match — more than one hundred and eight overs in a week. On paper that is heroism. In the body it is a countdown. I write down that countdown, because nobody else does. I always ask about the recovery day first, and about tactics after. Who rested, who didn't, who hasn't rested for how long — I keep that account on a separate page. Because if a side plays the same fast bowler across four straight matches, that is not courage, it is borrowing against the account. And a loan must be repaid one day — suddenly, in injury, suddenly, in a form slump.

1. The COVID hiatus. I was an assistant training-ground observer for Bashundhara Kings, and I lived in the team hotel for sixty-three straight days. I logged eighty-four training sessions and documented twelve empty-stadium matches. Those days taught me that an empty gallery is never a story of loneliness — it is a story of budget. Ticket price, travel cost, board allocation, kickoff time — without these four, every sentence written about an empty stadium is just emotion. And emotion pays no bill.

In those hotel days I learned something I still carry: silence can be measured. How many sit in the dining hall, who is not speaking to whom, how many are queuing at the physio's room — these, too, are data. I began putting locker-room silence and travel fatigue into match reports. Two or three sensory details per eight hundred words — I have followed that rule ever since. It keeps the writing from going dry, and the players began to trust me.

My pipeline in Khulna runs on the same logic. There is no tracking camera here, no live feed, no vast data team. There is a coach, a maidan, a bus, and a notebook. In that notebook I record who bowled how many overs, who got how many rest days, who never got a rest, who spent how many hours on the bus. These numbers never become headlines. But five years later, when someone asks why a certain fast bowler stopped at nineteen, the answer is in that notebook — not in the headline.

The training ground is where the truth shows up before the scoreboard. The scoreboard states only the result. The ground states the reason. A man is scoring a century — meaning what? Perhaps he has changed the habit of a small defence over six months, something no one saw on TV. A man is getting out — meaning what? Perhaps his feet slowed two deliveries earlier, which the camera did not catch.

Qatar. The 2026 World Cup. I worked embedded near Morocco's training base. Twenty-three sessions, seven matches. Sofyan Amrabat's forty-eight tackles, Morocco's 4-1-4-1 low block — all logged. After the group stage I could have drifted on the media hype. I couldn't. I waited three matches, then wrote a four-thousand-word tactical breakdown. I spoke to two kitmen and a physio to verify the training intensity. Morocco reached the semi-final, conceding only five goals in seven games. The result? Two Asian coaches cited my piece.

Here a decision needs stating. I never call a tactic a "revolution" after one match. After one match I write only: "One match. Holding." The word "holding" appears many times in my notebook.

And here is my most uncomfortable observation. Cricket's data no longer lives only on the coach's tablet or the broadcaster's graphic. The live feed goes straight to the bookmakers. Ball-by-ball data, the probability of the next delivery, the batsman's shot map — all reaching the market within seconds. Meaning part of what I am verifying has already entered the betting machine. This is the darkest side of cricket's datafication. The spectator is watching the game, and some are making money off that game's data, often without the spectator knowing.

I am not willing to cross that line. So my notebook has no betting column, no "odds," no "prediction." I write only what happened on the field, and what happened off it as money goes on a separate page, with separate questions. Without drawing that boundary, the difference between analysis and gambling disappears.

But this datafication has a bill too, which no one wants to count. When a club or board sells live data, how much of that money returns to player recovery? How much goes to the physio, to sports science, to mental-health support? That account is in my notebook too — a separate page, in red ink. Because the more data grows, the more urgent the question: whose data is it, and who is paying its price.

Now to the uncomfortable truth no professional analyst wants to admit. The industry wants speed; I give slowness. Some pass a verdict within seconds; I write after three matches. So where I wait, someone else — even if wrong — publishes first. I do not call that failure; I call it the price. Truth has a bill, and even if it comes late, I am the one who must pay it. Sometimes it is worse — I waited three weeks, the third source never came, and the story went cold. This is my greatest fear: that the truth I am verifying too slowly is being printed wrongly by someone else.

Still, I found a solution. I do not wait, but I do not lie either. I write with a source label — "one ground source, unconfirmed." Then I update the record rather than stalling it. This is my compromise: publish while the story is warm, but never give false certainty.

But the bigger trap is treating empty data as failure. "Insufficient information" means, in our cultural habit, that the writer has lost. So people fill the blank boxes with imagination. They turn one match's performance into "form." They turn one session's discussion into a "tactical revolution." They turn one win into a "change of culture." And most dangerously, they turn an empty stadium into romantic melancholy.

Filling the blank box is not journalism; admitting the blank box is.

Because melancholy is easy to write, tracing a budget is hard. About an empty gallery one can write, "a lonely evening." But one cannot easily write, "the ticket price was this, the board allocated this, the travel cost this, and the match began at an hour when the workers could not get home." The second is hard, the first is easy, and so the first gets printed more.

I know my writing bores readers. Some want excitement; I give accounts. Some want heroes and villains; I give structure — schedule, funding, board decisions. But my experience says readers are not fools. Between 2026 and 2026 I tracked Bashundhara Kings' shift to 4-1-4-1 slowly — Daniel Colindres's fourteen goals, nine assists. That notebook was later trusted by many, because they knew I do not hurry. Trust compounds slowly, one notebook page at a time.

So today's blank file is not a failure to me. It is a signal. It says: I will publish nothing until it is verified. I will wait. The training ground is where the truth shows up before the scoreboard, and the notebook holds that truth. Every match has a pulse; my job is to keep the count. Today's count is zero, but zero is a number too, and I recorded that as well. The notebook traveled from Khulna to the World Cup; I just kept writing.

If you want to go deeper into cricket, the next time you see a number, stop and ask — who wrote it, when, and how much tape verified it. If you get no answer, then know this: the white page is the most honest answer of all.