HomeAsian CricketTwo Tracks, One Team: Pakistan's White-Ball Reset and the Uneven Promise of Rawalpindi to Lahore

Two Tracks, One Team: Pakistan's White-Ball Reset and the Uneven Promise of Rawalpindi to Lahore

**Core answer:** Pakistan named separate T20I and ODI squads for a Sri Lanka T20I series and an England/Sri Lanka ODI tri-series, splitting white-ball captaincy by format — Sahibzada Farhan leads the T20Is, Shaheen Shah Afridi the ODIs. **Key facts:** - Three T20Is against Sri Lanka at Rawalpindi on October 9, 11 and 13. - Seven-match ODI tri-series (Pakistan, England, Sri Lanka); first three at Rawalpindi, rest and final at Lahore. - Sahibzada Farhan named T20I captain; Babar Azam appears only in the ODI squad. - Salman Ali Agha dropped from the T20I squad after losing the captaincy, retained for ODIs. - Razaullah and Mohammad Imran Randhawa receive maiden white-ball call-ups. **Source attribution:** Pakistan Cricket Board (PCB) squad announcement, October (year not specified in source). | Cross-checked: cricsultan.com **Related Q&A:** Q: Who captains Pakistan in the T20I series against Sri Lanka? A: Sahibzada Farhan, appointed on the basis of leading Pakistan at the Asian Games, per cricsultan.com squad records. Q: Why is Babar Azam absent from Pakistan's T20I squad? A: He is retained only in the ODI squad, consistent with a deliberate T20I rebuild around newer names. Q: Who leads Pakistan's ODI side in the tri-series? A: Shaheen Shah Afridi continues as ODI captain, per the PCB announcement.

I found the team — not on a cricket field, but in the silent gap of a squad list.

An October morning in Rawalpindi. What arrived was not a scorecard but two separate lists — one for T20Is, one for ODIs. Reading the first, my eye caught on the name that wasn't there — Babar Azam, absent from the T20I squad. Moving to the second, I saw Shaheen Shah Afridi captaining the ODI side while not even appearing in the T20I list. Then the third detail — Salman Ali Agha dropped from the T20I squad but retained in the ODI squad. One announcement, three names, and a team split cleanly in two.

At twenty-seven, sitting in the Brisbane Roar dressing room, I learned where a team truly finds itself. Not in press conferences. In hotel lobbies, behind the nets, in the exhaustion of airports — that is where a team's real character is assembled. So when I read Pakistan's announcement, I wasn't chasing scores. I was chasing the question — which team is actually walking out, and which one is still searching for its identity.

Context: Two Formats, Two Separate Logics

Two formats, two entirely separate logics. A three-match T20I series against Sri Lanka, all at Rawalpindi — on 9, 11 and 13 October. Then a seven-match ODI tri-series featuring Pakistan, England and Sri Lanka. The first three games at Rawalpindi, the rest and the final at Lahore.

One thing needs clarifying here — T20I and ODI cricket are never the same. In T20Is, the calculations of powerplay, middle and death overs are distinct. In ODIs, two new balls, spin control in the middle overs and acceleration in the final ten — an entirely different game. Reading the two squads together would be a mistake. They are two separate organisms, running on different pulses.

The venue speaks too. Rawalpindi has historically favoured pace and bounce. Lahore is slower, spin-friendly. Spreading a seven-match tournament across two venues introduces a pitch-condition variable — the Rawalpindi leg and the Lahore leg will tell different stories. October evening dew is another major factor, one that directly hurts the side bowling second.

And England's presence changes the weight of this series. The broadcast value of a routine bilateral against Sri Lanka jumps once England is involved. The tri-series format — everyone plays everyone, then a final — means the last game is a knockout-style psychological test that a routine bilateral never provides.

The year of this announcement is not explicitly stated. Only the October dates are given. So nothing certain can be said about calendar congestion, injury context, or its place in the FTP. What can be discussed is the structure of the squad — and that is the real signal.

Core Analysis: A Team Split in Two

The biggest signal in this announcement is not any single name — it is that Pakistan has now consciously split its white-ball cricket into two tracks. The ODI side keeps a senior spine; the T20I side is undergoing a full reset. This is not mere rotation; it is a structural decision.

The New T20I Captain: Sahibzada Farhan

Sahibzada Farhan has been made T20I captain — the stated basis being that he led Pakistan at the Asian Games. This is my first warning sign. The Asian Games is not full-strength bilateral cricket; it is a multi-sport event with a different team composition and different competitive intensity. Projecting T20I international captaincy success from that leadership experience is a weak predictive base.

Two Tracks, One Team: Pakistan's White-Ball Reset and the Uneven Promise of Rawalpindi to Lahore

Farhan is a right-handed opener. The modern benchmark for a T20I opener is generally around a 135–145 strike rate (this figure is pending verification). But the source contains no average, strike rate or recent-form data for him. So I cannot validate this appointment on merit — only identify its role. And that role says: making a T20I specialist opener captain means deliberately rebuilding the T20I side from scratch.

Shaheen Shah Afridi and the Burden of a Pace Captain

Shaheen Shah Afridi has been retained as ODI captain but left out of the T20I squad. This is a clear signal — Pakistan has split white-ball captaincy by format. A clear structural choice.

But an old picture returns here. Shaheen is a left-arm new-ball swing bowler; his value is front-loaded in the powerplay. The movement he extracts with the new ball is sharpest in the first spell. Yet concerns over his workload are nothing new — the injury history of this left-arm quick is a familiar story.

On top of that, captaincy means additional cognitive load. When a fast bowler sets fields, thinks through bowling changes and makes DRS calls, extra strain is added to a body already carrying a heavy burden. This pattern has appeared before: frontline quicks who captain often lose some edge with the ball, because attention is split in two places.

Babar Azam and the Format-Split Debate

Babar Azam appears only in the ODI squad, not the T20I squad. This is a major structural signal — the T20I side being built does not include its long-time batting figurehead.

There is a subtle argument here. In ODI cricket, Babar's anchor role — high average, moderate strike rate — is conventionally format-appropriate. But in the modern T20I template, exactly this profile has come under criticism. So his omission from T20Is and retention in ODIs are two sides of the same logic. The source, however, offers no data to gauge his current form, so this is a judgment of role, not of merit.

Razaullah and the Small-Sample Trap

Razaullah's maiden white-ball call-up — and the stated reason is his batting impression in the third Test against England. This is where I stop.

Projecting white-ball value from a single Test batting cameo is exactly the kind of inference my experience has repeatedly proven wrong. Test and white-ball cricket use different balls, different fields, different risk-taking. Assuming that a batting spell that works in a Test will work equally in a T20I powerplay or an ODI middle over means judging one format with another format's data.

There is, however, one positive signal: Razaullah has been named in both squads. The selectors see him as a multi-format asset. The question is only whether the basis for that trust — one Test batting cameo — is strong enough.

Salman Ali Agha: The Politics of Omission

Salman Ali Agha's case gives the most direct signal. After losing the T20I captaincy, he has been dropped entirely from the T20I squad — yet retained in the ODI squad.

Removing a captain and then omitting him completely from that format is not routine rotation; it is a forced leadership transition. And his presence in the ODI squad confirms the decision is format-specific — meaning the problem is not the individual but the specific format's structure.

Agha is an all-rounder — a middle-order batter and off-spinner. If his role does not fit the T20I template, that is a signal to the selectors of a rebuild. But a risk lurks here: if captaincy changes happen quickly and ambiguously, a power vacuum can form in the dressing room.

Two Tracks, One Team: Pakistan's White-Ball Reset and the Uneven Promise of Rawalpindi to Lahore

The Wicketkeeping Instability

A small but meaningful signal — the ODI squad carries two wicketkeepers (Ghori and Saad Baig), while the T20I squad carries one (Nafay). Saad Baig has been added to the ODI squad. Meanwhile Usman Khan — once a preferred wicketkeeper-batter — has been omitted.

Two Tracks, One Team: Pakistan's White-Ball Reset and the Uneven Promise of Rawalpindi to Lahore

Two different keepers across two formats, plus the omission of a familiar name, says the wicketkeeping slot is still unsettled. When a team is searching for its identity, these small ambiguities become big signals. Usman Tariq's omission is part of the same picture — a tilt toward new names over experience.

The Four Asian Games Pacers and the Workload Calculation

One fact deserves separate attention: four pacers from the Asian Games squad — Ali Raza, Wasim Jr, Akif Javed, Ahmed Daniyal — have been left out.

To me this does not look like a pure form decision. It may be a conscious workload-protection decision — in a busy home calendar where the T20I dates (9, 11, 13 October) run straight into an ODI tournament, there is almost no rest window.

And this is where the real sporting risk hides. Pakistan's ODI attack depends mainly on three frontline quicks — Shaheen, Naseem and Haris Rauf. All three carry injury histories. If all three are repeatedly used across a seven-match tournament, there is a real fear that the team's pace drops off in the later matches.

Two Faces of Batting Depth

The two squads do not have equal batting depth. The ODI side has Babar, Fakhar, Salman Agha and Saim Ayub — together an experienced structure. The T20I side has Farhan, Fakhar, Saim and Hasan Nawaz — promising but unproven.

The T20I side has been deliberately built free of senior anchors — that is the biggest structural truth of this announcement. The question is whether playing at home softens the learning cost, or whether this inexperience is exposed outright against a side with England's powerful batting depth.

Bench depth is also a question. A bench is being built around first-time call-ups like Razaullah and Randhawa — that seeds potential, not proven depth.

The Contrarian Read: What Many Are Misreading

Now to the place where my reading diverges from the market's conventional reading.

Many are reading this announcement in one of two ways — either as chaos (captaincy change, senior omissions), or as mere rest (Babar and Shaheen held back from T20Is). I think both readings are wrong.

The real signal is cooler, more calculating. Pakistan is using format-splitting as a strategy. In T20Is they want to build a new identity; in ODIs they want to hold onto the old spine. This is not chaos; it is a deliberate two-track approach.

But here is my real concern. This new T20I identity is being built on the weakest possible evidence base. Farhan's leadership comes from a multi-sport event where bilateral cricket's pressure does not exist. Razaullah's call-up comes from one Test cameo. Both are small-sample traps — and drawing big decisions from small samples has, in my experience, almost always taken its revenge.

Based on my years of watching matches, I have seen one pattern again and again: transfer-market and squad-building data models overrate young potential and underrate dressing-room chemistry. Here that exact picture appears — trust is being placed in someone like Razaullah on thin data, while the value of an experienced campaign-handler goes unmeasured.

And one more thing. What is clear in reading this announcement is the absence of information. There is no performance data for either format, no latest injury status, no innings-phase numbers. So I cannot call this squad a final verdict — it is a forward-looking gamble whose results are not yet written.

Luck factors like dew and the toss are also still out of the equation. On an October evening, dew is a cruel reality for the side bowling second — and in a tri-series, in a final, that dew alone can flip a match's fate.

Final Word: What to Wait and Watch

So before the final whistle, I will watch three things.

First, the Lahore leg. If the pitch is genuinely slow and spin-friendly, the battle between Sri Lanka's spin and England's batting depth becomes the real test of this series. Rawalpindi's pace and Lahore's spin — two venues will give two teams two different examinations.

Second, how long the split captaincy holds under pressure. When a team runs under two captains, the question of shared blame surfaces the moment results turn bad. If both Farhan and Shaheen are put under pressure at once, the dressing-room chemistry itself becomes the real story.

Third, Shaheen's workload. Across a seven-match tournament plus the preceding T20Is, how much a left-arm fast-bowling captain's body can take may well determine the fate of Pakistan's entire ODI campaign.

A squad list can tell you who will play. But who will actually forge this team's identity — only the field will tell. And that answer is still pending.