Two Squads, Two Captains: Pakistan's Quiet White-Ball Structural Reset

Last week I opened the Pakistan Cricket Board's squad release and did not reach for a pundit's reaction first. I laid the two squads side by side and matched the names. Shaheen Shah Afridi is not in the T20I list. Babar Azam is not in the T20I list. Both are in the ODI list. Same country, same month, same press release—yet two different teams and two different captains. In 2026, sitting in a Dhaka television studio the night the commentary box missed the location of the pressing trap, I started Dhaka Half-Space. The same feeling returns here: the way the announcement is framed hides the actual decision.

Let me lay out the facts, because there is no room for sentiment. A three-match T20I series against Sri Lanka at Rawalpindi—October 9, 11 and 13. Then a seven-match ODI tri-series featuring Pakistan, England and Sri Lanka; the first three matches at Rawalpindi, the rest and the final at Lahore. The T20I leg sits entirely at one venue; the ODI tournament is split across two. The release does not state the year, and the ODI tri-series dates are absent altogether—two gaps worth remembering when any calendar maths is attempted later.

Captaincy is split in two. In T20Is, a new face: Sahibzada Farhan, elevated on the back of leading Pakistan at the Asian Games. In ODIs, Shaheen Shah Afridi continues. Salman Ali Agha, having lost the T20I captaincy, is dropped from that squad but retained for the ODIs. Maiden white-ball call-ups went to Razaullah and Mohammad Imran Randhawa. Wicketkeeper-batter Saad Baig joins the ODI squad. Out went Usman Khan (wicketkeeper-batter) and Usman Tariq (spinner); and none of the four Asian Games pacers—Ali Raza, Wasim Jr, Akif Javed, Ahmed Daniyal—made the squad.

Based on my years of watching matches, the real information in a squad announcement never sits in the list of names—it sits in the gap between two teams. That gap is stark here. Pakistan's real decision is not selection but the construction of two separate white-ball identities—an experienced core in ODIs, a deliberate reset in T20Is. This two-lane architecture, running a senior core alongside a new side, is the defining feature of the announcement and the true test of the series.

Farhan's captaincy is a tactical question. The Asian Games is a full-strength, multi-sport context; reading leadership credentials from it is a weak predictive base. This is not to diminish Farhan—it is a statement about sample size. I want to watch how aggressively he sets the field in the powerplay, when he keeps a slip-point, and how late he brings on spin through the middle. In T20I cricket, captaincy is really a schedule of bowling changes and a set of field-angle decisions.

Shaheen is a different calculation. As a left-arm new-ball swing bowler, his value is front-loaded; hunting wickets in the powerplay is his job. On top of that, ODI captaincy adds non-bowling cognitive load—field changes, reviews, rotation, who bowls the death overs. For a fast bowler already under injury-management pressure, that extra load is another risk. This is where Pakistan's real structural weakness hides.

Babar Azam in ODIs only is no small signal. In the modern T20I template, the slow-strike anchor profile draws criticism; in ODIs the same profile fits. So the omission is a structural decision, not a form decision. The T20I side is being built without its long-time batting figurehead—and the result of that decision is not yet on any film. The dual-captain structure is legitimate, but history suggests friction when results diverge; if Farhan wins in T20Is and Shaheen loses in ODIs, the question of who actually leads will surface.

Razaullah's selection is the riskiest on sample size. Impressing with the bat in the third Test against England is an entirely different context; projecting white-ball value from one Test innings is a cross-format inference, exactly the kind this analytical frame flags as unreliable. Being named in both squads shows the selectors see him as a multi-format asset—but the base is one innings. Let expectation grow with the number of innings, not with the headlines.

The wicketkeeping slot is unsettled. Two keepers in the ODI squad (Ghori and Saad Baig), one in the T20I squad (Nafay). That pattern usually appears when nobody has nailed the slot. And the omission of Usman Khan, a previously fancied wicketkeeper-batter, suggests the selectors are rethinking it.

In cricket, a half-space is not a football corridor. I mean the gap behind point, the angle at the top of off, and the crease position that opens a field—those are the real spaces. In a white-ball series, the second real space is time. Moving from Rawalpindi to Lahore means a change of pitch character—Rawalpindi's pace and bounce, Lahore's potentially spin-friendly surface. In a two-venue ODI tournament, a pitch variable enters before the knockout; data from the Rawalpindi leg cannot project the Lahore final.

England's presence raises the competitive ceiling. In batting depth and resources, England sit ahead of Pakistan; Sri Lanka are a mid-tier side but dangerous on spin-friendly surfaces. The tournament is not merely a Pakistan–Sri Lanka bilateral—its competitive weight is different.

Then there is the geometry of the calendar. Three T20Is back to back on October 9, 11 and 13, immediately followed by the ODI tri-series. For players in both squads—Naseem, Shadab, Saim—the rest window is almost nil. October evening dew and day-night fixtures could add pressure to the side bowling second. I learned more from an empty Bundesliga ground than from a full press box—the sound of tired feet, a fielding range arriving late, running lines shortening. Fatigue geometry will bend fielding range, length and running lines here too. To me that is the real risk: the ODI attack leans on three frontline quicks (Shaheen, Naseem, Haris Rauf), all with injury histories. Leaving out the four Asian Games pacers is therefore not purely a form call—likely a deliberate workload-protection decision.

Now the part mainstream discussion skips. Home advantage here is real, but it is also the biggest trap. Home conditions soften the learning curve for newcomers; bad results hide, and good results look exaggerated. At the end of the series, the verdict that the reset worked could rest on misleading evidence.

Public debate will circle Babar's T20I absence and Agha's omission. The real blind spot, for me, is elsewhere—in the structure and the timing. Controlling a game is a tactic, not a virtue. Dot-ball percentage or run-rate comfort cannot measure control; trap efficiency can—how much pressure is built, how many wicket-taking edges are activated. The success of a T20I reset should be measured not on the scorecard but on field maps and delivery positions.

In the first T20I at Rawalpindi, my eye will be on the 15th-to-20th-over split—that is where fatigue shows first. Once England arrive, the question sharpens: will this new structure hold against deep batting? If someone says at the end that everything is fine, ask them this—can the Rawalpindi data explain the Lahore final?