Pakistan's Two-Track White Ball: What the Farhan-Shaheen Split Really Says

Last week, when the Pakistan Cricket Board (PCB) put two squads into a single press note — one for a three-match T20I series against Sri Lanka, one for a seven-match ODI tri-series between Pakistan, England and Sri Lanka — the first thing I noticed was not a name. It was a hole. No Babar Azam in the T20I squad. No Mohammad Rizwan. No Shaheen Shah Afridi. All three are in the ODI squad, and Shaheen captains it. The moment those two lists are read together, the question stops being who was dropped. The question becomes why the two squads have such different shapes. Since 2026 I have kept one habit: I write it down before I understand it. The notebook is not memory. It is evidence. And in this announcement the evidence is not in the names. It is in the two-track design. Let me lay out the dates first, because no decision can be weighed without a date. Three T20Is against Sri Lanka on 9, 11 and 13 October, all at Rawalpindi Cricket Stadium. Then a seven-match ODI tri-series, with hosts Pakistan joined by England and Sri Lanka; the first three games at Rawalpindi, the rest of the league and the final at Lahore. The ODI tri-series dates are not fully given in the release — the T20I dates are there, the ODI dates are not. The calendar year is absent from the source too. That is a real gap, and I have logged it, because without the year this series cannot be placed inside the FTP. Where information is missing, inference should not be dressed up as fact. That is where the first structural signal sits. The T20I series is entirely at one venue — Rawalpindi, historically a pitch that rewards pace and bounce. The ODI tri-series is split across two venues, Rawalpindi to Lahore. Two conditions inside one tournament means the same side has to rebalance itself on two different surfaces. Spin-friendly conditions have long suited Sri Lanka; pace and bounce suit Pakistan's core strength. That pitch variable is the thing most people wave away as the schedule. The tri-series format is a test in itself. A round-robin, then a final: teams must first survive, then risk everything in one game. England's presence lifts both the competitiveness and the commercial weight of the tournament; Sri Lanka is a permanently alert opponent on spin-friendly surfaces. In that three-team mix, Pakistan's edge is at home, its challenge is balance. And the whole contest is at home for Pakistan. How real home advantage is, I wrote into my notebook in 2026 while auditing empty-stadium data: when the crowd returns, the edge returns with it. Here that edge sits entirely with the hosts. Two formats, two pitches, two captains. Put simply, Pakistan does not have one white-ball team. It has two. Now to the actual data chain. Start with the T20I captaincy. Sahibzada Farhan has been handed the T20I leadership on the back of captaining Pakistan at the Asian Games. I pause there. The Asian Games context is not a full-strength format — it is a multi-sport event where cricket sides often do not field their best XI. Turning one tournament's leadership into another format's captaincy is a projection built on a weak base. That is not a criticism of Farhan. It is an admission of how thin the evidence is. Second signal: Shaheen Shah Afridi stays ODI captain but is not in the T20I squad. Pakistan has deliberately split its white-ball captaincy by format. As a left-arm new-ball swing bowler, Shaheen's value is front-loaded in the powerplay, and leadership adds mental load to a fast bowler's shoulders. Third: Babar Azam is ODI only. The T20I side is being rebuilt without its long-time batting figurehead. In the modern T20I template the anchor profile keeps drawing questions; Babar's ODI consistency lives in one place, the T20I rebuild in another. That division is the statement. Fourth, and the most telling: Salman Ali Agha was removed as T20I captain and then left out of the format entirely, while staying in the ODI squad. Removing a captain and then dropping him from the whole format is not routine rotation. It is a forced leadership transition. Keeping him in ODI tells you the decision is format-specific, not a verdict across formats. Fifth: Razaullah. His maiden white-ball call-up follows a batting impression in the third Test against England. My caution is plain: projecting white-ball value from one Test cameo is a small-sample projection, and pulling data across formats is exactly the error my framework keeps flagging. Yet he is in both squads, which means the selectors see him as a multi-format asset. Sixth: a maiden T20I call-up for Mohammad Imran Randhawa, and Saad Baig added to the ODI squad. That leaves two wicketkeepers in the ODI squad and one in the T20I squad — the keeping slot is not settled. Usman Khan and Usman Tariq are omitted. A previously fancied keeper-batter missing, two keepers retained: read together, the slot is under trial. Seventh, and the least discussed but most informative: four Asian Games pacers — Ali Raza, Wasim Jr, Akif Javed, Ahmed Daniyal — are out. That is where the picture clears for me. Seen whole, the squad architecture tells one story. The ODI batting is deep — Babar, Fakhar, Salman Agha, Saim Ayub. The T20I batting is thin and experimental — Farhan, Fakhar, Saim, Hasan Nawaz. Pakistan's pace is internationally competitive — Shaheen, Naseem, Haris Rauf — but the spin depth is less proven. The bench is average, with several uncapped names. The age structure is transitional: a senior core for ODI, newcomers for T20I. The easy explanation is that Pakistan is resetting its T20I side — new faces, new leader, senior stars rested. But that explanation skips a variable: workload. Look at the schedule again. Three T20Is on 9, 11 and 13 October, then straight into a seven-match ODI tri-series. For anyone in both squads — Naseem Shah, Shadab Khan, Saim Ayub — there is almost no rest window. Against that backdrop, dropping four Asian Games pacers and limiting Shaheen and Babar to one format cannot be read as mere preference. Correlation is not causation. New faces arrived and senior stars were dropped together, but that does not make the reset the only cause. The likelier cause is more ordinary: protect the core asset, the ODI core, in a squeezed calendar, and use the T20I leg as a pressure valve. Farhan and Randhawa get their chances because they sit outside the two squads' overlap — the risk lands on new shoulders, not on the stars'. The story is not the noise. It is the shape. While everyone debates who was dropped, the real signal is the two-track design and the two-venue pitch variable. For a side playing a seven-match tournament on two surfaces, the biggest question is never the names. It is the balance. So what will I watch in the coming games? Farhan's powerplay usage in T20Is and whether the newcomers can hold the middle overs. In ODIs, how the spin balance shifts from the Rawalpindi leg to the Lahore leg, and whether the split captaincy holds under knockout pressure in the final. The biggest test: can a divided leadership survive a losing streak? Because history says split captaincy works when results go well. When results go badly, the question becomes: so who is the leader?