Rawalpindi's Hush: Two Teams, One White-Ball Reset for Pakistan

An October evening in Rawalpindi. The afternoon slides into dusk, the floodlights come on, and the light draws a silver line along the seam of a white ball, while the empty seats of the gallery fill with a strange hush. That held-breath gap before a stadium becomes a story is my favourite place on earth. For days a line has been turning over in my notebook: Farhan is captain. It is not a scoreline, not a record. It is a decision by the Pakistan Cricket Board (PCB): two white-ball squads built separately—a three-match T20I series against Sri Lanka and a seven-match ODI tri-series with England and Sri Lanka.

I do not chase headlines; I chase the hush before a stadium becomes a story. The hush of this announcement says Pakistan has split its white-ball identity into two pieces—one for ODI, one for T20I. So the real question is not who plays; the real question is whether this split is a conscious plan, or the disguise of a team managing pressure and workload.

According to the PCB announcement, all three T20Is against Sri Lanka are at Rawalpindi Cricket Stadium—on 9, 11 and 13 October. The source does not specify the year, and that gap matters; it shows the moment you try to place the dates on a calendar. Then comes the seven-match ODI tri-series, where Pakistan's companions are England and Sri Lanka; the first three matches are in Rawalpindi, the rest of the league stage and the final in Lahore.

Two formats, two different teams. The T20I squad has no Babar Azam, no Mohammad Rizwan, no Shaheen Shah Afridi. In ODI, Babar is there, Shaheen is there—and Shaheen is the ODI captain. The T20I leadership goes to Sahibzada Farhan, who captained Pakistan at the Asian Games. Salman Ali Agha was removed as T20I captain and dropped from that format entirely, yet he stays in the ODI squad. Razaullah earned his maiden white-ball call-up—after catching the eye with his batting in the third Test against England—and Mohammad Imran Randhawa got a maiden T20I call-up. With wicketkeeper-batter Saad Baig added to the ODI squad, there are now two ODI keepers (Ghori and Baig) and one in T20I (Nafay). Usman Khan and Usman Tariq were left out. Four pacers from the Asian Games squad—Ali Raza, Wasim Jr, Akif Javed, Ahmed Daniyal—are out.

Reading this much, one thing is clear: this is not a single change, it is an architecture. And an architecture must be judged by its foundation, not its paint.

The loudest signal is not in any scoreline but in the comparison of the two squads. Pakistan has effectively split its white-ball captaincy by format: Farhan in T20I, Shaheen in ODI. The dual-captain model is not new to world cricket, and history shows it becomes a source of friction when results diverge. Two dressing rooms, two voices, two continuities—under one board's umbrella. Farhan was given the leadership at the Asian Games, but that tournament's reality was different: not a full-strength bilateral series, but a small window inside a multi-sport event where the logic of team-building is different. From that experience you can infer captaincy quality, but you cannot confirm it—the sample is small and the context is separate.

In Shaheen's case the load is doubled. A left-arm new-ball seamer whose value is front-loaded in the first few overs of the powerplay—swing, bounce, fear. Give that bowler the ODI captaincy and you add the weight of non-bowling decisions: field placement, the timing of bowling changes, the arithmetic of DRS. The history of frontline pace captains is mixed; when physical and mental load rise together, injury risk hides in the margins. And Pakistan's ODI attack leans on the same three frontline quicks—Shaheen, Naseem Shah, Haris Rauf—each with a known injury history.

On the template question, Babar's absence speaks loudest. Dropping Babar Azam from the T20I side is no routine rotation; it is the signal of deliberately removing that team's batting figurehead. In ODI, Babar's anchor profile—high average, moderate strike rate—is conventionally appropriate. In the modern fast-scoring T20 template, that profile has been questioned repeatedly. So keeping him in ODI and dropping him from T20I both look defensible. Yet years of watching matches from the boundary edge tell me that dropping a batter like Babar is never purely a template decision—load management, format-specific planning and a long calendar are working behind it too.

Razaullah's call-up demands separate caution. According to the source, his selection rests on a single batting innings in the third Test against England. This is where memory and expectation set their trap. In August 2026, a Trent Alexander-Arnold free-kick at Hoffenheim taught me that one touch can carry a city's memory—but however beautiful a free-kick is, it cannot forecast a whole season. Reading white-ball value from one Test cameo is the same: attractive, but a thin sample. And here lies the second trap—cross-format projection. Test batting and white-ball demands are different; the ball does not age, the field sets differ, the boundary pressure differs. Naming Razaullah in both squads means the selectors see a multi-format asset—but that view rests on potential, not proof.

With Salman Ali Agha the signal is even clearer. Removing a captain first and then omitting him from that format entirely is not routine rotation; it is a forced leadership handover. His retention in ODI confirms the decision is format-specific, not a verdict on his overall value. Such selections are usually the fruit of an earlier decision—meaning the captaincy change was settled long before this announcement.

The wicketkeeping slot is also unsettled. Two keepers in ODI, a different one in T20I—this arrangement offers flexibility, but it also signals uncertainty. The omission of a once-favoured keeper-batter like Usman Khan deepens that uncertainty.

The venue arithmetic is not to be ignored. Rawalpindi has historically favoured pacers—bounce and pace. Lahore has traditionally helped spinners more. So the first three ODI tri-series matches in Rawalpindi and the rest in Lahore—a two-venue structure—injects a pitch-condition variable into a single tournament. Pakistan's pace-led core will be comfortable in Rawalpindi; Sri Lanka's spin-heavy tradition may gain more in Lahore. And if the final is a Lahore evening, dew will put the second-innings bowling under direct question—raising the weight of the toss and casting the shadow of DLS. That is why I say the real test of the series is not the league table but that one Lahore night.

The absence of four Asian Games pacers—Ali Raza, Wasim Jr, Akif Javed, Ahmed Daniyal—is probably more than form. The T20Is run on 9, 11 and 13 October, immediately followed by the ODI tri-series—meaning those in both squads (like Naseem, Shadab, Saim Ayub) have almost no rest window. In that situation, resting a group of pacers signals workload protection, and if that is true, part of this announcement's selection bravery is actually the calendar's compulsion.

Home advantage is real and heavy here. The whole contest is in Pakistan—Rawalpindi and Lahore. Pakistan's home record is markedly stronger than its away record, and home conditions soften the learning curve for newcomers. But that softness is a double-edged blade: home pitches build newcomers' confidence, and cover their weaknesses too. England's presence lifts both the competitiveness and the commercial ceiling of the tri-series—this series carries more weight than a routine bilateral, because ahead lies a side deeper in batting and richer in resources.

On the public narrative, the risk is clear. Pakistan's cricket-mad following reacts fast when senior names are dropped; so the talk around Babar's and Shaheen's T20I absence will be louder than the newly capped youngsters—that is almost certain. And the excitement building around Razaullah rests on one innings. Writing a season's future from one innings is the classic small-sample trap.

Yet the contrarian view matters here. The collective memory is reading this announcement as a rebuild—bold, modern, fresh. The hidden truth is that this rebuild's laboratory has been set up at home, where conditions stand beside newcomers and cover their weaknesses. On Rawalpindi's batting-friendly deck a debutant can look good; in Lahore's dew the situation flips. Much of what we are calling the selectors' foresight is the calendar's pressure, the fear of injury, and the arithmetic of two identities across two formats. If load management is passed off as a rebuild, the real question gets buried—is the new side truly ready, or have the old ones simply been rested?

On Rawalpindi's first evening nobody will bowl a white ball, nobody will bat—only floodlights and empty chairs will remain, and the name of a new captain. When the dew falls on the Lahore final, it will become clear whether this two-piece white-ball future is standing or swaying. The story of a ground only begins when the hush ends—and this Pakistan side will be judged by that closing hush, not the opening one.