Pakistan's Rawalpindi Gamble: Spin Out, Uncapped Pace In — And the 4.63% Nobody Wants to Look At

Two days before the first Test, Pakistan removed Ali Usman and Abdullah Fazal from their squad. On the surface it reads routine — one injury, one form call. Count the squad, though, and the story changes: sixteen players, exactly one with spin as his primary job, and that man, Arafat Minhas, is also a lower-middle-order batter. Sajid Khan and Noman Ali, the spine of Pakistan's recent home Test attack, are not in it. This is not a squad update. It is a public declaration of a pitch read.

I have no personal notebook from this match, but one sheet from my lockdown spreadsheet still exists under the name "home Test pitch intent," and it taught me something that applies directly here: when a team abandons its most successful home weapon, it is never rotation. It is fear, or it is arithmetic. For Pakistan, it is both.

Context: Why Rawalpindi Carries So Much Noise

Pakistan's recent home Test template was spin-first — dry, turning surfaces, two specialist spinners, and a bet on the visiting side's technical frailty. Then 2026 against Bangladesh at home broke the template's back: flat tracks, 565 conceded in the first innings, a 2-0 series defeat. That loss planted a fear in the selection room: if the surface is batting-friendly, our spin attack is decoration.

Now comes Sri Lanka, seventh in the WTC standings, and a side that actually owns quality spin. This is where Pakistan's logic becomes interesting: preparing a turning track at home means feeding the visitor their strongest suit. So they inverted it — a seam-friendly or at least non-turning surface, and a squad built to match: Aamer Jamal as the seam-bowling allrounder, plus two uncapped quicks, Ali Shabbir and Saqib Khan.

The first Test starts in Rawalpindi on November 9; the second in Lahore from November 17. Eight days between them — no room for rotation, only a bet on fresh legs.

Core: Two Names Out, Two Different Stories

Abdullah Fazal's removal is not a form story. It is an injury story. The PCB media release says it plainly — lower back injury. This is the batter who debuted against Bangladesh earlier this year, who was Player of the Match in the Quaid-e-Azam Trophy final, who was recalled to the squad for the Edgbaston Test and did not play. The selectors rate him. His back does not. For a young opener, a lower back injury is rarely a one-off; it is the opening entry in a pattern — and Pakistan's top order has no cover for it.

Ali Usman's story is entirely different, and it is the real news. Usman has been released from the squad for a second consecutive Test, with no injury involved. In the warm-up he bowled two overs. Two. For a specialist spinner that number is the fastest possible signal that he was already outside the first-choice plan.

But the decisive evidence is Mike Hesson on the record. The coach said playing "a finger spinner who can't contribute with either bat or field" in those conditions is unlikely. I can recall very few instances of a specialist spinner being publicly devalued in such plain terms in Test cricket. This is a naked declaration of a modern Test selection criterion: a spinner must now offer something beyond bowling.

It also means Pakistan's selection philosophy is sliding toward an allrounder-heavy, bat-deep XI. Minhas is in the squad precisely because he spins and bats. But there is a logical crack here: if Pakistan is genuinely going spin-light into a pace attack, treating Minhas as the main spinner is a risk, because his spin is a rounding-up option, not a wicket-taking spearhead.

Contrarian: Where I Could Be Wrong, and Where the Selection Could Be

My biggest doubt is that I am over-theorising Hesson's quote. It may simply be media management — framing a spinner's omission as rational modern selection rather than a panic move. If Rawalpindi suddenly turns, that entire quote becomes comic inside four days.

The second, more concrete objection: Pakistan's pace attack is unproven right now. Two uncapped quicks in a match with zero margin for error is a bet on speed, not on quality. The case for dropping Sajid and Noman only holds if the new seamers extract movement. If Rawalpindi is dead with soft bounce, the uncapped quicks do nothing, Minhas does nothing, and Aamer Jamal is left bowling 25 overs alone. That is the scenario in which the selection panel's entire confidence turns to dust in four sessions.

The third point nobody is covering: the PCB offered no explanation for two notable removals. One is explicable by injury; the other only got Hesson's quote afterwards — but the board itself said nothing. That is a transparency question, and for a team already under pressure, silence becomes questions within a week.

Takeaway: The Truth of 4.63% and the November 9 Test

Here is the number Pakistani fan culture does not want to look at: a WTC points percentage of 4.63 — seven defeats in nine matches, plus over-rate penalties. That is roughly six times lower than the second-from-bottom side, West Indies. Over-rate penalties are not just a discipline symptom; they are a symptom of an unsettled bowling rotation. When you don't know who bowls when, overs go slowly.

My auditable claim is this: if Rawalpindi shows grass on the first morning and Pakistan bowls first after winning the toss, the selection will have been vindicated — regardless of the result. If the surface is flat and Minhas is handed the ball before the 20th over, the selection will have already been wrong — even if Pakistan win. I am grading intent and surface alignment, not outcome, because a team playing without its biggest weapon cannot be absolved by a win alone.

And if Fazal's back does not hold up long term, the real story won't be spin-gate. It will be that Pakistan's top order is again playing without a batter it chose itself. In my spreadsheet that column is called "how often injury picked the team." In Pakistan's team, that column is not empty today.