Rauf's Third Offence: The Demerit-Point Ledger the Scorecard Won't Show You

Lahore's Gaddafi Stadium, Sunday evening, the 46th over of Pakistan's innings. Haris Rauf, who normally takes the new ball, is standing at the non-striker's end — meaning the hosts have pushed their frontline fast bowler into a batting role deep into the death overs. An appeal for a wide starts an argument. Within moments, that argument becomes a three-part sequence: verbal dissent, a raised bat after an umpire's warning, and then advancing past the umpire toward the opposing player. The scorecard does not connect this episode to any result. But what is recorded in my ball-by-ball ledger is a story that lives outside the scorecard.

This report is not about the match result, the score, or the pitch. It is an audit of a disciplinary record. And it should begin not with the single incident but with the account of the last twenty-four months that public cricket documents tend to leave in the margins.

Under Article 2.2 of the ICC Code of Conduct, Rauf has been fined 20 percent of his match fee and handed one demerit point. The sanction itself is low-level — Level 1, the minimum penalty. But that is not the real number. The real number is that this is Rauf's third disciplinary offence in the last 24 months, and his total demerit points now stand at five.

I have logged every ball by hand since 2026, and in 2026, hand-logging a Ranji season, I learned that the scorecard is a summary written by someone with an interest. The same applies here. The match report will say Rauf was fined. It will not say that this fine is the third entry in a pattern, and that the next entry could remove him from the field.

The ICC demerit-point framework operates on a rolling 24-month basis with defined suspension thresholds — commonly cited at four points for a one-match suspension and eight points for a longer ban. If Rauf's prior two offences produced roughly four points, he has already crossed the first suspension threshold at some earlier point, and the fifth point now moves him toward the eight-point second tier. There is a transparency gap here: the available report makes no mention of any prior suspension, so this is inference, and the exact threshold requires verification against ICC records. But an inference only holds if there is a count behind it. My count says Rauf is now on the edge where the next mistake costs not just his pocket but his availability.

The sequence of this incident matters. First verbal argument, then a raised bat despite the umpire's warning, then advancing past the umpire toward the opponent. This is not a momentary flash but a three-stage escalation. And this is where I disagree with the grading. A raised bat, by my ledger, is more than verbal dissent — it is an intimidatory act. Yet it was placed at Level 1, with 20 percent and one point. That leniency is debatable. If the Code of Conduct exists to protect the "spirit of cricket," a raised bat is not close to that spirit — it is away from it.

One more thing the match report left out. Rauf standing at the non-striker's end in the 46th over suggests Pakistan were taking the innings deep, and sending a senior fast bowler to bat in the death overs is itself a team-management signal. What relationship that had to the result, I will not say — because the score is not available, and without a score, claiming a disciplinary event affected the outcome would be exactly the kind of speculation I criticise.

Now the most uncomfortable angle. I have seen many reports on Pakistan's bowling in recent years, and almost every time the question is technical — swing, seam, line. But Rauf's case is not technical; it is about availability. If a player who is the team's primary wicket-taking weapon sits out because of discipline, the loss is not just his numbers but the entire bowling plan. That risk is not administrative; it is sporting. In my view, this is the least-discussed aspect of the whole story.

And England? England have been fined 15 percent of their match fee for a slow over rate. It is a separate incident, but the same day, the same ground. In limited-overs cricket, over-rate breaches have become almost routine, and they are a signal of team discipline. I will be careful here: I will not say there is a systemic looseness in England's approach. A sample of one match is one match. But when two different teams face two different disciplinary actions on the same day, that is more than coincidence — it is a signal of the environment in which the matches are being played.

Let me also be clear about what my dataset covers and what it does not. This analysis rests on two public disciplinary decisions, not on any personal observation. I was not at that match; I did not hand-log a single ball. So what I am saying is a count of documents, and what I am not saying is just as important.

The real question here is not whether the fine on Rauf was right or wrong. The real question is whether the Code of Conduct's points system is working the way it appears to. Five points in twenty-four months — that number is not written in one place publicly. It is scattered, one per decision. And until someone adds it up, it does not become a pattern; it remains just events.

The next time Rauf takes the ball, the scorecard will show his economy. It will not show how much margin he has left. And perhaps that is the number that should have been looked at first.