Two-Track White Ball: Pakistan Splits Captaincy as T20I Reset Leaves Out Babar and Shaheen

I opened the travel ledger in Brisbane and closed it after the final whistle. In most years the first page of that ledger holds bus departure times, hotel room numbers, and the tally of the same black coffee. This time the first page holds a date, a city, and a name. The ninth, eleventh and thirteenth of October, Rawalpindi Cricket Stadium. The name is the new T20I captain — Sahibzada Farhan.

The Pakistan Cricket Board's announcement looks like a routine squad release. But when I set the names side by side in the ledger, the picture stops being routine. The announcement contains two separate white-ball squads: a three-match T20I series against Sri Lanka, and a seven-match ODI tri-series featuring hosts Pakistan alongside England and Sri Lanka. The tactical logic of T20I cricket — powerplay, middle overs, death overs — and the logic of ODI cricket — two new balls, spin control through the middle, acceleration in the final ten — are entirely distinct. That separation sits at the centre of the release.

One blank room in the ledger needs flagging first, because a blank room is itself information. The source does not name the year. Dates exist; the year does not. I cannot place this series precisely inside the international calendar. The second gap: the ODI tri-series dates are missing entirely — only the T20I dates are given. A schedule without ODI dates makes workload and rest windows impossible to measure. Both gaps stay in mind for everything that follows.

The venue accounting is clean. All three T20Is sit at Rawalpindi — 9, 11 and 13 October. The first three ODI tri-series matches also sit at Rawalpindi, with the rest of the league phase and the final at Lahore. The T20I leg is confined to one venue, while the ODI tournament is split across two. A tournament played at two venues introduces pitch character as a variable — Rawalpindi's pace and bounce against Lahore's spin-friendly tendency. That venue character is my own reading, not a claim in the source, so confidence is medium here. Another variable is absent from the source — October evening dew, which can materially weaken the side bowling second. That is a probable influence, not a proven cause.

Now the real column of the ledger, where names and roles sit together. The structural signature of this PCB release is a two-track architecture. The ODI track keeps a senior core — Babar Azam, Shaheen Shah Afridi, Fakhar Zaman, Salman Ali Agha, Saim Ayub. The T20I track strips out the senior anchors and promotes newer names — Farhan, Fakhar, Saim, Hasan Nawaz. The central decision of the release is here: Pakistan is not treating white-ball cricket as one identity, but dividing it into two format-based identities. Splitting the captaincy is the clearest statement of that split.

The new T20I captain, Sahibzada Farhan, is a right-handed opener. But the background column of his captaincy entry matters — he is elevated on the back of leading Pakistan at the Asian Games. An Asian Games squad is not a full-strength squad, and it is a multi-sport context. The base on which he is handed a full T20I side is therefore a weak predictive base. The source carries no performance numbers for him — no average, no strike rate, no situational splits, no recent trend. I cannot assess the appointment on merit, only read it as design: a deliberate T20I reset, not continuity.

In ODI cricket, Shaheen Shah Afridi continues as captain and is absent from the T20I squad. That single line draws the border between the two formats. Shaheen is a left-arm new-ball swing bowler; his value is front-loaded in the powerplay. Captaincy adds cognitive load to a fast bowler already carrying a heavy physical burden — a pattern that recurs with frontline-pace captains. His workload is a standing injury-management concern, and that is one of the biggest risks in this release.

Babar Azam appears only in the ODI squad, not the T20I squad. That is a structural signal — the T20I side is being rebuilt without its long-time batting figurehead. In ODI his anchor profile is conventionally format-appropriate; in the modern T20I template that same profile has drawn criticism, consistent with this omission. The source carries no current-form data, so I read this as a design signal, not a merit verdict.

Salman Ali Agha makes the ledger speak plainly. After losing the T20I captaincy he is omitted from that format entirely, yet retained in the ODI squad. Removing a captain and then dropping him from that format is not routine rotation; it signals a forced leadership transition. His retention in ODI confirms the decision is format-specific, reinforcing the two-identity theme. The phrase 'after being removed' implies the decision was taken before this announcement.

The new-names column holds two entries that demand separate attention. Razaullah — per the source, selected after impressing with his batting in the third Test against England. His role is batting-capable, likely a bowling all-rounder or lower-order batter. But projecting white-ball value from one Test batting impression is a cross-format projection, and it cannot be treated as reliable. His presence in both squads suggests the selectors see a multi-format asset — but the sample is small. The second name is Mohammad Imran Randhawa, handed a maiden T20I call-up and uncapped at this level.

The wicketkeeping room is unsettled. The ODI squad carries two keepers (Ghori and Saad Baig), the T20I squad one (Nafay). Saad Baig has been added to the ODI squad. That arrangement gives flexibility but also exposes an unresolved slot. In the omissions column sit Usman Khan (wicketkeeper-batter) and Usman Tariq (spinner) — both previously fancied names. Reading Usman Khan's omission alongside two ODI keepers suggests the keeping slot is not settled. Four Asian Games pacers — Ali Raza, Wasim Jr, Akif Javed and Ahmed Daniyal — are also left out. I read that cluster as a probable workload-protection signal rather than pure form, though that is a probable influence, not a proven cause.

In bowling combination the ODI track is pace-led — Shaheen, Naseem, Haris Rauf. The T20I track mixes pace and spin — Naseem, Shadab, Abrar, Sufiyan. Pakistan's pace is internationally competitive, but spin depth is less proven. In batting depth ODI is strong (Babar, Fakhar, Salman Agha, Saim), T20I thin and experimental. Bench depth is average — several uncapped or maiden call-ups. The age structure is transitional: a senior core held for ODI, the T20I side handed to newer names.

The opponent picture gives this architecture meaning. England is a top-tier power, ahead of Pakistan in batting depth. Sri Lanka is a mid-tier side, strong in spin-friendly conditions. A spin-prone Lahore leg could suit Sri Lanka's traditional strength, while Rawalpindi's pace and bounce may favour Pakistan's fast-bowling core. That is a low-confidence reading, since pitch character is not a source claim. Overall Pakistan enters as a home side in the middle tier of world white-ball cricket, facing a better-resourced England and a spin-capable Sri Lanka. Home advantage here is real and material — and must be weighted heavily in any future result interpretation.

Now the part where the outside story separates from the inside accounting. The outside narrative is clean: 'Pakistan's white-ball reset — a new T20I captain, senior names rested or dropped, fresh faces blooded at home.' Its fundamental support is medium — the changes are real and documented, but the source carries no data to judge whether the new selections are justified on merit. No match has been played, so the sample is zero. In the ledger that is a blank room, and a blank room does not get filled with speculation.

In my tactical notebook I pair every observation with a number or a document. Here the clearest mismatch is the expectation around Razaullah. He is elevated on the strength of a single Test batting cameo — a textbook small-sample basis. Leckie taught me something at this exact junction, and I test that lesson against two contrasting cases so one name does not become a synecdoche for the whole system. At the Qatar World Cup, Mathew Leckie's 60th-minute goal beat Denmark 1-0 and carried Australia to a second Round of 16. Mornings at training I watched Graham Arnold drill a compact 4-4-2 low block; nights in the locker room I logged players repeating the same set-piece cues. I refused to call it a fairytale until the data supported the tactics, comparing a 32 percent average possession to past World Cup upsets. Leckie works as precedent only when the data sits behind him. Here the data is absent — so one Test innings cannot become T20I proof.

Test Leckie against two contrasting cases. The first is Leckie himself: a decisive moment later backed by methodical evidence, so the narrative held. The second is Farhan's captaincy: Asian Games leadership does not carry the weight of full-strength leadership, so the base is light. The third is Razaullah: a maiden call-up off one innings. All three point to the same error — turning a small sample into proof for a large decision. And a second danger sits here: praising the new architecture can bury the real risks of the two tracks. 'Reset' describes a design, not a result.

Dew, toss and DLS do not yet apply, because no ball has been bowled. But schedule density does. Three T20Is on 9, 11 and 13 October, then straight into the ODI tri-series, leaves minimal rest windows for players in both squads (Naseem, Shadab, Saim). Here the contracts and the workload are the real story, not the headline speculation. The transfer market is a rhythm section: agents, clubs, and waiting — in international cricket those roles fall to NOCs, central contracts and the calendar. For a player in two formats, rest is a luxury.

Two cells in the risk matrix are heaviest. One is sporting: Shaheen, Naseem and Haris Rauf — three frontline pacers with chronic injury histories, carrying the entire ODI attack. That risk is high, likelihood medium, impact high. The second is personnel: an abrupt T20I captaincy change plus senior omissions can create leadership instability. A two-captain structure is legitimate, but historically a source of friction when results diverge. A third sporting risk: the T20I side is uncapped-heavy, so volatility is natural; home conditions soften the learning curve. A fourth is public opinion: dropping senior names is a classic trigger for debate among Pakistan's fans, and the captaincy change is the most emotionally charged element. That risk is medium and result-dependent.

Overall the risk rating is medium. Pace-bowling workload and injury risk is the headline sporting risk, leadership-transition instability second. No integrity or compliance red flags appear — this is purely domestic selection, not an eligibility or NOC dispute. The 2026 spot-fixing case stays as context only, with no direct link to this release.

In my notebook I keep proven causes and probable influences in separate columns. Proven: two separate squads, two captains, Salman Agha's omission, maiden call-ups for Razaullah and Randhawa, the omissions of Usman Khan and Usman Tariq, the exclusion of four Asian Games pacers. Probable: a workload-protection intent, venue-based strategy, the effect of dew. Unproven and limited: the merit of the new selections, because the source carries no performance data. Keeping those three columns apart is the job.

In the NSW hub, in empty stadiums, the broadcast mic became the only crowd. There I measured pressure by sound. Here that mic is still silent, because no ball has been bowled. What is audible is the paper of an announcement, and from paper I can read structure only, not result.

So the forward-looking signals, the entries I will write on the next page of the ledger. First: whether the two-track structure holds under first pressure — if Farhan's T20I leadership and Shaheen's ODI leadership succeed together, friction falls; if results diverge, friction rises. Second: the workload of Shaheen, Naseem and Haris — who rests and who does not will show how seriously the selectors weigh the calendar. Third: the pitch transfer from Rawalpindi to Lahore — how much spin bites will decide Sri Lanka's leg. Fourth: what the inexperienced T20I side does in the middle overs — that is the real test, not the powerplay or the death.

The low block is not cowardice; it is a metronome set to survive. Pakistan's two-track design is now a metronome too — the rhythm must hold, or pressure in one format will spill into the other. The ledger has no year, no ODI dates, no performance data. Those three blank rooms will be filled on the field, not in a press release. So the question is not how big the reset is; the question is whether these two rhythms can play together on one calendar.