Saim Ayub Out of Pakistan's ODI Tri-Series Squad, Sahibzada Farhan Called In: 21 Runs in Three Innings and a Risk-Managed Call

The scorer's desk at Lahore's Gaddafi Stadium sits in a corner of the stand from which one slice of the pitch is visible and the rest is hidden by shoulders. On the evening of the England match I saw two things there. The first was the old register in which every innings has its own column for balls faced — filled in, in pencil, all the way down. The second was the right-hand page of my own notebook, where against Saim Ayub's name there were exactly three numbers — 7, 8, 6 — and beside them, one blank column.

Pakistan won that match by one wicket and sealed a place in the tri-series final. The next morning the PCB release arrived: Ayub released from the squad, Sahibzada Farhan named as replacement. It came twenty-four hours after Shaheen Shah Afridi had said, on the record, that Ayub would not be dropped on the eve of the England game.

The story was not on the pitch. It was in the queue for the tea stall.

The format, and a flat Lahore deck

Pakistan are hosting England and Sri Lanka in an invitational tri-series that runs to 31 October. It is not an ICC global event and not a league — it is a home series, in home conditions, in front of home crowds. The one-wicket win over England put Pakistan in the final; one league fixture remains, against Sri Lanka at Gaddafi Stadium on Tuesday.

The 50-over structure matters here. Two new balls mean movement at both ends in the first ten overs. Overs eleven to forty are spin-control. Overs forty-one to fifty are acceleration. A top-order batter's job is not simply to score — it is to build a platform so that Babar Azam, Salman Ali Agha, Shadab Khan and Faheem Ashraf can change gear from the twentieth over. When the top order falls inside the powerplay, the middle order has to build and accelerate at once, and that combination rarely works.

Gaddafi Stadium has historically been a batter-friendly surface: even bounce, the ball coming nicely onto the bat, big scores unremarkable. That detail is decisive. Failure on a seaming away track leaves conditions as an explanation. Three single-digit scores on a flat home deck removes that explanation entirely.

One thing that is not verified is the actual composition of the England side. Whether England fielded a rotated or second-string XI in this calendar window is not in the source material. Until it is checked, a one-wicket win cannot be read as evidence of Pakistani strength. It is a result, not proof of a process.

Three numbers and one blank column

Ayub's tri-series: 7, 8, 6. Twenty-one runs at 7.00.

There is an arithmetic here that gets skipped. An average of 7.00 across three innings means three dismissals — not one unbeaten innings in the series. Likewise, the 60 runs in five innings since November at 12.00 means five dismissals. Had even one innings been unbeaten, the average would read 15.00.

This is not a shortage of runs. It is a failure to survive, not a failure of tempo. And that distinction changes the character of the whole decision. A batter who is out scoring slowly is technically alive and needs only a change of intent. A batter who is repeatedly out early has a problem in the first ten to fifteen overs of an innings — new-ball movement, defensive technique, or shot selection under early pressure.

This is exactly where my notebook is empty. Nowhere in the source material is it stated how many balls Ayub faced, or how he was dismissed — caught, bowled, lbw, run out. Without balls faced, a strike rate cannot be computed. And without a strike rate, the claim that he was batting slowly cannot be made either.

Which means the official framing of a form problem cannot be independently verified at the technical level. A counter-argument remains open: he may have been scoring quickly and being dismissed unluckily. I am not claiming that was the case. I am claiming that the people asserting a technical decline hold the same data I do, and that data does not carry the claim. In the years I have spent covering one-day cricket, the weakest argument in the room is always the one that reads technique off an average.

Eleven months, two separate assignments

Ayub's last ODI half-century came against South Africa in November last year. Roughly eleven months without a 50-plus ODI score.

The interval matters because it is not one tour or one season. It spans at least two separate assignments — the away South Africa and Zimbabwe window, then this home tri-series. When the failure repeats across different conditions, different bowling attacks and different roles, it stops being a slump and becomes a cycle.

The cleanest definition of poor form is not that runs are low. It is that the pattern of low runs does not change. Three scores of 7, 8 and 6 are numerically almost identical. That kind of sameness across separate innings usually means bowlers repeated one plan and it kept working.

Age twenty-four: this is not decline

There is a mistake that recurs in Pakistani cricket discussion — attaching a bad run to an age curve. Ayub is twenty-four. Batters usually peak between twenty-seven and thirty-three. A twenty-four-year-old is pre-peak.

This is a form and technique problem, not a career decline. That distinction matters enormously for management, because form recovers and decline does not. Had this been an age issue, sending him to domestic cricket would be an act of charity. Here it is an investment.

The format boundary

There is a second error buried in the framing, and it sits inside the article's own structure. Every number here is ODI. Transferring those numbers to judgments about his Test or T20I future crosses a line.

The reverse is equally true. If external context suggests his red-ball trajectory has been stronger in this period, that is not evidence that he is 'in form anyway'. It is evidence that this intervention is format-specific. To me that is the most important nuance in the story: Pakistan did not remove a player, they removed a format performance.

The top-order match-up has changed hands

Ayub is left-handed and bowls part-time spin — the squad list calls him a batting all-rounder. His replacement, Farhan, is right-handed.

That is not a name change. Sri Lanka's attack is usually built on off-spin and right-arm/left-arm seam angles. A left-right combination at the top determines which bowler can be attacked in the powerplay and from which angle. Losing a left-hand option and a part-time spin option happened in a single move.

On Tuesday, do not watch how many Farhan scores in the first ten overs. Watch which end Sri Lanka's off-spinner takes and what the Pakistani batter does in that first over. A changed combination shows up in match-ups, not in run columns.

The replacement's profile: six ODIs and a captaincy

Farhan has six ODIs. His last was in March, on the away series in Bangladesh. He is also Pakistan's T20I captain.

Six innings is statistically meaningless for evaluation, so I will not evaluate him. But two structural points are worth making.

First, this is a format-muscle-memory risk. A T20I captain's mental template is built on intent and run rate. The ODI top-order job is the inverse — leaving the ball, wearing down the new ball, building a platform for the thirtieth over. Asking a batter who has not played an ODI in four months to build an innings in his first game back is a fair risk, especially in a fixture where a defeat could break the rhythm before a final.

Second, the replacement is not a like-for-like swap. A left-handed top-order batter with a part-time spin option went out; a right-handed top-order batter with minimal ODI exposure came in. Whether that is an upgrade or a change will be known after Tuesday.

Domestic cricket: a double-edged prescription

The release says Ayub will go to domestic cricket to find form and confidence. It sounds clean. Both edges are sharp.

On one side, domestic bowling standards in Pakistan sit generally below international level. Runs there restore confidence but predict ODI translation weakly. Hitting a domestic spinner into the stands does not prove you will read an international off-spinner next month.

On the other, a failure there deepens the confidence problem in a way no scorecard will show. I have watched players return from 'a domestic round'. The ones who came back came back with runs. The ones who did not came back off the team sheet before the scorecard.

Domestic runs are not evidence. They are relief. Treating relief as evidence is the oldest habit in Pakistani selection debate.

The ankle: a thread still awaiting verification

External context suggests Ayub suffered an ankle injury in the field in South Africa in January 2026. I flag it because it is unverified — but if accurate, it redirects the entire argument.

A young three-format player returning from a significant lower-limb injury is a documented mechanism for a prolonged trough. Footwork slows. Balance loses trust. The body takes time to be believed again, and in that window batters unconsciously shorten their shots. All of it looks like 7, 8, 6.

I am not claiming that is the cause. I am claiming that if a twenty-four-year-old is being released, injury history belongs inside the public explanation rather than outside it. Readers are entitled to know whether this is a technical fix, a confidence intervention, or a body being repaired.

The dead-rubber window

Pakistan had already qualified. One league fixture remained. This is the window selectors call cheap. Removing a struggling top-order batter before a knockout is expensive — media storm, dressing-room questions, a captain's credibility dented. Doing it before a fixture whose result cannot change the table is cheap.

This decision is not cricket-brave. It is administratively shrewd. Distinguishing the two is the reader's job, because teams present them in the same language.

One more element joins the window. The squad list carries several uncapped or near-new names — Arafat Minhas, Maaz Sadaqat, Hasan Nawaz, Razaullah, Saad Baig. When five auditions are already in the room, the cost of removing one struggling incumbent falls further.

'On his own request': a face-saving construct

The release gestures at a player request. I am sceptical of that language, and here is why. Three single-digit scores at home, a captain's public backing twenty-four hours earlier, and then a sudden request. A player publicly protected by his captain does not usually ask to leave the next morning — unless the selection committee had already concluded.

'On his own request' is courtesy here, not causation. It serves two people: the player, who is to be selected again; and the management, which does not have to say it reversed the captain inside a day.

The contrarian read: the win concealed, the loss did not happen

The easiest conclusion after a one-wicket win is that the team wins without Ayub, so there is no place for him. That conclusion mistakes outcome for process.

A one-wicket win is the narrowest non-tie margin. It almost always indicates a top-order collapse rescued by the lower order, or a small target that dragged. In most one-wicket ODIs I have watched in recent years, the winning side's batting structure was broken.

In this match, a one-wicket win does not demonstrate Pakistani strength. It conceals Pakistani fragility. The top-order platform broke, the middle order soothed it, and the table looked healthy. This is where media and selectors make the same mistake: they treat the result as proof of the process.

The second contrarian read is that removing Ayub does not fix the top order. The problem belongs to an approach, not a name. How Pakistan's top order plays the powerplay — how many balls it leaves, which bowler it attacks, how long it waits for the second wicket — is a collective question. Swapping one name does not change it if the new pair is handed the same role.

Selection credibility is a resource

Here is the hard paragraph. The PCB allowed its captain to say publicly, before the England match, that the player would not be dropped — and dropped him the next morning. This is not a technical or cricketing problem. It is a sequencing problem, and sequencing is a board's most valuable non-cricketing asset.

When a captain's statement and a board's decision cross, the damage does not show in twenty-four hours. It shows three months later, when a captain says something about a player and nobody in the press box writes it down seriously. I have watched that cycle in several places. Trust leaves first; the press conference empties afterwards.

The board also did not clarify whether the call belonged to the selection committee, the captain, or management. When responsibility does not settle on a name, accountability will not either.

What to watch on Tuesday

When the first over begins at Gaddafi on Tuesday, do not watch the scoreboard. Watch Farhan's first fifteen balls. If he spends his first ten leaving and defending, he has caught the T20I habit in time. If he is trying to hit his way out in the second over, you will have seen format-muscle memory in public.

Watch too which over Sri Lanka's off-spinner takes. Without Ayub, Pakistan have no left-hand option at the top. If Sri Lanka attacks that window, it will not simply be the consequence of a selection — it will be a structural weakness that three single-digit scores had been hiding.

The next signal

Ayub is twenty-four, and a bad month is not a bad career. The real question is not why he went out. It is on what basis he comes back. If the basis is domestic runs, the return rests on a guess. If the basis is how he played his first twenty balls, the return rests on a measurement.

I kept the notebook open through the silence, because silence is also a scoreline. In this decision, the silence is the column where balls faced should have been written. Until that column is filled, all of us will keep repeating that the boy is out of form — and the next Saim Ayub will leave through the same blank column.

The press box taught me to listen for the voices missing from the seating chart. Here the voice is at the scorer's desk, where a man has counted balls faced for thirty years and nobody has asked him what actually happened in Ayub's three innings. Next time a release drops, ask him first.