The Document of Empty Cells: What Cricket's Disciplinary Ledger Never Writes Down

Eight sections. Forty-one table rows. Six risk flags. And in every cell, the same sentence: "insufficient information — cannot be assessed." Reading it at my Manchester desk, my first thought was that the file had reached the wrong address. Fifteen years of digging through match officials' paperwork had left me used to full tables, the ones with averages, ratios, trends, and that comfortable false belief that a number is the same thing as control. Here the reverse happened. The document that was supposed to be analysed contained no name, no ground, no over, no date. The scaffolding stood upright with no body inside it. My first instinct was to fill the empty cells with my own guesses — the oldest habit in the trade. The second was professional, and it is the one I obeyed: publish the null record as a null record. Guessing into an empty cell is manufacturing a lie with a table wrapped around it, and that lie comes back later wearing quotation marks. Cricket's disciplinary record is not one book. It is at least four. The first is the match referee's report — code-of-conduct levels, fines, demerit points. The second is the slow over-rate calculation — who was how many overs behind, whose shoulder carried the workload. The third is the DRS log — ball tracking, ultra-edge, umpire's call. The fourth sits outside the ground — no-objection certificates, central contracts, anti-corruption monitoring. Of these, what reaches the public is mainly the outcome of the first and the raw numbers of the third. The rest stays inside the institution. In 2026 I built my first disciplinary database — 380 matches, 1,142 yellow cards, 34 reds, and every referee's own threshold. The purpose was singular. The 2026 database turned discipline from a whispered verdict into a public pattern. That work happened in football, but the method travels to cricket, and cricket needs it more, because the decision chain is longer. An lbw review involves the on-field umpire, the third umpire, the ball-tracking software, the rule that sets the margin, and finally the captain who burned the review. Five stages. The public sees the last one. Take a case from that same year. On 18 June 2026 at The Oval, Pakistan beat India by 180 runs, Fakhar Zaman making 114. The scorecard from that match is fully public — every ball, every stroke, every extra. Now ask for the complete list of code-of-conduct notes the match referees filed across that tournament, incident by incident, warning by warning. It does not exist in public. Same ground, same day, same cameras. One record is transparent; the other is not. The Lord's final of 2026 is cleaner still. On 14 July 2026, England and New Zealand tied, the Super Over tied, and England won on boundary countback. The decision was announced. The reasoning was never published — no document explained why a boundary should outweigh a six. Ben Stokes's 84 and the post-match words are all on the record; the logic behind the rule is not. That is the architecture of cricket's disciplinary culture: publish the outcome, withhold the cause. So let me propose a plain instrument, and call it the Record Completeness Index. Five fields, with the weights declared before any scoring: format identifier 20 per cent, named entities 20, declarative information points 25, reasoning or viewpoint 20, date and source 15. One hundred in total. I set those weights myself, and admitting that is part of the rule — an index without published weights is not analysis, it is opinion in disguise. The document that prompted this piece scores zero. Not one of the five fields carries a fact. But here is the interesting part: cricket's everyday documents are not far ahead. A standard ICC sanction notice names the player, names the format, gives the date — 20 plus 20 plus 15, so 55. Which over the offence occurred in, how many warnings the referee issued first, how long the deliberation took — those are the 25-point and 20-point fields, and both sit empty. A formal sanction notice is 55 per cent complete. I will say the number plainly: fifty-five. Is the gap between zero and fifty-five a difference of degree or of kind? I think it is of kind. The zero document is at least honest — it declares that it knows nothing. The fifty-five document is dangerous, because it speaks in a confident voice while nearly half its body is missing. A reader finishes the notice believing the process was seen in full. What was seen was the result. Map the four ledgers and the gaps line up. From the referee's report we get the level of the sanction, never the timeline. From the over-rate calculation we get the instruction to bring an extra fielder inside the circle, never the arithmetic — which clock, which threshold, which prior warning. From the DRS log we get ball tracking, never the document that sets the software's margin or the person who verifies it. DRS is the most instructive exception. When the review system arrived in 2026, the argument for the first few years was about the machine — would the ball have hit leg stump, is the margin sound. Once the raw data became public, the argument moved. The question is no longer whether the technology is right; it is whether the captain reviewed well, how many reviews he wasted. The dispute migrated from reality to resource. That is progress, because resource arguments settle in numbers while reality arguments settle in trust. One corner stays dark. Umpire's call — the rule under which the on-field decision stands when less than half the ball is projected to strike the stumps — is shown as a result and never explained as a reason. The crowd sees the words on the screen and does not see why. That single phrase generates more argument in a season than the boundary-countback rule ever did. On 19 November 2026 in Ahmedabad, Australia beat India, Travis Head making 137. The match is fully documented. How the decision was taken to play the final on a used pitch is not. On 13 November 2026 in Melbourne, England beat Pakistan, Sam Curran the player of the tournament. Also documented. In neither tournament is there a published performance assessment of the match officials. Nowhere. A cross-domain comparison is available, and I will state its limits first. Football's disciplinary flow is continuous; cricket's decisions are discrete events, ball by ball, over by over. The review economics differ. Still, one thing transfers directly. In January 2026 Chelsea signed Enzo Fernández for £106.8m on an 8.5-year contract, and the amortisation arithmetic opened a gap in the rules. The transfer market has its own red cards, and most are never shown on television. Cricket's loan-with-obligation structures and franchise contracts carry the same defect — a smaller board spends years finishing half-built players for a bigger one, and the paperwork never surfaces. I once sat in the scorers' box at Old Trafford. A scorer was writing in pencil, every ball, every movement. Nobody reads that hand. At the close the book is put away. Yet that book held the most complete record in the building. That is cricket's disciplinary problem exactly: we keep plenty of ledgers, and we keep them closed. My position on transparency is simple, which is not the same as blind. More disclosure is not automatically better. First, once the DRS log went fully public, a new ailment appeared — technology theatre. The crowd now audits the machine and not the man. That umpire's training hours, his consecutive matches, his travel load appear in no table. Blame lands on the individual and never on the environment. Discipline is not a mood. It is a structure with timestamps — but if the structure is never shown, only the person is visible. Second, a null record is not always a failure. Sometimes it is a firewall: an anti-corruption inquiry, a player's medical file, mental welfare. Boards have legitimate reasons to withhold. The offence is not the withholding; it is withholding without publishing the list of what has been withheld. "We are not releasing this" and silence are not the same sentence. And I will name my own trap. Build an index and you can turn anything into a number. If I score decision consistency on weights of my own choosing, I have dressed a human judgement in arithmetic. Every index therefore needs a declaration attached: which fields still take human opinion as input, and which take measured counts. Empty stadiums in 2026 did not remove pressure; they moved it into the protocol. A transparency gap does the same — it does not remove accountability, it relocates it somewhere unwatched. My proposal is small and testable. Let every sanction notice carry a mandatory Record Completeness Declaration at the foot — five fields, pass or fail beside each. No additional secret is exposed; the reader simply learns which cell is blank. And when the first fully audited disciplinary year closes, cricket will have to answer one question: were those documents empty all along, or did somebody leave them that way?