Audit the Adeeb, Khuzaima and Paudel ICC sanctions

Keep the two incidents and three player records separate

The ICC release covers a shared on-field incident involving Adeeb Usmani and Rohit Paudel and a different equipment incident involving Khuzaima Tanveer. A precise audit should not collapse those events or their code articles, even though all three cases were announced together.

The ICC reported on 15 September that Adeeb and Paudel were fined 15 percent under Article 2.4, Khuzaima was fined 10 percent under Article 2.2, and each player received one demerit point. Disciplinary reporting needs separate rows for conduct, code article, charge, sanction, demerit point and hearing status. Keep players beside innings; compare over with described conduct by date, and leave article open until player is verified.

Reconstruct the Adeeb-Paudel incident

The release places their argument in the 31st over of Nepal's innings and says they did not follow umpire instructions. Record both players, the over and Article 2.4 in linked rows. The players, innings, over, described conduct and article belong on the disciplinary case grid. Attribute each procedural step to the official who performed it instead of compressing the process into one dramatic label. Name the owner of innings, the source for over, the unit attached to players and the condition that would change over.

Do not attribute Khuzaima's separate conduct to this incident. A past sanction documents a completed case and does not prove how any future player or match will behave. A reviewer should reproduce described conduct from article, trace player to innings and understand why innings was not substituted for over. Apply the instruction again in its narrow form: Record both players, the over and Article 2.4 in linked rows. Preserve the evidence for reconstruct the adeeb-paudel incident without copying passwords, authentication codes, private keys, recovery phrases or unnecessary identity images.

Reconstruct Khuzaima's incident

The second event occurred in the 46th over of the UAE innings after Khuzaima's dismissal. Connect the reported contact with the stumps to Article 2.2. The player, innings, over, conduct, dismissal and article belong on the disciplinary case grid. A past sanction documents a completed case and does not prove how any future player or match will behave. A reviewer should reproduce described conduct from article, trace player to innings and understand why innings was not substituted for over.

An equipment-abuse charge is not the same as disobeying an umpire. Disciplinary reporting needs separate rows for conduct, code article, charge, sanction, demerit point and hearing status. If over conflicts with player, retain both captures, recheck players and postpone any step that depends on article. Apply the instruction again in its narrow form: Connect the reported contact with the stumps to Article 2.2. Preserve the evidence for reconstruct khuzaima's incident without copying passwords, authentication codes, private keys, recovery phrases or unnecessary identity images.

Apply the fines separately

Adeeb and Paudel each received 15 percent fines while Khuzaima received 10 percent. Place percentage, player and incident on each row. The player, percentage, basis, match and decision date belong on the disciplinary case grid. Disciplinary reporting needs separate rows for conduct, code article, charge, sanction, demerit point and hearing status. If over conflicts with player, retain both captures, recheck players and postpone any step that depends on article.

Do not add the percentages into a team fine or shared sanction. Attribute each procedural step to the official who performed it instead of compressing the process into one dramatic label. The final decision must connect over to described conduct, preserve the boundary around innings and state when innings needs another observation. Apply the instruction again in its narrow form: Place percentage, player and incident on each row. Preserve the evidence for apply the fines separately without copying passwords, authentication codes, private keys, recovery phrases or unnecessary identity images.

Record demerit history

One point was added to each record, and the release says none had a prior offence in the preceding 24 months. Store the point and stated lookback without predicting suspension. The player, points added, prior points stated, lookback and expiry rule belong on the disciplinary case grid. Attribute each procedural step to the official who performed it instead of compressing the process into one dramatic label. The final decision must connect over to described conduct, preserve the boundary around innings and state when innings needs another observation.

One point is below the four-point conversion threshold described in the notes. A past sanction documents a completed case and does not prove how any future player or match will behave. Keep players beside innings; compare over with described conduct by date, and leave article open until player is verified. Apply the instruction again in its narrow form: Store the point and stated lookback without predicting suspension. Preserve the evidence for record demerit history without copying passwords, authentication codes, private keys, recovery phrases or unnecessary identity images.

Trace acceptance and officials

All three admitted the offences and accepted sanctions proposed by match referee Ali Naqvi, so formal hearings were unnecessary. Separate charge, admission, proposed sanction and hearing status. The charging umpires, referee, admission, acceptance and hearing belong on the disciplinary case grid. A past sanction documents a completed case and does not prove how any future player or match will behave. Keep players beside innings; compare over with described conduct by date, and leave article open until player is verified.

No hearing does not erase the offence or sanction. Disciplinary reporting needs separate rows for conduct, code article, charge, sanction, demerit point and hearing status. Name the owner of innings, the source for over, the unit attached to players and the condition that would change over. Apply the instruction again in its narrow form: Separate charge, admission, proposed sanction and hearing status. Preserve the evidence for trace acceptance and officials without copying passwords, authentication codes, private keys, recovery phrases or unnecessary identity images.

Use the ICC release for the completed procedures

The release provides the incidents, articles, fines, demerit points, officials and accepted-charge process. Cite ICC code-of-conduct media release with its HTTPS address and access date; use source-checked explainers only for supporting definitions. If over conflicts with player, retain both captures, recheck players and postpone any step that depends on article. Attribute each procedural step to the official who performed it instead of compressing the process into one dramatic label.

It does not establish future conduct, later unrelated cases or the outcome of another match. The final decision must connect over to described conduct, preserve the boundary around innings and state when innings needs another observation. A past sanction documents a completed case and does not prove how any future player or match will behave.

End each case at its own recorded consequence

Keep the official wording and avoid moral conclusions that go beyond the code finding and completed sanction. Name the owner of innings, the source for over, the unit attached to players and the condition that would change over. Disciplinary reporting needs separate rows for conduct, code article, charge, sanction, demerit point and hearing status.

Disciplinary history is not betting information; treat it as sports-governance context and never stake money on assumptions about future conduct. Adults 18+ who meet local law should protect essential money, set cash and time limits before any play, never borrow or chase losses, and use the responsible-play centre for stronger separation or confidential support. A reviewer should reproduce described conduct from article, trace player to innings and understand why innings was not substituted for over.