An Audit of One Demerit Point: Two Sanctions in Ranchi and the ICC's Ledger

In Ranchi, two large numbers held everyone's attention that evening — 250, and then 224 in Indore. Cricket talk keeps the big numbers. My notebook that day carried three small ones: six, thirteen, one.

The sixth over. The last stretch of the powerplay. Rovman Powell out, dismissed by Mayank Yadav. On his way off the field he used his bat to push the ball aside. Article 2.2 of the ICC Code of Conduct — abuse of cricket equipment, clothing, ground equipment or fixtures and fittings. Seven overs later, in the thirteenth over, Sherfane Rutherford. A delivery he believed should have been called wide; the umpire did not agree. Article 2.8 — showing dissent at an umpire's decision.

Two incidents, two charges, but one measurement: one demerit point each. The smallest whole number in the ICC's deterrence ledger. Everyone keeps the big numbers; nobody audits the small ones. This piece is an audit of that 'one'.

Context: the format before the notebook opens

The rules I work by should be stated first. Before writing any conclusion, I set a minimum-sample condition. The subject here is T20 International cricket — a bilateral series between India and the West Indies, played on Indian soil. Ranchi, then the third match in Indore. A three-match series, finished 2-1, with India regaining the lead in the Indore decider. Those three sentences are the entire format frame.

The second thing to fix is the limit of information. This report is essentially a disciplinary news item. It carries rich detail on the Code of Conduct process but almost nothing on player performance data, rankings or commercial matters. Where information is absent, I do not write an estimate; I write 'insufficient information'. That is an old habit — in a rented room in Rajshahi, PPDA once became a way of breathing, but breathing and lying have no relationship.

The two venues need to be recognised. The JSCA International Stadium Complex in Ranchi and the Holkar Stadium in Indore — both Indian decks, conventionally batting-friendly and high-scoring. The totals of 250 and 224 fit that character. Match environment, dew, weather or DLS are not mentioned in the source, so those cells stay blank in my notebook.

The core incident happened in Ranchi; the Indore match only tells us the series outcome. That night in Ranchi, the West Indies were chasing 250; in the Indore decider India made 224 and the West Indies fell 14 short. The source describes the West Indies as 'resilient' — they did not collapse, they fought. But no ranking, squad-structure or bench-depth figures appear. So at team level the only verifiable conclusion I can sign is that the series was competitive and India pulled the final match their way.

How the Code of Conduct actually works

The arithmetic of discipline has to be understood, otherwise the weight of a sanction cannot be judged. ICC Code of Conduct breaches are graded by level. Both breaches here are Level 1. The Level 1 penalty range runs from an official reprimand at the minimum to 50 per cent of the match fee at the maximum, plus one to two demerit points. Powell and Rutherford each received one demerit point — the lightest end of the range.

Three numbers must be remembered, because they are the system. First, one — the points each received. Second, twenty-four — months, the period the record holds the points. Third, four — the threshold at which demerit points convert into suspension points, which can bring a ban. In this report both are first offenders within a twenty-four-month window, so both remain far from four.

The process is clean. The charges were levelled by on-field umpires Jayaraman Madanagopal and Rohan Pandit, third umpire Nitin Menon and fourth umpire Virender Sharma. The match referee was Prakash Bhatt, of the Emirates ICC International Panel of Match Referees. Both players admitted the offences and accepted the proposed sanctions, so no formal hearing was required. One line, but an entire system stands inside it.

One more feature of the process is worth noting. No hearing means no dispute; no dispute usually means the evidence was clear — umpire reports, probably footage. Where evidence is clear, admission is the reasonable route, and that is what happened. It is also the familiar precedent: Level 1 on-field conduct breaches normally resolve this way, without heavy sanction or long investigation. There is no anti-corruption element here; this is purely on-field conduct.

Match log: two incidents, two different triggers

In my notebook I record incidents by over number, because behaviour cannot be read without context. The notes read like this:

1. In Ranchi the West Indies were chasing 250. Powell was dismissed in the sixth over by Mayank Yadav — at the very edge of the powerplay, with chase pressure at its peak.
2. After dismissal he pushed the ball away with his bat. The trigger was post-dismissal frustration; the act sat outside the game, not inside it.
3. In the thirteenth over Rutherford believed a delivery should have been called wide, the umpire did not call it, and he yelled at the umpire in dissent. The trigger was live and ongoing — at the transition from middle overs into the death.
4. In Indore India made 224, the West Indies fell 14 short, and India regained the series lead.

The difference between the two triggers is the real information here. One is frustration about one's own performance — the batter has failed and has no way to settle the account, so it lands on the equipment. The other is frustration about an official decision — the batter believes he was denied. One turns inward, the other turns on the system. The penalty arithmetic is identical, but the behavioural source is not; and in future those two paths can diverge.

One more thing deserves notice: Ranchi and Indore are separate matches with separate innings totals. 250 and 224 cannot be merged, just as the two incidents cannot be merged. Labels must match before numbers can. The notebook filled before the stadium did, so the labels were already in place.

The one clean performance data point

This report carries little playing data, but what it carries is bright. In Indore Abhishek Sharma's fifty came off 18 balls. That works out to a strike rate of roughly 278 — elite by any T20I standard. An elite T20 powerplay strike rate usually sits in the 150 to 170 band; 278 means the innings was powerplay-dominant and extremely high-tempo.

This is where my sample condition applies. Eighteen balls in one innings is an event, not a trend. I will not inflate it into a 'new Indian batting philosophy'. It is one data point, and its meaning is that India's top order seized the first half of the powerplay in Indore.

Mayank Yadav appears for one reason — Powell's wicket. The source gives no economy or pace data for him. His identity can be inferred: an express-pace strike bowler with the new ball or in the early overs, able to strike at the edge of the powerplay. Without numbers that is inference, not verified fact.

Naman Dhir appears in a cross-referenced headline — 'Economical' Naman Dhir proving his worth in India's T20 set-up. There is no analysis of him inside this report. Still, the headline hints that India were auditioning fringe T20 talent in this series. A lead, not evidence.

Contrarian: you cannot write a culture from n=2

The easiest and most wrong conclusion is this — two West Indies players were sanctioned in the same match, therefore a 'dissent culture' is forming in the West Indies camp. Easy, because two names side by side make a story. Wrong, because the sample is two, and both sit inside a single match.

Correlation is not causation. Two players' behaviour drew the same sanction — that is a correlation. It does not prove they acted for the same reason or under the same cultural influence. Powell's incident was post-dismissal; Rutherford's was post-wide-call. Selling two separate personal moments as one team-wide cultural tendency is exactly the move I discard when I reconcile a piece with the match log.

The real anomaly is not in the sanction but in the marginal call. The delivery Rutherford believed was wide is a boundary line tied to the outcome of the game. That kind of marginal wide call is what normally produces umpiring controversy, review and resentment. The source mentions no DRS referral and no systemic umpiring complaint. So the controversy here is personal, not institutional.

Sanctions are cheap; marginal calls are expensive. In the ICC ledger one demerit point is worth close to nothing — no match impact, no ban, spent within twenty-four months. But the decision that produced the resentment can change the course of a game, and if repeated it becomes an umpiring controversy. The two incidents differ in weight even though they are identical in arithmetic.

The market angle: the gap between headline and column

In a transfer window there is a wrong way to read this kind of story — bolting on suspension panic. Powell is a familiar name in T20 franchise cricket, has played in the IPL and has captained the West Indies in T20I; Rutherford is an IPL-contracted power-hitter. The natural question follows: will the sanctions affect their franchise availability?

The answer comes from the ledger. Genuine franchise-availability risk is created by suspension points, which arrive once four demerit points accumulate. Here each player received one. Both are first offenders. So commercial or availability risk is effectively zero at this moment. What looks enormous in the headline is negligible in the column. The transfer market lies in headlines; it tells truth in columns.

Across the border, the same story can read differently — the West Indies' discipline record is seen one way in a Dhaka newsroom and another way elsewhere. But here the numbers agree: one point, first offence, twenty-four months. Where the numbers agree, the cross-border framing is not needed, so I drop it.

The risk ledger

Disciplinary risk is minimal. The points expire inside the twenty-four-month window if there is no re-offence; even a repeat Level 1 breach (two points) would leave both well short of the four-point threshold. The most likely outcome is immediate closure, with no impact on play or availability. No appeal or contest is reported, which suggests the players and their board judged the sanctions proportionate.

One risk I record separately, though the source omits it — Mayank Yadav's workload. For express-pace bowlers this risk is a professional reality. His name appears here because of one wicket; the source says nothing about his bowling load. I keep that cell open for future accounting.

Another blank cell — attendance. Crowd numbers at Ranchi or Indore, the sound of the stands, the silence of the broadcast — none of it is in the source. I audited the empty seats until the silence became a metric; here that metric is absent too. An absent number is also information: this story had no crowd narrative, only the arithmetic of a process.

Outlook: the next-round signal

Three things to watch going forward. First, the twenty-four-month rolling window — when these two points are 'spent'. Second, whether the dissent signal repeats; two incidents are not a pattern, but repeated occurrences in the same squad certainly warrant monitoring. Third, and most important, the marginal wide-call story — because the call that breeds resentment is the one that opens the door to systemic debate later.

I do not chase narratives; I reconcile them with the match log. What the notebook recorded on that Ranchi evening is brief: six, thirteen, one. Big numbers leave; small numbers stay — and they tell you where to look in the next match.

The crowd left, the data stayed, and I learned to hear structure.