Sadaqat's 96, Imran's 3/11: Pakistan win by 82 in Rawalpindi, but what the scorecard hides

The first three legal deliveries of the 16th over. Three sixes. Under the Rawalpindi floodlights the ball landed in the stands three times, and the television camera kept cutting back to the face of one off-spinner — Maheesh Theekshana, who that night recorded the most expensive figures of his T20I career. Going back through the scorecard afterwards, my eye stuck on a single comparison: Pakistan hit 12 sixes in this match, Sri Lanka three. The result read 215 against 133, a margin of 82.

In cricket, margin and dominance are not the same thing. An 82-run win in a bilateral T20I can be a genuine gap in quality, and it can also be the joint signature of three dropped catches, a flat pitch and one spinner bowling into the arc. I opened the scorecard again and read it twice — once in the language of the batting column, once in the language of catches, over-blocks and economy rates.

Let us set the context. This was the second T20I, in Rawalpindi, under lights. Pakistan had won the first and led 1-0; this win took them to 2-0. Sri Lanka made three changes and rested their frontline seamer, Dushmantha Chameera. They had batted first in game one; here they chose to chase. I read that as a decision, but a reactive one — the Stage-1 record gives no toss or pitch explanation that would make it a confident plan.

The venue matters. The Rawalpindi surface was a batting-friendly flat track with the odd ball gripping. Two truths hide inside that one sentence. First, a pitch where the ball occasionally grips is not a pitch without weapons — Imran proved that. Second, on a surface where runs come easily, an 82-run margin cannot be read as proof of structural superiority. Dew is also a factor in a night game, though the Stage-1 account does not state it explicitly. Dew under lights usually makes chasing easier, which makes Sri Lanka's powerplay collapse a stronger indicator of their own execution than of conditions.

Two team-level things stand out. Pakistan are in the middle of a generational refresh — a new captain in Sahibzada Farhan, and a 21-year-old in Maaz Sadaqat in the squad. Sri Lanka are in transition, calling in the likes of Jayawardena and testing combinations. On this night Sri Lanka dropped at least three catches, one of them a reprieve for Farhan off a top-edged slower ball. A drop is an accident; repeated drops are a habit. In T20I cricket a drop is expensive, because a single reprieve turns into twenty runs in the next ten balls.

Now to the real work: taking the innings apart. Maaz Sadaqat made 96, dismissed off the last ball, four short of a century. The shape of the innings is interesting: 6 fours and 7 sixes produced 66 runs in boundaries, roughly 69 per cent of his runs. Elite modern T20 finishers usually sit between 60 and 70 per cent. Sadaqat's figure sits right at the ceiling — a classic modern, aggressive top-order profile, where he chose to spend balls sighting the ball and then send it to the rope rather than accumulate.

The tempo change says more. From 51 off 30 balls to 76 off 40 — he started patiently and accelerated as the overs went on. In T20I cricket this rising-tempo structure is valuable, because it shows a batter who can read the pulse of an innings, not just swing. But the brakes have to go on here: Sadaqat's innings is a single-innings sample, and it came at home, on a batting-friendly pitch, against a rotated and error-prone side. The Stage-1 record does not even give the exact number of balls he faced, which means his true strike rate is data pending verification. Without that verification, the 'young sensation' label is a label built on credit.

Sahibzada Farhan's 73 sits in Sadaqat's shadow numerically but not in significance. He reached fifty off 31 balls, a strike rate of roughly 161 to that point. The T20I top-order benchmark is usually 130 to 150. Farhan was above it. But his innings is not only a batting statistic; it is a leadership statement — as the new captain he led by performance rather than by proclamation. That leadership-by-performance model builds acceptance inside a dressing room quickly, and it carries a risk: if a team's fortunes start resting on one bat, that bat eventually comes back to hurt you.

Now to the number that, for me, is the most transferable and repeatable signal in the match. Mohammad Imran took 3 for 11 from four overs — an economy of about 2.75. In T20I cricket anything under seven is excellent, and 2.75 on a flat pitch means holding the match in your own hand. The report describes him keeping the right lengths without losing his radar, bowling on a natural angle into right-handers' bodies, and taking two in two. That angle is not an accident; it is a skill, and skills outlive accidents. The way he strangled the tourists through the middle overs is what pinned the Sri Lankan innings in one place.

In the pace department, Mirza supported him with 2 for 28. What the two of them did together was a tactical job: making it hard to find big overs by attacking the bodies of right-handers. Sri Lanka could not find those big overs — that one line is the summary of their innings.

At the other end of the story sits Theekshana. Three sixes off four balls in the 16th over, and the most expensive figures of his T20I career. I opened the scorecard again, frame by frame, and there is a fine but vital distinction here: Theekshana was not destroyed by a lack of talent; he was destroyed by a tactical decision. Bowling slot ball after slot ball to a set, in-form batter in the death overs means putting the ball where the batter wants it. A spinner's death-overs weapons are variations of length, changes of flight, and the width of the crease. Theekshana did not use them — or did not get the chance, because Sadaqat had already taken the over into his own rhythm.

Sri Lanka's batting innings reduces to 35 for 2 after six overs. Two wickets inside the powerplay means the foundation of a T20 innings has shifted, because every over after that demands extra risk, and extra risk means more wickets. A fifty-run stand did emerge late, but it only postponed the defeat. That stand nonetheless carries an important piece of information: Sri Lanka's middle-order batters were not entirely incapable — they simply lost the calculation after an early collapse.

Now to the part where I disagree with the standard account. The 82-run margin is the most visible number in the match, and it is also the most misleading one. The report states plainly that Sri Lanka dropped at least three catches, including a reprieve for Farhan. Hold those catches, let one top-order batter survive two more overs, and the margin is probably much smaller. I am not saying Pakistan would have lost; I am saying 'crushed them by 82' is the language of the scorecard, not the language of the match.

My second disagreement concerns the shape of Pakistan's scorecard. 215 for 3 is a fine total, but it came mainly from two batters. Outside those two, the batting line-up was effectively untested. On a flat pitch this top-heavy structure worked, but it conceals a structural weakness — if the top order falls to a good attack, how much can that middle order absorb? This match did not answer that question. Cricket's DRS taught me a habit: we trust technology for line calls, but under pressure we still trust a human for judgement. In the same way, we believe a flash of an innings, but a structure's durability needs many matches of evidence.

My third disagreement is about home conditions and squad context. Pakistan are playing at home; Sri Lanka are touring, have made three changes, and have rested their frontline seamer Chameera. Reading this 2-0 lead as a pure talent gap ignores a large piece of information. Resting a frontline seamer mid-series sends one of two messages: workload management, or a tactical concession. Both suggest Sri Lanka were not treating this specific match as their highest priority. That does not explain away their failures, but it is context.

And here is the tension I keep seeing: emotion versus rule, highlight versus over-by-over accounting. After a match, the crowd remembers the sixes; the analyst should remember the economies. The scorecard is the headline; the boundary-run share is the investigation. Sadaqat's 69 per cent boundary-run share is the headline, Imran's 2.75 economy is the investigation — and over the long run the investigation tells more truth.

Referee's Eye | Scenario: an over-by-over deep analysis of a single innings

So what should you watch from here? Five signals, and they are conditions rather than a list. First, Sadaqat's consistency: if this boundary-heavy profile holds across at least five matches, especially away, then the word 'sensation' earns its place; otherwise it is a one-night light. Second, Pakistan's middle-order usage: how many runs and balls batters four to seven get will reveal whether the side stays top-heavy. Third, Sri Lanka's drop count: two or more drops a match stops being an accident and becomes a coaching matter. Fourth, Imran's economy: sustained sub-seven numbers mean a genuine control asset is emerging. Fifth, Chameera's status: a prolonged absence turns Sri Lanka's pace depth into a series-level risk.

I leave one question open, because nobody has the answer yet. In T20 cricket, have we made the scorecard the hero — where a flash of one innings is read as the strength of a structure, and 82 runs on a flat pitch is remembered as dominance? Sadaqat was genuinely brilliant that night; Imran genuinely controlled it. Which of them lasts longer will be written not under the Rawalpindi floodlights, but on the harder pitches of the next tour.